RabbitMQ should communicate through a different network rather than api_network

Bug #1642878 reported by Satya Sanjibani Routray
This bug report is a duplicate of:  Bug #1583655: rabbitmq setup from secondary IP. Edit Remove
14
This bug affects 3 people
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_dist_use_interface, {% raw %}{{% endraw %}{{ api_interface_address | regex_replace('\.', ',') }}}},
    {inet_dist_listen_min, {{ rabbitmq_cluster_port }}},
    {inet_dist_listen_max, {{ rabbitmq_cluster_port }}}
  ]},
  {rabbit, [
    {tcp_listeners, [
      {"{{ api_interface_address }}", {{ rabbitmq_port }}}
    ]}{% if orchestration_engine == 'ANSIBLE' %},
    {cluster_partition_handling, autoheal}
    {%- endif %}
  ]},
  {rabbitmq_management, [
    {listener, [
      {ip, "{{ api_interface_address }}"},
      {port, {{ rabbitmq_management_port }}}
    ]},
    {load_definitions, "/etc/rabbitmq/definitions.json"}
  ]}{% if orchestration_engine == 'ANSIBLE' %},
  {rabbitmq_clusterer, [{config, "/etc/rabbitmq/rabbitmq-clusterer.config"}]}
{%- endif %}
].
% EOF

Revision history for this message
Satya Sanjibani Routray (satroutr) wrote :
affects: kolla → kolla-ansible
Changed in kolla-ansible:
assignee: nobody → Satya Sanjibani Routray (satroutr)
Revision history for this message
David Turner (dt.turner) wrote :

To elaborate on Satya's proposal, the messaging_interface & messaging_interface_address parameters could be added to Kolla and have a default value to that of the api_interface / address. The rabbitmq role template along with all other service role templates referring to rabbitmq address would need to be updated to replace api_interface_address messaging_interface_address.

We've tested these changes in our multinode / multirack dev environment.

Currently Kolla assumes that the primary hostname is set from the API interface. The changes proposed here could still allow for that assumption, while providing the option to override it.

Revision history for this message
David Turner (dt.turner) wrote :

Slight correction to my previous comment:

..."The rabbitmq role template along with all other service role templates referring to rabbitmq address would need to be updated to replace api_interface_address *with messaging_interface_address."

Changed in kolla-ansible:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.