@@ -111,9 +111,6 @@ jobs:
m32: m32
opts: --disable-ssl
- - compiler: gcc
- deb_package: deb
-
steps:
- name: checkout
uses: actions/checkout@v2
deleted file mode 100644
@@ -1,27 +0,0 @@
-*.debhelper
-*.debhelper.log
-*.substvars
-/autoreconf.after
-/autoreconf.before
-/control
-/copyright
-/files
-/libopenvswitch
-/libopenvswitch-dev
-/nicira-switch
-/openvswitch
-/openvswitch-common
-/openvswitch-common.copyright
-/openvswitch-datapath-source
-/openvswitch-datapath-dkms
-/openvswitch-dbg
-/openvswitch-ipsec
-/openvswitch-pki
-/openvswitch-switch
-/openvswitch-switch.copyright
-/openvswitch-test
-/openvswitch-testcontroller
-/openvswitch-vtep
-/python-openvswitch
-/python3-openvswitch
-/tmp
@@ -1,82 +1,2 @@
EXTRA_DIST += \
- debian/changelog \
- debian/compat \
- debian/control \
- debian/control.modules.in \
- debian/copyright \
- debian/copyright.in \
- debian/dkms.conf.in \
- debian/dirs \
- debian/libopenvswitch.install \
- debian/libopenvswitch-dev.install \
- debian/openvswitch-common.dirs \
- debian/openvswitch-common.docs \
- debian/openvswitch-common.install \
- debian/openvswitch-common.manpages \
- debian/openvswitch-datapath-module-_KVERS_.postinst.modules.in \
- debian/openvswitch-datapath-dkms.postinst \
- debian/openvswitch-datapath-dkms.prerm \
- debian/openvswitch-datapath-source.README.Debian \
- debian/openvswitch-datapath-source.copyright \
- debian/openvswitch-datapath-source.dirs \
- debian/openvswitch-datapath-source.install \
- debian/openvswitch-ipsec.dirs \
- debian/openvswitch-ipsec.init \
- debian/openvswitch-ipsec.install \
- debian/openvswitch-pki.dirs \
- debian/openvswitch-pki.postinst \
- debian/openvswitch-pki.postrm \
- debian/openvswitch-switch.README.Debian \
- debian/openvswitch-switch.dirs \
- debian/openvswitch-switch.init \
- debian/openvswitch-switch.install \
- debian/openvswitch-switch.logrotate \
- debian/openvswitch-switch.manpages \
- debian/openvswitch-switch.postinst \
- debian/openvswitch-switch.postrm \
- debian/openvswitch-switch.template \
- debian/openvswitch-switch.links \
- debian/openvswitch-test.dirs \
- debian/openvswitch-test.install \
- debian/openvswitch-test.manpages \
- debian/openvswitch-testcontroller.README.Debian \
- debian/openvswitch-testcontroller.default \
- debian/openvswitch-testcontroller.dirs \
- debian/openvswitch-testcontroller.init \
- debian/openvswitch-testcontroller.install \
- debian/openvswitch-testcontroller.manpages \
- debian/openvswitch-testcontroller.postinst \
- debian/openvswitch-testcontroller.postrm \
- debian/openvswitch-vtep.default \
- debian/openvswitch-vtep.dirs \
- debian/openvswitch-vtep.init \
- debian/openvswitch-vtep.install \
- debian/openvswitch-vtep.manpages \
- debian/python3-openvswitch.dirs \
- debian/python3-openvswitch.install \
- debian/rules \
- debian/rules.modules \
- debian/ifupdown.sh \
- debian/source/format
-
-check-debian-changelog-version:
- @DEB_VERSION=`echo '$(VERSION)' | sed 's/pre/~pre/'`; \
- if $(FGREP) '($(DEB_VERSION)' $(srcdir)/debian/changelog >/dev/null; \
- then \
- :; \
- else \
- echo "Update debian/changelog to mention version $(VERSION)"; \
- exit 1; \
- fi
-ALL_LOCAL += check-debian-changelog-version
-DIST_HOOKS += check-debian-changelog-version
-
-$(srcdir)/debian/copyright: AUTHORS.rst debian/copyright.in
- $(AM_V_GEN) \
- { sed -n -e '/%AUTHORS%/q' -e p < $(srcdir)/debian/copyright.in; \
- sed '34,/^$$/d' $(srcdir)/AUTHORS.rst | \
- sed -n -e '/^$$/q' -e 's/^/ /p'; \
- sed -e '34,/%AUTHORS%/d' $(srcdir)/debian/copyright.in; \
- } > $@
-
-CLEANFILES += debian/copyright
+ debian/changelog
deleted file mode 100644
@@ -1 +0,0 @@
-9
deleted file mode 100644
@@ -1,266 +0,0 @@
-Source: openvswitch
-Section: net
-Priority: extra
-Maintainer: Open vSwitch developers <dev@openvswitch.org>
-Uploaders: Simon Horman <horms@debian.org>
-Build-Depends: graphviz,
- autoconf (>= 2.64),
- automake (>= 1.10) | automake1.10,
- bzip2,
- debhelper (>= 8),
- dh-autoreconf,
- libssl-dev,
- libtool,
- openssl,
- procps,
- python3-all,
- python3-sphinx,
- python3-twisted,
- python3-zope.interface,
- libunbound-dev,
- libunwind-dev
-Standards-Version: 3.9.3
-Homepage: http://openvswitch.org/
-
-Package: openvswitch-datapath-source
-Architecture: all
-Depends: bzip2, debhelper (>= 5.0.37), module-assistant, ${misc:Depends}
-Suggests: openvswitch-switch
-Description: Open vSwitch datapath module source - module-assistant version
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package provides the Open vSwitch datapath module source code
- that is needed by openvswitch-switch. The kernel module can be built
- from it using module-assistant or make-kpkg. README.Debian in this
- package provides further instructions.
-
-Package: openvswitch-datapath-dkms
-Architecture: all
-Depends: dkms (>= 1.95), libc6-dev, libelf-dev, make, ${misc:Depends}, ${python3:Depends}
-Description: Open vSwitch datapath module source - DKMS version
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package provides the Open vSwitch datapath module source code
- that is needed by openvswitch-switch. DKMS can built the kernel
- module from it.
-
-Package: openvswitch-common
-Architecture: linux-any
-Multi-Arch: foreign
-Depends: python3,
- libopenvswitch (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Suggests: ethtool
-Replaces: openvswitch-switch (<< 2.5.90)
-Breaks: openvswitch-switch (<< 2.5.90)
-Description: Open vSwitch common components
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- openvswitch-common provides components required by both openvswitch-switch
- and openvswitch-testcontroller.
-
-Package: libopenvswitch
-Architecture: linux-any
-Multi-Arch: same
-Depends: openssl,
- ${misc:Depends},
- ${shlibs:Depends}
-Description: Open vSwitch common components
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- libopenvswitch provides runtime libraries for use by openvswitch binaries
-
-Package: openvswitch-switch
-Architecture: linux-any
-Suggests: openvswitch-datapath-module
-Depends: kmod | module-init-tools,
- netbase,
- openvswitch-common (= ${binary:Version}),
- procps,
- uuid-runtime,
- ${misc:Depends},
- ${python3:Depends},
- ${shlibs:Depends}
-Description: Open vSwitch switch implementations
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- openvswitch-switch provides the userspace components and utilities for
- the Open vSwitch kernel-based switch.
-
-Package: openvswitch-pki
-Architecture: all
-Depends: openvswitch-common (<< ${source:Version}.1~),
- openvswitch-common (>= ${source:Version}),
- ${misc:Depends}
-Description: Open vSwitch public key infrastructure dependency package
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- openvswitch-pki provides PKI (public key infrastructure) support for
- Open vSwitch switches and controllers, reducing the risk of
- man-in-the-middle attacks on the Open vSwitch network infrastructure.
-
-Package: openvswitch-testcontroller
-Architecture: linux-any
-Depends: openvswitch-common (= ${binary:Version}),
- openvswitch-pki (= ${source:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Description: Simple controller for testing OpenFlow setups
- This controller enables OpenFlow switches that connect to it to act
- as MAC-learning Ethernet switches. It can be used for initial
- testing of OpenFlow networks. It is not a necessary or desirable
- part of a production OpenFlow deployment.
-
-Package: openvswitch-dbg
-Section: debug
-Architecture: linux-any
-Depends: openvswitch-common (= ${binary:Version}),
- openvswitch-switch (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Conflicts: openvswitch-testcontroller (<< ${binary:Version}),
- openvswitch-testcontroller (>> ${binary:Version})
-Description: Debug symbols for Open vSwitch packages
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package contains the debug symbols for all the other openvswitch-*
- packages. Install it to debug one of them or to examine a core dump
- produced by one of them.
-
-Package: python3-openvswitch
-Architecture: all
-Section: python
-Depends: ${misc:Depends}, ${python3:Depends}
-Description: Python bindings for Open vSwitch
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package contains the full Python bindings for Open vSwitch database.
-
-Package: openvswitch-test
-Architecture: all
-Depends: python3,
- python3-twisted,
- ${misc:Depends},
- ${python3:Depends}
-Description: Open vSwitch test package
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package contains utilities that are useful to diagnose
- performance and connectivity issues in Open vSwitch setup.
-
-Package: openvswitch-vtep
-Architecture: linux-any
-Depends: openvswitch-common (>= ${binary:Version}),
- openvswitch-switch (>= ${binary:Version}),
- python3,
- python3-openvswitch (>= ${source:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Description: Open vSwitch VTEP utilities
- Open vSwitch is a production quality, multilayer, software-based, Ethernet
- virtual switch. It is designed to enable massive network automation through
- programmatic extension, while still supporting standard management interfaces
- and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In
- addition, it is designed to support distribution across multiple physical
- servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus
- 1000V.
- .
- This package provides utilities that are useful to interact with a
- VTEP-configured database and a VTEP emulator.
-
-Package: libopenvswitch-dev
-Architecture: linux-any
-Multi-Arch: same
-Depends:
- libopenvswitch (>= ${binary:Version}),
- libssl-dev,
- libunbound-dev,
- ${misc:Depends}
-Conflicts: openvswitch-dev
-Replaces: openvswitch-dev
-Description: Open vSwitch development package
- Open vSwitch is a production quality, multilayer, software-based, Ethernet
- virtual switch. It is designed to enable massive network automation through
- programmatic extension, while still supporting standard management interfaces
- and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In
- addition, it is designed to support distribution across multiple physical
- servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus
- 1000V.
- .
- This package provides openvswitch headers and libopenvswitch for developers.
-
-Package: openvswitch-ipsec
-Architecture: linux-any
-Depends: iproute2,
- openvswitch-common (= ${binary:Version}),
- openvswitch-switch (= ${binary:Version}),
- python3,
- python3-openvswitch (= ${source:Version}),
- strongswan,
- ${misc:Depends},
- ${shlibs:Depends}
-Description: Open vSwitch IPsec tunneling support
- Open vSwitch is a production quality, multilayer, software-based,
- Ethernet virtual switch. It is designed to enable massive network
- automation through programmatic extension, while still supporting
- standard management interfaces and protocols (e.g. NetFlow, IPFIX,
- sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In addition, it is designed
- to support distribution across multiple physical servers similar to
- VMware's vNetwork distributed vswitch or Cisco's Nexus 1000V.
- .
- This package provides IPsec tunneling support for OVS tunnels.
deleted file mode 100644
@@ -1,20 +0,0 @@
-Source: openvswitch
-Section: net
-Priority: extra
-Maintainer: Open vSwitch developers <dev@openvswitch.org>
-Build-Depends: debhelper (>= 5.0.37)
-Standards-Version: 3.7.3
-
-Package: openvswitch-datapath-module-_KVERS_
-Architecture: any
-Recommends: kernel-image-_KVERS_, openvswitch-switch
-Provides: openvswitch-datapath-module
-Description: Open vSwitch Linux datapath kernel module
- This package contains the Open vSwitch loadable datapath kernel modules for
- the kernel-image-_KVERS_ package.
- .
- If you compiled a custom kernel, you will most likely need to compile
- a custom version of this module as well. The
- openvswitch-datapath-source package has been provided for this
- purpose. Refer to README.Debian provided in that package for further
- instructions.
deleted file mode 100644
@@ -1,711 +0,0 @@
-The original sources for this package can be found at:
-
- http://openvswitch.org/
-
-Upstream Authors (from AUTHORS):
-
-%AUTHORS%
-
-Upstream Copyright Holders:
-
- 6WIND S.A.
- Alexandru Copot <alex.mihai.c@gmail.com>, with support from IXIA.
- Alexey I. Froloff.
- Amir Vadai <amir@vadai.me>
- Arm Limited
- Avaya, Inc.
- Benjamin Kosnik <bkoz@redhat.com>
- Cisco Systems, Inc
- Citrix Systems, Inc.
- Cloudbase Solutions Srl
- Cumulus Netowkrs
- Daniel Baluta <dbaluta@ixiacom.com>
- Daniel Hartmeier
- Dan Nicholson <dbn.lists@gmail.com>
- Dustin J. Mitchell <dustin@zmanda.com>
- Ed Maste
- Eelco Chaudron
- Ericsson AB
- Free Software Foundation, Inc.,
- Gaetano Catalli
- Gary S. Brown.
- Geoffrey Wossum (gwossum@acm.org)
- Gleb Smirnoff <glebius@FreeBSD.org>
- Grant Jenks
- Henning Brauer
- Hewlett Packard Enterprise Development LP
- Horms Solutions Ltd.
- IBM
- Ilya Maximets <i.maximets@samsung.com>
- Javier Fernandez-Sanguino <jfs@debian.org>
- Jean Tourrilhes - HP-Labs.
- Jiri Pirko <jiri@resnulli.us>
- Kmindg <kmindg@gmail.com>
- Krzesimir Nowak <qdlacz@gmail.com>
- M3S, Srl - Italy
- Mark Pilgrim
- Mellanox Technologies, Ltd.
- Michael Chapman
- Moritz Klammler
- Netronome
- Nicira, Inc.
- Open Networking Foundation
- Paolo Abeni <pabeni@redhat.com>
- Paul Norman <penorman@mac.com>
- Red Hat, Inc.
- Roy Stogner <roystgnr@ices.utexas.edu>
- Samsung Electronics Co.,Ltd.
- Scott James Remnant <scott@netsplit.com>
- Scott Pakin <pakin@uiuc.edu>
- Siemens AG
- Sten Spans <sten@blinkenlights.nl>
- Stephen Finucane <stephen@that.guru>
- The Board of Trustees of The Leland Stanford Junior University
- The NetBSD Foundation, Inc.
- The Regents of the University of California.
- The University of Waikato
- USAGI/WIDE Project
- Vincent Bernat <bernat@luffy.cx>
- VMware, Inc.
- WIDE Project.
- WindRiver, Inc.
- YAMAMOTO Takashi
- Zack Weinberg <zackw@panix.com>
- Zmanda Inc. <http://www.zmanda.com/>
-
-License:
-
-* The following components are licensed under the
- GNU Lesser General Public License version 2.1 only
- with the exception clause below as a pre-amble.
-
- xenserver/etc_xensource_scripts_vif
- xenserver/opt_xensource_libexec_InterfaceReconfigure.py
- xenserver/opt_xensource_libexec_InterfaceReconfigureBridge.py
- xenserver/opt_xensource_libexec_InterfaceReconfigureVswitch.py
- xenserver/opt_xensource_libexec_interface-reconfigure
- xenserver/usr_lib_xsconsole_plugins-base_XSFeatureVSwitch.py
-
- * These components are only distributed in the source package.
- They do not appear in any binary packages.
-
- On Debian systems, the complete text of the
- GNU Lesser General Public License version 2.1 can be found in
- `/usr/share/common-licenses/LGPL-2.1'
-
- The exception clause pre-amble reads:
-
- As a special exception to the GNU Lesser General Public License, you
- may link, statically or dynamically, a "work that uses the Library"
- with a publicly distributed version of the Library to produce an
- executable file containing portions of the Library, and distribute
- that executable file under terms of your choice, without any of the
- additional requirements listed in clause 6 of the GNU Lesser General
- Public License. By "a publicly distributed version of the Library",
- we mean either the unmodified Library as distributed, or a
- modified version of the Library that is distributed under the
- conditions defined in clause 3 of the GNU Library General Public
- License. This exception does not however invalidate any other reasons
- why the executable file might be covered by the GNU Lesser General
- Public License.
-
-* The following components are licensed under the
- GNU Lesser General Public License version 2.1.
-
- utilities/bugtool/ovs-bugtool
- utilities/bugtool/ovs-bugtool-*
- utilities/bugtool/plugins/kernel-info/openvswitch.xml
- utilities/bugtool/plugins/network-status/openvswitch.xml
- utilities/bugtool/plugins/system-configuration.xml
- utilities/bugtool/plugins/system-configuration/openvswitch.xml
-
- On Debian systems, the complete text of the
- GNU Lesser General Public License version 2.1 can be found in
- `/usr/share/common-licenses/LGPL-2.1'
-
-* The following component is licensed under the GNU General Public License
- version 2.
-
- datapath/
-
- On Debian systems, the complete text of the GNU General Public License
- version 2 can be found in `/usr/share/common-licenses/GPL-2'
-
-* The following file is licensed under the GNU General Public License
- version 2.
-
- build-aux/cccl
-
-* The following files are licensed under the 2-clause BSD license.
-
- lib/getopt_long.c
- include/windows/getopt.h
- datapath-windows/ovsext/Conntrack-tcp.c
- lib/conntrack-tcp.c
-
-* The following files are licensed under the 3-clause BSD-license
-
- include/windows/netinet/icmp6.h
- include/windows/netinet/ip6.h
- lib/strsep.c
-
-* The following components are dual-licensed under the
- GNU General Public License version 2 and the Apache License Version 2.0.
-
- datapath/linux/compat/include/linux/openvswitch.h
-
- On Debian systems, the complete text of the GNU General Public License
- version 2 can be found in `/usr/share/common-licenses/GPL-2'.
- On Debian systems, the complete text of the Apache License version 2.0
- can be found in '/usr/share/common-licenses/Apache-2.0'.
-
-* The following components are licensed under the terms of either the
- Sun Industry Standard Source License 1.1 or the InMon sFlow License:
-
- lib/sflow.h
- lib/sflow_agent.c
- lib/sflow_api.h
- lib/sflow_poller.c
- lib/sflow_receiver.c
- lib/sflow_sampler.c
-
- These licenses are available, respectively, the following URLs:
-
- http://host-sflow.sourceforge.net/sissl.html
- http://www.inmon.com/technology/sflowlicense.txt
-
- The full text of each license is also appended to the end of this
- file.
-
-* The following components are licensed for use as desired without restriction:
-
- lib/crc32c.c
-
-* lib/ovs.tmac in the source distribution, and manpages in the
- binaries, includes troff macros from groff 1.21 that contain the
- following notice:
-
- .\" an-ext.tmac
- .\"
- .\" Written by Eric S. Raymond <esr@thyrsus.com>
- .\" Werner Lemberg <wl@gnu.org>
- .\"
- .\" Version 2007-Feb-02
- .\"
- .\" Copyright (C) 2007, 2009, 2011 Free Software Foundation, Inc.
- .\" You may freely use, modify and/or distribute this file.
-
-* m4/absolute-header.m4, by Derek Price, and m4/include_next.m4, by
- Paul Eggert and Derek Price bear the following notices:
-
- Copyright (C) 2006-2013 Free Software Foundation, Inc.
- This file is free software; the Free Software Foundation
- gives unlimited permission to copy and/or distribute it,
- with or without modifications, as long as this notice is preserved.
-
-* The following files are licensed under the ISC-license
-
- lib/lldp/aa-structs.h
- lib/lldp/lldpd.c
- lib/lldp/lldpd.h
- lib/lldp/lldpd-structs.c
- lib/lldp/lldpd-structs.h
- lib/lldp/lldp.c
- lib/lldp/lldp-tlv.h
- lib/lldp/lldp-const.h
-
-* All other components of this package are licensed under
- The Apache License Version 2.0.
-
- On Debian systems, the complete text of the Apache License version 2.0
- can be found in '/usr/share/common-licenses/Apache-2.0'.
-
-----------------------------------------------------------------------
-
-Retrieved from http://host-sflow.sourceforge.net/sissl.html, 2011-12-12:
-
- Sun Industry Standards Source License - Version 1.1
-
- 1.0 DEFINITIONS
-
- 1.1 "Commercial Use" means distribution or otherwise making the
- Original Code available to a third party.
-
- 1.2 "Contributor Version" means the combination of the Original Code,
- and the Modifications made by that particular Contributor.
-
- 1.3 "Electronic Distribution Mechanism" means a mechanism generally
- accepted in the software development community for the electronic
- transfer of data.
-
- 1.4 "Executable" means Original Code in any form other than Source
- Code.
-
- 1.5 "Initial Developer" means the individual or entity identified as
- the Initial Developer in the Source Code notice required by Exhibit A.
-
- 1.6 "Larger Work" means a work which combines Original Code or portions
- thereof with code not governed by the terms of this License.
-
- 1.7 "License" means this document.
-
- 1.8 "Licensable" means having the right to grant, to the maximum extent
- possible, whether at the time of the initial grant or subsequently
- acquired, any and all of the rights conveyed herein.
-
- 1.9 "Modifications" means any addition to or deletion from the
- substance or structure of either the Original Code or any previous
- Modifications. A Modification is:
-
- A. Any addition to or deletion from the contents of a file containing
- Original Code or previous Modifications.
-
- B. Any new file that contains any part of the Original Code or previous
- Modifications.
-
- 1.10 "Original Code" means Source Code of computer software code which
- is described in the Source Code notice required by Exhibit A as
- Original Code.
-
- 1.11 "Patent Claims" means any patent claim(s), now owned or hereafter
- acquired, including without limitation, method, process, and apparatus
- claims, in any patent Licensable by grantor.
-
- 1.12 "Source Code" means the preferred form of the Original Code for
- making modifications to it, including all modules it contains, plus any
- associated interface definition files, or scripts used to control
- compilation and installation of an Executable.
-
- 1.13 "Standards" means the standards identified in Exhibit B.
-
- 1.14 "You" (or "Your") means an individual or a legal entity exercising
- rights under, and complying with all of the terms of, this License or a
- future version of this License issued under Section 6.1. For legal
- entities, "You'' includes any entity which controls, is controlled by,
- or is under common control with You. For purposes of this definition,
- "control'' means (a) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (b) ownership of more than fifty percent (50%) of the
- outstanding shares or beneficial ownership of such entity.
-
- 2.0 SOURCE CODE LICENSE
-
- 2.1 The Initial Developer Grant
- The Initial Developer hereby grants You a world-wide, royalty-free,
- non-exclusive license, subject to third party intellectual property
- claims:
-
- (a) under intellectual property rights (other than patent or trademark)
- Licensable by Initial Developer to use, reproduce, modify, display,
- perform, sublicense and distribute the Original Code (or portions
- thereof) with or without Modifications, and/or as part of a Larger
- Work; and
-
- (b) under Patents Claims infringed by the making, using or selling of
- Original Code, to make, have made, use, practice, sell, and offer for
- sale, and/or otherwise dispose of the Original Code (or portions
- thereof).
-
- (c) the licenses granted in this Section 2.1(a) and (b) are effective
- on the date Initial Developer first distributes Original Code under the
- terms of this License.
-
- (d) Notwithstanding Section 2.1(b) above, no patent license is granted:
- 1) for code that You delete from the Original Code; 2) separate from
- the Original Code; or 3) for infringements caused by: i) the
- modification of the Original Code or ii) the combination of the
- Original Code with other software or devices, including but not limited
- to Modifications.
- 3.0 DISTRIBUTION OBLIGATIONS
-
- 3.1 Application of License.
- The Source Code version of Original Code may be distributed only under
- the terms of this License or a future version of this License released
- under Section 6.1, and You must include a copy of this License with
- every copy of the Source Code You distribute. You may not offer or
- impose any terms on any Source Code version that alters or restricts
- the applicable version of this License or the recipients' rights
- hereunder. Your license for shipment of the Contributor Version is
- conditioned upon Your full compliance with this Section. The
- Modifications which You create must comply with all requirements set
- out by the Standards body in effect one hundred twenty (120) days
- before You ship the Contributor Version. In the event that the
- Modifications do not meet such requirements, You agree to publish
- either (i) any deviation from the Standards protocol resulting from
- implementation of Your Modifications and a reference implementation of
- Your Modifications or (ii) Your Modifications in Source Code form, and
- to make any such deviation and reference implementation or
- Modifications available to all third parties under the same terms as
- this license on a royalty free basis within thirty (30) days of Your
- first customer shipment of Your Modifications.
-
- 3.2 Required Notices.
- You must duplicate the notice in Exhibit A in each file of the Source
- Code. If it is not possible to put such notice in a particular Source
- Code file due to its structure, then You must include such notice in a
- location (such as a relevant directory) where a user would be likely to
- look for such a notice. If You created one or more Modification(s) You
- may add Your name as a Contributor to the notice described in Exhibit
- A. You must also duplicate this License in any documentation for the
- Source Code where You describe recipients' rights or ownership rights
- relating to Initial Code. You may choose to offer, and to charge a fee
- for, warranty, support, indemnity or liability obligations to one or
- more recipients of Your version of the Code. However, You may do so
- only on Your own behalf, and not on behalf of the Initial Developer.
- You must make it absolutely clear than any such warranty, support,
- indemnity or liability obligation is offered by You alone, and You
- hereby agree to indemnify the Initial Developer for any liability
- incurred by the Initial Developer as a result of warranty, support,
- indemnity or liability terms You offer.
-
- 3.3 Distribution of Executable Versions.
- You may distribute Original Code in Executable and Source form only if
- the requirements of Sections 3.1 and 3.2 have been met for that
- Original Code, and if You include a notice stating that the Source Code
- version of the Original Code is available under the terms of this
- License. The notice must be conspicuously included in any notice in an
- Executable or Source versions, related documentation or collateral in
- which You describe recipients' rights relating to the Original Code.
- You may distribute the Executable and Source versions of Your version
- of the Code or ownership rights under a license of Your choice, which
- may contain terms different from this License, provided that You are in
- compliance with the terms of this License. If You distribute the
- Executable and Source versions under a different license You must make
- it absolutely clear that any terms which differ from this License are
- offered by You alone, not by the Initial Developer. You hereby agree to
- indemnify the Initial Developer for any liability incurred by the
- Initial Developer as a result of any such terms You offer.
-
- 3.4 Larger Works.
- You may create a Larger Work by combining Original Code with other code
- not governed by the terms of this License and distribute the Larger
- Work as a single product. In such a case, You must make sure the
- requirements of this License are fulfilled for the Original Code.
-
- 4.0 INABILITY TO COMPLY DUE TO STATUTE OR REGULATION
-
- If it is impossible for You to comply with any of the terms of this
- License with respect to some or all of the Original Code due to
- statute, judicial order, or regulation then You must: (a) comply with
- the terms of this License to the maximum extent possible; and (b)
- describe the limitations and the code they affect. Such description
- must be included in the LEGAL file described in Section 3.2 and must be
- included with all distributions of the Source Code. Except to the
- extent prohibited by statute or regulation, such description must be
- sufficiently detailed for a recipient of ordinary skill to be able to
- understand it.
-
- 5.0 APPLICATION OF THIS LICENSE
-
- This License applies to code to which the Initial Developer has
- attached the notice in Exhibit A and to related Modifications as set
- out in Section 3.1.
-
- 6.0 VERSIONS OF THE LICENSE
-
- 6.1 New Versions.
- Sun may publish revised and/or new versions of the License from time to
- time. Each version will be given a distinguishing version number.
-
- 6.2 Effect of New Versions.
- Once Original Code has been published under a particular version of the
- License, You may always continue to use it under the terms of that
- version. You may also choose to use such Original Code under the terms
- of any subsequent version of the License published by Sun. No one other
- than Sun has the right to modify the terms applicable to Original Code.
-
- 7.0 DISCLAIMER OF WARRANTY
-
- ORIGINAL CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
- WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
- WITHOUT LIMITATION, WARRANTIES THAT THE ORIGINAL CODE IS FREE OF
- DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING.
- THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE ORIGINAL CODE
- IS WITH YOU. SHOULD ANY ORIGINAL CODE PROVE DEFECTIVE IN ANY RESPECT,
- YOU (NOT THE INITIAL DEVELOPER) ASSUME THE COST OF ANY NECESSARY
- SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY
- CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY ORIGINAL
- CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
-
- 8.0 TERMINATION
-
- 8.1 This License and the rights granted hereunder will terminate
- automatically if You fail to comply with terms herein and fail to cure
- such breach within 30 days of becoming aware of the breach. All
- sublicenses to the Original Code which are properly granted shall
- survive any termination of this License. Provisions which, by their
- nature, must remain in effect beyond the termination of this License
- shall survive.
-
- 8.2 In the event of termination under Section 8.1 above, all end user
- license agreements (excluding distributors and resellers) which have
- been validly granted by You or any distributor hereunder prior to
- termination shall survive termination.
-
- 9.0 LIMIT OF LIABILITY
-
- UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
- (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL
- DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF ORIGINAL CODE,
- OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
- INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY
- CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,
- WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
- COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
- INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
- LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY
- RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
- PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE
- EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS
- EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
-
- 10.0 U.S. GOVERNMENT END USERS
-
- U.S. Government: If this Software is being acquired by or on behalf of
- the U.S. Government or by a U.S. Government prime contractor or
- subcontractor (at any tier), then the Government's rights in the
- Software and accompanying documentation shall be only as set forth in
- this license; this is in accordance with 48 C.F.R. 227.7201 through
- 227.7202-4 (for Department of Defense (DoD) acquisitions) and with 48
- C.F.R. 2.101 and 12.212 (for non-DoD acquisitions).
-
- 11.0 MISCELLANEOUS
-
- This License represents the complete agreement concerning subject
- matter hereof. If any provision of this License is held to be
- unenforceable, such provision shall be reformed only to the extent
- necessary to make it enforceable. This License shall be governed by
- California law provisions (except to the extent applicable law, if any,
- provides otherwise), excluding its conflict-of-law provisions. With
- respect to disputes in which at least one party is a citizen of, or an
- entity chartered or registered to do business in the United States of
- America, any litigation relating to this License shall be subject to
- the jurisdiction of the Federal Courts of the Northern District of
- California, with venue lying in Santa Clara County, California, with
- the losing party responsible for costs, including without limitation,
- court costs and reasonable attorneys' fees and expenses. The
- application of the United Nations Convention on Contracts for the
- International Sale of Goods is expressly excluded. Any law or
- regulation which provides that the language of a contract shall be
- construed against the drafter shall not apply to this License.
-
- EXHIBIT A - Sun Standards License
-"The contents of this file are subject to the Sun Standards
-License Version 1.1 (the "License");
-You may not use this file except in compliance with the
-License. You may obtain a copy of the
-License at _______________________________.
-
-Software distributed under the License is distributed on
-an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
-express or implied. See the License for the specific
-language governing rights and limitations under the License.
-
-The Original Code is ______________________________________.
-
-The Initial Developer of the Original Code is:
-InMon Corp.
-
-Portions created by: _______________________________________
-
-are Copyright (C): _______________________________________
-
-All Rights Reserved.
-
-Contributor(s): _______________________________________
-
- EXHIBIT B - Standards
-
- The Standard is defined as the following:
-
- sFlow Specification, located at
- [1]http://sflow.org/developers/specifications.php
-
-References
-
- 1. http://sflow.org/developers/specifications.php
-
-----------------------------------------------------------------------
-
-Retrieved from http://www.inmon.com/technology/sflowlicense.txt, 2011-12-12:
-
-LICENSE AGREEMENT
-
-PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFORE REPRODUCING OR IN ANY WAY
-UTILIZING THE sFlow(R) SOFTWARE ("SOFTWARE") AND/OR ANY ACCOMPANYING DOCUMENTATION
-("DOCUMENTATION") AND/OR THE RELATED SPECIFICATIONS ("SPECIFICATIONS"). YOUR REPRODUCTION
-OR USE OF THE SOFTWARE AND/OR THE DOCUMENTATION AND/OR THE SPECIFICATIONS CONSTITUTES YOUR
-ACCEPTANCE OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO BE BOUND
-BY THE TERMS AND CONDITIONS OF THIS AGREEMENT, YOU MAY NOT REPRODUCE OR IN ANY WAY UTILIZE
-THE SOFTWARE OR THE DOCUMENTATION OR THE SPECIFICATIONS.
-
-1. Definitions.
-
-"Documentation" means the user manuals, training materials, and operating materials, if any,
-InMon provides to Licensee under this Agreement.
-
-"InMon" means InMon Corporation, its affiliates and subsidiaries.
-
-"Intellectual Property Rights" means any trade secrets, patents, including without
-limitation any patents covering the Software, copyrights, know-how, moral rights and
-similar rights of any type under the laws of any governmental authority, domestic or
-foreign, including all applications and registrations relating to any of the foregoing.
-
-"Licensee Hardware" means all computers, routers, or other equipment owned or controlled by
-or on behalf of Licensee.
-
-"Products" means any and all software applications, computers, routers, or other equipment
-manufactured by or on behalf of Licensee for the purpose of resale or lease to any other
-third party, or otherwise made available by Licensee free of charge.
-
-"Software" means the sFlow(R) software programs, in source or binary code format, that
-Licensee licenses from InMon under this Agreement and any bug fixes or error corrections
-which InMon may provide to Licensee.
-
-"Specifications" means the published specifications provided or otherwise made available by
-InMon at: http://www.sflow.org.
-
-"Trademark" means InMon's "sFlow(R)" trademark.
-
-2. License Grant.
-
-2.1 Software, Documentation and Specifications License Grant. InMon hereby grants to
-Licensee, under all of InMon's Intellectual Property Rights therein, a perpetual (subject
-to InMon's termination rights under Section 7 below), nonexclusive, royalty-free, worldwide,
-transferable, sublicensable license, to: (i) use and reproduce the Software, the
-Documentation, and the Specifications; (ii) modify the Software; (iii) implement the
-Specifications in the Products; (iv) install the Software, or software in which the
-Specifications have been implemented, on Licensee Hardware and Products, and (v) distribute
-any Products that include the Software, the Documentation, or software in which the
-Specifications have been implemented.
-
-2.2 Trademark License. InMon hereby grants to Licensee a perpetual (subject to InMon's
-termination rights under Section 7 below), nonexclusive, royalty-free, worldwide,
-transferable, sublicensable license to use the Trademark on or in connection with the
-Software, the Documentation, the Specifications and any software that implements the
-Specifications.
-
-2.3 Restrictions. Licensee agrees that it will not use the Software in a way
-inconsistent with the license granted in Section 2.1. Further, Licensee agrees that, in
-exercising its rights under the license granted to it in this Agreement, Licensee will:
-(i) strictly adhere to and fully comply with the Specifications; (ii) use the Trademark,
-and no other mark, to identify the Software, the Documentation, the Specifications and any
-Products that implement the Specifications; (iii) place, in a font or graphic design
-designated by InMon, the phrase "sFlow(R)" on any technical documentation,
-sales/marketing materials, catalogs, or other such materials relating to products it
-manufactures or markets which it has configured to be compatible with the Software or
-otherwise implement the Specifications; (iv) in connection with any Products shipped to or
-sold in other countries that include the Software or any software that implements the
-Specifications, comply with the patent and trademark laws and practice of such other
-country; and (v) not alter or impair any acknowledgment of copyright or trademark rights of
-InMon that may appear in or on the Software, the Documentation or the Specifications. In
-the event InMon determines that Licensee is not complying with its obligations under
-clauses (i)-(v) above, InMon shall notify Licensee of such non-compliance, and if Licensee
-fails to correct such non-compliance within three (3) months, InMon may immediately
-terminate this Agreement as provided under paragraph 7 below and pursue any and all
-actions and remedies as it deems necessary, including, but not limited to breach of
-contract.
-
-3. Ownership. Except for the license expressly granted in Section 2, Inmon hereby
-retains all right, title, and interest in and to the Trademark and all its Intellectual
-Property Rights in the Software, the Documentation and the Specifications. Licensee
-obtains no rights hereunder in the Trademark, Software, Documentation or Specifications by
-implication, estoppel or otherwise. Licensee acknowledges that the Trademark, Software,
-Documentation and Specifications are being licensed and not sold under this Agreement, and
-that this Agreement does not transfer title in the Trademark, Software, Documentation or
-Specifications, or any copy thereof, to Licensee.
-
-4. Support. Inmon shall have no obligation under this Agreement to (a) supply
-maintenance or support, bug fixes or error corrections to the Licensed Software,
-(b) supply future versions of the Licensed Software or (c) provide Licensed Software
-development tools to Licensee.
-
-5. Warranty. INMON HEREBY DISCLAIMS ALL WARRANTIES, EITHER EXPRESS, IMPLIED OR
-STATUTORY, WITH RESPECT TO THE TRADEMARK, THE SOFTWARE, THE DOCUMENTATION, THE
-SPECIFICATIONS. OR OTHERWISE, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF ANY INTELLECTUAL
-PROPERTY RIGHTS.
-
-6. Limitation of Liability. IN NO EVENT SHALL INMON OR ITS SUPPLIERS OR LICENSORS BE
-LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, SPECIAL, INDIRECT OR EXEMPLARY DAMAGES WHATSOEVER,
-WHETHER RELATED TO OR ARISING OUT OF THIS AGREEMENT, THE TRADEMARK, THE SOFTWARE, THE
-DOCUMENTATION, THE SPECIFICATIONS, OR OTHERWISE, INCLUDING WITHOUT LIMITATION, DAMAGES FOR
-LOSS OF PROFITS, BUSINESS INTERRUPTION, LOSS OF DATA, COSTS OF PROCUREMENT OF SUBSTITUTE
-GOODS OR SERVICES OR FOR ANY CLAIM OR DEMAND AGAINST LICENSEE BY ANY OTHER PARTY, OR OTHER
-PECUNIARY LOSS, EVEN IF INMON HAS BEEN ADVISED OF OR KNOWS OF THE POSSIBILITY OF SUCH
-DAMAGES.
-
-7. Term and Termination. The term of this Agreement will begin on the Effective Date,
-which shall be deemed to be the date of delivery of the Software and/or Documentation and/or
-Specifications to Licensee, and shall continue indefinitely unless and until terminated by
-Licensee's giving written notice of termination to InMon, or by InMon pursuant to InMon's
-termination rights as set forth in Section 2.3 above. Upon any termination of this
-Agreement, Licensee shall cease exercising its license rights under this Agreement,
-including the right to distribute Products that incorporate the Software or Documentation
-or that implement the Specifications. The rights and obligations contained in Sections 1,
-3, 5, 6, 7, and 8 shall survive any termination of this Agreement.
-
-8. General Provisions.
-
-8.1 Assignment. This Agreement shall be binding upon and inure to the benefit of the
-parties hereto and their permitted successors and permitted assigns. InMon will have the
-right to assign this Agreement without notice to Licensee. Licensee may assign or transfer
-(whether by merger, operation of law or in any other manner) any of its rights or delegate
-any of its obligations hereunder without the prior written consent of InMon, provided the
-assignee assumes in writing all of Licensee's obligations hereunder.
-
-8.2 Notices. All notices permitted or required under this Agreement shall be in
-writing and shall be delivered in person or mailed by first class, registered or certified
-mail, postage prepaid, to the address of the party specified in this Agreement or such
-other address as either party may specify in writing. Such notice shall be deemed to have
-been given upon receipt.
-
-8.3 Non-Waiver. No term or provision hereof shall be deemed waived, and no breach
-excused, unless such waiver or consent shall be in writing and signed by the party claimed
-to have waived or consented. Any consent or waiver, whether express or implied, shall not
-constitute a consent or waiver of, or excuse for any separate, different or subsequent
-breach.
-
-8.4 Independent Contractor. The parties' relationship shall be solely that of
-independent contractors, and nothing contained in this Agreement shall be construed to make
-either party an agent, partner, representative or principal of the other for any purpose.
-
-8.5 Choice of Law and Forum. This Agreement shall be governed by and construed under
-the laws of the State of California, without giving effect to such state's conflict of laws
-principles. The parties hereby submit to the personal jurisdiction of, and agree that any
-legal proceeding with respect to or arising under this Agreement shall be brought in, the
-United States District Court for the Northern District of California or the state courts
-of the State of California for the County of San Francisco.
-
-8.6 U.S. Government Licenses. The Software and Documentation are considered a
-"commercial item" as that term is defined at 48 C.F.R 2.101, or "commercial computer
-software" and "commercial computer software documentation" as such terms are used in
-48 C.F.R 12.212 of the Federal Acquisition Regulations and its successors, and
-48 C.F.R. 227.7202 of the DoD FAR Supplement and its successors.
-
-8.7 Severability. If any provision of this Agreement is held to be unenforceable under
-applicable law, then such provision shall be excluded from this Agreement and the balance
-of this Agreement shall be interpreted as if such provision were so excluded and shall be
-enforceable in accordance with its terms. The court in its discretion may substitute for
-the excluded provision an enforceable provision which in economic substance reasonably
-approximates the excluded provision.
-
-8.8 Compliance With Law. Licensee shall comply with all applicable laws and
-regulations (including privacy laws and regulations) having application to or governing its
- use and/or operation of the Software and agrees to indemnify and hold InMon harmless from
-and against any claims, damages, losses or obligations suffered or incurred by InMon
-arising from its failure to so comply.
-
-8.9 Entire Agreement; Amendment. This Agreement constitutes the final, complete and
-entire agreement between the parties with respect to the subject matter hereof, and
-supersedes any previous proposals, negotiations, agreements, or arrangements, whether
-verbal or written, made between the parties with respect to such subject matter. This
-Agreement shall control over any additional or conflicting terms in any of Licensee's
-purchase orders or other business forms. This Agreement may only be amended or modified
-by mutual agreement of authorized representatives of the parties in writing.
-
-InMon Corp.
-580 California Street, 5th Floor, San Francisco, CA 94104
-Phone: (415) 283-3260
-URL: www.inmon.com
-Email: info@inmon.com
deleted file mode 100644
@@ -1,2 +0,0 @@
-usr/bin
-usr/sbin
deleted file mode 100644
@@ -1,11 +0,0 @@
-MODULES=( __MODULES__ )
-
-PACKAGE_NAME="openvswitch"
-PACKAGE_VERSION="__VERSION__"
-MAKE="./configure --with-linux='${kernel_source_dir}' && make -C datapath/linux"
-for __idx in ${!MODULES[@]}; do
- BUILT_MODULE_NAME[__idx]=${MODULES[__idx]}
- BUILT_MODULE_LOCATION[__idx]=datapath/linux/
- DEST_MODULE_LOCATION[__idx]=/kernel/drivers/net/openvswitch/
-done
-AUTOINSTALL=yes
deleted file mode 100755
@@ -1,107 +0,0 @@
-#! /bin/sh
-
-# Copyright (c) 2012, 2013 Nicira, Inc.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at:
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-# Have a look at /usr/share/doc/openvswitch-switch/README.Debian
-# for more information about configuring the /etc/network/interfaces.
-
-if [ -z "${IF_OVS_TYPE}" ]; then
- exit 0
-fi
-
-ovs_vsctl() {
- ovs-vsctl --timeout=5 "$@"
-}
-
-if (ovs_vsctl --version) > /dev/null 2>&1; then :; else
- exit 0
-fi
-
-if /etc/init.d/openvswitch-switch status > /dev/null 2>&1; then :; else
- /etc/init.d/openvswitch-switch start
-fi
-
-if [ "${MODE}" = "start" ]; then
- eval OVS_EXTRA=\"${IF_OVS_EXTRA}\"
-
- case "${IF_OVS_TYPE}" in
- OVSBridge)
- ovs_vsctl -- --may-exist add-br "${IFACE}" ${IF_OVS_OPTIONS}\
- ${OVS_EXTRA+-- $OVS_EXTRA}
-
- if [ ! -z "${IF_OVS_PORTS}" ]; then
- ifup --allow="${IFACE}" ${IF_OVS_PORTS}
- fi
- ;;
- OVSPort)
- ovs_vsctl -- --may-exist add-port "${IF_OVS_BRIDGE}"\
- "${IFACE}" ${IF_OVS_OPTIONS} \
- ${OVS_EXTRA+-- $OVS_EXTRA}
-
- ip link set "${IFACE}" up
- ;;
- OVSIntPort)
- ovs_vsctl -- --may-exist add-port "${IF_OVS_BRIDGE}"\
- "${IFACE}" ${IF_OVS_OPTIONS} -- set Interface "${IFACE}"\
- type=internal ${OVS_EXTRA+-- $OVS_EXTRA}
-
- ip link set "${IFACE}" up
- ;;
- OVSBond)
- ovs_vsctl -- --fake-iface --may-exist add-bond "${IF_OVS_BRIDGE}"\
- "${IFACE}" ${IF_OVS_BONDS} ${IF_OVS_OPTIONS} \
- ${OVS_EXTRA+-- $OVS_EXTRA}
-
- ip link set "${IFACE}" up
- for member in ${IF_OVS_BONDS}
- do
- ip link set "${member}" up
- done
- ;;
- OVSPatchPort)
- ovs_vsctl -- --may-exist add-port "${IF_OVS_BRIDGE}"\
- "${IFACE}" ${IF_OVS_OPTIONS} -- set Interface "${IFACE}" \
- type=patch options:peer="${IF_OVS_PATCH_PEER}" \
- ${OVS_EXTRA+-- $OVS_EXTRA}
- ;;
- OVSTunnel)
- ovs_vsctl -- --may-exist add-port "${IF_OVS_BRIDGE}"\
- "${IFACE}" ${IF_OVS_OPTIONS} -- set Interface "${IFACE}" \
- type=${IF_OVS_TUNNEL_TYPE} ${IF_OVS_TUNNEL_OPTIONS} \
- ${OVS_EXTRA+-- $OVS_EXTRA}
- ;;
- *)
- exit 0
- ;;
- esac
-elif [ "${MODE}" = "stop" ]; then
- case "${IF_OVS_TYPE}" in
- OVSBridge)
- if [ ! -z "${IF_OVS_PORTS}" ]; then
- ifdown --allow="${IFACE}" ${IF_OVS_PORTS}
- fi
-
- ovs_vsctl -- --if-exists del-br "${IFACE}"
- ;;
- OVSPort|OVSIntPort|OVSBond|OVSPatchPort|OVSTunnel)
- ovs_vsctl -- --if-exists del-port "${IF_OVS_BRIDGE}" "${IFACE}"
- ;;
- *)
- exit 0
- ;;
- esac
-fi
-
-exit 0
deleted file mode 100644
@@ -1,19 +0,0 @@
-usr/lib/*/libopenvswitch*.so
-usr/lib/*/libofproto*.so
-usr/lib/*/libovsdb*.so
-usr/lib/*/libsflow*.so
-usr/lib/*/libvtep*.so
-usr/lib/*/libopenvswitch*.a
-usr/lib/*/libofproto*.a
-usr/lib/*/libovsdb*.a
-usr/lib/*/libsflow*.a
-usr/lib/*/libvtep*.a
-usr/lib/*/pkgconfig
-include/*.h usr/include/openvswitch
-include/openflow/*.h usr/include/openvswitch/openflow
-include/openvswitch/*.h usr/include/openvswitch/openvswitch
-include/sparse/*.h usr/include/openvswitch/sparse
-include/sparse/arpa/*.h usr/include/openvswitch/sparse/arpa
-include/sparse/netinet/*.h usr/include/openvswitch/sparse/netinet
-include/sparse/sys/*.h usr/include/openvswitch/sparse/sys
-lib/*.h usr/include/openvswitch/lib
deleted file mode 100644
@@ -1,5 +0,0 @@
-usr/lib/*/libopenvswitch*.so.*
-usr/lib/*/libofproto*.so.*
-usr/lib/*/libovsdb*.so.*
-usr/lib/*/libsflow*.so.*
-usr/lib/*/libvtep*.so.*
deleted file mode 100644
@@ -1 +0,0 @@
-var/log/openvswitch
deleted file mode 100644
deleted file mode 100644
@@ -1,11 +0,0 @@
-etc/bash_completion.d/ovs-appctl-bashcomp.bash
-usr/bin/ovs-appctl
-usr/bin/ovs-docker
-usr/bin/ovs-ofctl
-usr/bin/ovs-parse-backtrace
-usr/bin/ovs-pki
-usr/bin/ovsdb-client
-usr/sbin/ovs-bugtool
-usr/share/openvswitch/bugtool-plugins
-usr/share/openvswitch/scripts/ovs-bugtool-*
-usr/share/openvswitch/scripts/ovs-lib
deleted file mode 100644
@@ -1,7 +0,0 @@
-ovsdb/ovsdb-client.1
-ovsdb/ovsdb-tool.1
-utilities/bugtool/ovs-bugtool.8
-debian/tmp/usr/share/man/man8/ovs-appctl.8
-utilities/ovs-ofctl.8
-debian/tmp/usr/share/man/man8/ovs-parse-backtrace.8
-debian/tmp/usr/share/man/man8/ovs-pki.8
deleted file mode 100644
@@ -1,21 +0,0 @@
-#!/bin/sh
-
-set -e
-
-package=openvswitch-datapath-dkms
-name=openvswitch
-
-version=`dpkg-query -W -f='${Version}' "$package" \
- |rev|cut -d- -f2-|rev|cut -d':' -f2|tr -d "\n"`
-
-isadded=`dkms status -m "$name" -v "$version"`
-
-if [ "x${isadded}" = "x" ] ; then
- dkms add -m "$name" -v "$version"
-fi
-
-if [ "$1" = 'configure' ] ; then
- dkms build -m "$name" -v "$version" && dkms install -m "$name" -v "$version" || true
-fi
-
-#DEBHELPER#
deleted file mode 100644
@@ -1,15 +0,0 @@
-#!/bin/sh
-
-set -e
-
-package=openvswitch-datapath-dkms
-name=openvswitch
-
-version=`dpkg-query -W -f='${Version}' "$package" \
- |rev|cut -d- -f2-|rev|cut -d':' -f2|tr -d "\n"`
-
-dkms remove -m "$name" -v "$version" --all || true
-
-#DEBHELPER#
-
-exit 0
deleted file mode 100755
@@ -1,27 +0,0 @@
-#!/bin/sh
-# postinst script for #PACKAGE#
-#
-# see: dh_installdeb(1)
-
-set -e
-
-#DEBHELPER#
-
-# If the kernel module is already loaded, we have nothing to do here.
-# A force-reload-kmod should be run manually to use the new kernel module.
-if [ -e /sys/module/openvswitch ]; then
- exit 0
-fi
-
-# If the kernel module is not loaded, then it is likely because none
-# was installed before and therefore Open vSwitch couldn't be started.
-# Try to start it now.
-#
-# (Ideally we'd only want to do this if this package corresponds to the
-# running kernel, but I don't know a reliable way to check.)
-INIT=/etc/init.d/openvswitch-switch
-if test -x $INIT; then
- $INIT start || true
-fi
-
-exit 0
deleted file mode 100644
@@ -1,31 +0,0 @@
-Open vSwitch for Debian
-----------------------
-
-* How do I build this module the Debian way?
-
- - Building with module-assistant:
-
- $ module-assistant auto-install openvswitch-datapath
- or
- $ m-a a-i openvswitch-datapath
-
- If kernel source or headers are in a non-standard directory, add
- the option -k /path/to/kernel/source with the correct path.
-
- - Building with make-kpkg
-
- $ cd /usr/src/
- $ tar jxvf openvswitch.tar.bz2
- $ cd /usr/src/kernel-source-2.6.26
- $ make-kpkg --added-modules=openvswitch modules
-
- - Building without make-kpkg
-
- $ cd /usr/src/
- $ tar jxvf openvswitch.tar.bz2
- $ cd modules/openvswitch
- $ fakeroot debian/rules kdist_image
-
- If you run this as root, fakeroot is not needed.
-
- -- Ben Pfaff <blp@nicira.com>, Wed, 22 Jun 2011 09:51:28 -0700
deleted file mode 100644
@@ -1,15 +0,0 @@
-Upstream Authors:
-
- Nicira, Inc.
-
-Copyright:
-
- Copyright (C) 2008 Nicira, Inc.
-
-License:
-
- Files in the datapath/ and its sub-directories are covered under the GNU
- General Public License Version 2.
-
- On Debian systems, the complete text of the GNU General
- Public License can be found in `/usr/share/common-licenses/GPL'.
deleted file mode 100644
@@ -1 +0,0 @@
-usr/src/modules/openvswitch-datapath/debian
deleted file mode 100644
@@ -1,5 +0,0 @@
-debian/*.modules.in usr/src/modules/openvswitch-datapath/debian
-debian/changelog usr/src/modules/openvswitch-datapath/debian
-debian/compat usr/src/modules/openvswitch-datapath/debian
-debian/control usr/src/modules/openvswitch-datapath/debian
-openvswitch.tar.gz usr/src/modules/openvswitch-datapath
deleted file mode 100644
@@ -1 +0,0 @@
-usr/share/openvswitch/scripts
\ No newline at end of file
deleted file mode 100644
@@ -1,181 +0,0 @@
-#!/bin/sh
-#
-# Copyright (c) 2007, 2009 Javier Fernandez-Sanguino <jfs@debian.org>
-#
-# This is free software; you may redistribute it and/or modify
-# it under the terms of the GNU General Public License as
-# published by the Free Software Foundation; either version 2,
-# or (at your option) any later version.
-#
-# This is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License with
-# the Debian operating system, in /usr/share/common-licenses/GPL; if
-# not, write to the Free Software Foundation, Inc., 59 Temple Place,
-# Suite 330, Boston, MA 02111-1307 USA
-#
-### BEGIN INIT INFO
-# Provides: openvswitch-ipsec
-# Required-Start: $network $local_fs $remote_fs openvswitch-switch
-# Required-Stop: $remote_fs
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Open vSwitch GRE-over-IPsec daemon
-# Description: The ovs-monitor-ipsec script provides support for
-# encrypting GRE tunnels with IPsec.
-### END INIT INFO
-
-PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
-
-DAEMON=/usr/share/openvswitch/scripts/ovs-monitor-ipsec # Daemon's location
-NAME=ovs-monitor-ipsec # Introduce the short server's name here
-LOGDIR=/var/log/openvswitch # Log directory to use
-DATADIR=/usr/share/openvswitch
-
-PIDFILE=/var/run/openvswitch/$NAME.pid
-
-test -x $DAEMON || exit 0
-
-. /lib/lsb/init-functions
-
-DODTIME=10 # Time to wait for the server to die, in seconds
- # If this value is set too low you might not
- # let some servers to die gracefully and
- # 'restart' will not work
-
-set -e
-
-running_pid() {
-# Check if a given process pid's cmdline matches a given name
- pid=$1
- name=$2
- [ -z "$pid" ] && return 1
- [ ! -d /proc/$pid ] && return 1
- cmd=`cat /proc/$pid/cmdline | tr "\000" " "|cut -d " " -f 2`
- # Is this the expected server
- [ "$cmd" != "$name" ] && return 1
- return 0
-}
-
-running() {
-# Check if the process is running looking at /proc
-# (works for all users)
-
- # No pidfile, probably no daemon present
- [ ! -f "$PIDFILE" ] && return 1
- pid=`cat $PIDFILE`
- running_pid $pid $DAEMON || return 1
- return 0
-}
-
-start_server() {
- ${DATADIR}/scripts/ovs-ctl --ike-daemon=strongswan start-ovs-ipsec
- return 0
-}
-
-stop_server() {
- ${DATADIR}/scripts/ovs-ctl stop-ovs-ipsec
- return 0
-}
-
-force_stop() {
-# Force the process to die killing it manually
- [ ! -e "$PIDFILE" ] && return
- if running ; then
- kill -15 $pid
- # Is it really dead?
- sleep "$DODTIME"
- if running ; then
- kill -9 $pid
- sleep "$DODTIME"
- if running ; then
- echo "Cannot kill $NAME (pid=$pid)!"
- exit 1
- fi
- fi
- fi
- rm -f $PIDFILE
-}
-
-
-case "$1" in
- start)
- log_daemon_msg "Starting $NAME"
- # Check if it's running first
- if running ; then
- log_progress_msg "apparently already running"
- log_end_msg 0
- exit 0
- fi
- if start_server && running ; then
- # It's ok, the server started and is running
- log_end_msg 0
- else
- # Either we could not start it or it is not running
- # after we did
- # NOTE: Some servers might die some time after they start,
- # this code does not try to detect this and might give
- # a false positive (use 'status' for that)
- log_end_msg 1
- fi
- ;;
- stop)
- log_daemon_msg "Stopping $NAME"
- if running ; then
- # Only stop the server if we see it running
- stop_server
- log_end_msg $?
- else
- # If it's not running don't do anything
- log_progress_msg "apparently not running"
- log_end_msg 0
- exit 0
- fi
- ;;
- force-stop)
- # First try to stop gracefully the program
- $0 stop
- if running; then
- # If it's still running try to kill it more forcefully
- log_daemon_msg "Stopping (force) $NAME"
- force_stop
- log_end_msg $?
- fi
- ;;
- restart|force-reload)
- log_daemon_msg "Restarting $NAME"
- stop_server
- # Wait some sensible amount, some server need this
- [ -n "$DODTIME" ] && sleep $DODTIME
- start_server
- running
- log_end_msg $?
- ;;
- status)
- log_daemon_msg "Checking status of $NAME"
- if running ; then
- log_progress_msg "running"
- log_end_msg 0
- else
- log_progress_msg "apparently not running"
- log_end_msg 1
- exit 1
- fi
- ;;
- # Use this if the daemon cannot reload
- reload)
- log_warning_msg "Reloading $NAME daemon: not implemented, as the"
- log_warning_msg "deamon cannot re-read the config file (use restart)."
- ;;
- *)
- N=/etc/init.d/openvswitch-ipsec
- echo "Usage: $N {start|stop|force-stop|restart|force-reload|status}" \
- >&2
- exit 1
- ;;
-esac
-
-exit 0
deleted file mode 100644
@@ -1 +0,0 @@
-ipsec/ovs-monitor-ipsec usr/share/openvswitch/scripts
deleted file mode 100644
@@ -1 +0,0 @@
-/var/lib/openvswitch
deleted file mode 100755
@@ -1,41 +0,0 @@
-#!/bin/sh
-# postinst script for openvswitch-pki
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postinst> `configure' <most-recently-configured-version>
-# * <old-postinst> `abort-upgrade' <new version>
-# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
-# <new-version>
-# * <postinst> `abort-remove'
-# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-# <failed-install-package> <version> `removing'
-# <conflicting-package> <version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-case "$1" in
- configure)
- # Create certificate authorities.
- if test ! -e /var/lib/openvswitch/pki; then
- ovs-pki init
- fi
- ;;
-
- abort-upgrade|abort-remove|abort-deconfigure)
- ;;
-
- *)
- echo "postinst called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-#DEBHELPER#
-
-exit 0
-
-
deleted file mode 100755
@@ -1,43 +0,0 @@
-#!/bin/sh
-# postrm script for openvswitch-pki
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postrm> `remove'
-# * <postrm> `purge'
-# * <old-postrm> `upgrade' <new-version>
-# * <new-postrm> `failed-upgrade' <old-version>
-# * <new-postrm> `abort-install'
-# * <new-postrm> `abort-install' <old-version>
-# * <new-postrm> `abort-upgrade' <old-version>
-# * <disappearer's-postrm> `disappear' <overwriter>
-# <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
- purge)
- rm -f /var/log/openvswitch/ovs-pki.log* || true
- ;;
-
- remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
- ;;
-
- *)
- echo "postrm called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-
deleted file mode 100644
@@ -1,316 +0,0 @@
-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.
-
-
-Debian network scripts (ifupdown) integration
-------------------------------------------------
-This package lets 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.
-
-The stanzas that configure the OVS bridges should begin with "allow-ovs"
-followed by name of the bridge. Here is an example.
-allow-ovs br0
-
-The stanzas that configure the OVS ports should begin with
-"allow-${bridge-name}" followed by name of the port. Here is an example.
-allow-br0 eth0
-
-The following OVS specific "command" options are supported:
-
- - ovs_type: This can either be OVSBridge, OVSPort, OVSIntPort, OVSBond,
- OVSPatchPort or OVSTunnel depending on whether you configure a bridge,
- port, an internal port, a bond, a patch port or a tunnel. This is a
- required option.
-
- - ovs_ports: This option specifies all the ports that belong to a bridge.
-
- - ovs_bridge: This options specifies a bridge to which a port belongs.
- This is a required option for a port.
-
- - ovs_bonds: This option specifies the list of physical interfaces to be
- bonded together.
-
- - ovs_patch_peer: For "OVSPatchPort" interfaces, this field specifies
- the patch's peer on the other bridge.
-
- - ovs_tunnel_type: For "OVSTunnel" interfaces, the type of the tunnel.
- For example, "gre", "vxlan", etc.
-
- - ovs_tunnel_options: For "OVSTunnel" interfaces, this field should be
- used to specify the tunnel options like remote_ip, key, etc.
-
- - ovs_options: This option lets you add extra arguments to a ovs-vsctl
- command. See examples.
-
- - ovs_extra: This option lets you run additional ovs-vsctl commands,
- separated by "--" (double dash). Variables can be part of the "ovs_extra"
- option. You can provide all the standard environmental variables
- described in the interfaces(5) man page. You can also pass shell
- commands.
-
-More implementation specific details can be seen in the examples.
-
-Examples:
---------
-ex 1: A standalone bridge.
-
-allow-ovs br0
-iface br0 inet static
- address 192.168.1.1
- netmask 255.255.255.0
- ovs_type OVSBridge
-
-ex 2: A bridge with one port.
-
-allow-ovs br0
-iface br0 inet dhcp
- ovs_type OVSBridge
- ovs_ports eth0
-
-allow-br0 eth0
-iface eth0 inet manual
- ovs_bridge br0
- ovs_type OVSPort
-
-ex 3: A bridge with multiple physical ports.
-
-allow-ovs br0
-iface br0 inet dhcp
- ovs_type OVSBridge
- ovs_ports eth0 eth1
-
-allow-br0 eth0
-iface eth0 inet manual
- ovs_bridge br0
- ovs_type OVSPort
-
-allow-br0 eth1
-iface eth1 inet manual
- ovs_bridge br0
- ovs_type OVSPort
-
-ex 4: A bridge with an OVS internal port.
-
-allow-ovs br1
-iface br1 inet static
- address 192.168.1.1
- netmask 255.255.255.0
- ovs_type OVSBridge
- ovs_ports vlan100
-
-allow-br1 vlan100
-iface vlan100 inet manual
- ovs_bridge br1
- ovs_type OVSIntPort
- ovs_options tag=100
- ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname -s)
-
-ex 5: Bonding.
-
-allow-ovs br2
-iface br2 inet static
- address 192.170.1.1
- netmask 255.255.255.0
- ovs_type OVSBridge
- ovs_ports bond0
-
-allow-br2 bond0
-iface bond0 inet manual
- ovs_bridge br2
- ovs_type OVSBond
- ovs_bonds eth2 eth3
- ovs_options bond_mode=balance-tcp lacp=active
-
-ex 6: Patch ports.
-
-allow-ovs br0
-iface br0 inet manual
- ovs_type OVSBridge
- ovs_ports patch0
-
-allow-br0 patch0
-iface patch0 inet manual
- ovs_bridge br0
- ovs_type OVSPatchPort
- ovs_patch_peer patch1
-
-allow-ovs br1
-iface br1 inet manual
- ovs_type OVSBridge
- ovs_ports patch1
-
-allow-br1 patch1
-iface patch1 inet manual
- ovs_bridge br1
- ovs_type OVSPatchPort
- ovs_patch_peer patch0
-
-ex 7: Tunnel.
-
-allow-ovs br1
-iface br1 inet static
- address 192.168.1.1
- netmask 255.255.255.0
- ovs_type OVSBridge
- ovs_ports gre1
-
-allow-br1 gre1
-iface gre1 inet manual
- ovs_bridge br1
- ovs_type OVSTunnel
- ovs_tunnel_type gre
- ovs_tunnel_options options:remote_ip=182.168.1.2 options:key=1
-
-ex 8: Create and destroy bridges.
-
-ifup --allow=ovs $list_of_bridges
-ifdown --allow=ovs $list_of_bridges
-
-Open vSwitch integration with systemd-networkd
------------------------------------------------
-
-There is no native integration of OVS with systemd-networkd. That is,
-you cannot create OVS bridges, ports and bonds by simply writing configuration
-files in /etc/systemd/network. But, you can create OVS devices using ovs-vsctl
-and then write configuration files to provide them IP addresses.
-
-As soon as a OVS device is visible, systemd-networkd will provide that device
-an IP address. Since OVS database is persistent across reboots, the OVS
-devices will get re-created after a reboot as soon as OVS startup script is
-invoked. And systemd-networkd will immediately assign the configuration defined
-in /etc/systemd/network.
-
-Example:
-
-If you have a physical ethernet device "ens160" which has been configured with
-DHCP, your systemd-networkd's .network config file will look something like
-this:
-
-```
-[Match]
-Name=ens160
-
-[Network]
-DHCP=ipv4
-
-[DHCP]
-ClientIdentifier=mac
-```
-
-Please note how the DHCP ClientIdentifier above has been configured with the
-mac address.
-
-To create a OVS bridge "br-ens160" and add "ens160" as a port of that
-bridge, you can change the .network configuration for "ens160" to look like:
-
-```
-[Match]
-Name=ens160
-```
-
-Now create a new .network configuration file for "br-ens160". Something like:
-
-```
-[Match]
-Name=br-ens160
-
-[Network]
-DHCP=ipv4
-
-[DHCP]
-ClientIdentifier=mac
-```
-
-Now, use ovs-vsctl to create br-ens160 and add ens160 as a port of it. You
-will also have to flush the IP address of ens160 and restart systemd-networkd
-in the same line. It is important to let br-ens160 have the same mac address as
-ens160 to get the same IP address to br-ens160 from the DHCP server. In the
-below command, "$mac_of_ens160" holds the mac address of ens160. For e.g:
-
-```
-mac_of_ens160='"00:0c:29:77:27:7a"'
-ovs-vsctl --may-exist add-br br-ens160 -- \
- --may-exist add-port br-ens160 ens160 -- \
- set interface br-ens160 mac="$mac_of_ens160"; ip addr flush dev ens160; \
- systemctl restart systemd-networkd
-```
-
-br-ens160 should now have the same DHCP IP. It should also have the correct
-DNS resolution servers configured.
-
-Notes on dependencies:
----------------------
-
-openvswitch-switch depends on $network, $named $remote_fs and $syslog to start.
-This creates some startup dependency issues.
-
-* 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.
-
-* 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.
-
-* 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.
-
-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.
-
-* 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'.
deleted file mode 100644
@@ -1,2 +0,0 @@
-/etc/openvswitch
-/usr/share/openvswitch/switch
deleted file mode 100755
@@ -1,147 +0,0 @@
-#! /bin/sh
-#
-# Copyright (C) 2011, 2012, 2016 Nicira, Inc.
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at:
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-### BEGIN INIT INFO
-# Provides: openvswitch-switch
-# Required-Start: $network $named $remote_fs $syslog
-# Required-Stop: $remote_fs
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Open vSwitch switch
-# Description: openvswitch-switch provides the userspace components and utilities for
-# the Open vSwitch kernel-based switch.
-### END INIT INFO
-
-(test -x /usr/sbin/ovs-vswitchd && test -x /usr/sbin/ovsdb-server) || exit 0
-
-_SYSTEMCTL_SKIP_REDIRECT=yes
-SYSTEMCTL_SKIP_REDIRECT=yes
-
-. /usr/share/openvswitch/scripts/ovs-lib
-test -e /etc/default/openvswitch-switch && . /etc/default/openvswitch-switch
-
-network_interfaces () {
- INTERFACES="/etc/network/interfaces"
- [ -e "${INTERFACES}" ] || return
- bridges=`ifquery --allow ovs --list`
- [ -n "${bridges}" ] && $1 --allow=ovs ${bridges}
-}
-
-load_kmod () {
- ovs_ctl load-kmod || exit $?
-}
-
-start () {
- if ovs_ctl load-kmod; then
- :
- else
- echo "Module has probably not been built for this kernel."
- if ! test -d /usr/share/doc/openvswitch-datapath-source; then
- echo "Install the openvswitch-datapath-source package, then read"
- else
- echo "For instructions, read"
- fi
- echo "/usr/share/doc/openvswitch-datapath-source/README.Debian"
-
- if test X"$OVS_MISSING_KMOD_OK" = Xyes; then
- # We're being invoked by the package postinst. Do not
- # fail package installation just because the kernel module
- # is not available.
- exit 0
- fi
- fi
- set ovs_ctl ${1-start} --system-id=random
- if test X"$FORCE_COREFILES" != X; then
- set "$@" --force-corefiles="$FORCE_COREFILES"
- fi
- set "$@" $OVS_CTL_OPTS
- "$@" || exit $?
- if [ "$2" = "start" ] && [ "$READ_INTERFACES" != "no" ]; then
- network_interfaces ifup
- fi
-}
-
-stop () {
- [ "$READ_INTERFACES" != "no" ] && network_interfaces ifdown
- ovs_ctl stop
-}
-
-restart () {
- # OVS_FORCE_RELOAD_KMOD can be set by package postinst script.
- if [ "$1" = "--save-flows=yes" ] || \
- [ "${OVS_FORCE_RELOAD_KMOD}" = "no" ]; then
- start restart
- elif [ "${OVS_FORCE_RELOAD_KMOD}" = "yes" ]; then
- depmod -a
-
- if [ -e /sys/module/openvswitch ]; then
- LOADED_SRCVERSION=`cat /sys/module/openvswitch/srcversion \
- 2>/dev/null`
- LOADED_VERSION=`cat /sys/module/openvswitch/version \
- 2>/dev/null`
- fi
- SRCVERSION=`modinfo -F srcversion openvswitch 2>/dev/null`
- VERSION=`modinfo -F version openvswitch 2>/dev/null`
-
- ovs_ctl_log "Package upgrading:\n"\
- "Loaded version: ${LOADED_VERSION} ${LOADED_SRCVERSION}.\n"\
- "Version on disk: ${VERSION} ${SRCVERSION}."
-
- # If the kernel module was previously loaded and it is different than
- # the kernel module on disk, then do a 'force-reload-kmod'.
- if [ -n "${LOADED_SRCVERSION}" ] && [ -n "${SRCVERSION}" ] && \
- [ "${SRCVERSION}" != "${LOADED_SRCVERSION}" ]; then
- start force-reload-kmod
- else
- start restart
- fi
- else
- READ_INTERFACES="no" stop
- READ_INTERFACES="no" start
- fi
-}
-
-case $1 in
- start)
- start
- ;;
- stop | force-stop)
- stop
- ;;
- reload | force-reload)
- # The OVS daemons keep up-to-date.
- ;;
- restart)
- shift
- restart "$@"
- ;;
- status)
- ovs_ctl status
- exit $?
- ;;
- force-reload-kmod)
- start force-reload-kmod
- ;;
- load-kmod)
- load_kmod
- ;;
- *)
- echo "Usage: $0 {start|stop|restart|force-reload|status|force-stop|force-reload-kmod|load-kmod}" >&2
- exit 1
- ;;
-esac
-
-exit 0
deleted file mode 100644
@@ -1,17 +0,0 @@
-debian/ifupdown.sh usr/share/openvswitch/scripts
-etc/bash_completion.d/ovs-vsctl-bashcomp.bash
-usr/bin/ovs-dpctl
-usr/bin/ovs-dpctl-top
-usr/bin/ovs-pcap
-usr/bin/ovs-tcpdump
-usr/bin/ovs-tcpundump
-usr/bin/ovs-vlan-test
-usr/bin/ovs-vsctl
-usr/bin/ovsdb-tool
-usr/sbin/ovs-vswitchd
-usr/sbin/ovsdb-server
-usr/share/openvswitch/scripts/ovs-check-dead-ifs
-usr/share/openvswitch/scripts/ovs-ctl
-usr/share/openvswitch/scripts/ovs-kmod-ctl
-usr/share/openvswitch/scripts/ovs-save
-usr/share/openvswitch/vswitch.ovsschema
deleted file mode 100644
@@ -1,2 +0,0 @@
-usr/share/openvswitch/scripts/ifupdown.sh etc/network/if-post-down.d/openvswitch
-usr/share/openvswitch/scripts/ifupdown.sh etc/network/if-pre-up.d/openvswitch
deleted file mode 100644
@@ -1,16 +0,0 @@
-/var/log/openvswitch/*.log {
- daily
- compress
- sharedscripts
- create 640 root adm
- missingok
- rotate 30
- postrotate
- # Tell Open vSwitch daemons to reopen their log files
- if [ -d /var/run/openvswitch ]; then
- for ctl in /var/run/openvswitch/*.ctl; do
- ovs-appctl -t "$ctl" vlog/reopen 2>/dev/null || :
- done
- fi
- endscript
-}
deleted file mode 100644
@@ -1,12 +0,0 @@
-ovsdb/ovsdb-server.1
-ovsdb/ovsdb-server.5
-debian/tmp/usr/share/man/man8/ovs-ctl.8
-utilities/ovs-dpctl-top.8
-utilities/ovs-dpctl.8
-utilities/ovs-kmod-ctl.8
-utilities/ovs-pcap.1
-debian/tmp/usr/share/man/man8/ovs-tcpdump.8
-debian/tmp/usr/share/man/man1/ovs-tcpundump.1
-utilities/ovs-vsctl.8
-vswitchd/ovs-vswitchd.8
-vswitchd/ovs-vswitchd.conf.db.5
deleted file mode 100755
@@ -1,60 +0,0 @@
-#!/bin/sh
-# postinst script for openvswitch-switch
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postinst> `configure' <most-recently-configured-version>
-# * <old-postinst> `abort-upgrade' <new version>
-# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
-# <new-version>
-# * <postinst> `abort-remove'
-# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-# <failed-install-package> <version> `removing'
-# <conflicting-package> <version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
- configure)
- DEFAULT=/etc/default/openvswitch-switch
- TEMPLATE=/usr/share/openvswitch/switch/default.template
- if ! test -e $DEFAULT; then
- cp $TEMPLATE $DEFAULT
- fi
- # Certain versions of upstream Ubuntu's openvswitch packages (which
- # are forks) may install upstart files which are incompatible
- # with the packages generated from this repo. Remove them.
- if [ -e "/etc/init/openvswitch-switch.conf" ]; then
- rm /etc/init/openvswitch-switch.conf
- fi
- if [ -e "/etc/init/openvswitch-force-reload-kmod.conf" ]; then
- rm /etc/init/openvswitch-force-reload-kmod.conf
- fi
- ;;
-
- abort-upgrade|abort-remove|abort-deconfigure)
- ;;
-
- *)
- echo "postinst called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-# Do not fail package installation just because the kernel module
-# is not available.
-OVS_MISSING_KMOD_OK=yes
-export OVS_MISSING_KMOD_OK
-
-# force-reload-kmod during upgrade. If a user wants to override this,
-# they can set the variable OVS_FORCE_RELOAD_KMOD=no while installing.
-[ -z "${OVS_FORCE_RELOAD_KMOD}" ] && OVS_FORCE_RELOAD_KMOD=yes || true
-export OVS_FORCE_RELOAD_KMOD
-
-#DEBHELPER#
-
-exit 0
deleted file mode 100755
@@ -1,48 +0,0 @@
-#!/bin/sh
-# postrm script for openvswitch-switch
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postrm> `remove'
-# * <postrm> `purge'
-# * <old-postrm> `upgrade' <new-version>
-# * <new-postrm> `failed-upgrade' <old-version>
-# * <new-postrm> `abort-install'
-# * <new-postrm> `abort-install' <old-version>
-# * <new-postrm> `abort-upgrade' <old-version>
-# * <disappearer's-postrm> `disappear' <overwriter>
-# <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
- purge)
- rm -f /etc/openvswitch/conf.db
- rm -f /etc/openvswitch/.conf.db.~lock~
- rm -f /etc/default/openvswitch-switch
- rm -f /var/log/openvswitch/ovs-vswitchd.log* || true
- rm -f /var/log/openvswitch/ovsdb-server.log* || true
- rm -f /etc/openvswitch/system-id.conf
- ;;
-
- remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
- ;;
-
- *)
- echo "postrm called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
-
-
deleted file mode 100644
@@ -1,8 +0,0 @@
-# This is a POSIX shell fragment -*- sh -*-
-
-# FORCE_COREFILES: If 'yes' then core files will be enabled.
-# FORCE_COREFILES=yes
-
-# OVS_CTL_OPTS: Extra options to pass to ovs-ctl. This is, for example,
-# a suitable place to specify --ovs-vswitchd-wrapper=valgrind.
-# OVS_CTL_OPTS=
deleted file mode 100644
@@ -1 +0,0 @@
-usr/share/pyshared/ovstest/
deleted file mode 100644
@@ -1,3 +0,0 @@
-usr/bin/ovs-l3ping
-usr/bin/ovs-test
-usr/share/openvswitch/python/ovstest usr/lib/python3.7/dist-packages/
deleted file mode 100644
@@ -1 +0,0 @@
-debian/tmp/usr/share/man/man8/ovs-l3ping.8
deleted file mode 100644
@@ -1,12 +0,0 @@
-README.Debian for openvswitch-testcontroller
---------------------------------------------
-
-The controller in this package enables OpenFlow switches that connect
-to it to act as MAC-learning Ethernet switches. It can be used for
-initial testing of OpenFlow networks. It is not a necessary or
-desirable part of a production OpenFlow deployment.
-
-To (re)configure the controller, edit /etc/default/openvswitch-testcontroller
-and run "/etc/init.d/openvswitch-testcontroller restart".
-
- -- Ben Pfaff <pfaffben@debian.org>, Thu, 14 Aug 2014 10:49:34 -0700
deleted file mode 100644
@@ -1,29 +0,0 @@
-# This is a POSIX shell fragment -*- sh -*-
-
-# LISTEN: What OpenFlow connection methods should the controller listen on?
-#
-# This is a space-delimited list of connection methods:
-#
-# * "pssl:[PORT]": Listen for SSL connections on the specified PORT
-# (default: 6653). The private key, certificate, and CA certificate
-# must be specified below.
-#
-# * "ptcp:[PORT]": Listen for TCP connections on the specified PORT
-# (default: 6653). Not recommended for security reasons.
-#
-LISTEN="pssl:"
-
-# PRIVKEY: Name of file containing controller's private key.
-# Required if SSL enabled.
-PRIVKEY=/etc/openvswitch-testcontroller/privkey.pem
-
-# CERT: Name of file containing certificate for private key.
-# Required if SSL enabled.
-CERT=/etc/openvswitch-testcontroller/cert.pem
-
-# CACERT: Name of file containing switch CA certificate.
-# Required if SSL enabled.
-CACERT=/etc/openvswitch-testcontroller/cacert.pem
-
-# Additional options to pass to ovs-testcontroller, e.g. "--hub"
-DAEMON_OPTS=""
deleted file mode 100644
@@ -1 +0,0 @@
-etc/openvswitch-testcontroller
deleted file mode 100755
@@ -1,278 +0,0 @@
-#!/bin/sh
-#
-# Copyright (c) 2011, 2014 Nicira, Inc.
-# Copyright (c) 2007, 2009 Javier Fernandez-Sanguino <jfs@debian.org>
-#
-# This is free software; you may redistribute it and/or modify
-# it under the terms of the GNU General Public License as
-# published by the Free Software Foundation; either version 2,
-# or (at your option) any later version.
-#
-# This is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License with
-# the Debian operating system, in /usr/share/common-licenses/GPL; if
-# not, write to the Free Software Foundation, Inc., 59 Temple Place,
-# Suite 330, Boston, MA 02111-1307 USA
-#
-### BEGIN INIT INFO
-# Provides: openvswitch-testcontroller
-# Required-Start: $network $local_fs $remote_fs
-# Required-Stop: $remote_fs
-# Should-Start: $named
-# Should-Stop:
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Simple OpenFlow controller for testing
-# Description: This controller enables OpenFlow switches that connect to
-# it to act as MAC-learning Ethernet switches.
-### END INIT INFO
-
-PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
-
-DAEMON=/usr/bin/ovs-testcontroller # Introduce the server's location here
-NAME=ovs-testcontroller # Introduce the short server's name here
-DESC=ovs-testcontroller # Introduce a short description here
-LOGDIR=/var/log/openvswitch # Log directory to use
-
-PIDFILE=/var/run/openvswitch/$NAME.pid
-
-test -x $DAEMON || exit 0
-
-. /lib/lsb/init-functions
-
-# Default options, these can be overriden by the information
-# at /etc/default/openvswitch-testcontroller
-DAEMON_OPTS="" # Additional options given to the server
-
-DODTIME=10 # Time to wait for the server to die, in seconds
- # If this value is set too low you might not
- # let some servers to die gracefully and
- # 'restart' will not work
-
-LOGFILE=$LOGDIR/$NAME.log # Server logfile
-#DAEMONUSER= # User to run the daemons as. If this value
- # is set start-stop-daemon will chuid the server
-
-# Include defaults if available
-default=/etc/default/openvswitch-testcontroller
-if [ -f $default ] ; then
- . $default
-fi
-
-# Check that the user exists (if we set a user)
-# Does the user exist?
-if [ -n "$DAEMONUSER" ] ; then
- if getent passwd | grep -q "^$DAEMONUSER:"; then
- # Obtain the uid and gid
- DAEMONUID=`getent passwd |grep "^$DAEMONUSER:" | awk -F : '{print $3}'`
- DAEMONGID=`getent passwd |grep "^$DAEMONUSER:" | awk -F : '{print $4}'`
- else
- log_failure_msg "The user $DAEMONUSER, required to run $NAME does not exist."
- exit 1
- fi
-fi
-
-
-set -e
-
-running_pid() {
-# Check if a given process pid's cmdline matches a given name
- pid=$1
- name=$2
- [ -z "$pid" ] && return 1
- [ ! -d /proc/$pid ] && return 1
- cmd=`cat /proc/$pid/cmdline | tr "\000" "\n"|head -n 1 |cut -d : -f 1`
- # Is this the expected server
- [ "$cmd" != "$name" ] && return 1
- return 0
-}
-
-running() {
-# Check if the process is running looking at /proc
-# (works for all users)
-
- # No pidfile, probably no daemon present
- [ ! -f "$PIDFILE" ] && return 1
- pid=`cat $PIDFILE`
- running_pid $pid $DAEMON || return 1
- return 0
-}
-
-start_server() {
- if [ -z "$LISTEN" ]; then
- echo "$default: No connection methods configured, controller disabled" >&2
- exit 0
- fi
-
- if [ ! -d /var/run/openvswitch ]; then
- install -d -m 755 -o root -g root /var/run/openvswitch
- fi
-
- SSL_OPTS=
- case $LISTEN in
- *ssl*)
- : ${PRIVKEY:=/etc/openvswitch-testcontroller/privkey.pem}
- : ${CERT:=/etc/openvswitch-testcontroller/cert.pem}
- : ${CACERT:=/etc/openvswitch-testcontroller/cacert.pem}
- if test ! -e "$PRIVKEY" || test ! -e "$CERT" ||
- test ! -e "$CACERT"; then
- if test ! -e "$PRIVKEY"; then
- echo "$PRIVKEY: private key missing" >&2
- fi
- if test ! -e "$CERT"; then
- echo "$CERT: certificate for private key missing" >&2
- fi
- if test ! -e "$CACERT"; then
- echo "$CACERT: CA certificate missing" >&2
- fi
- exit 1
- fi
- SSL_OPTS="--private-key=$PRIVKEY --certificate=$CERT --ca-cert=$CACERT"
- ;;
- esac
-
-# Start the process using the wrapper
- if [ -z "$DAEMONUSER" ] ; then
- start-stop-daemon --start --pidfile $PIDFILE \
- --exec $DAEMON -- --detach --pidfile=$PIDFILE \
- $LISTEN $DAEMON_OPTS $SSL_OPTS
- errcode=$?
- else
-# if we are using a daemonuser then change the user id
- start-stop-daemon --start --quiet --pidfile $PIDFILE \
- --chuid $DAEMONUSER --exec $DAEMON -- \
- --detach --pidfile=$PIDFILE $LISTEN $DAEMON_OPTS \
- $SSL_OPTS
- errcode=$?
- fi
- return $errcode
-}
-
-stop_server() {
-# Stop the process using the wrapper
- if [ -z "$DAEMONUSER" ] ; then
- start-stop-daemon --stop --quiet --pidfile $PIDFILE \
- --exec $DAEMON
- errcode=$?
- else
-# if we are using a daemonuser then look for process that match
- start-stop-daemon --stop --quiet --pidfile $PIDFILE \
- --user $DAEMONUSER --exec $DAEMON
- errcode=$?
- fi
-
- return $errcode
-}
-
-reload_server() {
- [ ! -f "$PIDFILE" ] && return 1
- pid=`cat $PIDFILE` # This is the daemon's pid
- # Send a SIGHUP
- kill -1 $pid
- return $?
-}
-
-force_stop() {
-# Force the process to die killing it manually
- [ ! -e "$PIDFILE" ] && return
- if running ; then
- kill -15 $pid
- # Is it really dead?
- sleep "$DODTIME"
- if running ; then
- kill -9 $pid
- sleep "$DODTIME"
- if running ; then
- echo "Cannot kill $NAME (pid=$pid)!"
- exit 1
- fi
- fi
- fi
- rm -f $PIDFILE
-}
-
-
-case "$1" in
- start)
- log_daemon_msg "Starting $DESC " "$NAME"
- # Check if it's running first
- if running ; then
- log_progress_msg "apparently already running"
- log_end_msg 0
- exit 0
- fi
- if start_server && running ; then
- # It's ok, the server started and is running
- log_end_msg 0
- else
- # Either we could not start it or it is not running
- # after we did
- # NOTE: Some servers might die some time after they start,
- # this code does not try to detect this and might give
- # a false positive (use 'status' for that)
- log_end_msg 1
- fi
- ;;
- stop)
- log_daemon_msg "Stopping $DESC" "$NAME"
- if running ; then
- # Only stop the server if we see it running
- stop_server
- log_end_msg $?
- else
- # If it's not running don't do anything
- log_progress_msg "apparently not running"
- log_end_msg 0
- exit 0
- fi
- ;;
- force-stop)
- # First try to stop gracefully the program
- $0 stop
- if running; then
- # If it's still running try to kill it more forcefully
- log_daemon_msg "Stopping (force) $DESC" "$NAME"
- force_stop
- log_end_msg $?
- fi
- ;;
- restart|force-reload)
- log_daemon_msg "Restarting $DESC" "$NAME"
- if running; then
- stop_server
- # Wait some sensible amount, some server need this.
- [ -n "$DODTIME" ] && sleep $DODTIME
- fi
- start_server
- running
- log_end_msg $?
- ;;
- status)
-
- log_daemon_msg "Checking status of $DESC" "$NAME"
- if running ; then
- log_progress_msg "running"
- log_end_msg 0
- else
- log_progress_msg "apparently not running"
- log_end_msg 1
- exit 1
- fi
- ;;
- # Use this if the daemon cannot reload
- reload)
- log_warning_msg "Reloading $NAME daemon: not implemented, as the daemon"
- log_warning_msg "cannot re-read the config file (use restart)."
- ;;
- *)
- N=/etc/init.d/openvswitch-testcontroller
- echo "Usage: $N {start|stop|force-stop|restart|force-reload|status}" >&2
- exit 1
- ;;
-esac
-
-exit 0
deleted file mode 100644
@@ -1 +0,0 @@
-usr/bin/ovs-testcontroller
deleted file mode 100644
@@ -1 +0,0 @@
-utilities/ovs-testcontroller.8
deleted file mode 100755
@@ -1,52 +0,0 @@
-#!/bin/sh
-# postinst script for openvswitch-testcontroller
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postinst> `configure' <most-recently-configured-version>
-# * <old-postinst> `abort-upgrade' <new version>
-# * <conflictor's-postinst> `abort-remove' `in-favour' <package>
-# <new-version>
-# * <postinst> `abort-remove'
-# * <deconfigured's-postinst> `abort-deconfigure' `in-favour'
-# <failed-install-package> <version> `removing'
-# <conflicting-package> <version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
- configure)
- cd /etc/openvswitch-testcontroller
- if ! test -e cacert.pem; then
- ln -s /var/lib/openvswitch/pki/switchca/cacert.pem cacert.pem
- fi
- if ! test -e privkey.pem || ! test -e cert.pem; then
- oldumask=$(umask)
- umask 077
- ovs-pki req+sign tmp controller >/dev/null
- mv tmp-privkey.pem privkey.pem
- mv tmp-cert.pem cert.pem
- mv tmp-req.pem req.pem
- chmod go+r cert.pem req.pem
- umask $oldumask
- fi
- ;;
-
- abort-upgrade|abort-remove|abort-deconfigure)
- ;;
-
- *)
- echo "postinst called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-#DEBHELPER#
-
-exit 0
-
-
deleted file mode 100755
@@ -1,44 +0,0 @@
-#!/bin/sh
-# postrm script for openvswitch-testcontroller
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-# * <postrm> `remove'
-# * <postrm> `purge'
-# * <old-postrm> `upgrade' <new-version>
-# * <new-postrm> `failed-upgrade' <old-version>
-# * <new-postrm> `abort-install'
-# * <new-postrm> `abort-install' <old-version>
-# * <new-postrm> `abort-upgrade' <old-version>
-# * <disappearer's-postrm> `disappear' <overwriter>
-# <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
- purge)
- if cd /etc/openvswitch-testcontroller; then
- rm -f cacert.pem cert.pem privkey.pem req.pem
- rm -f tmp-privkey.pem tmp-cert.pem tmp-req.pem
- fi
- ;;
-
- remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
- ;;
-
- *)
- echo "postrm called with unknown argument \`$1'" >&2
- exit 1
- ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0
deleted file mode 100644
@@ -1,4 +0,0 @@
-# This is a POSIX shell fragment -*- sh -*-
-
-# ENABLE_OVS_VTEP: Whether to start ovs-vtep.
-ENABLE_OVS_VTEP="false"
deleted file mode 100644
@@ -1 +0,0 @@
-/usr/share/openvswitch
deleted file mode 100644
@@ -1,78 +0,0 @@
-#!/bin/sh
-
-### BEGIN INIT INFO
-# Provides: openvswitch-vtep
-# Required-Start: $network $named $remote_fs $syslog
-# Required-Stop: $remote_fs
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: Open vSwitch VTEP emulator
-# Description: Initializes the Open vSwitch VTEP emulator
-### END INIT INFO
-
-
-# Include defaults if available
-default=/etc/default/openvswitch-vtep
-if [ -f $default ] ; then
- . $default
-fi
-
-start () {
- if [ "$ENABLE_OVS_VTEP" = "false" ]; then
- exit 0
- fi
-
- update-rc.d -f openvswitch-switch remove >/dev/null 2>&1
- /etc/init.d/openvswitch-switch stop
-
- mkdir -p "/var/run/openvswitch"
-
- if [ ! -e "/etc/openvswitch/conf.db" ]; then
- ovsdb-tool create /etc/openvswitch/conf.db /usr/share/openvswitch/vswitch.ovsschema
- fi
-
- if [ ! -e "/etc/openvswitch/vtep.db" ]; then
- ovsdb-tool create /etc/openvswitch/vtep.db /usr/share/openvswitch/vtep.ovsschema
- fi
-
- if [ ! -e "/etc/openvswitch/ovsclient-cert.pem" ]; then
- export RANDFILE="/root/.rnd"
- cd /etc/openvswitch && ovs-pki req ovsclient && ovs-pki self-sign ovsclient
- fi
-
- ovsdb-server --pidfile --detach --log-file --remote \
- punix:/var/run/openvswitch/db.sock \
- --remote=db:hardware_vtep,Global,managers \
- --private-key=/etc/openvswitch/ovsclient-privkey.pem \
- --certificate=/etc/openvswitch/ovsclient-cert.pem \
- --bootstrap-ca-cert=/etc/openvswitch/vswitchd.cacert \
- /etc/openvswitch/conf.db /etc/openvswitch/vtep.db
-
- modprobe openvswitch
-
- ovs-vswitchd --pidfile --detach --log-file \
- unix:/var/run/openvswitch/db.sock
-}
-
-stop () {
- /etc/init.d/openvswitch-switch stop
-}
-
-case $1 in
- start)
- start
- ;;
- stop)
- stop
- ;;
- restart|force-reload)
- stop
- start
- ;;
- *)
- echo "Usage: $0 {start|stop|restart|force-reload}" >&2
- exit 1
- ;;
-esac
-
-exit 0
deleted file mode 100644
@@ -1,3 +0,0 @@
-usr/share/openvswitch/scripts/ovs-vtep
-usr/share/openvswitch/vtep.ovsschema
-usr/bin/vtep-ctl
deleted file mode 100644
@@ -1 +0,0 @@
-vtep/vtep-ctl.8
deleted file mode 100644
@@ -1,2 +0,0 @@
-usr/share/pyshared/ovs/
-usr/share/pyshared/ovs/db/
deleted file mode 100644
@@ -1 +0,0 @@
-usr/share/openvswitch/python/ovs usr/lib/python3.7/dist-packages/
deleted file mode 100755
@@ -1,94 +0,0 @@
-#!/usr/bin/make -f
-# -*- makefile -*-
-# Sample debian/rules that uses debhelper.
-#
-# This file was originally written by Joey Hess and Craig Small.
-# As a special exception, when this file is copied by dh-make into a
-# dh-make output file, you may use that output file without restriction.
-# This special exception was added by Craig Small in version 0.37 of dh-make.
-#
-# Modified to make a template file for a multi-binary package with separated
-# build-arch and build-indep targets by Bill Allombert 2001
-#export DH_VERBOSE=1
-
-PACKAGE=openvswitch
-PACKAGE_DKMS=openvswitch-datapath-dkms
-include /usr/share/dpkg/pkg-info.mk
-
-ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
-PARALLEL = -j$(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
-else
-PARALLEL =
-endif
-
-%:
- dh $@ --with autoreconf,python3 --parallel
-
-# use --as-needed only if supported by dh-autoreconf (to simplify backporting)
-DH_AS_NEEDED=$(shell dpkg --compare-versions $$(dpkg --status dh-autoreconf | grep Version | cut -d' ' -f2) ge 6 && echo --as-needed)
-override_dh_autoreconf:
- dh_autoreconf $(DH_AS_NEEDED)
-
-override_dh_auto_configure:
- dh_auto_configure -- --enable-ssl --enable-shared $(DATAPATH_CONFIGURE_OPTS) $(EXTRA_CONFIGURE_OPTS)
-
-override_dh_auto_test:
-ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
- if $(MAKE) check TESTSUITEFLAGS='$(PARALLEL)' RECHECK=yes; then :; \
- else \
- cat tests/testsuite.log; \
- exit 1; \
- fi
-endif
-
-override_dh_auto_build:
- dh_auto_build -- dist distdir=openvswitch
-
-override_dh_auto_clean:
- rm -f python/ovs/*.pyc python/ovs/db/*.pyc
- dh_auto_clean
-
-override_dh_install-arch:
- dh_install
- # openvswitch-switch
- cp debian/openvswitch-switch.template debian/openvswitch-switch/usr/share/openvswitch/switch/default.template
-
-override_dh_install-indep:
- dh_install
-
- # openvswitch-datapath-source
- cp debian/rules.modules debian/openvswitch-datapath-source/usr/src/modules/openvswitch-datapath/debian/rules
- chmod 755 debian/openvswitch-datapath-source/usr/src/modules/openvswitch-datapath/debian/rules
- cd debian/openvswitch-datapath-source/usr/src && tar -c modules | bzip2 -9 > openvswitch-datapath.tar.bz2 && rm -rf modules
-
- # openvswitch-datapath-dkms
- # setup the dirs
- dh_installdirs -p$(PACKAGE_DKMS) usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM)
-
- # copy the source
- cd debian/$(PACKAGE_DKMS)/usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM) && tar xvzf $(CURDIR)/openvswitch.tar.gz && mv openvswitch/* openvswitch/.[a-z]* . && rmdir openvswitch
-
- # check we can get kernel module names
- $(MAKE) -C datapath print-build-modules
-
- # Prepare dkms.conf from the dkms.conf.in template
- sed "s/__VERSION__/$(DEB_VERSION_UPSTREAM)/g; s/__MODULES__/$(shell $(MAKE) -C datapath print-build-modules | grep -v make)/" debian/dkms.conf.in > debian/$(PACKAGE_DKMS)/usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM)/dkms.conf
-
- # We don't need the debian folder in there, just upstream sources...
- rm -rf debian/$(PACKAGE_DKMS)/usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM)/debian
- # We don't need the rhel stuff in there either
- rm -rf debian/$(PACKAGE_DKMS)/usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM)/rhel
- # And we should also clean useless license files, which are already
- # described in our debian/copyright anyway.
- rm -f debian/$(PACKAGE_DKMS)/usr/src/$(PACKAGE)-$(DEB_VERSION_UPSTREAM)/xenserver/LICENSE
-
-override_dh_installinit:
- dh_installinit -R
-
-override_dh_strip:
- dh_strip --dbg-package=openvswitch-dbg
-
-override_dh_usrlocal:
-
-override_dh_installman:
- dh_installman --language=C
deleted file mode 100755
@@ -1,39 +0,0 @@
-#! /usr/bin/make -f
-
-PACKAGE=openvswitch-datapath-module
-MA_DIR ?= /usr/share/modass
--include $(MA_DIR)/include/generic.make
--include $(MA_DIR)/include/common-rules.make
-
-DATAPATH_CONFIGURE_OPTS =
-
-kdist_clean:
- dh_testdir
- dh_testroot
- dh_clean
- rm -rf openvswitch
-
-.PHONY: kdist_config
-kdist_config: prep-deb-files
-
-.PHONY: binary-modules
-binary-modules: DSTDIR = $(CURDIR)/debian/$(PKGNAME)/lib/modules/$(KVERS)/updates
-binary-modules: prep-deb-files
- dh_testdir
- dh_testroot
- dh_clean -k
- tar xzf openvswitch.tar.gz
- cd openvswitch && ./configure --with-linux=$(KSRC) $(DATAPATH_CONFIGURE_OPTS)
- cd openvswitch && $(MAKE) -C datapath/linux
- install -d -m755 $(DSTDIR)
- install -m644 openvswitch/datapath/linux/*.ko $(DSTDIR)/
- dh_installmodules
- dh_installdocs
- dh_installchangelogs
- dh_compress
- dh_fixperms
- dh_installdeb
- dh_gencontrol
- dh_md5sums
- dh_builddeb --destdir=$(DEB_DESTDIR)
-
deleted file mode 100644
@@ -1 +0,0 @@
-3.0 (quilt)
The packaging source in the OVS repository has drifted away from what is currently in Debian and Ubuntu. This state is problematic because from time to time someone tries to build packages from the upstream OVS debian package source and then expect that package to work with up-/down-grades from-/to/ distro versions. To support the on-going work to remove the out of tree OVS kernel driver from the repository [0], an update to the debian packaging is also required. On the back of the discussion in [0] we agreed that replacing the current version with what Debian and Ubuntu is currently converging on would be preferable. This commit is a first in a series to update the upstream OVS debian packaging source to be up to date with what is currently in Debian and Ubuntu. 0: https://mail.openvswitch.org/pipermail/ovs-dev/2022-June/394634.html Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com> --- .github/workflows/build-and-test.yml | 3 - debian/.gitignore | 27 - debian/automake.mk | 82 +- debian/compat | 1 - debian/control | 266 ------- debian/control.modules.in | 20 - debian/copyright.in | 711 ------------------ debian/dirs | 2 - debian/dkms.conf.in | 11 - debian/ifupdown.sh | 107 --- debian/libopenvswitch-dev.install | 19 - debian/libopenvswitch.install | 5 - debian/openvswitch-common.dirs | 1 - debian/openvswitch-common.docs | 0 debian/openvswitch-common.install | 11 - debian/openvswitch-common.manpages | 7 - debian/openvswitch-datapath-dkms.postinst | 21 - debian/openvswitch-datapath-dkms.prerm | 15 - ...atapath-module-_KVERS_.postinst.modules.in | 27 - .../openvswitch-datapath-source.README.Debian | 31 - debian/openvswitch-datapath-source.copyright | 15 - debian/openvswitch-datapath-source.dirs | 1 - debian/openvswitch-datapath-source.install | 5 - debian/openvswitch-ipsec.dirs | 1 - debian/openvswitch-ipsec.init | 181 ----- debian/openvswitch-ipsec.install | 1 - debian/openvswitch-pki.dirs | 1 - debian/openvswitch-pki.postinst | 41 - debian/openvswitch-pki.postrm | 43 -- debian/openvswitch-switch.README.Debian | 316 -------- debian/openvswitch-switch.dirs | 2 - debian/openvswitch-switch.init | 147 ---- debian/openvswitch-switch.install | 17 - debian/openvswitch-switch.links | 2 - debian/openvswitch-switch.logrotate | 16 - debian/openvswitch-switch.manpages | 12 - debian/openvswitch-switch.postinst | 60 -- debian/openvswitch-switch.postrm | 48 -- debian/openvswitch-switch.template | 8 - debian/openvswitch-test.dirs | 1 - debian/openvswitch-test.install | 3 - debian/openvswitch-test.manpages | 1 - .../openvswitch-testcontroller.README.Debian | 12 - debian/openvswitch-testcontroller.default | 29 - debian/openvswitch-testcontroller.dirs | 1 - debian/openvswitch-testcontroller.init | 278 ------- debian/openvswitch-testcontroller.install | 1 - debian/openvswitch-testcontroller.manpages | 1 - debian/openvswitch-testcontroller.postinst | 52 -- debian/openvswitch-testcontroller.postrm | 44 -- debian/openvswitch-vtep.default | 4 - debian/openvswitch-vtep.dirs | 1 - debian/openvswitch-vtep.init | 78 -- debian/openvswitch-vtep.install | 3 - debian/openvswitch-vtep.manpages | 1 - debian/python3-openvswitch.dirs | 2 - debian/python3-openvswitch.install | 1 - debian/rules | 94 --- debian/rules.modules | 39 - debian/source/format | 1 - 60 files changed, 1 insertion(+), 2930 deletions(-) delete mode 100644 debian/.gitignore delete mode 100644 debian/compat delete mode 100644 debian/control delete mode 100644 debian/control.modules.in delete mode 100644 debian/copyright.in delete mode 100644 debian/dirs delete mode 100644 debian/dkms.conf.in delete mode 100755 debian/ifupdown.sh delete mode 100644 debian/libopenvswitch-dev.install delete mode 100644 debian/libopenvswitch.install delete mode 100644 debian/openvswitch-common.dirs delete mode 100644 debian/openvswitch-common.docs delete mode 100644 debian/openvswitch-common.install delete mode 100644 debian/openvswitch-common.manpages delete mode 100644 debian/openvswitch-datapath-dkms.postinst delete mode 100644 debian/openvswitch-datapath-dkms.prerm delete mode 100755 debian/openvswitch-datapath-module-_KVERS_.postinst.modules.in delete mode 100644 debian/openvswitch-datapath-source.README.Debian delete mode 100644 debian/openvswitch-datapath-source.copyright delete mode 100644 debian/openvswitch-datapath-source.dirs delete mode 100644 debian/openvswitch-datapath-source.install delete mode 100644 debian/openvswitch-ipsec.dirs delete mode 100644 debian/openvswitch-ipsec.init delete mode 100644 debian/openvswitch-ipsec.install delete mode 100644 debian/openvswitch-pki.dirs delete mode 100755 debian/openvswitch-pki.postinst delete mode 100755 debian/openvswitch-pki.postrm delete mode 100644 debian/openvswitch-switch.README.Debian delete mode 100644 debian/openvswitch-switch.dirs delete mode 100755 debian/openvswitch-switch.init delete mode 100644 debian/openvswitch-switch.install delete mode 100644 debian/openvswitch-switch.links delete mode 100644 debian/openvswitch-switch.logrotate delete mode 100644 debian/openvswitch-switch.manpages delete mode 100755 debian/openvswitch-switch.postinst delete mode 100755 debian/openvswitch-switch.postrm delete mode 100644 debian/openvswitch-switch.template delete mode 100644 debian/openvswitch-test.dirs delete mode 100644 debian/openvswitch-test.install delete mode 100644 debian/openvswitch-test.manpages delete mode 100644 debian/openvswitch-testcontroller.README.Debian delete mode 100644 debian/openvswitch-testcontroller.default delete mode 100644 debian/openvswitch-testcontroller.dirs delete mode 100755 debian/openvswitch-testcontroller.init delete mode 100644 debian/openvswitch-testcontroller.install delete mode 100644 debian/openvswitch-testcontroller.manpages delete mode 100755 debian/openvswitch-testcontroller.postinst delete mode 100755 debian/openvswitch-testcontroller.postrm delete mode 100644 debian/openvswitch-vtep.default delete mode 100644 debian/openvswitch-vtep.dirs delete mode 100644 debian/openvswitch-vtep.init delete mode 100644 debian/openvswitch-vtep.install delete mode 100644 debian/openvswitch-vtep.manpages delete mode 100644 debian/python3-openvswitch.dirs delete mode 100644 debian/python3-openvswitch.install delete mode 100755 debian/rules delete mode 100755 debian/rules.modules delete mode 100644 debian/source/format