Cinder¶
This page is the starting point for Cinder, the cinder role: the containers cinder_api, cinder_scheduler,
cinder_volume and cinder_backup, on the control and storage nodes of the example inventory, selected by the tag
cinder. iscsid and tgtd are in the iscsi play, not under -t cinder (Tags
§3.1). 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¶
No operation page gives a command line for the cinder tag. The scenario above describes
kolla-ansible -t <svc> reconfigure for an API service such as keystone, glance, cinder, heat or placement; its command
example is keystone (Reconfigure a single service
§1.1).
Impact and risk¶
Dependencies¶
- Dependencies: Component dependencies §3
Evidence¶
- Fact sheet: fact sheet C §3
- Image side: Kolla images
§4 (row
cinder-api), Kolla images §5
Before and after a run¶
- Pre-execution checklist, step 6 (workload gates): no live migrations,
resizes, image uploads or volume migrations in flight on the targeted hosts; one of its two checks is
openstack volume list --status *ing. - 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. Glance and cinder transfers in progress are SIGKILLed after 10 s (R24). - fact sheet C §3.8, item 7:
the cinder role itself does not target computes; enabling
enable_cinder_backend_iscsi/LVM also flips glance-api to privileged with/dev, so glance-api is recreated. - 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, e.g.cinderv2andcinderv3for cinder, 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, row
cinder: nohost/backend_host/cluster; etcd coordination uses only the first etcd host; Ceph backup driver default without a Ceph config. Status: CODE. - F3, "
docker_graceful_timeoutanddocker_client_timeoutare ignored" CODE: on every restart, a service still running 10 s after SIGTERM is SIGKILLed with its in-flight work (heat-engine, cinder copies, glance uploads). - F5, "
reconfigure=deploy": a reconfigure re-runs Keystone registration, DB creation/grants and the DB-sync bootstrap containers of most services CODE. - fact sheet C §3.8,
"Operational notes", nine items: no
host/backend_host/clusterset in cinder.conf; cinder-volume restart impact; cinder-backup restart; upgrade restarts every cinder-volume and cinder-backup at once; oddity: backup driver vs. ceph files; multipath is never configured; compute-host touchpoints; external Ceph needs cinder-volume and cinder-backup hosts in thestoragegroup; the sanity check (if enabled) creates a 1 GB volume on every deploy/reconfigure. - fact sheet C §8,
"NOT AVAILABLE list", items 5 to 7: NOT AVAILABLE: whether cinder-backup works with default
cinder_backup_driver=cephandcinder_backend_ceph=no; whether the volumes owned by one of several RBD cinder-volume nodes can still be managed while that node is down, and what state an in-flight create-from-image is in after a cinder-volume restart; Cinder RPC pinning afterkolla-ansible upgrade. - fact sheet C §6: a reconfigure with a bumped image tag runs cinder's
db syncwithout its online data migration step; whether this leaves cinder in a partially upgraded state is NOT AVAILABLE. - Kolla images §6, item 10: recursive chown on data volumes at every
start:
kolla_set_configsmakes onechownper file of thecindervolume, twice for cinder-volume, on everyCOPY_ALWAYSstart CODE. - What is not known: fact sheet C has its own NOT AVAILABLE list, and its §3.8 is among the sections that contain NOT AVAILABLE marks.
- Open questions has no entry on Cinder.
Service card¶
The rows of the card are explained on the Components page.
| Item | Value |
|---|---|
| Play | site.yml:683 |
| Tags | cinder |
| Play host patterns | cinder-api, cinder-backup, cinder-scheduler, cinder-volume |
| Node types in play (example inventory) | control, storage |
| Node types running its containers | control, storage |
| Containers | cinder_api, cinder_scheduler, cinder_volume, cinder_backup |
deploy/reconfigure flow (tasks/) |
register → config → check-containers → clone (if) → bootstrap → flush handlers → check |
| Task files | bootstrap.yml, bootstrap_service.yml, check-containers.yml, check.yml, clone.yml, config.yml, copy-certs.yml, deploy-containers.yml, deploy.yml, external_ceph.yml, loadbalancer.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, register.yml, stop.yml, upgrade.yml |
| Templates | cinder-api.json.j2, cinder-backup.json.j2, cinder-scheduler.json.j2, cinder-volume.json.j2, cinder-wsgi.conf.j2, cinder.conf.j2 |
| Handlers (definition order) | Restart cinder-api container; Restart cinder-scheduler container; Restart cinder-volume container; Restart cinder-backup container |
| Key variables | enable_cinder, enable_cinder_backend_*, cinder_backend_ceph, cinder_backup_driver, cinder_coordination_backend |
| Role dependencies | common (meta) |
Related¶
- Reconfigure a single service — what
-t <svc> reconfigureruns for an API service such as cinder, with the risks and the verification - iscsid / tgtd — the
iscsirole, on which cinder-volume (LVM) depends - Glance — enabling the cinder iSCSI/LVM backend recreates glance-api
- Nova — Nova needs Cinder for volume-backed boots
- R24 — cinder-volume copies are among the in-flight work SIGKILLed 10 s after SIGTERM
- Pre-execution checklist — the eight checks before every production run
- Components — the other component pages