Uploaded image for project: 'Red Hat Enterprise Linux AI'
  1. Red Hat Enterprise Linux AI
  2. RHELAI-4531

enable tagging on cloud resources to satisfy PG&E requirements

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • DevOps
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Sprint 2

      Takeaways from "Cloud account: required tags policy compliance" email:

      First link "policy & faq" is a good explanation.

      We need to tag our cloud resources in all four clouds:

      • "app-code: The CMDB Application ID of the application or workload. From discussion in Slack, we need our own, so I've filled out the form to get our own. Ticket in progress. New CMDB ID is RHAI-008. I completed the PIA July 2 2025.
      • "service-phase": The deployment environment. dev, stage or prod. We use "dev" in our spreadsheet, so "dev" sounds appropriate.
      • "cost-center": Our instructlab cost center is "687"

      In PG&E's spreadsheet, Dan is still the Point of Contact for AWS, and we should change that.

      To comply: We could enable PG&E's "auto tagger" (form). This ticket will track that work.

      Accounts for which I will enable auto-tagging:

      • AWS: 851725220677 instructlab (DPP-17578)
      • GCP: it-cloud-gcp-instructlab-dev    it-cloud-gcp-instructlab-dev    36891655294 (DPP-17579)
      • Azure: Subscription 4ff849d2-aaae-4d0d-859b-02d0a260bb2d    instructlab (DPP-17727)
      • IBM Cloud: 8064a02a442140dbbfa41b260ff190cb    2814521    Red Hat AI (DPP-17728)

       

       

              kdreyer@redhat.com Ken Dreyer
              kdreyer@redhat.com Ken Dreyer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: