Risk and impact¶

Potentially dangerous operations on a running Kolla-Ansible Ussuri platform, what a tag really executes, and why a small change can create a large workload. Ratings are relative to a production cloud with running VMs.
Start from¶
- By operation: the Operations catalogue has one row per operation page, with the risks that the page names.
- By tag: Tags §3 says what a tag executes, on which hosts, and which containers can restart. The tag index goes from a tag to its component page.
- By component: Components has one page per component; its "Where to look" section lists the risks of the component's tag when the study names some.
- By severity: the summary table of the risk register gives the likelihood and the severity of each of the 25 risks.
Pages¶
- Risk register — 25 risks (R1–R25), each with what actually happens, its blast radius, VM and API impact, likelihood, severity, precautions and evidence.
- What a tag really executes — How tags actually select work in Kolla-Ansible Ussuri, and what each important tag executes: on which hosts, and which containers can restart.
- Tag index — One row per tag: the component page of the tag, or the full row for the three rows without a component page.
- Why a small change creates a large workload — Six small changes, each with why it is large and its source, and the per-host work that every run pays.
Related¶
- Pre-execution checklist — what to check before a run
- Open questions — the open questions behind the NOT AVAILABLE cells of the risk register
- Technical findings — the fifteen headline findings, each with its evidence
- Conventions and evidence labels — the impact classes shown on
operation pages, among them
critical - Compute scaling §5 — the work multiplier and the restart multiplier