Barbican¶
This page is the starting point for Barbican, the barbican role: the containers barbican_api,
barbican_keystone_listener and barbican_worker, on the control nodes of the example inventory, selected by the tag
barbican. Its DB sync runs on every deploy and reconfigure, and barbican_crypto_key comes from passwords.yml
(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¶
No operation page gives a command line for the barbican tag, and the tag has no row of its own in Tags
§3 or in the Tag index. What the
study says about running it is in fact sheet D: the plays the tag selects
(§1.1) and the task flow
per action
(§1.3).
Dependencies¶
- Dependencies: Component dependencies §3
Evidence¶
- Fact sheet: fact sheet D §1
- Image side: Kolla images
§4 (row
barbican-api), Kolla images §5
Before and after a run¶
- Pre-execution checklist, step 8 (rollback material): previous
/etc/kolla/config,globals.yml,passwords.ymland inventory under git. - fact sheet D
§1.6: the crypto
KEK lives in
passwords.yml(barbican_crypto_key); this key must be in thepasswords.ymlbackup. - fact sheet D
§1.3:
reconfigure=deploy, so keystone registration and the DB bootstrap container re-run on every reconfigure. - R2, precautions for enabling or disabling a service that has a logrotate or fluentd
input entry (
enable_Xfor most OpenStack services, e.g. barbican): treatenable_*changes as fleet-wide changes; roll out with--limitbatches. - Reconfigure Nova §3, row
enable_barbican: yes(Barbican not even deployed):nova.confis rewritten everywhere (adds[barbican]), withtd-agent.confandlogrotate.conf; all nova containers restart, libvirt included on every compute, with fluentd, cron and kolla_toolbox CODE.
Known limits and open points¶
- What is not known: the sources do not establish whether
a
[barbican]section rendered before Barbican exists has any effect before encrypted volumes are used. - Execution flow §2.2: Barbican
comes after Nova, Cinder and Glance in the deployment order; with
enable_barbican, Nova and Cinder render a[barbican]section, and on a first deploy they start configured with it before Barbican exists CODE. - fact sheet D
§1.6,
"Operationally notable", four points: the crypto KEK lives in passwords.yml (NOT AVAILABLE: whether losing or changing
barbican_crypto_keymakes stored secrets undecryptable); p11_crypto: the library path is not mounted into the containers and no task generates the MKEK or HMAC keys (NOT AVAILABLE: what else an HSM setup needs); runningkolla-ansible deploy -t barbicanalone does not run the keystone play, so thebarbican_notificationstopic is not enabled in keystone.conf (NOT AVAILABLE: whether barbican-keystone-listener then receives project-deletion events); copying the policy file usesbecome: true. - fact sheet D §7, item 15: Barbican and other bootstraps (octavia, manila, ceilometer, masakari, zun, cyborg) re-run their DB sync container on every deploy/reconfigure.
- 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: fact sheet D has its own NOT AVAILABLE list, and its §1.6 is among the sections that contain NOT AVAILABLE marks.
- Known bugs and limitations, Open questions and Findings have no entry on Barbican.
Service card¶
The rows of the card are explained on the Components page.
| Item | Value |
|---|---|
| Play | site.yml:995 |
| Tags | barbican |
| Play host patterns | barbican-api, barbican-keystone-listener, barbican-worker |
| Node types in play (example inventory) | control |
| Node types running its containers | control |
| Containers | barbican_api, barbican_keystone_listener, barbican_worker |
deploy/reconfigure flow (tasks/) |
register → config → check-containers → clone (if) → 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 | barbican-api.ini.j2, barbican-api.json.j2, barbican-keystone-listener.json.j2, barbican-worker.json.j2, barbican.conf.j2 |
| Handlers (definition order) | Restart barbican-api container; Restart barbican-keystone-listener container; Restart barbican-worker container |
| Key variables | enable_barbican, barbican_crypto_key (passwords.yml) |
| Role dependencies | common (meta) |
Related¶
- fact sheet D §1 — the per-role evidence: plays, services, task flow, config files and dependencies
- Keystone —
-t barbicanalone does not run the keystone play, so thebarbican_notificationstopic is not enabled in keystone.conf - Nova — the compute
nova.confchanges when barbican is enabled - Common: fluentd, cron, kolla_toolbox — enabling a service such as barbican changes
td-agent.confand/orlogrotate.confon every host - Why a small change creates a large workload —
enable_<new service>: yeschanges fluentd/logrotate on every host andnova.confsections on every compute - Components — the other component pages