Please fill in the following information:

Issue description

Step 1. This states that you can either log in to the CLI or login to the web interface, however, all subsequent commands are done assuming you have logged in using the CLI.  This happens in several other places in the course (so should be fixed there as well).

We either need to show alternative solutions where we have the CLI and the web interface, or just mention the web interface, but explain that the solutions/steps assume you are using the CLI.

Step 2.1 shows `egrep -e "^NAME|nova"`

First, I've seen this go back and forth from this to `grep -e NAME -e nova`.  I prefer the latter-use `-e NAME -e nova` because it is easier to understand as a beginner (otherwise you have to understand `egrep`, `^`, and `|`).  Pick one method and mix all the ways we show it in the course.

Second, there is no reason in this particular command to grep for NAME at all.  There is no header to look for, so remove the NAME part anyway.  Just `| grep nova`.

Step 2.4. Why do we do this?  What are we supposed to see?  What is interesting/important?  We need more context to guide the students for why this might be important.

Step 3 should include information in why NovaCompute does not show anything (talking to the developers, it sounds like it was a bug).  We should tell them it is a bug and explain what it should show.

Step 4.1 I think I have a different issue open for the movement between jq/jsonpath and yq.  We should be able to do everything with a newer version of yq.

Step 5.5 seems out of the blue.  How do I find this secret?  Is there some other way to view this information?  It seems like we lead the students to information in the previous steps, but this one it seems like we lead them right there without any direction.  Either find this a different way, or lead them to it in more steps.

Step 6, 6.2 and 6.2 seem like a lot of work to get to the compute nodes.  Can't we create an entry in ~/.ssh/config to get them there?  Something like:
  

Host compute*
  ProxyJump lab@utility

...then they can `ssh root@compute01.srv.example.com` from workstation.

It seems like we are making it harder than it should be by making them jump through the proxy host (utility).

Step 6.4 I thought nslookup was deprecated?  In any case I think host or dig are better commands to view DNS information.

Step 6.5 Is curl the best way to test this?  It always shows a not allowed or other error.  Why not just use nc -v rabbitmq-cell1.openstack.svc 5671?  It shows the connection, then reset by peer.

Step 6.6 should be prefaced by `podman ps` to view teh container names.

Step 6.7 Ah, in the container, you don't have `nc`, you only have curl.  So, take my comment about step 6.5 with a grain of salt.