From ff2ece6aa07d03c596965d79e280c4e2358fde59 Mon Sep 17 00:00:00 2001
From: Michael Sherman <shermanm@uchicago.edu>
Date: Wed, 21 Aug 2024 12:49:46 -0500
Subject: [PATCH] update typos

---
 docs/xena-antelope-upgrade.md | 38 +++++++++++++++++------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/docs/xena-antelope-upgrade.md b/docs/xena-antelope-upgrade.md
index 2eebb7f2..bee93c43 100644
--- a/docs/xena-antelope-upgrade.md
+++ b/docs/xena-antelope-upgrade.md
@@ -41,7 +41,7 @@ Welcome to the Antelope/2023.1 Release of CHI-in-a-Box! This release rolls up a
 * Interface name changes during release-upgrade: Dependng on the network card driver in use, the "stable interface name" may change unexpectly after the upgrade, potentially breaking remote acess to the controller node. To avoid this, ensure each interface in netplan has a `match` stanza, like the following:
     ```
     dataplane1:
-    match:
+      match:
         macaddress: 04:3f:72:ff:9b:33
         driver: mlx5_core
     set-name: dataplane1
@@ -147,37 +147,35 @@ After deploying the new version, you will instead see containers named `letsencr
 1. Make a backup of:
     1. Deploy host: chi-in-a-box and site-config directories
     1. Control node: /etc/kolla directory
-1. Shut down haproxy container to prevent users from modifying system state
 1. Use ./cc-ansible mariadb_backup to create a full DB backup
 1. Copy DB backup from mariadb_backup container to somewhere else
 
-Note: don’t shut down other containers! Especially rabbitmq will be a problem if shut down early.
-
 ### Execute:
 
 #### On target control node:
 1. Get to the latest stable package versions and clean up old kernels:
-1. apt-get update && apt-get dist-upgrade
-1. Reboot, then apt-get autoremove
-1. Do-release-upgrade to move from 20.04 -> 22.04
+    1. `apt-get update && apt-get dist-upgrade`
+    1. Reboot, then `apt-get autoremove`
+1. ensure netplan interfaces have a `match` stanza
+1. `do-release-upgrade` to move from 20.04 -> 22.04
 1. Reboot
 1. Check on interface definitions and any apt sources that need updating
-1. Delete kolla virtualenv from /etc/ansible/venv
+1. Delete kolla virtualenv from `/etc/ansible/venv`
 
 #### On deploy host:
-1. install python3.10
-    1. TODO: add instructions and PPA
-1. Delete chi-in-a-box venv from chi-in-a-box/venv
+1. Delete chi-in-a-box venv from `chi-in-a-box/venv`
 1. Delete any tools venv from site-config
-1. Delete any venv from /etc/ansible/venv
+1. Delete any venv from `/etc/ansible/venv`
 1. Update chi-in-a-box via:
-    1. git checkout stable/2023.1
-    1. git pull
-    1. git submodule update –init
+   ```
+   git checkout stable/2023.1
+   git pull
+   git submodule update –init
+   ```
 1. Install new tools into venv via:
-    1. cc-ansible install_deps # this doesn’t need a site-config
+    1. `cc-ansible install_deps` # this doesn’t need a site-config
     1. Source the new venv:
-       Source venv/bin/activate
+       `source venv/bin/activate`
 1. Update site-config/inventory/hosts by:
     1. mv inventory/hosts inventory/hosts.bak
     1. cp chi-in-a-box/site-config.example/inventory/hosts site-config/inventory/hosts
@@ -205,8 +203,10 @@ Note: don’t shut down other containers! Especially rabbitmq will be a problem
 1. Cc-ansible upgrade (this should now complete)
 1. Apply cleanups for keystone admin endpoints:
     1. Cc-ansible deploy –tags keystone
-    1. TODO: script to remove all existing admin api endpoints
-
+    ```
+    openstack endpoint list --interface admin -f value | \
+    awk '!/keystone/ {print $1}' | xargs openstack endpoint delete
+    ```
 
 ### Verification and cleanup after upgrade