Method and limits of the study¶
A source-level study of Kolla-Ansible ussuri-eol (openstack/kolla-ansible, tag ussuri-eol, HEAD 8a94fe9). It
covers how Kolla-Ansible orchestrates an OpenStack platform, what each tag really executes, how runs scale with the
number of compute nodes, and what Kolla-Ansible commands do to a running production platform.
All conclusions come from the Ussuri implementation, not from newer releases. Each one is labelled with its evidence level: CODE or NOT AVAILABLE (see Evidence labels).
Note
Key answers
- Limits of the study: source code only and no timings; every statement about data-plane or VM impact is NOT AVAILABLE (Limits of this study).
Method¶
| Phase | What was done |
|---|---|
| 1. Source exploration | Cloned ussuri-eol; read tools/, site.yml, nova.yml, gather-facts.yml, group_vars/, the kolla_docker/kolla_toolbox modules, merge_configs, filters, and the common, nova, nova-cell, neutron, openvswitch and service-* helper roles in full. Also read the kolla image repository (ussuri-eol) for the image start path and the one-shot containers (Kolla images) |
| 2. Static analysis | Generated tables of all plays, containers, roles and handlers (tools/). Five parallel source-reading passes produced the fact sheets, which were then spot-checked |
| 3. Dependency mapping | Template references, transport URLs and group loops → Component dependencies |
| 4. Performance analysis | Per-host task chains read from the role sources and the --list-tasks listing → Compute scaling |
| 5. Operational analysis | Day-2 scenarios traced through the role sources → Operations, Risk register |
| 6. Validation | Ansible 2.9.27 (the supported version): --list-tags/--list-tasks listings of the real playbook (Ansible listings); loop-notify and tag inheritance read in the Ansible 2.9.27 source; the kolla_docker timeout override read in the module source |
Limits of this study¶
- Source code only. The study rests only on reading source code: kolla-ansible
ussuri-eol, the kolla image repositoryussuri-eol, and the Ansible 2.9.27 source (2.8.20 for comparison). The only Ansible output used is its--list-tags/--list-tasksparse of the playbooks (Ansible listings), which runs nothing against a host. The semantics ofkolla_set_configs --checkare read from the kolla source (Kolla images §3). - There are no timings. No run is used, so no wall time is known; work can only be counted from the code (Compute scaling).
- No container or VM behaviour is used as evidence. Every statement about data-plane or VM impact is NOT AVAILABLE.
- The depth of reading varies. The core services are traced in the pages of the study other than the fact sheets; the other roles are covered by the fact sheets only.
- The kolla image sources were read, not built or run. From the kolla
ussuri-eolrepository: the base start path (docker/base:Dockerfile.j2,start.sh,set_configs.py,copy_cacerts.sh,httpd_setup.sh,sudoers, healthcheck scripts) and the start scripts of the images listed in Kolla images (Nova, Neutron, Open vSwitch, OVN, Keystone, Glance, Placement, Cinder, Heat, Horizon, Barbican, Octavia, Manila, Swift, MariaDB, RabbitMQ, memcached, HAProxy, keepalived incl.check_alive.sh, fluentd, cron, kolla-toolbox, chrony, iscsid, tgtd). Of the other images only theironic-apibootstrap branch and thebifrost-deployENTRYPOINT/CMDwere read, and every Dockerfile was searched forHEALTHCHECKand forENTRYPOINT/CMDoverrides. What the scripts do against real services and data is NOT AVAILABLE.
Related¶
- Conventions and evidence labels — the definition of CODE and NOT AVAILABLE
- What is not known — everything marked NOT AVAILABLE, by topic
- Open questions — the open questions Q1–Q14
- Technical findings — the fifteen headline findings, each with its evidence
- Per-role fact sheets — the five fact sheets and how they were checked
- Ansible listings — the
--list-tagsand--list-taskslistings used in the validation phase
To remember
Lumo: if you keep only 5 things from this page, keep these.
- The study rests only on reading source code: kolla-ansible
ussuri-eol, the kolla image repositoryussuri-eoland the Ansible 2.9.27 source. - All conclusions come from the Ussuri implementation, not from newer releases.
- There are no timings: no run is used, so no wall time is known; work can only be counted from the code.
- No container or VM behaviour is used as evidence: every statement about data-plane or VM impact is not available. NOT AVAILABLE
- The kolla image sources were read, not built or run: what the scripts do against real services and data is not available. NOT AVAILABLE
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.