Operations¶

What Kolla-Ansible Ussuri commands do when they run against a live platform, read from the source of the unmodified
site.yml, its roles and Ansible 2.9.27. Nothing was run against a host.
Real kolla-ansible (Ussuri) invocations with what they select, their scope and their impact.
Note
Key answers
- A service tag also touches the HAProxy frontends of the service,
commonon every host of the service play, Keystone registration, for most services DB creation and schema sync (Neutron's DB sync only ondeployby default), and hosts outside--limit(Reconfigure a single service §2). A controller membership change is a fleet-wide restart event for every messaging consumer (Change control-plane membership §2); what adding a compute withdeploy --limittouches: Add a compute node §2. - Recommended pattern:
genconfig, thendeploy-containers --limitbatch by batch, with its caveats CODE (Write config first, apply in controlled batches §2). Why a small change can create a large workload: Why a small change creates a large workload. - Leave HAProxy alone:
--skip-tags haproxy(Reconfigure a single service §1.2). Pushcommonchanges:-t chrony, because-t commonis a no-op (Applycommonchanges (fluentd, cron, kolla_toolbox) §1.1). - Add a compute:
bootstrap-servers,pullanddeploy, each with--limit(Add a compute node §1.1). Per-tag quick lookup of hosts touched, possible restarts and one-shot containers: Command quick lookup by tag.
Operations catalogue¶
One row per operation page, in the order of the navigation. The commands are copied from each page. The impact classes are defined in Operation impact classes. The risk numbers are those the page cites, in its text or in its "Related" list.
| Operation | Commands covered | Impact | Risks |
|---|---|---|---|
| Pre-execution checklist | kolla-ansible genconfigdocker exec -u root <c> /usr/kolla-ansible pullkolla-ansible mariadb_backupand the openstack checks of its steps 5 and 6 |
writes-config |
– |
| Predict and inspect a run | EXTRA_OPTS="--list-tags" kolla-ansible -i multinode deployEXTRA_OPTS="--list-hosts" kolla-ansible -i multinode -t nova reconfigureEXTRA_OPTS="--list-tasks" …kolla-ansible -i multinode genconfig [-t <svc>] [--limit <hosts>]docker exec -u root <container> /usr/EXTRA_OPTS="--check --diff" kolla-ansible … reconfigurekolla-ansible -i multinode prechecks [-t <svc>] |
read-only, writes-config |
– |
| Reconfigure a single service | kolla-ansible -i multinode -t keystone reconfigurekolla-ansible -i multinode -t nova --skip-tags haproxy reconfigure |
restarts-on-drift |
R8, R19, R20, R23, R24 |
| Reconfigure Nova | kolla-ansible -i multinode -t nova reconfigurekolla-ansible -i multinode -t nova-api reconfigurekolla-ansible -i multinode -t nova-cell reconfigure |
restarts-on-drift |
R1, R2, R3, R24 |
| Reconfigure Neutron | kolla-ansible -i multinode -t neutron reconfigurekolla-ansible -i multinode -t neutron reconfigure --limit network01kolla-ansible -i multinode -t openvswitch reconfigure --limit compute042 |
restarts-on-drift, critical |
R5, R6, R7 |
Apply common changes (fluentd, cron, kolla_toolbox) |
kolla-ansible -i multinode -t chrony reconfigurekolla-ansible -i multinode -t chrony reconfigure --limit 'compute[0:49]' |
restarts-on-drift |
R2, R25 |
| Write config first, apply in controlled batches | kolla-ansible -i multinode -t nova-cell genconfigkolla-ansible -i multinode -t nova-cell deploy-containers --limit 'compute[0:9]'kolla-ansible -i multinode -t nova-cell deploy-containers --limit 'compute[10:19]'ANSIBLE_SERIAL=10 kolla-ansible -i multinode -t nova reconfigure |
writes-config, restarts-on-drift |
R1 |
| Update container images | kolla-ansible -i multinode pullkolla-ansible -i multinode -t nova pull --limit computekolla-ansible -i multinode upgradeANSIBLE_SERIAL=20 kolla-ansible -i multinode -t nova upgrade |
pulls-images, recreates-containers, critical |
R7, R11, R12, R13 |
| Add a compute node | kolla-ansible -i multinode bootstrap-servers --limit compute501kolla-ansible -i multinode pull --limit compute501kolla-ansible -i multinode deploy --limit compute501 |
– | R14, R23 |
| Change control-plane membership | no command line in its command section; its scenario reads -t nova,neutron reconfigure |
restarts-on-drift, maintenance-window |
R3, R4 |
| Database operations | kolla-ansible -i multinode mariadb_backupkolla-ansible -i multinode mariadb_recovery |
recovery |
R18 |
| Stop and destroy | kolla-ansible -i multinode stop --yes-i-really-really-mean-it -t heat --limit control03kolla-ansible -i multinode destroy --yes-i-really-really-mean-it |
critical |
R15, R16 |
| Command quick lookup by tag | -t <tag> reconfigure for 12 tagsreconfigure (no tag)deploy-containers -t Xgenconfig -t Xpull -t X |
restarts-on-drift, writes-config, pulls-images |
by tag, in the "Risks" bullet of the component pages |
Assumed deployment¶
Every scenario assumes the same deployed state: 3 controllers, 2 network nodes, 3 computes, 1 storage node and 1 monitoring node, with Keystone, Glance, Placement, Nova, Neutron/OVS, Cinder/LVM, Heat and Horizon.
Conventions used by the command sections¶
These two lists apply to the command sections of every operation page and to the Command quick lookup by tag.
The examples assume:
- the inventory is
/etc/kolla/multinode(adapt-i); globals.ymlandpasswords.ymlare in/etc/kolla;- Ansible is 2.9.
Conventions:
- Scope = plays and hosts touched.
- Restarts = containers that can restart (only if drift is detected).
- One-shot = bootstrap containers that run regardless of drift.
Drift¶
Drift means what compare_container detects: a changed image or container parameter, or kolla_set_configs --check
exiting 1 (library/kolla_docker.py:326-332; Kolla images
§3).
Code guarantees and environment dependence¶
On the operation pages:
- The code guarantees = what Kolla will do (tasks, restarts) given the inputs.
- Depends on the environment = what that does to VMs and APIs; mostly NOT AVAILABLE in these sources.
These two notions head the columns of the tables in Reconfigure Nova §5 ("Guaranteed by code", "Depends on environment") and Reconfigure Neutron §4 ("code-guaranteed", "environment-dependent").
The evidence labels CODE and NOT AVAILABLE are defined once, in the Conventions and evidence labels.
Three mechanisms that explain almost every surprise¶
Three mechanisms explain almost every surprise on the operation pages, so they are restated here, each with the section that establishes it:
- Config drift ⇒ full container stop/start. It is never a reload. The stop timeout is effectively 10 s (Repository architecture §6).
- Loop-notify. One changed container in a role's loop restarts every container of that role on that host (Tags §2.4).
- Global inputs.
enable_*flags, group membership and passwords are rendered into per-host files on every host (Component dependencies §5).
Related¶
- Tags §3 (what each tag executes)
- Risk register (risks R1–R25)
- Nova deep dive §5 (nova-libvirt restarts)
- Tag index and What is not known (tag index, everything marked NOT AVAILABLE)
- Repository architecture §2 (the CLI →
playbook mapping and the
kolla_serialpass-through rules) - Tags (tag semantics)
- Conventions and evidence labels (evidence labels)