Skip to content

Open vSwitch

This page is the starting point for Open vSwitch, the openvswitch role: the containers openvswitch_db and openvswitch_vswitchd, on the compute and network nodes of the example inventory, selected by the tag openvswitch. The play runs only while enable_ovs_dpdk is no; ovs-dpdk has its own play and tag (site.yml:546-566). The risk register rates a restart or recreate of openvswitch_vswitchd Critical (R7). 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

Impact and risk

Dependencies

Evidence

Before and after a run

  • Tags §3.1, row openvswitch: safe on its own "yes if unchanged"; changed in 2023.1: system-id and hw-offload are set through the openvswitch_db module in kolla_toolbox, and a change notifies Restart openvswitch-vswitchd container (roles/openvswitch/tasks/post-config.yml:3-22) CODE; whether the module reports ok when the value is already set is NOT AVAILABLE (the module is not in these sources). Image changes per host batch; prerequisite: the openvswitch kernel module.
  • R7, precautions: upgrade or recreate OVS host by host with evacuation or acceptance; never fleet-wide with serial 0.
  • Update container images §4: an OVS image change recreates openvswitch_vswitchd on every OVS host simultaneously (serial 0); NOT AVAILABLE whether VM networking is interrupted on every compute at the same time. Upgrade OVS per batch with ANSIBLE_SERIAL=<n> kolla-ansible -t openvswitch upgrade, or use --limit batches.
  • Reconfigure a single service §3: openvswitch is 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

  • Known bugs and limitations, row openvswitch: the Ussuri Set system-id command that always reported changed is gone; 2023.1 uses the openvswitch_db module and restarts openvswitch_vswitchd when it reports changed (roles/openvswitch/tasks/post-config.yml:3-22) CODE. Whether it reports changed on an unchanged host: NOT AVAILABLE.
  • Known bugs and limitations, row ovs-dpdk: the pull bug is fixed in 2023.1 (pull imports service-images-pull, which reads ovsdpdk_services through kolla_role_name: "ovsdpdk"; roles/ovs-dpdk/tasks/pull.yml:2-3, vars/main.yml:4, roles/service-images-pull/tasks/main.yml:14); the NIC mapping file is still written once (gen_config only if the file is absent, roles/ovs-dpdk/files/ovs-dpdkctl.sh:350-353); the 300 s wait handler still has no port (roles/ovs-dpdk/handlers/main.yml:88-92), but the notify that should reach it is spelled wait for dpdk tunnel ip while the handler is named Wait for dpdk tunnel ip (roles/ovs-dpdk/handlers/main.yml:21, :88), so whether the wait runs at all, or the run fails on the missing handler, is NOT AVAILABLE; see fact sheet A §6. Status: CODE.
  • Q3: "Data-plane loss during an openvswitch_vswitchd restart or recreate". Status: NOT AVAILABLE.
  • What is not known, row "openvswitch_vswitchd restart or recreate": the sources do not establish whether the OpenFlow tables are lost, whether the OVS agent or ovn-controller reprograms them, and whether all VM traffic on the host is interrupted, and for how long. Same table: whether VM network traffic stops under kolla-ansible stop.
  • What is not known: the sources do not establish whether services started by a shell wrapper that does not exec them (neutron-l3-agent, haproxy, ovs-vswitchd, ovsdb-server) receive SIGTERM at all before the container stops; start-ovs runs ovs-vswitchd without exec (roles/openvswitch/templates/start-ovs.j2:2).
  • Q14, answered from the source CODE: agent, OVS and OVN images have no one-shot branch (no KOLLA_BOOTSTRAP/KOLLA_UPGRADE in kolla docker/openvswitch/*).
  • F13, "The Nova deploy order" puts nova-compute before OVS and the Neutron agents on new computes (site.yml:544 imports nova.yml before the openvswitch play at :546) CODE; NOT AVAILABLE whether instances can be scheduled on such a compute before the later plays finish.
  • fact sheet A §6.8, "Operationally notable" for the ovs-dpdk role (no fact sheet covers openvswitch): any ovsdpdk-db restart also restarts ovs-vswitchd; NIC rebinding and unit installation run on every deploy, reconfigure, upgrade and genconfig; sticky configuration.
  • Kolla images §6, item 13: an openvswitch_vswitchd restart replaces only the userspace daemon; the kernel module stays loaded and conf.db keeps bridges and ports CODE. NOT AVAILABLE Whether the OpenFlow tables are lost and must be reprogrammed by the OVS agent or ovn-controller.

Service card

The rows of the card are explained in How to read a service card.

Item Value
Play site.yml:546
Tags openvswitch
Play host patterns openvswitch
Node types in play (example inventory) compute, network
Node types running its containers compute, network
Containers openvswitch_db, openvswitch_vswitchd
deploy/reconfigure flow (tasks/deploy.yml) config-host → config → check-containers → flush handlers → post-config
Task files check-containers.yml, check.yml, config-host.yml, config.yml, config_validate.yml, deploy-containers.yml, deploy.yml, main.yml, post-config.yml, precheck.yml, pull.yml, reconfigure.yml, stop.yml, upgrade.yml
Templates openvswitch-db-server.json.j2, openvswitch-vswitchd.json.j2, ovs-vsctl.j2, start-ovs.j2, start-ovsdb-server.j2
Handlers (definition order) Restart openvswitch-db-server container; Waiting for openvswitch_db service to be ready; Restart openvswitch-vswitchd container
Key variables enable_openvswitch, neutron_bridge_name, neutron_external_interface, computes_need_external_bridge
Role dependencies none