Ten things to know before a production run¶
Ten things to know before running Kolla-Ansible Ussuri on production. Most items link to the section that gives the evidence.
reconfigureisdeployfor 70 of the 72 roles that have areconfigure.yml. It re-runs Keystone registration, DB creation and the DB-sync bootstrap containers for most services; Neutron's DB sync is the default exception. The only lightweight path isgenconfigfollowed bydeploy-containers(Execution flow §4).- Config is applied by a full stop/start, never a reload, and the effective SIGKILL timeout is 10 s.
docker_graceful_timeoutis silently ignored (Repository architecture §6). The only signal Kolla sends is aSIGHUPtonova_scheduler, which refreshes its cell cache. - One changed container restarts all containers of its role on that host (Ansible 2.9 loop-notify). With the default Nova settings, a nova-compute config change restarts nova_libvirt on every compute (Tags §2.4).
- Without batching, handlers restart a service on every host of the play at once. Batching is
ANSIBLE_SERIALforreconfigure/upgradeand-e kolla_serial=Nfordeploy, which ignoresANSIBLE_SERIAL. Only MariaDB (4 waves) and RabbitMQ (one by one) roll by themselves. - A service tag is never just that service. For a service with a frontend it also runs the haproxy frontend config
(and can restart HAProxy). It runs the
commonrole on every host of the play (memcached and multipathd excepted) and, for API services, Keystone registration and DB sync (Tags §3, Reconfigure a single service §2). -t commondoes nothing (Tags §2.1). Use-t chronyor a service tag to push fluentd/cron changes.- Global settings land in per-host files.
enable_*, RabbitMQ/memcached membership and passwords end up in compute-side configs, so small central changes cause fleet-wide restarts (Why a small change creates a large workload). deploynever pulls an image that is already present. Rebuilt images under the same tag needpull. A tag change applied withdeployrecreates the entire fleet at once (Update container images).--limitdoes not contain everything. Delegated tasks still run ongroups[x][0]controllers, and all hosts' facts are gathered serially by the limited hosts (Compute scaling, Add a compute node §2).--list-taskscannot predict a run. Usegenconfigpluskolla_set_configs --check, or staging (Predict and inspect a run). Two things to know about the check:- It compares only the files listed in
config.json, not itscommandorpermissions: memcached lists no files, so a change to its command line never shows as drift. A plainreconfigurestill applies it (the changedconfig.jsonnotifies the restart handler), but oncegenconfighas written it, no later run restarts the container for it; it takes effect at the next restart for another reason (Write config first, apply in controlled batches §1.1). - A newly rendered optional file whose destination is not yet in the container makes
--checkexit 2, unless an entry listed before it already differs (then it exits 1 and the container restarts). Exit 2 is real drift, but the check task fails instead of restarting the container (Kolla images §3).
- It compares only the files listed in
Related¶
- Find it fast — typical operator questions and the section that answers them
- Pre-execution checklist — what to check before a run
- Risk register — the risks R1–R25, with their precautions
- Technical findings — the fifteen headline findings, each with its evidence
- Operations — the operation pages, each with its commands
To remember
Lumo: if you keep only 5 things from this page, keep these.
reconfigureisdeployfor 70 of the 72 roles that have areconfigure.yml; the only lightweight path isgenconfigfollowed bydeploy-containers.- Config is applied by a full stop/start, never a reload, and the effective SIGKILL timeout is 10 s:
docker_graceful_timeoutis silently ignored. - One changed container restarts all containers of its role on that host.
- Without batching, handlers restart a service on every host of the play at once;
deployignoresANSIBLE_SERIALand needs-e kolla_serial=N. deploynever pulls an image that is already present: rebuilt images under the same tag needpull.
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.