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

implement MariaDBAccount consumption in all mariadb-enabled operators

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
    • ?
    • ?
    • PIDONE Board

      Right now, downstream controllers such as that of nova, glance, neutron, keystone have fields for databaseUser and Secret, which is passed along to create a MariaDBDatabase instance with that username and password; the username right now must match the configured database name used by that controller as these cannot be separate.

       

      The goal is to replace databaseUser with databaseAccount in each CRD, and use new API functions in mariadb-operator to ensure that a MariaDBAccount + Secret exists at controller init time, and to consume the new username/pw from that API.  These changes will allow operators to correctly consume MariaDBAccounts which will later be created by openstack-operator ahead of time.    This change delivers rotateable username+password functionality to each operator, where changing databaseAccount to a new name will generate and deploy for a new username/pw in mariadb for that instance.

      The initial proof of concept is in glance at https://github.com/openstack-k8s-operators/glance-operator/pull/426

       

          There are no Sub-Tasks for this issue.

              Unassigned Unassigned
              rhn-engineering-mbayer Michael Bayer (Inactive)
              rhos-dfg-pidone
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: