Why a small change creates a large workload¶
Why a small change can create a large workload: six small changes, each with why it is large and the source lines and sections that show it. The per-host work that every run pays, independently of restarts, closes the page.
| Small change | Why it is large | Source |
|---|---|---|
| One option for nova-compute | targets every compute; loop-notify adds libvirt + ssh restarts | nova.yml:117-135; Tags §2.4; Reconfigure Nova §3 |
enable_<new service>: yes |
changes fluentd/logrotate on every host and nova.conf sections on every compute |
roles/, roles/; Reconfigure Nova §3 |
| One extra controller | changes the transport URL in every messaging service everywhere | group_vars/; Change control-plane membership §2 |
| A server-side ML2 option | no longer reaches the agents: ml2_conf.ini (and its overrides) is rendered for neutron-server and neutron-infoblox-ipam-agent only, and openvswitch_agent.ini no longer merges the ml2_conf.ini overrides (Ussuri did). A file added under neutron/ in the custom config is still copied to every OVS and Linux bridge agent and restarts them |
roles/, :197-211, :15-21, :462-482; Reconfigure Neutron §3 |
| Rebuilt image of one service | its siblings on the same host restart too | module_utils/; Tags §2.4; Update container images §2 |
Any OpenStack API service -t <svc> |
runs the service's include in the loadbalancer play (haproxy configuration) and Keystone registration even with no change. It no longer runs common: Ussuri pulled common in through each role's meta dependency, 2023.1 roles have no meta and the common play is tagged common only; the DB sync runs on every deploy and, for most services, on every reconfigure. Neutron now too: its bootstrap (neutron-db-manage ... upgrade head) has no kolla_action condition any more and runs on every deploy and reconfigure. Infrastructure tags such as -t haproxy run the loadbalancer play with every service include, but no Keystone registration or DB sync |
Reconfigure Neutron §2, Reconfigure a single service §2; site.yml:86-97, :99-342; roles/, roles/, roles/; kolla docker/ |
And independently of restarts, every run pays the per-host work CODE. Every full deploy or reconfigure makes
10 compare_container calls per compute (common 3, iscsid with Cinder LVM, openvswitch 2, neutron 1, nova-cell 3;
Ussuri had 11 with chrony, a role that no longer exists), each one a kolla_set_configs --check exec once the
container exists (roles/common/tasks/check-containers.yml:2-17, roles/nova-cell/tasks/check-containers.yml,
roles/openvswitch/tasks/check-containers.yml, roles/neutron/tasks/check-containers.yml,
roles/iscsi/tasks/check-containers.yml; module_utils/kolla_container_worker.py:20, :59-66,
module_utils/kolla_docker_worker.py:155-162). The remote module invocations
of a no-change -t nova run are counted from the task files in Compute scaling
§2. The number of task
results per compute is NOT AVAILABLE.
Related¶
- Compute scaling §5 — the work multiplier and the restart multiplier
- Tags §2.4 — loop-notify
- Technical findings — F6: global inputs are rendered into per-host files
- Write config first, apply in controlled batches —
genconfig, thendeploy-containers --limitbatch by batch - Risk register — the risks R1–R25
To remember
Lumo: if you keep only 5 things from this page, keep these.
- One option for nova-compute is not small: it targets every compute, and loop-notify adds the libvirt and ssh restarts.
- A rebuilt image of one service restarts its sibling containers on the same host too.
- One extra controller changes the transport URL in every messaging service everywhere.
- Every run pays the per-host work: every full
deployorreconfiguremakes 10compare_containercalls per compute, independently of restarts. CODE - Write config first, apply in controlled batches:
genconfig, thendeploy-containers --limitbatch by batch.
What would you do?
Lumo: a situation you could meet on a real platform, and three ways to react. Pick the one you would choose: I will tell you what this page says about it. Nothing is recorded.
Check yourself
Lumo: 3 quick questions to check the main ideas of this page. Choose an answer to see the explanation and the section that gives the evidence. Your score counts your first choices and stays in this browser only.
Lumo: ready for the next step? Take your time: you can come back to this page whenever you need it.
Lumo: nicely done! One more page on your journey.