0b4ddeecea
As it's recommended to have an independent RabbitMQ cluster for Trove Guestagent, we need to make it possible to easily use also different user/password set for it. It's also important to control quorum queues independently, as migration between quorum queues and classic queues for guestagent cluster is quite cumbersome and potentially should be avoided as might bring severe disturbances. Change-Id: Ib68778a8cb8535d7400be04f02d332ba0344d20e |
||
---|---|---|
.. | ||
.placeholder | ||
deprecate_auth_plugin-451832a71b967e27.yaml | ||
oslo-messaging-backends-65287400dba86fce.yaml | ||
public-uri-proto-a1f05edd1a594f7f.yaml | ||
remove_rpc_backend-78139a469235891f.yaml | ||
remove-requirements-git-88e681504fbd8db1.yaml | ||
rpc-encryption-b75fb0d08579a7dd.yaml | ||
service_net_endpoint_type-60dbb87c4f68403c.yaml | ||
tls12-only-d7221a33188dc7a0.yaml | ||
trove_guest_quorum_queues-bdba87bbe0fba3f3.yaml | ||
trove_image_upload-c289c73cd2ddacfb.yaml | ||
trove_init_time_settings-dd293238c53c517.yaml | ||
trove_merge_config-f52eecb1e3501fd6.yaml | ||
trove_service_subnet-011acf408754f6d9.yaml | ||
trove-init-config-overrides-a78ed428a32adef8.yaml | ||
trove-service-setup-host-5bb64b2356ca81e2.yaml |