Hi, I'm Lumo, your guide
New to Kolla-Ansible Day-2 operations? We'll take this one step at a time. The learning journey walks you through five stages, and every page tells you where you are and what to read next. (My name comes from lumen, Latin for light: like my lantern, the Academy sheds light on what the code really does.)
Continue where you left off: Conventions and evidence labels (stage 1) Continue where you left off: Ten things to know before a production run (stage 1) Continue where you left off: Glossary (stage 1) Continue where you left off: Find it fast (stage 1) Continue where you left off: Repository architecture (stage 2) Continue where you left off: Deployment execution flow (stage 2) Continue where you left off: Kolla images: start path and one-shot containers (stage 2) Continue where you left off: Compute scaling and performance (stage 2) Continue where you left off: Pre-execution checklist (stage 3) Continue where you left off: Predict and inspect a run (stage 3) Continue where you left off: Reconfigure a single service (stage 3) Continue where you left off: Write config first, apply in controlled batches (stage 3) Continue where you left off: Command quick lookup by tag (stage 3) Continue where you left off: What a tag really executes (stage 4) Continue where you left off: Why a small change creates a large workload (stage 4) Continue where you left off: Risk register (stage 4) Continue where you left off: Known bugs and limitations (stage 4) Continue where you left off: Component dependencies (stage 5) Continue where you left off: Nova deep dive (stage 5) Continue where you left off: Technical findings (stage 5) Continue where you left off: Method and limits of the study (stage 5) Continue where you left off: What is not known (stage 5)
Start from what you need¶
-
Operations: one page per Day-2 operation, with its commands, its impact classes and the risks it names.
-
A run did something unexpected
Troubleshooting: where to start during an incident. A symptom index, the known bugs and limitations, the open questions, and what is not known.
-
I need the facts about one component
Components: one page per OpenStack service and per infrastructure component, each ending with its service card.
-
I need to judge the risk of a change
Risk and impact: the 25 rated risks (R25 does not apply to 2023.1), what a tag really executes, and why a small change creates a large workload.
-
I want to understand how a run works
Concepts: repository architecture, deployment execution flow, compute scaling, and what the kolla images do at container start.
-
Reference: findings, glossary, generated inventory, per-role fact sheets, Ansible listings, and the method and limits of the study.
Seven operator situations, from an incident to a failed VM deployment, are mapped to the pages to open first in Start from a situation.
Frequently used procedures¶
The operation pages that Find it fast and Ten things to know before a production run point to most often:
- Reconfigure a single service — what a single-service reconfigure such as
-t keystoneruns, and what the tag also touches - Reconfigure Nova — what
-t nova reconfigureruns on the controllers and on every compute - Write config first, apply in controlled batches —
genconfig, thendeploy-containers --limitbatch by batch, or a rollingreconfigurewithANSIBLE_SERIAL - Update container images — how
pull,deploy,reconfigureandupgradetreat images - Add a compute node — the three commands with
--limit, and whatdeploy --limittouches on the other hosts
Every operation page is in the Operations catalogue, and the Command quick lookup by tag has one row per command and tag.
Before any production run¶
- Pre-execution checklist — the eight checks to make before every production run
- Predict and inspect a run — the commands that show what a run would target, render and restart
- Ten things to know before a production run — ten points, most of them with the section that gives the evidence
Recently updated¶
Every change is in the commit history of the repository.
How to read this portal¶
Every statement carries one of two evidence labels, defined in Evidence labels:
- CODE shown by the sources, with a
path:linecitation nearby. - NOT AVAILABLE the sources do not establish it.
An operation page shows its impact classes under its title. A class says that at least one command of the page has that impact, not that all do. The classes and the sections that support each one are in Operation impact classes:
read-only— the corpus says the command changes nothing.writes-config— the command renders config and restarts no Docker container.pulls-images— the command downloads images; running containers do not change.restarts-on-drift— the command can restart containers, only if drift is detected.recreates-containers— the command recreates containers (stop, rm, create, start) when their image or parameters differ.critical— the page covers an operation rated Critical in the risk register.maintenance-window— the corpus asks to plan the operation as a maintenance.recovery— the page is a backup or recovery procedure.
Find it fast lists typical operator questions and the section that answers each one. There are four more ways into the study: by tag (Tag index), by service (Components), by term (Glossary) and by what is not known (What is not known). This page adds no finding of its own: every entry restates what the linked section says, and the linked section is the reference.
Scope¶
The portal is a source-level study of Kolla-Ansible 2023.1-eol (openstack/kolla-ansible, tag 2023.1-eol, commit
4891a21). All conclusions come from the 2023.1 implementation, not from older or newer releases (Method and limits
of the study).
| Component | Version |
|---|---|
| OpenStack release | 2023.1 (openstack_release: "2023.1", ansible/) |
| Kolla-Ansible | 16.x series, the 2023.1 series: tag 2023.1-eol, commit 4891a21 |
| Kolla (images) | tag 2023.1-eol of openstack/kolla, commit de82941 |
| ansible-collection-kolla | tag 2023.1-eol (pinned by requirements.yml: unmaintained/) |
| Ansible | ansible-core 2.14.18 (tools/ accepts 2.13 to 2.14) |
- Source code only. The study rests only on reading source code: kolla-ansible
2023.1-eol, the kolla image repository2023.1-eol, ansible-collection-kolla2023.1-eoland the ansible-core 2.14.18 source. The only Ansible output used is its--list-tags/--list-tasksparse of the playbooks, which runs nothing against a host. - 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.
The other limits are in Limits of this study.