RabbitMQ should communicate through a different network rather than api_network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Confirmed
|
Undecided
|
Satya Sanjibani Routray |
Bug Description
Currently by the kolla deployment the rabbitMQ communicate through the api_network.
it should be flexible to use the mgmt network also if anyone want the traffic to be segregated between the mgmt network and api network
snip form the current code
<snip>
[
{kernel, [
{inet_
{inet_
{inet_
]},
{rabbit, [
{tcp_listeners, [
{"{{ api_interface_
]}{% if orchestration_
{cluster_
{%- endif %}
]},
{rabbitmq_
{listener, [
{ip, "{{ api_interface_
{port, {{ rabbitmq_
]},
{load_
]}{% if orchestration_
{rabbitmq_
{%- endif %}
].
% EOF
affects: | kolla → kolla-ansible |
Changed in kolla-ansible: | |
assignee: | nobody → Satya Sanjibani Routray (satroutr) |
Changed in kolla-ansible: | |
status: | New → Confirmed |
example for the usecase "https:/ /bugs.launchpad .net/kolla/ +bug/1583655"