ovn-nbd(8) connects to the OVN Northbound Database above it
- and the OVN Database below it. It translates the logical network
- configuration in terms of conventional network concepts, taken from the
- OVN Northbound Database, into logical datapath flows in the OVN Database
- below it.
+ and the OVN Southbound Database below it. It translates the
+ logical network configuration in terms of conventional network
+ concepts, taken from the OVN Northbound Database, into logical
+ datapath flows in the OVN Southbound Database below it.
- The OVN Database is the center of the system. Its clients
- are ovn-nbd(8) above it and ovn-controller(8)
- on every transport node below it.
+ The OVN Southbound Database is the center of the system.
+ Its clients are ovn-nbd(8) above it and
+ ovn-controller(8) on every transport node below it.
- The OVN Database contains three kinds of data: Physical + The OVN Southbound Database contains three kinds of data: Physical Network (PN) tables that specify how to reach hypervisor and other nodes, Logical Network (LN) tables that describe the logical network in terms of ``logical datapath flows,'' and @@ -134,9 +134,10 @@
- OVN Database performance must scale with the number of transport nodes.
- This will likely require some work on ovsdb-server(1) as
- we encounter bottlenecks. Clustering for availability may be needed.
+ OVN Southbound Database performance must scale with the number of
+ transport nodes. This will likely require some work on
+ ovsdb-server(1) as we encounter bottlenecks.
+ Clustering for availability may be needed.
ovn-controller(8) is OVN's agent on each hypervisor and
- software gateway. Northbound, it connects to the OVN Database to learn
- about OVN configuration and status and to populate the PN table and the
- Chassis column in Bindings table with the
- hypervisor's status. Southbound, it connects to
- ovs-vswitchd(8) as an OpenFlow controller, for control over
- network traffic, and to the local ovsdb-server(1) to allow
- it to monitor and control Open vSwitch configuration.
+ software gateway. Northbound, it connects to the OVN Southbound
+ Database to learn about OVN configuration and status and to
+ populate the PN table and the Chassis column in
+ Bindings table with the hypervisor's status.
+ Southbound, it connects to ovs-vswitchd(8) as an
+ OpenFlow controller, for control over network traffic, and to the
+ local ovsdb-server(1) to allow it to monitor and
+ control Open vSwitch configuration.
The steps in this example refer often to details of the OVN and OVN
- Northbound database schemas. Please see ovn(5) and
+ Northbound database schemas. Please see ovn-sb(5) and
ovn-nb(5), respectively, for the full story on these
databases.
ovn-nbd receives the OVN Northbound database update. In
- turn, it makes the corresponding updates to the OVN database, by adding
- rows to the OVN database Pipeline table to reflect the new
- port, e.g. add a flow to recognize that packets destined to the new
- port's MAC address should be delivered to it, and update the flow that
- delivers broadcast and multicast packets to include the new port. It
- also creates a record in the Bindings table and populates
- all its columns except the column that identifies the
+ ovn-nbd receives the OVN Northbound database update.
+ In turn, it makes the corresponding updates to the OVN Southbound
+ database, by adding rows to the OVN Southbound database
+ Pipeline table to reflect the new port, e.g. add a
+ flow to recognize that packets destined to the new port's MAC
+ address should be delivered to it, and update the flow that
+ delivers broadcast and multicast packets to include the new port.
+ It also creates a record in the Bindings table and
+ populates all its columns except the column that identifies the
chassis.
ovn-nbd receives the OVN Northbound update and in turn
- updates the OVN database accordingly, by removing or updating the
- rows from the OVN database Pipeline table and
- Bindings table that were related to the now-destroyed VIF.
+ updates the OVN Southbound database accordingly, by removing or
+ updating the rows from the OVN Southbound database
+ Pipeline table and Bindings table that
+ were related to the now-destroyed VIF.
ovn-nbd receives the OVN Northbound database update. In
- turn, it makes the corresponding updates to the OVN database, by adding
- rows to the OVN database's Pipeline table to reflect the new
- port and also by creating a new row in the Bindings table
- and populating all its columns except the column that identifies the
+ turn, it makes the corresponding updates to the OVN Southbound
+ database, by adding rows to the OVN Southbound database's
+ Pipeline table to reflect the new port and also by
+ creating a new row in the Bindings table and
+ populating all its columns except the column that identifies the
chassis.
ovn-nbd receives the OVN Northbound update and in turn
- updates the OVN database accordingly, by removing or updating the
- rows from the OVN database Pipeline table that were related
- to the now-destroyed CIF. It also deletes the row in the
- Bindings table for that CIF.
+ updates the OVN Southbound database accordingly, by removing or
+ updating the rows from the OVN Southbound database
+ Pipeline table that were related to the now-destroyed
+ CIF. It also deletes the row in the Bindings table
+ for that CIF.
ovn-nbd program monitors
the database contents, transforms it, and stores it into the database.
+ db="OVN_Southbound"/> database.
@@ -117,13 +117,13 @@
ovn-nbd, rather than by the CMS
- plugin as is most of this database. When a logical port is bound to a
- physical location in the OVN database
- table, ovn-nbd sets this column to true;
- otherwise, or if the port becomes unbound later, it sets it to
- false. This allows the CMS to wait for a VM's
- (or container's) networking to become active before it allows the
- VM (or container) to start.
+ plugin as is most of this database. When a logical port is bound
+ to a physical location in the OVN Southbound database table, ovn-nbd
+ sets this column to true; otherwise, or if the port
+ becomes unbound later, it sets it to false. This
+ allows the CMS to wait for a VM's (or container's) networking to
+ become active before it allows the VM (or container) to start.
- Exact syntax is TBD. One could simply use comma- or space-separated L2 - and L3 addresses in each set member, or replace this by a subset of the - general-purpose expression language used for the column in the OVN database's table. + Exact syntax is TBD. One could simply use comma- or + space-separated L2 and L3 addresses in each set member, or + replace this by a subset of the general-purpose expression + language used for the column in the OVN Southbound database's + table.
@@ -184,13 +185,15 @@inport and outport against names of logical
- ports within to implement ingress and egress ACLs,
- respectively. In logical switches connected to logical routers, the
- special port name ROUTER refers to the logical router port.
+ The packets that the ACL should match, in the same expression
+ language used for the column in the OVN Southbound database's table. Match
+ inport and outport against names of
+ logical ports within to implement ingress
+ and egress ACLs, respectively. In logical switches connected to
+ logical routers, the special port name ROUTER refers
+ to the logical router port.
This database holds logical and physical configuration and state for the Open Virtual Network (OVN) system to support virtual network abstraction. @@ -7,17 +7,18 @@
- The OVN database sits at the center of the OVN architecture. It is the one
- component that speaks both southbound directly to all the hypervisors and
- gateways, via ovn-controller, and northbound to the Cloud
- Management System, via ovn-nbd:
+ The OVN Southbound database sits at the center of the OVN
+ architecture. It is the one component that speaks both southbound
+ directly to all the hypervisors and gateways, via
+ ovn-controller, and northbound to the Cloud Management
+ System, via ovn-nbd:
- The OVN database contains three classes of data with different properties, - as described in the sections below. + The OVN Southbound database contains three classes of data with + different properties, as described in the sections below.