Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-15048

Support customer Tenant and TenantDomain names in octavia-operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhos-18.0.8
    • None
    • octavia-operator
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • octavia-operator-container-1.0.10-5
    • VANS-013, VANS-014
    • 2

      Goal: 

      • Users should be able to set a custom TenantName and TenantDomainName in the octavia-operator
      • These parameters will be used by the operator to authenticate against the Openstack APIs
      • The resources originally created by the operator in the "service" tenant will be create in this custom tenant
      • The operator still uses the "octavia" user in the "Default" domain
      • The "octavia" service user should have the "admin" and "service" role in this custom tenant

      Acceptance Criteria:

      • Neutron resources, Glance Image, etc... are created in this tenant (note: the octavia-provider-network belongs to the admin tenant)

              rhn-support-gthiemon Gregory Thiemonge
              rhn-support-gthiemon Gregory Thiemonge
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: