Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-14823

Various typos in CL170ch03/CL0003L lab

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • CL170 - RHOSO18.0-en-1-20241127
    • CL170
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • en-US (English)

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/cl170-18.0/pages/ch03s05
      Reporter RHNID: gls-ftaylor
      Section Title:             h2. Lab: Customize OpenStack Services                                                           

      Issue description

      Step 1.2 shows `oc project openstack`, but that was never mentioned in the step (just in the solutions).  If you don't want to mention that in step 1, that command probably belongs just before step 2.2 where we actually do something that would require that namespace/project.

       

      Step 2 says:

      Use the oc api-resources command to fetch short names, which you can use in place
      of the OpenShiftControlPlane CR

      CHANGE TO:

      Use the oc api-resources command to fetch short names, which you can use in place
      of the OpenStackControlPlane CR

       

      (change OpenShift to OpenStack)

      (This is just like the issue in ch03s04)

       

      Step 2 also mentions that you can use a short name to refer to the CR.  I don't think that is necessary.  They did that in the GE, so you should be able to just use `oc get oscp` without further explanation.

       

      Step 2.2 shows `oc get osctlplane`.  Why not just use `oc get oscp`?

       

      In step 2, we showed students how to find the short names.  In step 3 we use `oc get oscp`, but in step 5 we revert to OpenStackControlPlane for some reason.  If there is a reason, please explain in step 5.  Otherwise, just use `oscp`.

       

      Step 3 says:
      Apply the changes to the openstack-control-plane custom resource (CR) of the OpenStackControlPlane kind.

      However, we actually apply the changes in step 4.  Maybe change that line to:

      Verify that the name of the CR is `openstack-control-plane` and the kind is `OpenStackControlPlane`.

       

      In ch01s03, we told students to use --dry-run=client.  In ch03s05 step 4.1, we do actually use --dry-run=client.  However, in every other place, we use --dry-run=server.  Was that intentional?  If so we need more context/content.  Otherwise we should pick the type of dry run (server or client) and make it consistent throughout the course and lessons.  This applies to several places in ch03 (including the content and ch03s04 GE step 4.3) as well as ch07. 

       

      In step 4.1 we show --validate instead of --validate=true like we've show everywhere else.  It seems to work, but why change the standard here?  Please make it consistent.

      Step 4.4 command is:

      [student@workstation ~]$ oc get OpenStackControlPlane -n openstack -w

      CHANGE TO:

      [student@workstation ~]$ oc get oscp -w

       

      We already used the shortname earlier, so use `oscp` here too.  We also change the project to openstack, so `-n openstack` is not needed.

       

      Step 5 command is:

      oc get pods -n openstack | grep horizon

      `-n openstack` is redundant (like step 4.4), so change it to:

      oc get pods | grep horizon

      OR

      oc get pods -l service=horizon

      (like we showed in the GE)

              rhn-gps-adandrea Ashley D’Andrea
              gls-ftaylor Forrest Taylor (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: