Skip to content

Risk and impact

A white stone lighthouse stands on a green sea cliff above distant ships and terracotta roofs.

Potentially dangerous operations on a running Kolla-Ansible 2023.1 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, and whether it still applies to 2023.1 (R25 does not; R5, R8, R9, R10 and R24 changed).
  • What a tag really executes — How tags actually select work in Kolla-Ansible 2023.1, 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.