Remove storage management network from controllers

There is no need to connect controllers nodes to the storage management
network by default. It should only be used by storage nodes.

Change-Id: I6fa7640658fd112aaddbe08c4af01711fb1f7916
Story: 2006273
Task: 35973
This commit is contained in:
Pierre Riteau 2019-08-06 14:13:41 +01:00
parent 2bce627040
commit f5490793fb
5 changed files with 7 additions and 12 deletions

View File

@ -24,7 +24,6 @@ controller_default_network_interfaces: >
inspection_net_name,
internal_net_name,
storage_net_name,
storage_mgmt_net_name,
ceph_storage_net_name,
swift_storage_net_name,
cleaning_net_name] | reject('none') | unique | list }}

View File

@ -718,7 +718,6 @@ By default, controllers are attached to the following networks:
* workload (compute) cleaning network
* internal network
* storage network
* storage management network
In addition, if the controllers are also in the ``network`` group, they are
attached to the following networks:

View File

@ -27,11 +27,6 @@
# storage_net_bridge_ports:
# storage_net_bond_slaves:
# Storage management network IP information.
# storage_mgmt_net_interface:
# storage_mgmt_net_bridge_ports:
# storage_mgmt_net_bond_slaves:
# Storage network IP information.
# ceph_storage_net_interface:
# ceph_storage_net_bridge_ports:

View File

@ -27,11 +27,6 @@
# storage_net_bridge_ports:
# storage_net_bond_slaves:
# Storage management network IP information.
# storage_mgmt_net_interface:
# storage_mgmt_net_bridge_ports:
# storage_mgmt_net_bond_slaves:
###############################################################################
# Dummy variable to allow Ansible to accept this file.
workaround_ansible_issue_8743: yes

View File

@ -0,0 +1,7 @@
---
upgrade:
- |
Controllers are no longer connected to the storage management network by
default, since generally only storage nodes need access to this network. If
needed, the existing configuration can be retained by adding the storage
management network to the ``controller_extra_network_interfaces`` list.