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

Mandatory course-wide updates

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/
      Reporter RHNID: gls-ftaylor
      Section Title: Entire course (Lectures, Guided Exercises, and Labs)

      Do not fix until all in-progress/review bugs are Done, but DO please fix.

      This Jira issue is for bugs that were originally located within lesson-targeted bug reports, but that are actually course-wide, and that must be fixed.

      This was created because some of the other CL170 Jira bugs contain issues that are actually course-wide and not limited to the lessons for which they were reported.

      Please note that the following three issues have been factored out to their own Backlog items:

      • Excessive switching between the openstack and default projects: Moved to PTL-15228
      • Remove web console from Step 1: Moved to PTL-15232
      • Consistent grep usage: Moved to PTL-15233

      Use bash when connecting to OpenStack pods: Use oc rsh --shell=/usr/bin/bash openstackclient for the connection to the openstackclient pod throughout the course. You also get tab-completion if you do that. This was reported in PTL-14863 and PTL-14865 and has been copied here. 

      TODO: Change all occurrences of oc rsh openstackclient to oc rsh --shell=/usr/bin/bash openstackclient instead, and likewise for any other oc rsh OpenStack destination. Then change all occurrences of sh-5.1$ (following the updated rsh command) to the appropriate prompt depending what is being connected to, for example [cloud-admin@openstackclient ~]$ or [nova@nova-cell1-conductor-0 /]$ and so on. Take care to check that the line breaks are still under 76 columns or so, otherwise there will likely be rendering issues for those lines.

      This must be completed in order to sync up with the same fixes already applied to PTL-14863 and PTL-14865.

      AFFECTED SECTIONS: Any lecture, GE, or Lab with an oc rsh that drops in to a shell that hasn't already been fixed. See search results at CL0003L, CL0004L, CL0005L, CL0006LCL0010L


      Update IPs throughout the GEs/Labs to match revised lab environment: The lab environment was updated and, in the process, various IPs have changed... in a good way. However this also means we ought to walk through every GE and Lab to ensure that the IPs used in them match up with the revised lab environment. This was reported in PTL-15215 and has been moved here. PTL-15215 is now closed.

      TODO: Please walk through the GEs and Labs and adjust any IPs that are now different in the new lab environment build. This includes any Python that verifies specific IP addresses. (Some of the code dynamically checks for the correct IPs and will not need to be updated.) Per the CLA, the ansible host and compute IPs (data plane nodes) have been adjusted.

      edpm-compute-1 192.168.50.31 Ansible Host
      edpm-compute-2 192.168.50.32 Ansible Host
      compute01.srv.example.com 192.168.51.31 Data plane node
      compute02.srv.example.com 192.168.51.32 Data plane node

      This must be completed to help ensure a successful QA review. In cooperation with the QA team, it may also be possible to have them catch any expected discrepancies and fix those during QA. 

      AFFECTED SECTIONS: Any lecture, GE, or Lab that references IP addresses in the lab environment and that is expected to match. See search results at CL170, CL0004L (ansible host) and CL170, CL0004L, CL0005L, CL0006L, CL0009L (data plane node)


      Use newer yq along the lines of what was done in PTL-14844. This will simplify many of the oc get commands. This was also reported in PTL-14841 and has been moved here.

      TODO: Update all oc get commands that use yq along the lines of what was done in PTL-14844.

      This must be completed in order to sync up with the same fixes already applied to PTL-14844.

      AFFECTED SECTIONS: Any lecture, GE, or Lab with a yq that is not taking advantage of the aforementioned simplification. A giveaway that it isn't using the newest features is if you see it using the --prettyPrint option. Contrast with instances where this has already been fixed to help understand how to apply the changes. See search results at CL0003L, CL0005L, CL0006LCL0008L


      Use ssh to reach compute nodes from workstation without going through utility: This was fixed as part of the lab environment update. Some lessons incorporate the change, but possibly not all. There is no longer any need to use the utility server for anything other than running wait.sh.

      TODO: See PTL-14875 PR#39 for examples of how to avoid logging in to utility to reach the compute nodes. They can now be reached from workstation with a simple ssh command. Change any remaining content that uses utility for any reason other than running wait.sh. This includes making OpenShift edits on utility; this is not needed, make those edits on workstation as per usual. 

      This must be completed in order to sync up with the same fixes already applied to PTL-14875.

      AFFECTED SECTIONS: Any lecture, GE, or Lab that uses ssh lab@utility in order to do anything other than run wait.sh. See search results at CL0006L


      Use lower-case text for all placeholder values in AsciiDoc and GE/Lab templates: AFAIK, we use all uppercase only if that is the expected format for the replaced value.

      TODO: See this Slack thread for details. There may be several of these to be changed throughout the course.

      AFFECTED SECTIONS: Any lecture, GE, or Lab that uses upper-case text for any placeholder text. Double check text such as IP-address to see if mixed case is warranted. See search results at CL0003L, CL0004L, CL0006L, CL0009L

      Note that some placeholder text is in the format of the expected result, such as CL0005L.


      Update occurrences of the CHANGEME placeholder to be more specific: Our current convention is to use italics to mark up values that the learner must replace. AFAIK, we do not use the CHANGEME placeholder, and we use all uppercase only if that is the expected format for the replaced value.

      TODO: See this Slack thread for details. Since there only appear to be a handful (five or six) of these, it should be a quick lift. Some/all of these may also be handled in the course of TE review for the remaining dev tasks.

      AFFECTED SECTIONS: Any GE or Lab that uses CHANGEME instead of more specific placeholder text. See search results at CL0003L, CL0004L, CL0006L

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

                Created:
                Updated:
                Resolved: