Skip to content
main
Switch branches/tags
Code

Latest commit

Add the debug command in case lflow conjunction ids mapping needs to be
checked during trouble shooting. Also use the dump function in test
cases.

An example output:

$ ovn-appctl -t ovn-controller debug/dump-lflow-conj-ids
Conjunction IDs allocations:
lflow: 4445d4a0-3ca3-4385-a677-c0199d65ea4d, start: 1145427104, n: 1
lflow: 711b0d24-52bc-41a4-9af2-5cdea2d5167d, start: 1897598244, n: 1
lflow: 6e712ecb-f863-4a0c-a7c4-367d59914d35, start: 1852911307, n: 1
----
Total 3 IDs used.

Suggested-by: Numan Siddique <numans@ovn.org>
Signed-off-by: Han Zhou <hzhou@ovn.org>
Acked-by: Numan Siddique <numans@ovn.org>
fd8b017

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
.ci
 
 
 
 
 
 
 
 
ic
 
 
 
 
lib
 
 
m4
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

OVN

What is OVN?

OVN (Open Virtual Network) is a series of daemons that translates virtual network configuration into OpenFlow, and installs them into Open vSwitch. It is licensed under the open source Apache 2 license.

OVN provides a higher-layer abstraction then Open vSwitch, working with logical routers and logical switches, rather than flows. OVN is intended to be used by cloud management software (CMS). For details about the architecture of OVN, see the ovn-architecture manpage. Some high-level features offered by OVN include:

  • Distributed virtual routers
  • Distributed logical switches
  • Access Control Lists
  • DHCP
  • DNS server

Like Open vSwitch, OVN is written in platform-independent C. OVN runs entirely in userspace and therefore requires no kernel modules to be installed.

Until recently, OVN code lived within the Open vSwitch codebase. OVN has recently been split into its own repo. There is much to do to complete this split entirely. See the TODO_SPLIT.rst file for a list of known tasks that need to be completed.

What's here?

The main components of this distribution are:

  • ovn-northd, a centralized daemon that translates northbound configuration from a CMS into logical flows for the southbound database.
  • ovn-controller, a daemon that runs on every hypervisor in the cluster. It translates the logical flows in the southbound database into OpenFlow for Open vSwitch. It also handles certain traffic, such as DHCP and DNS.
  • ovn-nbctl, a tool for interfacing with the northbound database.
  • ovn-sbctl, a tool for interfacing with the southbound database.
  • ovn-trace, a debugging utility that allows for tracing of packets through the logical network.
  • Scripts and specs for building RPMs.

What other documentation is available?

To install OVN on a regular Linux or FreeBSD host, please read the installation guide. For specifics around installation on a specific platform, refer to one of the other installation guides

For answers to common questions, refer to the FAQ.

To learn about some advanced features of the Open vSwitch software switch, read the tutorial.

Each OVN program is accompanied by a manpage. Many of the manpages are customized to your configuration as part of the build process, so we recommend building OVN before reading the manpages.

License

The following is a summary of the licensing of files in this distribution. As mentioned, OVN is licensed under the open source Apache 2 license. Some files may be marked specifically with a different license, in which case that license applies to the file in question.

File build-aux/cccl is licensed under the GNU General Public License, version 2.

Files under the xenserver directory are licensed on a file-by-file basis. Refer to each file for details.

Contact

bugs@openvswitch.org