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

Neutron - as a user I want to get notifications from the deployed neutron cluster

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • neutron-operator
    • None
    • as a user I want to get notifications from the deployed neutron cluster
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-982Use an single but independent message bus for OpenStack notification traffic
    • Not Selected
    • Proposed
    • Proposed
    • Done
    • RHOSSTRAT-982 - Use an single but independent message bus for OpenStack notification traffic
    • Proposed
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done

      Goal:

      • I as a user want to get neutron notifications from the 18.0 deployment, from a separate Notifications bus not colocated with either of RPC buses.
      • I as a user want to be able to provide a message bus to be used for the notification.

      We should discuss the CRD interface as keystone- and barbican-operator uses a generic interface for notification transport_url configuration already. They don't take a RabbitMqCluster name but take a Secret name only and expecting a transport_url field in the Secret. This interface potentially allows other than rabbit based driver to be configured (e.g. kafka)

       

      Acceptance Criteria:

      <-- Notes for defining Acceptance Criteria  - remove these notes before saving -->

      •  

              rh-ee-auniyal Amit Uniyal
              rh-ee-auniyal Amit Uniyal
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: