main/openvswitch: fix network script / improve docs / integrate LXC

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.

1 files changed, 70 insertions, 0 deletions

diff --git a/main/openvswitch/readme.debian.patch b/main/openvswitch/readme.debian.patch
new file mode 100644
index 0000000000..33f002e39a
--- /dev/null
+++ b/main/openvswitch/readme.debian.patch
@@ -0,0 +1,70 @@
+--- openvswitch-2.3.2/debian/openvswitch-switch.README.Debian	2015-06-18 19:32:47.000000000 +0000
++++ openvswitch-2.3.2/debian/openvswitch-switch.README.Debian.new	2015-07-10 17:03:12.791341980 +0000
+@@ -1,44 +1,5 @@
+-README.Debian for openvswitch-switch
+----------------------------------
+-
+-To use the Linux kernel-based switch implementation, you will need an
+-Open vSwitch kernel module.  There are multiple ways to obtain one.
+-In order of increasing manual effort, these are:
+-
+-       * Use a Linux kernel 3.3 or later, which has an integrated Open
+-	 vSwitch kernel module.
+-
+-	 The upstream Linux kernel module lacks a few features that
+-	 are in the third-party module.  For details, please see the
+-	 FAQ, "What features are not available in the Open vSwitch
+-	 kernel datapath that ships as part of the upstream Linux
+-	 kernel?".
+-
+-       * Install the "openvswitch-datapath-dkms" Debian package that
+-	 you built earlier.  This should automatically build and
+-	 install the Open vSwitch kernel module for your running
+-	 kernel.
+-
+-	 This option requires that you have a compiler and toolchain
+-	 installed on the machine where you run Open vSwitch, which
+-	 may be unacceptable in some production server environments.
+-
+-       * Install the "openvswitch-datapath-source" Debian package, use
+-	 "module-assistant" to build a Debian package of the Open
+-	 vSwitch kernel module for your kernel, and then install that
+-	 Debian package.
+-
+-	 You can install the kernel module Debian packages that you
+-	 build this way on the same machine where you built it or on
+-	 another machine or machines, which means that you don't
+-	 necessarily have to have any build infrastructure on the
+-	 machines where you use the kernel module.
+-
+-	 /usr/share/doc/openvswitch-datapath-source/README.Debian has
+-	 details on the build process.
+-
+-       * Build and install the kernel module by hand.
+-
++README.Alpine for Openvswitch
++-----------------------------
+ 
+ Debian network scripts integration
+ ----------------------------------
+@@ -172,11 +133,6 @@ iface gre1 inet manual
+     ovs_tunnel_type gre
+     ovs_tunnel_options options:remote_ip=182.168.1.2 options:key=1
+ 
+-ex 7: Create and destroy bridges.
+-
+-ifup --allow=ovs $list_of_bridges
+-ifdown --allow=ovs $list_of_bridges
+-
+ Notes on dependencies:
+ ---------------------
+ 
+@@ -203,3 +159,8 @@ 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:
++-----------------------------------
++
++See 'ovsup' & 'ovsdown' https://github.com/itoffshore/lxc-scripts