Placement¶
This page is the starting point for Placement, the placement role: one container, placement_api, on the control
nodes of the example inventory, selected by the tag placement. Its bootstrap container runs the DB sync and the online
data migrations on every deploy and reconfigure (Component dependencies §3).
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 a single service §2, Reconfigure a single service §3
- Command: Command quick lookup by tag
Impact and risk¶
- What the tag executes (
placement): Tags §3, row<svc>; Tags §3.1, row<svc>API service - Risks: R8, R24
Dependencies¶
- Dependencies: Component dependencies §3
Evidence¶
- Fact sheet: fact sheet C §2
- Image side: Kolla images
§4 (row
placement-api), Kolla images §5
Before and after a run¶
- Tags §3.1, row
<svc>API service: safe on its own "yes, it is the intended unit; it still runs Keystone registration and DB sync"; batch withANSIBLE_SERIAL. Prerequisites: MariaDB, RabbitMQ, memcached, Keystone (registration), HAProxy VIP. - fact sheet C §2.8: rotating
placement_keystone_passwordneeds a reconfigure of placement and nova (all computes) and neutron. - R8, precautions for a HAProxy config change:
ANSIBLE_SERIAL=1for haproxy changes;--skip-tags haproxywhen you don't intend to change frontends. - R24, precautions for the effective container stop timeout of 10 s: drain long
operations before restarts; patch
kolla_dockeror passgraceful_timeoutif needed. - Reconfigure a single service
§3,
verification of
-t <svc> reconfigure: before,kolla-ansible -t <svc> genconfig, thenkolla_set_configs --checkin each<svc>container and a diff of/etc/kolla/haproxy/services.d/<svc>*.cfgagainst the previous version; after,openstack endpoint list --service <name>is unchanged for each Keystone service the role registers, the API answers through the VIP, the container start times show which hosts restarted, anddocker ps --filter name=haproxyshows whether HAProxy restarted.
Known limits and open points¶
- Known bugs and limitations, second row
site.yml: placement haproxy include lackswhen: enable_placement. Status: CODE. - Q14, answered from the source CODE: Placement's
KOLLA_BOOTSTRAPrunsdb sync+online_data_migrationson every deploy/reconfigure. - F15, "What the bootstrap containers run differs per image": Placement's
KOLLA_BOOTSTRAPcontainer also runsonline_data_migrations, on every deploy/reconfigure CODE. - F5, "
reconfigure=deploy": a reconfigure re-runs Keystone registration, DB creation/grants and the DB-sync bootstrap containers of most services CODE. - What is not known, row on upstream Nova behaviour when a dependency is missing: for Placement, the sources do not establish whether scheduling stops while it restarts.
- Nova deep dive §3, item 4: Placement serves the scheduler's allocation candidates and nova-compute's resource-provider updates; NOT AVAILABLE whether scheduling stops and computes log errors without it.
- fact sheet C §2.8, "Operational notes and the relation to nova", three points: consumers authenticate as the placement user; NOT AVAILABLE (upstream nova): how scheduling and the nova-compute resource tracker periodic task behave during a placement-api outage or restart; the upgrade db sync and online data migrations run while the old placement-api is still serving.
- Kolla images §6, item 6: Placement's online data migrations run on
every deploy/reconfigure, inside
bootstrap_placement, and twice on upgrade; a tag change applied withdeploytherefore runs them CODE.
Service card¶
The rows of the card are explained on the Components page.
| Item | Value |
|---|---|
| Play | site.yml:697 |
| Tags | placement |
| Play host patterns | placement-api |
| Node types in play (example inventory) | control |
| Node types running its containers | control |
| Containers | placement_api |
deploy/reconfigure flow (tasks/) |
register → clone (if) → config → check-containers → bootstrap → flush handlers |
| Task files | bootstrap.yml, bootstrap_service.yml, check-containers.yml, check.yml, clone.yml, config.yml, copy-certs.yml, deploy-containers.yml, deploy.yml, loadbalancer.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, register.yml, stop.yml, upgrade.yml |
| Templates | migrate-db.rc.j2, placement-api-wsgi.conf.j2, placement-api.json.j2, placement.conf.j2 |
| Handlers (definition order) | Restart placement-api container |
| Key variables | enable_placement |
| Role dependencies | common (meta) |
Related¶
- Reconfigure a single service — what
-t <svc> reconfigureruns for an API service such as placement, with the risks and the verification - Nova — the scheduler and nova-compute use Placement
- Nova deep dive §3 — Placement among what must be available before Nova can operate
- Neutron — one of the consumers that authenticate as the placement user
- Update container images §4 — a tag change applied with
deployruns no online data migrations, except Placement's - Component dependencies §6 — Placement is deployed before Nova
- Components — the other component pages