OVN¶
This page is the starting point for OVN, the ovn role, used if neutron_plugin_agent: ovn: the containers
ovn_controller, ovn_northd, ovn_nb_db and ovn_sb_db, on the compute, control and network nodes of the example
inventory, selected by the tag ovn. The lists below say where the study covers how to operate it, its impact, its
dependencies and the evidence, what to check around a run and what stays open; the service card follows them.
Where to look¶
Operate¶
- Scenario: Reconfigure Neutron §4 (row "OVN")
No operation page gives a command line for the ovn tag, and no risk register item is about a run of this tag. What the
study says about running it is in the rows linked under Impact and risk and in fact sheet A
§5.8.
Impact and risk¶
Dependencies¶
- Dependencies: Component dependencies §2, Component dependencies §4
Evidence¶
- Fact sheet: fact sheet A §5
- Image side: Kolla images §5 (rows
ovn-*)
Before and after a run¶
- Tags §3.1, row
ovn: safe on its own "check manualovn-cms-optionsfirst"; prerequisite: Open vSwitch. - fact sheet A §5.8, item (E): any manual
ovn-cms-optionsvalue, such as availability-zone hints, is overwritten or removed on every reconfigure; the impact of that loss is NOT AVAILABLE. - fact sheet A §5.8, item (A): any change to
ovn-nb-db/ovn-sb-dbrestarts every member at once under serial 0. Mitigation:ANSIBLE_SERIALgives a rolling restart, at the cost of making every play serial. - Reconfigure a single service
§3:
ovnis one of the tags that can restart the containers that Tags §3.1 traces to running VMs CODE; what those restarts do to running VMs is NOT AVAILABLE.
Known limits and open points¶
- What is not known, row "OVN": the sources do not
establish whether an
ovn-controllerrestart re-programs flows on the host, and whether Kolla-Ansible's directovn-ctlcall creates and upgrades the DB schema. - Q3: "Data-plane loss during an
openvswitch_vswitchdrestart or recreate". Status: NOT AVAILABLE. Its row in What is not known includes whether the OVS agent orovn-controllerreprograms the OpenFlow tables. - Q14, answered from the source CODE: agent, OVS and OVN images have no one-shot branch.
- fact sheet A §5.8, "Operationally notable", items (A) to (H): the whole DB cluster restarts at once; whether the seed host is a single point of failure for re-deploys is NOT AVAILABLE; ovn-controller restarts; bootstrap cost scales with computes; gateway options are clobbered; security; OVN + DPDK cannot work in this release (inference from code); missing inventory groups are not caught.
- fact sheet A §5.8, item (C): the OVN manifests
have no
config_files, sokolla_set_configs --checkalways exits 0: a command-line change written bygenconfigis applied neither bydeploy-containersnor by a later run, until the container restarts for another reason. - Kolla images §7: not available from the
sources:
ovn-ctlschema creation and upgrade with Kolla-Ansible's direct call, and its hard-coded/usr/share/ovn/scripts/path on distributions that shipovn-ctlelsewhere. - Known bugs and limitations and Findings have no entry on OVN.
Service card¶
The rows of the card are explained in How to read a service card.
| Item | Value |
|---|---|
| Play | site.yml:734 |
| Tags | ovn |
| Play host patterns | ovn-controller, ovn-nb-db, ovn-northd, ovn-sb-db |
| Node types in play (example inventory) | compute, control, network |
| Node types running its containers | compute, control, network |
| Containers | ovn_controller, ovn_northd, ovn_nb_db, ovn_sb_db |
deploy/reconfigure flow (tasks/) |
config → check-containers → bootstrap → flush handlers |
| Task files | bootstrap.yml, check-containers.yml, check.yml, config.yml, deploy-containers.yml, deploy.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, stop.yml, upgrade.yml |
| Templates | ovn-controller.json.j2, ovn-nb-db.json.j2, ovn-northd.json.j2, ovn-sb-db.json.j2 |
| Handlers (definition order) | Restart ovn-nb-db container; Restart ovn-sb-db container; Wait for ovn-nb-db; Wait for ovn-sb-db; Restart ovn-northd container; Restart ovn-controller container |
| Key variables | enable_ovn, neutron_plugin_agent: ovn, neutron_ovn_distributed_fip |
| Role dependencies | common (meta) |
Related¶
- Open vSwitch — OVN needs OVS running: its bootstrap commands exec into
openvswitch_vswitchd - Neutron — neutron-server (ML2/OVN) and
neutron-ovn-metadata-agentdepend on OVN - Reconfigure Neutron §4 — what
-t neutronand-t ovntouch with OVN - Component dependencies §4 — the networking containers and their placement
- Components — the other component pages