summaryrefslogtreecommitdiff
path: root/debian/openvswitch-switch.template
Commit message (Collapse)AuthorAgeFilesLines
* openvswitch: Remove Linux bridge compatibility.Pravin B Shelar2012-12-271-4/+0
| | | | | | | | | Currently brcompat does not work on master due to recent datapath changes. We have decided to remove it as it is not used very widely. Signed-off-by: Pravin B Shelar <pshelar@nicira.com> Acked-by: Jesse Gross <jesse@nicira.com>
* debian: Enable passing extra options to ovs-ctl from init scripts.Ben Pfaff2012-06-151-0/+4
| | | | | | | | This is useful for passing wrapper script options and possibly for other purposes. Bug #11889. Signed-off-by: Ben Pfaff <blp@nicira.com>
* debian: Add support for bridge compatibility.Ben Pfaff2011-07-261-0/+4
| | | | | | | This adds support for bridge compatibility to the generic Open vSwitch init scripts and to the Debian packaging. See https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/808224.
* debian: Remove obsolete comment.Ben Pfaff2011-07-181-5/+0
| | | | | The comment is obsolete because the switch now starts by default, without prior configuration.
* Refactor initscripts into distro-independent and distro-specific pieces.Ben Pfaff2011-06-171-18/+2
| | | | This should make it easier to add OVS support to new distributions.
* debian: Bring Debian packaging in-line with new file locationsJustin Pettit2010-03-311-1/+1
| | | | | This commit brings the Debian packaging in-line with the similar changes that were made to XenServer in commit bc39196.
* Enable daemon monitoring and automatic restart by default.Ben Pfaff2010-01-151-0/+4
| | | | | | Tested on a XenServer by running "kill -SEGV" on the daemon processes and watching them restart automatically and by running plain "kill" and watching them terminate normally.
* debian: Change openvswitch-switch deb to use ovsdb-server and ovs-vswitchd.Ben Pfaff2009-12-151-150/+6
| | | | | | This appears to work in that it creates the database on installation, starts and stops the programs and loads and unloads the kernel modules at the right times, but it has not been tested beyond that.
* Merge citrix into master.Ben Pfaff2009-08-191-11/+11
|\ | | | | | | | | | | | | | | | | | | | | | | This was a somewhat difficult merge since there was a fair amount of superficially divergent development on the two branches, especially in the datapath. This has been build-tested against XenServer 5.5.0 and XenServer 5.7.0 build 15122. It has been booted and connected to XenCenter on 5.5.0. The merge revealed a couple of outstanding bugs, which will be fixed on citrix and then merged back into master.
| * Merge commit 'origin/citrix'Justin Pettit2009-07-281-2/+2
| |\ | | | | | | | | | | | | | | | Conflicts: configure.ac
| * | Rename "secchan" to "ofproto" (library) and "ovs-openflowd" (program).Ben Pfaff2009-07-081-11/+11
| | | | | | | | | | | | These names are more meaningful, so we prefer them.
* | | Reduce default probe interval to 5 seconds (and fail-open timeout to 15).Ben Pfaff2009-07-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before now, the default probe interval (the idle time after which an echo request is sent on an OpenFlow connection) was set to 15 seconds. The fail-open timeout is 3 times the probe interval, so this meant that it took 45 seconds for a switch to fail open. Users at Nicira have commented that this is too long. They don't like the idea that the network will be down for most of a minute before it begins to recover. So this commit changes the default probe interval to 5 seconds, hence the fail-open timeout to 15 seconds.
* | | Reduce default maximum connection timeout from 15 seconds to 8 seconds.Ben Pfaff2009-07-291-2/+2
| |/ |/| | | | | | | | | | | | | Users at Nicira have commented that a maximum reconnection time of 15 seconds, which was the default, is too long. This commit cuts it to 8 seconds, on the theory that an administrator is willing to wait that long before deciding that a change that should restore connectivity did not work.
* | Do not try to resolve DNS for OpenFlow controllers or netflow collectors.Ben Pfaff2009-07-211-2/+2
|/ | | | | | | | | | | | | | | | | | Until now, setting a netflow collector to a DNS name would cause secchan to attempt to resolve that DNS name each time that the set of netflow collectors is re-set. For the vswitch, this is every time that the vswitch reconfigures itself. Unfortunately, DNS lookup within secchan cannot work as currently implemented, because it needs both an asynchronous DNS resolver library and in-band control updates. Currently we have neither. Attempting to look up DNS anyway just hangs. This commit disables DNS lookup entirely, and updates the documentation to change user expectations. DNS still won't work, but at least it won't hang. Bug #1609.
* Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.v0.90.0Ben Pfaff2009-07-081-0/+165