diff options
Diffstat (limited to 'main/openvswitch/readme.debian.patch')
| -rw-r--r-- | main/openvswitch/readme.debian.patch | 85 |
1 files changed, 65 insertions, 20 deletions
diff --git a/main/openvswitch/readme.debian.patch b/main/openvswitch/readme.debian.patch index 82c186c671..e641e70914 100644 --- a/main/openvswitch/readme.debian.patch +++ b/main/openvswitch/readme.debian.patch @@ -1,6 +1,6 @@ ---- openvswitch-2.4.0/debian/openvswitch-switch.README.Debian 2015-08-22 18:26:22.381124884 +0000 -+++ openvswitch-2.4.0/debian/openvswitch-switch.README.Debian.new 2015-08-22 18:44:37.717142304 +0000 -@@ -1,44 +1,5 @@ +--- a/debian/openvswitch-switch.README.Debian +--- b/debian/openvswitch-switch.README.Debian +@@ -1,48 +1,8 @@ -README.Debian for openvswitch-switch ---------------------------------- - @@ -42,12 +42,19 @@ - - * Build and install the kernel module by hand. - +- +-Debian network scripts integration +----------------------------------- +-This package lets a user to optionally configure Open vSwitch bridges +README.Alpine for Openvswitch +----------------------------- ++network scripts integration ++----------------------------- ++This package enables a user to optionally configure Open vSwitch bridges + and ports from /etc/network/interfaces. Please refer to the interfaces(5) + manpage for more details regarding /etc/network/interfaces. - Debian network scripts integration - ---------------------------------- -@@ -202,8 +163,8 @@ iface gre1 inet manual +@@ -202,43 +162,29 @@ ex 8: Create and destroy bridges. @@ -56,19 +63,57 @@ +ifup $list_of_bridges +ifdown $list_of_bridges - Notes on dependencies: - --------------------- -@@ -231,3 +192,12 @@ in the 'auto' section, openvswitch-switc - ifupdown kicks in. In a case like this, the admin needs to make sure that /usr - has already been mounted and that a remote $syslog (if used) is ready to - receive openvswitch logs. -+ -+Notes on LXC / ifupdown integration: -+------------------------------------ +-Notes on dependencies: +---------------------- ++Notes on LXC integration: ++------------------------- + +-openvswitch-switch depends on $network, $named $remote_fs and $syslog to start. +-This creates some startup dependency issues. ++To prevent containers failing to start after hard reboots create: ++----------------------------------------------------------------- + +-* Since openvswitch utilities are placed in /usr and /usr can be mounted +-through NFS, openvswitch has to start after it. But if a user uses openvswitch +-for all his networking needs and hence to mount NFS, there will be a deadlock. +-So, if /usr is mounted through NFS and openvswitch is used for all networking, +-the administrator should figure out a way to mount NFS before starting OVS. +-One way to do this is in initramfs. ++/etc/lxc/ovsup: + +-* Since openvswitch starts after $network, $remote_fs and $syslog, any startup +-script that depends on openvswitch but starts before it, needs to be changed +-to depend on openvswitch-switch too. ++#!/bin/sh ++ovs-vsctl --if-exists del-port $5 ++----------------------------------------------------------------- + +-* Ideally, an admin should not add openvswitch bridges in the 'auto' +-section of the 'interfaces' file (i.e., if "br0" is a OVS bridge, you should +-not have a line "auto br0"). This is because, when ifupdown starts +-working on bridges listed in 'auto', openvswitch has not yet started. ++/etc/lxc/ovsdown: + +-But, if the admin wants to go down this route and adds openvswitch bridges +-in the 'auto' section, openvswitch-switch will forcefully be started when +-ifupdown kicks in. In a case like this, the admin needs to make sure that /usr +-has already been mounted and that a remote $syslog (if used) is ready to +-receive openvswitch logs. ++#!/bin/sh + +-* With systemd, adding openvswitch bridges in the 'auto' section of the +-'interfaces' file can cause race conditions (i.e., if "br0" is a OVS bridge, +-you should not have a line "auto br0"). Debian systems have added a +-systemd ifup@.service file. This file will call ifdown and ifup on interfaces +-in "auto" section automatically when the interfaces disappear and appear +-respectively. This will cause race conditions if you delete and add the same +-bridges using tools like "ovs-vsctl" or "ovs-dpctl". This is also a problem +-when you upgrade your openvswitch kernel module using commands like +-'force-reload-kmod'. ++ovs-vsctl --if-exists del-port veth.$LXC_NAME ++----------------------------------------------------------------- + -+LXC has partial support for ovs (ports are added but not fully removed) -+https://github.com/lxc/lxc/issues/590 ++& add to the container config file: + -+See 'ovsup' & 'ovsdown' https://github.com/itoffshore/lxc-scripts -+these scripts allow networking to be restarted & containers do not lose -+connectivity. ++lxc.hook.pre-start = /etc/lxc/ovsup ++lxc.hook.post-stop = /etc/lxc/ovsdown |