Skip to content

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/kolla-ansible, site.yml, nova.yml, gather-facts.yml, group_vars/all.yml, 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/extract_kolla_inventory.py). 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 repository ussuri-eol, and the Ansible 2.9.27 source (2.8.20 for comparison). The only Ansible output used is its --list-tags/--list-tasks parse of the playbooks (Ansible listings), which runs nothing against a host. The semantics of kolla_set_configs --check are 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-eol repository: 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 the ironic-api bootstrap branch and the bifrost-deploy ENTRYPOINT/CMD were read, and every Dockerfile was searched for HEALTHCHECK and for ENTRYPOINT/CMD overrides. What the scripts do against real services and data is NOT AVAILABLE.

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 repository ussuri-eol and 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.

1. Does the Ussuri study use any run against a host as evidence?
Show the answer

Answer: No: the only Ansible output used is the --list-tags/--list-tasks parse of the playbooks, which runs nothing against a host. The study rests only on reading source code: kolla-ansible ussuri-eol, the kolla image repository ussuri-eol, and the Ansible 2.9.27 source. Read the section.

2. Can you take restart or deploy wall times from this study?
Show the answer

Answer: No: no run is used, so no wall time is known; work can only be counted from the code. There are no timings. The performance analysis read per-host task chains from the role sources and the --list-tasks listing; it ran nothing. Read the section.

3. Were the kolla images built and run to see what their start scripts do?
Show the answer

Answer: No: the kolla image sources were read, not built or run. The base start path and the start scripts of the listed images were read from the kolla ussuri-eol repository. What the scripts do against real services and data is NOT AVAILABLE. Read the section.