Architecture and concepts¶

How Kolla-Ansible 2023.1 is built, how it decides what runs when, how its work grows with the number of compute nodes, and what the kolla images do when a container starts. Repository architecture defines the vocabulary that the other pages build on.
Pages¶
- Repository architecture — How the machine is built: which entry points exist, how a
CLI command becomes an
ansible-playbookrun, howsite.ymlis laid out, what every service role has in common, which custom modules actually touch the hosts, and what ansible-collection-kolla (pulled byrequirements.yml) contributes. - Deployment execution flow — How Kolla-Ansible 2023.1 decides what runs when: play
order, the steps inside each role, handler flush points, batching, and how
deploy,reconfigure,upgrade,deploy-containers,genconfig,pullandstopdiffer. - Compute scaling and performance — Which Kolla-Ansible 2023.1 operations grow with the number of compute nodes, why, and how to bound them. No timings are given: work is counted as operations read from the source.
- Kolla images: start path and one-shot containers — What the kolla images do when a container
starts, and what the one-shot containers that Kolla-Ansible starts with
KOLLA_BOOTSTRAP,KOLLA_UPGRADE,KOLLA_OSMand similar variables actually run. The images were read, not built or run.
Related¶
- What a tag really executes — how tags select the work described here
- Component dependencies — runtime communication, which is not deployment order
- Nova deep dive — the nova plays
- Generated inventory — every play, container, role and handler
- Glossary — the terms the study uses, with the place where each is defined