Skip to content

OzarLand home An OzarLand project

Kolla-Ansible Academy

Ussuri · Kolla-Ansible 10.x tag ussuri-eol

Source-level study of Kolla-Ansible 10.x (OpenStack Ussuri, tag ussuri-eol): what each tag really executes and what commands do to a running platform.

A diverse group of travellers studies a map on a wooden terrace above a bright island city and sea.
Lumo, the guide, waves hello while raising a glowing brass lantern.

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.)

Start the learning journey

Start from what you need

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:

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

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:line citation 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 ussuri-eol (openstack/kolla-ansible, tag ussuri-eol, HEAD 8a94fe9). All conclusions come from the Ussuri implementation, not from newer releases (Method and limits of the study).

Component Version
OpenStack release Ussuri (openstack_release: "ussuri", ansible/group_vars/all.yml:530)
Kolla-Ansible 10.x series, the Ussuri series: tag ussuri-eol, commit 8a94fe9. The last numbered release tag of the series in openstack/kolla-ansible is 10.4.0; ussuri-eol is a later commit
Kolla (images) tag ussuri-eol of openstack/kolla
Ansible 2.9.27
  • 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, 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.