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

Nova - as a user I want to get notifications from the deployed nova cluster

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • rhos-18.0.10 FR 3
    • rhos-18.0.0
    • nova-operator
    • None
    • as a user I want to get notifications from the deployed nova cluster
    • False
    • False
    • RHOSSTRAT-680Use an single but independent message bus for Nova notification traffic
    • Proposed
    • Proposed
    • Done
    • RHOSSTRAT-680 - Use an single but independent message bus for Nova notification traffic
    • Proposed
    • rhos-workloads-compute
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done

      • I as a user want to get nova 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.
        • The deployment engine should support having a single message bus for all cells.

      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)

       

      Stretched Goals

      • The deployment engine should support having different message buses per cell
      • The deployment engine should support reusing the RPC message bus for notifications

              ashigupt@redhat.com Ashish Gupta
              rh-ee-bgibizer Balazs Gibizer
              rhos-workloads-compute
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: