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

Use a naming convention that is more inline with purpose

XMLWordPrintable

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

      None

      Show
      None
    • False
    • en-US (English)

      Please fill in the following information:


      URL:  
      Reporter RHNID: gls-ftaylor
      Section Title:                                                                        

      Issue description

      The naming convention we use for resources should better match their purpose/usage.  For instance, the OpenStack node set is named openstack-data-plane, but the OpenStack deployment is also named openstack-data-plane.  This leads to confusion in many places, including the Ansible EE names.  Ansible EE names use a convention of <service><deployment><node set>, and because the deployment name and node set name are the same, it looks like a repeating pattern (`bootstrap-openstack-data-plane-openstack-data-plane`).  Ideally, we could use a name that is more indicative of the usage, e.g., `openstack-node-set` for the node set name and `openstack-deployment` or `openstack-initial-deployment` for the deployment name.  This helps students to see the pattern more easily than if we use the same name for two different things.

       

       

       

              glsbugs-hybridcloud@redhat.com PTL - RHEL Team
              gls-ftaylor Forrest Taylor (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: