Common: fluentd, cron, kolla_toolbox¶
This page is the starting point for the common role: the containers fluentd, kolla_toolbox and cron, on the
compute, control, monitoring, network and storage nodes of the example inventory. The role is a meta dependency of 68
roles (not memcached, multipathd or the helper roles): it runs in the first play that reaches each host and inherits
the tag of that play, and -t common alone is a no-op. 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: Apply
commonchanges (fluentd, cron, kolla_toolbox) - Command: Apply
commonchanges (fluentd, cron, kolla_toolbox) §1.1
Impact and risk¶
- What the tag executes (
common): Tags §3 and Tags §3.1, rowscommon; why it is a no-op: Tags §2.1 - Risks: R25, R2
Dependencies¶
- Dependencies: Component dependencies §1, Component dependencies §2 (row "Fluentd"), Component dependencies §5
Evidence¶
- Fact sheet: – (see Repository architecture §5.1)
- Image side: Kolla images §5 (rows
fluentd,cron,kolla-toolbox) - Also: Apply
commonchanges (fluentd, cron, kolla_toolbox); handlers: Tags §5
Before and after a run¶
- Pre-execution checklist, step 7 (scope): never use
-t commonexpecting it to do something. - R25, precautions: use
-t chrony(all hosts) or a service tag; verify withdocker exec … kolla_set_configs --check. - R2, precautions: treat
enable_*changes as fleet-wide changes; roll out with--limitbatches. - Apply
commonchanges (fluentd, cron, kolla_toolbox) §4, verification: before,genconfig, thenkolla_set_configs --checkin each offluentd,cronandkolla_toolbox(1 in any of them = all three will restart, by loop-notify); the check does not cover image or volume changes. After,docker psshows fresh start times,docker logs fluentdhas no parse errors and logs still reach the configured output. - Tags §3.1, row
common: config files that can change: none (no-op) CODE; safe on its own: "safe but does nothing".
Known limits and open points¶
- Known bugs and limitations, row
common:-t commonno-op (F2). Status: CODE. - F2, "
-t commonis a no-op": tags on the dynamicinclude_tasksdo not propagate to the included tasks CODE. Why it matters:commonchanges (fluentd/cron/toolbox) are applied by whatever run first reaches the host, often unexpectedly. - F1, "Loop-notify amplification": a change for one container restarts every container of that role on that host CODE.
- Q10, answered from the source CODE: the code that produces F1 and F2 is the same in Ansible 2.8.20 and 2.9.27.
- F6, "Global inputs are rendered into per-host files":
enable_*flags, RabbitMQ/memcached membership, service passwords and the external FQDN end up in compute-side files CODE. - What is not known: the sources do not
establish whether restarts that touch none of the containers the study traces to running VMs (the
commoncontainers, the control-plane services) affect running VMs, APIs or traffic another way. - What is not known, row "fluentd": the sources do not establish whether the tail read positions survive a config-only restart, and whether they are lost on a recreate.
- Kolla images §6, item 9: a changed
rabbitmq_cluster_cookierecreates the brokers but their cookie file keeps the old value, whilekolla_toolboxgets the new one CODE (consequences NOT AVAILABLE).
Service card¶
The rows of the card are explained in How to read a service card.
| Item | Value |
|---|---|
| Play | meta dependency of 68 roles (not memcached, multipathd or the helper roles); runs in the first play that reaches each host |
| Tags | inherits the tag of the first play reaching the host (-t common alone is a no-op) |
| Play host patterns | first play reaching each host (chrony by default) |
| Node types in play (example inventory) | compute, control, monitoring, network, storage |
| Node types running its containers | compute, control, monitoring, network, storage |
| Containers | fluentd, kolla_toolbox, cron |
deploy/reconfigure flow (tasks/) |
config → check-containers → bootstrap → flush handlers |
| Task files | bootstrap.yml, check-containers.yml, check.yml, config.yml, copy-certs.yml, deploy-containers.yml, deploy.yml, main.yml, precheck.yml, pull.yml, reconfigure.yml, stop.yml, upgrade.yml |
| Templates | admin-openrc.sh.j2, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, conf/, cron-logrotate-ansible.conf.j2, cron-logrotate-aodh.conf.j2, cron-logrotate-barbican.conf.j2, cron-logrotate-blazar.conf.j2, cron-logrotate-ceilometer.conf.j2 … (+63) |
| Handlers (definition order) | Restart fluentd container; Restart kolla-toolbox container; Initializing toolbox container using normal user; Restart cron container |
| Key variables | enable_fluentd, enable_* (all, via td-agent/, elasticsearch_address, enable_monasca |
| Role dependencies | none |
Related¶
- Apply
commonchanges (fluentd, cron, kolla_toolbox) — the commands that pushcommonchanges, what restarts and how to verify - Chrony —
-t chronyreaches every host (chrony runs everywhere by default) and is the recommended way to pushcommonchanges - Tags §2.1 — the tag semantics that make
-t commona no-op - Repository architecture §5.1 —
the
common_runguard and the globalfluentdandcronconfigs - Why a small change creates a large workload —
enable_<new service>: yeschanges fluentd/logrotate on every host - Components — the other component pages