| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** NB: please move openvswitch-2.3.2-r1.apk in edge ---> stable ***
Changes in 2.4.0:
https://github.com/openvswitch/ovs/blob/master/NEWS
Added bash-completions
ovs 2.3.2 & 2.4.0 both have partial support for LXC:
see: https://github.com/itoffshore/lxc-scripts
ovsup / ovsdown stop LXC containers losing connectivity when networking
is restarted.
|
| |
|
|
|
|
|
|
| |
starting ovs-vswitchd from the ifupdown script did not start the depends
during boot.
ovs will now start correctly with networking if it is stopped or if none
of the ovs services have been configured.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
small fix for /etc/network/if-pre-up.d/openvswitch. When networking is
started now ovs-vswitchd will be started if stopped.
added /usr/share/doc/openvswitch/README.alpine which provides
instructions on how to use /etc/network/pre-up.d/openvswitch.
You can now configure bridges / ports / bonds in /etc/network/interfaces.
You can also integrate LXC into OVS / ifupdown easily via 'ovsup' & 'ovsdown':
https://github.com/itoffshore/lxc-scripts
If you install 'apk-post-messages' & 'openvswitch-doc' detailed instructions
are printed.
|
| |
|
|
|
|
|
|
|
| |
Notes for anyone using ovs with lxc & updating from Alpine 3.1 --> 3.2
In LXC 1.1.2 the mount entries in container/config have changed a little
& need to be modified (create a new container to find the new config format).
Changing these & rebooting with the new ovs worked without issue. Not doing
this broke the networking.
|
| | |
|
| | |
|
| |
|
