1 <?xml version="1.0" encoding="utf-8"?>
2 <database name="ovn-sb" title="OVN Southbound Database">
4 This database holds logical and physical configuration and state for the
5 Open Virtual Network (OVN) system to support virtual network abstraction.
6 For an introduction to OVN, please see <code>ovn-architecture</code>(7).
10 The OVN Southbound database sits at the center of the OVN
11 architecture. It is the one component that speaks both southbound
12 directly to all the hypervisors and gateways, via
13 <code>ovn-controller</code>/<code>ovn-controller-vtep</code>, and
14 northbound to the Cloud Management System, via <code>ovn-northd</code>:
17 <h2>Database Structure</h2>
20 The OVN Southbound database contains three classes of data with
21 different properties, as described in the sections below.
24 <h3>Physical Network (PN) data</h3>
27 PN tables contain information about the chassis nodes in the system. This
28 contains all the information necessary to wire the overlay, such as IP
29 addresses, supported tunnel types, and security keys.
33 The amount of PN data is small (O(n) in the number of chassis) and it
34 changes infrequently, so it can be replicated to every chassis.
38 The <ref table="Chassis"/> table comprises the PN tables.
41 <h3>Logical Network (LN) data</h3>
44 LN tables contain the topology of logical switches and routers, ACLs,
45 firewall rules, and everything needed to describe how packets traverse a
46 logical network, represented as logical datapath flows (see Logical
47 Datapath Flows, below).
51 LN data may be large (O(n) in the number of logical ports, ACL rules,
52 etc.). Thus, to improve scaling, each chassis should receive only data
53 related to logical networks in which that chassis participates. Past
54 experience shows that in the presence of large logical networks, even
55 finer-grained partitioning of data, e.g. designing logical flows so that
56 only the chassis hosting a logical port needs related flows, pays off
57 scale-wise. (This is not necessary initially but it is worth bearing in
62 The LN is a slave of the cloud management system running northbound of OVN.
63 That CMS determines the entire OVN logical configuration and therefore the
64 LN's content at any given time is a deterministic function of the CMS's
65 configuration, although that happens indirectly via the
66 <ref db="OVN_Northbound"/> database and <code>ovn-northd</code>.
70 LN data is likely to change more quickly than PN data. This is especially
71 true in a container environment where VMs are created and destroyed (and
72 therefore added to and deleted from logical switches) quickly.
76 <ref table="Logical_Flow"/> and <ref table="Multicast_Group"/> contain LN
80 <h3>Bindings data</h3>
83 Bindings data link logical and physical components. They show the current
84 placement of logical components (such as VMs and VIFs) onto chassis, and
85 map logical entities to the values that represent them in tunnel
90 Bindings change frequently, at least every time a VM powers up or down
91 or migrates, and especially quickly in a container environment. The
92 amount of data per VM (or VIF) is small.
96 Each chassis is authoritative about the VMs and VIFs that it hosts at any
97 given time and can efficiently flood that state to a central location, so
98 the consistency needs are minimal.
102 The <ref table="Port_Binding"/> and <ref table="Datapath_Binding"/> tables
103 contain binding data.
106 <h2>Common Columns</h2>
109 Some tables contain a special column named <code>external_ids</code>. This
110 column has the same form and purpose each place that it appears, so we
111 describe it here to save space later.
115 <dt><code>external_ids</code>: map of string-string pairs</dt>
117 Key-value pairs for use by the software that manages the OVN Southbound
118 database rather than by
119 <code>ovn-controller</code>/<code>ovn-controller-vtep</code>. In
120 particular, <code>ovn-northd</code> can use key-value pairs in this
121 column to relate entities in the southbound database to higher-level
122 entities (such as entities in the OVN Northbound database). Individual
123 key-value pairs in this column may be documented in some cases to aid
124 in understanding and troubleshooting, but the reader should not mistake
125 such documentation as comprehensive.
129 <table name="Chassis" title="Physical Network Hypervisor and Gateway Information">
131 Each row in this table represents a hypervisor or gateway (a chassis) in
132 the physical network (PN). Each chassis, via
133 <code>ovn-controller</code>/<code>ovn-controller-vtep</code>, adds
134 and updates its own row, and keeps a copy of the remaining rows to
135 determine how to reach other hypervisors.
139 When a chassis shuts down gracefully, it should remove its own row.
140 (This is not critical because resources hosted on the chassis are equally
141 unreachable regardless of whether the row is present.) If a chassis
142 shuts down permanently without removing its row, some kind of manual or
143 automatic cleanup is eventually needed; we can devise a process for that
148 A chassis name, taken from <ref key="system-id" table="Open_vSwitch"
149 column="external_ids" db="Open_vSwitch"/> in the Open_vSwitch
150 database's <ref table="Open_vSwitch" db="Open_vSwitch"/> table. OVN does
151 not prescribe a particular format for chassis names.
154 <group title="Encapsulation Configuration">
156 OVN uses encapsulation to transmit logical dataplane packets
160 <column name="encaps">
161 Points to supported encapsulation configurations to transmit
162 logical dataplane packets to this chassis. Each entry is a <ref
163 table="Encap"/> record that describes the configuration.
167 <group title="Gateway Configuration">
169 A <dfn>gateway</dfn> is a chassis that forwards traffic between the
170 OVN-managed part of a logical network and a physical VLAN, extending a
171 tunnel-based logical network into a physical network. Gateways are
172 typically dedicated nodes that do not host VMs and will be controlled
173 by <code>ovn-controller-vtep</code>.
176 <column name="vtep_logical_switches">
177 Stores all VTEP logical switch names connected by this gateway
178 chassis. The <ref table="Port_Binding"/> table entry with
179 <ref column="options" table="Port_Binding"/>:<code>vtep-physical-switch</code>
180 equal <ref table="Chassis"/> <ref column="name" table="Chassis"/>, and
181 <ref column="options" table="Port_Binding"/>:<code>vtep-logical-switch</code>
182 value in <ref table="Chassis"/>
183 <ref column="vtep_logical_switches" table="Chassis"/>, will be
184 associated with this <ref table="Chassis"/>.
189 <table name="Encap" title="Encapsulation Types">
191 The <ref column="encaps" table="Chassis"/> column in the <ref
192 table="Chassis"/> table refers to rows in this table to identify
193 how OVN may transmit logical dataplane packets to this chassis.
194 Each chassis, via <code>ovn-controller</code>(8) or
195 <code>ovn-controller-vtep</code>(8), adds and updates its own rows
196 and keeps a copy of the remaining rows to determine how to reach
201 The encapsulation to use to transmit packets to this chassis.
202 Hypervisors must use either <code>geneve</code> or
203 <code>stt</code>. Gateways may use <code>vxlan</code>,
204 <code>geneve</code>, or <code>stt</code>.
207 <column name="options">
208 Options for configuring the encapsulation, e.g. IPsec parameters when
209 IPsec support is introduced. No options are currently defined.
213 The IPv4 address of the encapsulation tunnel endpoint.
217 <table name="Logical_Flow" title="Logical Network Flows">
219 Each row in this table represents one logical flow.
220 <code>ovn-northd</code> populates this table with logical flows
221 that implement the L2 and L3 topologies specified in the
222 <ref db="OVN_Northbound"/> database. Each hypervisor, via
223 <code>ovn-controller</code>, translates the logical flows into
224 OpenFlow flows specific to its hypervisor and installs them into
229 Logical flows are expressed in an OVN-specific format, described here. A
230 logical datapath flow is much like an OpenFlow flow, except that the
231 flows are written in terms of logical ports and logical datapaths instead
232 of physical ports and physical datapaths. Translation between logical
233 and physical flows helps to ensure isolation between logical datapaths.
234 (The logical flow abstraction also allows the OVN centralized
235 components to do less work, since they do not have to separately
236 compute and push out physical flows to each chassis.)
240 The default action when no flow matches is to drop packets.
243 <p><em>Architectural Logical Life Cycle of a Packet</em></p>
246 This following description focuses on the life cycle of a packet through
247 a logical datapath, ignoring physical details of the implementation.
248 Please refer to <em>Architectural Physical Life Cycle of a Packet</em> in
249 <code>ovn-architecture</code>(7) for the physical information.
253 The description here is written as if OVN itself executes these steps,
254 but in fact OVN (that is, <code>ovn-controller</code>) programs Open
255 vSwitch, via OpenFlow and OVSDB, to execute them on its behalf.
259 At a high level, OVN passes each packet through the logical datapath's
260 logical ingress pipeline, which may output the packet to one or more
261 logical port or logical multicast groups. For each such logical output
262 port, OVN passes the packet through the datapath's logical egress
263 pipeline, which may either drop the packet or deliver it to the
264 destination. Between the two pipelines, outputs to logical multicast
265 groups are expanded into logical ports, so that the egress pipeline only
266 processes a single logical output port at a time. Between the two
267 pipelines is also where, when necessary, OVN encapsulates a packet in a
268 tunnel (or tunnels) to transmit to remote hypervisors.
272 In more detail, to start, OVN searches the <ref table="Logical_Flow"/>
273 table for a row with correct <ref column="logical_datapath"/>, a <ref
274 column="pipeline"/> of <code>ingress</code>, a <ref column="table_id"/>
275 of 0, and a <ref column="match"/> that is true for the packet. If none
276 is found, OVN drops the packet. If OVN finds more than one, it chooses
277 the match with the highest <ref column="priority"/>. Then OVN executes
278 each of the actions specified in the row's <ref table="actions"/> column,
279 in the order specified. Some actions, such as those to modify packet
280 headers, require no further details. The <code>next</code> and
281 <code>output</code> actions are special.
285 The <code>next</code> action causes the above process to be repeated
286 recursively, except that OVN searches for <ref column="table_id"/> of 1
287 instead of 0. Similarly, any <code>next</code> action in a row found in
288 that table would cause a further search for a <ref column="table_id"/> of
289 2, and so on. When recursive processing completes, flow control returns
290 to the action following <code>next</code>.
294 The <code>output</code> action also introduces recursion. Its effect
295 depends on the current value of the <code>outport</code> field. Suppose
296 <code>outport</code> designates a logical port. First, OVN compares
297 <code>inport</code> to <code>outport</code>; if they are equal, it treats
298 the <code>output</code> as a no-op. In the common case, where they are
299 different, the packet enters the egress pipeline. This transition to the
300 egress pipeline discards register data, e.g. <code>reg0</code> ...
301 <code>reg4</code> and connection tracking state, to achieve
302 uniform behavior regardless of whether the egress pipeline is on a
303 different hypervisor (because registers aren't preserve across
304 tunnel encapsulation).
308 To execute the egress pipeline, OVN again searches the <ref
309 table="Logical_Flow"/> table for a row with correct <ref
310 column="logical_datapath"/>, a <ref column="table_id"/> of 0, a <ref
311 column="match"/> that is true for the packet, but now looking for a <ref
312 column="pipeline"/> of <code>egress</code>. If no matching row is found,
313 the output becomes a no-op. Otherwise, OVN executes the actions for the
314 matching flow (which is chosen from multiple, if necessary, as already
319 In the <code>egress</code> pipeline, the <code>next</code> action acts as
320 already described, except that it, of course, searches for
321 <code>egress</code> flows. The <code>output</code> action, however, now
322 directly outputs the packet to the output port (which is now fixed,
323 because <code>outport</code> is read-only within the egress pipeline).
327 The description earlier assumed that <code>outport</code> referred to a
328 logical port. If it instead designates a logical multicast group, then
329 the description above still applies, with the addition of fan-out from
330 the logical multicast group to each logical port in the group. For each
331 member of the group, OVN executes the logical pipeline as described, with
332 the logical output port replaced by the group member.
335 <p><em>Pipeline Stages</em></p>
338 <code>ovn-northd</code> is responsible for populating the
339 <ref table="Logical_Flow"/> table, so the stages are an
340 implementation detail and subject to change. This section
341 describes the current logical flow table.
345 The ingress pipeline consists of the following stages:
349 Port Security (Table 0): Validates the source address, drops
350 packets with a VLAN tag, and, if configured, verifies that the
351 logical port is allowed to send with the source address.
355 L2 Destination Lookup (Table 1): Forwards known unicast
356 addresses to the appropriate logical port. Unicast packets to
357 unknown hosts are forwarded to logical ports configured with the
358 special <code>unknown</code> mac address. Broadcast, and
359 multicast are flooded to all ports in the logical switch.
364 The egress pipeline consists of the following stages:
368 ACL (Table 0): Applies any specified access control lists.
372 Port Security (Table 1): If configured, verifies that the
373 logical port is allowed to receive packets with the destination
378 <column name="logical_datapath">
379 The logical datapath to which the logical flow belongs.
382 <column name="pipeline">
384 The primary flows used for deciding on a packet's destination are the
385 <code>ingress</code> flows. The <code>egress</code> flows implement
386 ACLs. See <em>Logical Life Cycle of a Packet</em>, above, for details.
390 <column name="table_id">
391 The stage in the logical pipeline, analogous to an OpenFlow table number.
394 <column name="priority">
395 The flow's priority. Flows with numerically higher priority take
396 precedence over those with lower. If two logical datapath flows with the
397 same priority both match, then the one actually applied to the packet is
401 <column name="match">
403 A matching expression. OVN provides a superset of OpenFlow matching
404 capabilities, using a syntax similar to Boolean expressions in a
405 programming language.
409 The most important components of match expression are
410 <dfn>comparisons</dfn> between <dfn>symbols</dfn> and
411 <dfn>constants</dfn>, e.g. <code>ip4.dst == 192.168.0.1</code>,
412 <code>ip.proto == 6</code>, <code>arp.op == 1</code>, <code>eth.type ==
413 0x800</code>. The logical AND operator <code>&&</code> and
414 logical OR operator <code>||</code> can combine comparisons into a
419 Matching expressions also support parentheses for grouping, the logical
420 NOT prefix operator <code>!</code>, and literals <code>0</code> and
421 <code>1</code> to express ``false'' or ``true,'' respectively. The
422 latter is useful by itself as a catch-all expression that matches every
426 <p><em>Symbols</em></p>
429 <em>Type</em>. Symbols have <dfn>integer</dfn> or <dfn>string</dfn>
430 type. Integer symbols have a <dfn>width</dfn> in bits.
434 <em>Kinds</em>. There are three kinds of symbols:
440 <dfn>Fields</dfn>. A field symbol represents a packet header or
441 metadata field. For example, a field
442 named <code>vlan.tci</code> might represent the VLAN TCI field in a
447 A field symbol can have integer or string type. Integer fields can
448 be nominal or ordinal (see <em>Level of Measurement</em>,
455 <dfn>Subfields</dfn>. A subfield represents a subset of bits from
456 a larger field. For example, a field <code>vlan.vid</code> might
457 be defined as an alias for <code>vlan.tci[0..11]</code>. Subfields
458 are provided for syntactic convenience, because it is always
459 possible to instead refer to a subset of bits from a field
464 Only ordinal fields (see <em>Level of Measurement</em>,
465 below) may have subfields. Subfields are always ordinal.
471 <dfn>Predicates</dfn>. A predicate is shorthand for a Boolean
472 expression. Predicates may be used much like 1-bit fields. For
473 example, <code>ip4</code> might expand to <code>eth.type ==
474 0x800</code>. Predicates are provided for syntactic convenience,
475 because it is always possible to instead specify the underlying
480 A predicate whose expansion refers to any nominal field or
481 predicate (see <em>Level of Measurement</em>, below) is nominal;
482 other predicates have Boolean level of measurement.
488 <em>Level of Measurement</em>. See
489 http://en.wikipedia.org/wiki/Level_of_measurement for the statistical
490 concept on which this classification is based. There are three
497 <dfn>Ordinal</dfn>. In statistics, ordinal values can be ordered
498 on a scale. OVN considers a field (or subfield) to be ordinal if
499 its bits can be examined individually. This is true for the
500 OpenFlow fields that OpenFlow or Open vSwitch makes ``maskable.''
504 Any use of a nominal field may specify a single bit or a range of
505 bits, e.g. <code>vlan.tci[13..15]</code> refers to the PCP field
506 within the VLAN TCI, and <code>eth.dst[40]</code> refers to the
507 multicast bit in the Ethernet destination address.
511 OVN supports all the usual arithmetic relations (<code>==</code>,
512 <code>!=</code>, <code><</code>, <code><=</code>,
513 <code>></code>, and <code>>=</code>) on ordinal fields and
514 their subfields, because OVN can implement these in OpenFlow and
515 Open vSwitch as collections of bitwise tests.
521 <dfn>Nominal</dfn>. In statistics, nominal values cannot be
522 usefully compared except for equality. This is true of OpenFlow
523 port numbers, Ethernet types, and IP protocols are examples: all of
524 these are just identifiers assigned arbitrarily with no deeper
525 meaning. In OpenFlow and Open vSwitch, bits in these fields
526 generally aren't individually addressable.
530 OVN only supports arithmetic tests for equality on nominal fields,
531 because OpenFlow and Open vSwitch provide no way for a flow to
532 efficiently implement other comparisons on them. (A test for
533 inequality can be sort of built out of two flows with different
534 priorities, but OVN matching expressions always generate flows with
539 String fields are always nominal.
545 <dfn>Boolean</dfn>. A nominal field that has only two values, 0
546 and 1, is somewhat exceptional, since it is easy to support both
547 equality and inequality tests on such a field: either one can be
548 implemented as a test for 0 or 1.
552 Only predicates (see above) have a Boolean level of measurement.
556 This isn't a standard level of measurement.
562 <em>Prerequisites</em>. Any symbol can have prerequisites, which are
563 additional condition implied by the use of the symbol. For example,
564 For example, <code>icmp4.type</code> symbol might have prerequisite
565 <code>icmp4</code>, which would cause an expression <code>icmp4.type ==
566 0</code> to be interpreted as <code>icmp4.type == 0 &&
567 icmp4</code>, which would in turn expand to <code>icmp4.type == 0
568 && eth.type == 0x800 && ip4.proto == 1</code> (assuming
569 <code>icmp4</code> is a predicate defined as suggested under
570 <em>Types</em> above).
573 <p><em>Relational operators</em></p>
576 All of the standard relational operators <code>==</code>,
577 <code>!=</code>, <code><</code>, <code><=</code>,
578 <code>></code>, and <code>>=</code> are supported. Nominal
579 fields support only <code>==</code> and <code>!=</code>, and only in a
580 positive sense when outer <code>!</code> are taken into account,
581 e.g. given string field <code>inport</code>, <code>inport ==
582 "eth0"</code> and <code>!(inport != "eth0")</code> are acceptable, but
583 not <code>inport != "eth0"</code>.
587 The implementation of <code>==</code> (or <code>!=</code> when it is
588 negated), is more efficient than that of the other relational
592 <p><em>Constants</em></p>
595 Integer constants may be expressed in decimal, hexadecimal prefixed by
596 <code>0x</code>, or as dotted-quad IPv4 addresses, IPv6 addresses in
597 their standard forms, or Ethernet addresses as colon-separated hex
598 digits. A constant in any of these forms may be followed by a slash
599 and a second constant (the mask) in the same form, to form a masked
600 constant. IPv4 and IPv6 masks may be given as integers, to express
605 String constants have the same syntax as quoted strings in JSON (thus,
606 they are Unicode strings).
610 Some operators support sets of constants written inside curly braces
611 <code>{</code> ... <code>}</code>. Commas between elements of a set,
612 and after the last elements, are optional. With <code>==</code>,
613 ``<code><var>field</var> == { <var>constant1</var>,
614 <var>constant2</var>,</code> ... <code>}</code>'' is syntactic sugar
615 for ``<code><var>field</var> == <var>constant1</var> ||
616 <var>field</var> == <var>constant2</var> || </code>...<code></code>.
617 Similarly, ``<code><var>field</var> != { <var>constant1</var>,
618 <var>constant2</var>, </code>...<code> }</code>'' is equivalent to
619 ``<code><var>field</var> != <var>constant1</var> &&
620 <var>field</var> != <var>constant2</var> &&
621 </code>...<code></code>''.
624 <p><em>Miscellaneous</em></p>
627 Comparisons may name the symbol or the constant first,
628 e.g. <code>tcp.src == 80</code> and <code>80 == tcp.src</code> are both
633 Tests for a range may be expressed using a syntax like <code>1024 <=
634 tcp.src <= 49151</code>, which is equivalent to <code>1024 <=
635 tcp.src && tcp.src <= 49151</code>.
639 For a one-bit field or predicate, a mention of its name is equivalent
640 to <code><var>symobl</var> == 1</code>, e.g. <code>vlan.present</code>
641 is equivalent to <code>vlan.present == 1</code>. The same is true for
642 one-bit subfields, e.g. <code>vlan.tci[12]</code>. There is no
643 technical limitation to implementing the same for ordinal fields of all
644 widths, but the implementation is expensive enough that the syntax
645 parser requires writing an explicit comparison against zero to make
646 mistakes less likely, e.g. in <code>tcp.src != 0</code> the comparison
647 against 0 is required.
651 <em>Operator precedence</em> is as shown below, from highest to lowest.
652 There are two exceptions where parentheses are required even though the
653 table would suggest that they are not: <code>&&</code> and
654 <code>||</code> require parentheses when used together, and
655 <code>!</code> requires parentheses when applied to a relational
656 expression. Thus, in <code>(eth.type == 0x800 || eth.type == 0x86dd)
657 && ip.proto == 6</code> or <code>!(arp.op == 1)</code>, the
658 parentheses are mandatory.
662 <li><code>()</code></li>
663 <li><code>== != < <= > >=</code></li>
664 <li><code>!</code></li>
665 <li><code>&& ||</code></li>
669 <em>Comments</em> may be introduced by <code>//</code>, which extends
670 to the next new-line. Comments within a line may be bracketed by
671 <code>/*</code> and <code>*/</code>. Multiline comments are not
675 <p><em>Symbols</em></p>
678 Most of the symbols below have integer type. Only <code>inport</code>
679 and <code>outport</code> have string type. <code>inport</code> names a
680 logical port. Thus, its value is a <ref column="logical_port"/> name
681 from the <ref table="Port_Binding"/> table. <code>outport</code> may
682 name a logical port, as <code>inport</code>, or a logical multicast
683 group defined in the <ref table="Multicast_Group"/> table. For both
684 symbols, only names within the flow's logical datapath may be used.
688 <li><code>reg0</code>...<code>reg4</code></li>
689 <li><code>inport</code> <code>outport</code></li>
690 <li><code>eth.src</code> <code>eth.dst</code> <code>eth.type</code></li>
691 <li><code>vlan.tci</code> <code>vlan.vid</code> <code>vlan.pcp</code> <code>vlan.present</code></li>
692 <li><code>ip.proto</code> <code>ip.dscp</code> <code>ip.ecn</code> <code>ip.ttl</code> <code>ip.frag</code></li>
693 <li><code>ip4.src</code> <code>ip4.dst</code></li>
694 <li><code>ip6.src</code> <code>ip6.dst</code> <code>ip6.label</code></li>
695 <li><code>arp.op</code> <code>arp.spa</code> <code>arp.tpa</code> <code>arp.sha</code> <code>arp.tha</code></li>
696 <li><code>tcp.src</code> <code>tcp.dst</code> <code>tcp.flags</code></li>
697 <li><code>udp.src</code> <code>udp.dst</code></li>
698 <li><code>sctp.src</code> <code>sctp.dst</code></li>
699 <li><code>icmp4.type</code> <code>icmp4.code</code></li>
700 <li><code>icmp6.type</code> <code>icmp6.code</code></li>
701 <li><code>nd.target</code> <code>nd.sll</code> <code>nd.tll</code></li>
704 <code>ct_state</code>, which has the following Boolean subfields:
707 <li><code>ct.new</code>: True for a new flow</li>
708 <li><code>ct.est</code>: True for an established flow</li>
709 <li><code>ct.rel</code>: True for a related flow</li>
710 <li><code>ct.rpl</code>: True for a reply flow</li>
711 <li><code>ct.inv</code>: True for a connection entry in a bad state</li>
714 <code>ct_state</code> and its subfields are initialized by the
715 <code>ct_next</code> action, described below.
721 The following predicates are supported:
725 <li><code>eth.bcast</code> expands to <code>eth.dst == ff:ff:ff:ff:ff:ff</code></li>
726 <li><code>eth.mcast</code> expands to <code>eth.dst[40]</code></li>
727 <li><code>vlan.present</code> expands to <code>vlan.tci[12]</code></li>
728 <li><code>ip4</code> expands to <code>eth.type == 0x800</code></li>
729 <li><code>ip4.mcast</code> expands to <code>ip4.dst[28..31] == 0xe</code></li>
730 <li><code>ip6</code> expands to <code>eth.type == 0x86dd</code></li>
731 <li><code>ip</code> expands to <code>ip4 || ip6</code></li>
732 <li><code>icmp4</code> expands to <code>ip4 && ip.proto == 1</code></li>
733 <li><code>icmp6</code> expands to <code>ip6 && ip.proto == 58</code></li>
734 <li><code>icmp</code> expands to <code>icmp4 || icmp6</code></li>
735 <li><code>ip.is_frag</code> expands to <code>ip.frag[0]</code></li>
736 <li><code>ip.later_frag</code> expands to <code>ip.frag[1]</code></li>
737 <li><code>ip.first_frag</code> expands to <code>ip.is_frag && !ip.later_frag</code></li>
738 <li><code>arp</code> expands to <code>eth.type == 0x806</code></li>
739 <li><code>nd</code> expands to <code>icmp6.type == {135, 136} && icmp6.code == 0</code></li>
740 <li><code>tcp</code> expands to <code>ip.proto == 6</code></li>
741 <li><code>udp</code> expands to <code>ip.proto == 17</code></li>
742 <li><code>sctp</code> expands to <code>ip.proto == 132</code></li>
746 <column name="actions">
748 Logical datapath actions, to be executed when the logical flow
749 represented by this row is the highest-priority match.
753 Actions share lexical syntax with the <ref column="match"/> column. An
754 empty set of actions (or one that contains just white space or
755 comments), or a set of actions that consists of just
756 <code>drop;</code>, causes the matched packets to be dropped.
757 Otherwise, the column should contain a sequence of actions, each
758 terminated by a semicolon.
762 The following actions are defined:
766 <dt><code>output;</code></dt>
769 In the ingress pipeline, this action executes the
770 <code>egress</code> pipeline as a subroutine. If
771 <code>outport</code> names a logical port, the egress pipeline
772 executes once; if it is a multicast group, the egress pipeline runs
773 once for each logical port in the group.
777 In the egress pipeline, this action performs the actual
778 output to the <code>outport</code> logical port. (In the egress
779 pipeline, <code>outport</code> never names a multicast group.)
783 Output to the input port is implicitly dropped, that is,
784 <code>output</code> becomes a no-op if <code>outport</code> ==
785 <code>inport</code>. Occasionally it may be useful to override
786 this behavior, e.g. to send an ARP reply to an ARP request; to do
787 so, use <code>inport = "";</code> to set the logical input port to
788 an empty string (which should not be used as the name of any
793 <dt><code>next;</code></dt>
794 <dt><code>next(<var>table</var>);</code></dt>
796 Executes another logical datapath table as a subroutine. By default,
797 the table after the current one is executed. Specify
798 <var>table</var> to jump to a specific table in the same pipeline.
801 <dt><code><var>field</var> = <var>constant</var>;</code></dt>
804 Sets data or metadata field <var>field</var> to constant value
805 <var>constant</var>, e.g. <code>outport = "vif0";</code> to set the
806 logical output port. To set only a subset of bits in a field,
807 specify a subfield for <var>field</var> or a masked
808 <var>constant</var>, e.g. one may use <code>vlan.pcp[2] = 1;</code>
809 or <code>vlan.pcp = 4/4;</code> to set the most sigificant bit of
814 Assigning to a field with prerequisites implicitly adds those
815 prerequisites to <ref column="match"/>; thus, for example, a flow
816 that sets <code>tcp.dst</code> applies only to TCP flows,
817 regardless of whether its <ref column="match"/> mentions any TCP
822 Not all fields are modifiable (e.g. <code>eth.type</code> and
823 <code>ip.proto</code> are read-only), and not all modifiable fields
824 may be partially modified (e.g. <code>ip.ttl</code> must assigned
825 as a whole). The <code>outport</code> field is modifiable in the
826 <code>ingress</code> pipeline but not in the <code>egress</code>
831 <dt><code><var>field1</var> = <var>field2</var>;</code></dt>
834 Sets data or metadata field <var>field1</var> to the value of data
835 or metadata field <var>field2</var>, e.g. <code>reg0 =
836 ip4.src;</code> copies <code>ip4.src</code> into <code>reg0</code>.
837 To modify only a subset of a field's bits, specify a subfield for
838 <var>field1</var> or <var>field2</var> or both, e.g. <code>vlan.pcp
839 = reg0[0..2];</code> copies the least-significant bits of
840 <code>reg0</code> into the VLAN PCP.
844 <var>field1</var> and <var>field2</var> must be the same type,
845 either both string or both integer fields. If they are both
846 integer fields, they must have the same width.
850 If <var>field1</var> or <var>field2</var> has prerequisites, they
851 are added implicitly to <ref column="match"/>. It is possible to
852 write an assignment with contradictory prerequisites, such as
853 <code>ip4.src = ip6.src[0..31];</code>, but the contradiction means
854 that a logical flow with such an assignment will never be matched.
858 <dt><code><var>field1</var> <-> <var>field2</var>;</code></dt>
861 Similar to <code><var>field1</var> = <var>field2</var>;</code>
862 except that the two values are exchanged instead of copied. Both
863 <var>field1</var> and <var>field2</var> must modifiable.
867 <dt><code>ip.ttl--;</code></dt>
870 Decrements the IPv4 or IPv6 TTL. If this would make the TTL zero
871 or negative, then processing of the packet halts; no further
872 actions are processed. (To properly handle such cases, a
873 higher-priority flow should match on
874 <code>ip.ttl == {0, 1};</code>.)
877 <p><b>Prerequisite:</b> <code>ip</code></p>
880 <dt><code>ct_next;</code></dt>
883 Apply connection tracking to the flow, initializing
884 <code>ct_state</code> for matching in later tables.
885 Automatically moves on to the next table, as if followed by
890 As a side effect, IP fragments will be reassembled for matching.
891 If a fragmented packet is output, then it will be sent with any
892 overlapping fragments squashed. The connection tracking state is
893 scoped by the logical port, so overlapping addresses may be used.
894 To allow traffic related to the matched flow, execute
895 <code>ct_commit</code>.
899 It is possible to have actions follow <code>ct_next</code>,
900 but they will not have access to any of its side-effects and
901 is not generally useful.
905 <dt><code>ct_commit;</code></dt>
907 Commit the flow to the connection tracking entry associated
908 with it by a previous call to <code>ct_next</code>.
913 The following actions will likely be useful later, but they have not
914 been thought out carefully.
919 <dt><code>arp { <var>action</var>; </code>...<code> };</code></dt>
922 Temporarily replaces the IPv4 packet being processed by an ARP
923 packet and executes each nested <var>action</var> on the ARP
924 packet. Actions following the <var>arp</var> action, if any, apply
925 to the original, unmodified packet.
929 The ARP packet that this action operates on is initialized based on
930 the IPv4 packet being processed, as follows. These are default
931 values that the nested actions will probably want to change:
935 <li><code>eth.src</code> unchanged</li>
936 <li><code>eth.dst</code> unchanged</li>
937 <li><code>eth.type = 0x0806</code></li>
938 <li><code>arp.op = 1</code> (ARP request)</li>
939 <li><code>arp.sha</code> copied from <code>eth.src</code></li>
940 <li><code>arp.spa</code> copied from <code>ip4.src</code></li>
941 <li><code>arp.tha = 00:00:00:00:00:00</code></li>
942 <li><code>arp.tpa</code> copied from <code>ip4.dst</code></li>
945 <p><b>Prerequisite:</b> <code>ip4</code></p>
948 <dt><code>icmp4 { <var>action</var>; </code>...<code> };</code></dt>
951 Temporarily replaces the IPv4 packet being processed by an ICMPv4
952 packet and executes each nested <var>action</var> on the ICMPv4
953 packet. Actions following the <var>icmp4</var> action, if any,
954 apply to the original, unmodified packet.
958 The ICMPv4 packet that this action operates on is initialized based
959 on the IPv4 packet being processed, as follows. These are default
960 values that the nested actions will probably want to change.
961 Ethernet and IPv4 fields not listed here are not changed:
965 <li><code>ip.proto = 1</code> (ICMPv4)</li>
966 <li><code>ip.frag = 0</code> (not a fragment)</li>
967 <li><code>icmp4.type = 3</code> (destination unreachable)</li>
968 <li><code>icmp4.code = 1</code> (host unreachable)</li>
975 <p><b>Prerequisite:</b> <code>ip4</code></p>
978 <dt><code>tcp_reset;</code></dt>
981 This action transforms the current TCP packet according to the
982 following pseudocode:
989 tcp.ack = tcp.seq + length(tcp.payload);
996 Then, the action drops all TCP options and payload data, and
997 updates the TCP checksum.
1004 <p><b>Prerequisite:</b> <code>tcp</code></p>
1009 <column name="external_ids" key="stage-name">
1010 Human-readable name for this flow's stage in the pipeline.
1013 <group title="Common Columns">
1014 The overall purpose of these columns is described under <code>Common
1015 Columns</code> at the beginning of this document.
1017 <column name="external_ids"/>
1021 <table name="Multicast_Group" title="Logical Port Multicast Groups">
1023 The rows in this table define multicast groups of logical ports.
1024 Multicast groups allow a single packet transmitted over a tunnel to a
1025 hypervisor to be delivered to multiple VMs on that hypervisor, which
1026 uses bandwidth more efficiently.
1030 Each row in this table defines a logical multicast group numbered <ref
1031 column="tunnel_key"/> within <ref column="datapath"/>, whose logical
1032 ports are listed in the <ref column="ports"/> column.
1035 <column name="datapath">
1036 The logical datapath in which the multicast group resides.
1039 <column name="tunnel_key">
1040 The value used to designate this logical egress port in tunnel
1041 encapsulations. An index forces the key to be unique within the <ref
1042 column="datapath"/>. The unusual range ensures that multicast group IDs
1043 do not overlap with logical port IDs.
1046 <column name="name">
1048 The logical multicast group's name. An index forces the name to be
1049 unique within the <ref column="datapath"/>. Logical flows in the
1050 ingress pipeline may output to the group just as for individual logical
1051 ports, by assigning the group's name to <code>outport</code> and
1052 executing an <code>output</code> action.
1056 Multicast group names and logical port names share a single namespace
1057 and thus should not overlap (but the database schema cannot enforce
1058 this). To try to avoid conflicts, <code>ovn-northd</code> uses names
1059 that begin with <code>_MC_</code>.
1063 <column name="ports">
1064 The logical ports included in the multicast group. All of these ports
1065 must be in the <ref column="datapath"/> logical datapath (but the
1066 database schema cannot enforce this).
1070 <table name="Datapath_Binding" title="Physical-Logical Datapath Bindings">
1072 Each row in this table identifies physical bindings of a logical
1073 datapath. A logical datapath implements a logical pipeline among the
1074 ports in the <ref table="Port_Binding"/> table associated with it. In
1075 practice, the pipeline in a given logical datapath implements either a
1076 logical switch or a logical router.
1079 <column name="tunnel_key">
1080 The tunnel key value to which the logical datapath is bound.
1081 The <code>Tunnel Encapsulation</code> section in
1082 <code>ovn-architecture</code>(7) describes how tunnel keys are
1083 constructed for each supported encapsulation.
1086 <group title="OVN_Northbound Relationship">
1088 Each row in <ref table="Datapath_Binding"/> is associated with some
1089 logical datapath. <code>ovn-northd</code> uses these keys to track the
1090 association of a logical datapath with concepts in the <ref
1091 db="OVN_Northbound"/> database.
1094 <column name="external_ids" key="logical-switch" type='{"type": "uuid"}'>
1095 For a logical datapath that represents a logical switch,
1096 <code>ovn-northd</code> stores in this key the UUID of the
1097 corresponding <ref table="Logical_Switch" db="OVN_Northbound"/> row in
1098 the <ref db="OVN_Northbound"/> database.
1101 <column name="external_ids" key="logical-router" type='{"type": "uuid"}'>
1102 For a logical datapath that represents a logical router,
1103 <code>ovn-northd</code> stores in this key the UUID of the
1104 corresponding <ref table="Logical_Router" db="OVN_Northbound"/> row in
1105 the <ref db="OVN_Northbound"/> database.
1109 <group title="Common Columns">
1110 The overall purpose of these columns is described under <code>Common
1111 Columns</code> at the beginning of this document.
1113 <column name="external_ids"/>
1117 <table name="Port_Binding" title="Physical-Logical Port Bindings">
1119 Most rows in this table identify the physical location of a logical port.
1120 (The exceptions are logical patch ports, which do not have any physical
1125 For every <code>Logical_Port</code> record in <code>OVN_Northbound</code>
1126 database, <code>ovn-northd</code> creates a record in this table.
1127 <code>ovn-northd</code> populates and maintains every column except
1128 the <code>chassis</code> column, which it leaves empty in new records.
1132 <code>ovn-controller</code>/<code>ovn-controller-vtep</code>
1133 populates the <code>chassis</code> column for the records that
1134 identify the logical ports that are located on its hypervisor/gateway,
1135 which <code>ovn-controller</code>/<code>ovn-controller-vtep</code> in
1136 turn finds out by monitoring the local hypervisor's Open_vSwitch
1137 database, which identifies logical ports via the conventions described
1138 in <code>IntegrationGuide.md</code>.
1142 When a chassis shuts down gracefully, it should clean up the
1143 <code>chassis</code> column that it previously had populated.
1144 (This is not critical because resources hosted on the chassis are equally
1145 unreachable regardless of whether their rows are present.) To handle the
1146 case where a VM is shut down abruptly on one chassis, then brought up
1147 again on a different one,
1148 <code>ovn-controller</code>/<code>ovn-controller-vtep</code> must
1149 overwrite the <code>chassis</code> column with new information.
1152 <group title="Core Features">
1153 <column name="datapath">
1154 The logical datapath to which the logical port belongs.
1157 <column name="logical_port">
1158 A logical port, taken from <ref table="Logical_Port" column="name"
1159 db="OVN_Northbound"/> in the OVN_Northbound database's <ref
1160 table="Logical_Port" db="OVN_Northbound"/> table. OVN does not
1161 prescribe a particular format for the logical port ID.
1164 <column name="chassis">
1165 The physical location of the logical port. To successfully identify a
1166 chassis, this column must be a <ref table="Chassis"/> record. This is
1168 <code>ovn-controller</code>/<code>ovn-controller-vtep</code>.
1171 <column name="tunnel_key">
1173 A number that represents the logical port in the key (e.g. STT key or
1174 Geneve TLV) field carried within tunnel protocol packets.
1178 The tunnel ID must be unique within the scope of a logical datapath.
1184 The Ethernet address or addresses used as a source address on the
1185 logical port, each in the form
1186 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
1187 The string <code>unknown</code> is also allowed to indicate that the
1188 logical port has an unknown set of (additional) source addresses.
1192 A VM interface would ordinarily have a single Ethernet address. A
1193 gateway port might initially only have <code>unknown</code>, and then
1194 add MAC addresses to the set as it learns new source addresses.
1198 <column name="type">
1200 A type for this logical port. Logical ports can be used to model other
1201 types of connectivity into an OVN logical switch. The following types
1206 <dt>(empty string)</dt>
1207 <dd>VM (or VIF) interface.</dd>
1209 <dt><code>patch</code></dt>
1211 One of a pair of logical ports that act as if connected by a patch
1212 cable. Useful for connecting two logical datapaths, e.g. to connect
1213 a logical router to a logical switch or to another logical router.
1216 <dt><code>localnet</code></dt>
1218 A connection to a locally accessible network from each
1219 <code>ovn-controller</code> instance. A logical switch can only
1220 have a single <code>localnet</code> port attached and at most one
1221 regular logical port. This is used to model direct connectivity to
1222 an existing network.
1225 <dt><code>vtep</code></dt>
1227 A port to a logical switch on a VTEP gateway chassis. In order to
1228 get this port correctly recognized by the OVN controller, the <ref
1230 table="Port_Binding"/>:<code>vtep-physical-switch</code> and <ref
1232 table="Port_Binding"/>:<code>vtep-logical-switch</code> must also
1239 <group title="Patch Options">
1241 These options apply to logical ports with <ref column="type"/> of
1245 <column name="options" key="peer">
1246 The <ref column="logical_port"/> in the <ref table="Port_Binding"/>
1247 record for the other side of the patch. The named <ref
1248 column="logical_port"/> must specify this <ref column="logical_port"/>
1249 in its own <code>peer</code> option. That is, the two patch logical
1250 ports must have reversed <ref column="logical_port"/> and
1251 <code>peer</code> values.
1255 <group title="Localnet Options">
1257 These options apply to logical ports with <ref column="type"/> of
1258 <code>localnet</code>.
1261 <column name="options" key="network_name">
1262 Required. <code>ovn-controller</code> uses the configuration entry
1263 <code>ovn-bridge-mappings</code> to determine how to connect to this
1264 network. <code>ovn-bridge-mappings</code> is a list of network names
1265 mapped to a local OVS bridge that provides access to that network. An
1266 example of configuring <code>ovn-bridge-mappings</code> would be:
1268 <pre>$ ovs-vsctl set open . external-ids:ovn-bridge-mappings=physnet1:br-eth0,physnet2:br-eth1</pre>
1271 When a logical switch has a <code>localnet</code> port attached,
1272 every chassis that may have a local vif attached to that logical
1273 switch must have a bridge mapping configured to reach that
1274 <code>localnet</code>. Traffic that arrives on a
1275 <code>localnet</code> port is never forwarded over a tunnel to
1281 If set, indicates that the port represents a connection to a specific
1282 VLAN on a locally accessible network. The VLAN ID is used to match
1283 incoming traffic and is also added to outgoing traffic.
1287 <group title="VTEP Options">
1289 These options apply to logical ports with <ref column="type"/> of
1293 <column name="options" key="vtep-physical-switch">
1294 Required. The name of the VTEP gateway.
1297 <column name="options" key="vtep-logical-switch">
1298 Required. A logical switch name connected by the VTEP gateway. Must
1299 be set when <ref column="type"/> is <code>vtep</code>.
1303 <group title="Nested Containers">
1305 These columns support containers nested within a VM. Specifically,
1306 they are used when <ref column="type"/> is empty and <ref
1307 column="logical_port"/> identifies the interface of a container spawned
1308 inside a VM. They are empty for containers or VMs that run directly on
1312 <column name="parent_port">
1314 <ref table="Logical_Port" column="parent_name" db="OVN_Northbound"/>
1315 in the OVN_Northbound database's <ref table="Logical_Port"
1316 db="OVN_Northbound"/> table.
1321 Identifies the VLAN tag in the network traffic associated with that
1322 container's network interface.
1326 This column is used for a different purpose when <ref column="type"/>
1327 is <code>localnet</code> (see <code>Localnet Options</code>, above).