Replace qdrouterd backend with rabbitmq in Sc03
qdrouterd for RPC is not a supported backend in RHOSP, updating sc03 to test rabbitmq which is a supported backend for RPC communication. Trying to run with qdrouterd backend in downstream fails because python-pyngus is not added as dependency downstream[1] python-pyngus available since RHOSP13 but is not added as dep for oslo-messaging rpm with reasoning[2]. ~~~ ModuleNotFoundError: No module named 'pyngus' ~~~ Sc03 provides desginate testing coverage, This change will allow us to run standalone sc03 in downstream pipelines keeping sc03 env files in sync in upstream and downstream. This patch will be backported to wallaby. [1] https://github.com/rdo-packages/oslo-messaging-distgit/blob/wallaby-rdo/python-oslo-messaging.spec#L89-L91 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1791364#c13 Change-Id: Ib49223709e20931abcec4d16301db9882c64c06f
This commit is contained in:
parent
a4cc72390f
commit
9962b52a0a
|
@ -6,7 +6,7 @@ resource_registry:
|
|||
OS::TripleO::Services::SwiftProxy: OS::Heat::None
|
||||
OS::TripleO::Services::SwiftStorage: OS::Heat::None
|
||||
OS::TripleO::Services::SwiftRingBuilder: OS::Heat::None
|
||||
OS::TripleO::Services::OsloMessagingRpc: ../../deployment/messaging/rpc-qdrouterd-container-puppet.yaml
|
||||
OS::TripleO::Services::OsloMessagingRpc: ../../deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml
|
||||
OS::TripleO::Services::OsloMessagingNotify: ../../deployment/rabbitmq/rabbitmq-messaging-notify-shared-puppet.yaml
|
||||
OS::TripleO::Services::DesignateApi: ../../deployment/designate/designate-api-container-puppet.yaml
|
||||
OS::TripleO::Services::DesignateCentral: ../../deployment/designate/designate-central-container-puppet.yaml
|
||||
|
@ -25,7 +25,6 @@ parameter_defaults:
|
|||
SwiftCeilometerPipelineEnabled: false
|
||||
NotificationDriver: 'noop'
|
||||
NeutronPluginExtensions: qos,port_security,dns_domain_ports
|
||||
RpcPort: 31459
|
||||
NotifyPort: 5672
|
||||
ContainerCli: podman
|
||||
DesignateBackendListenIPs: ["192.168.24.20"]
|
||||
|
|
Loading…
Reference in New Issue