Add creation of a management network to the network isolation tripleo-heat-templates as well as a port on that network for all overcloud nodes.
This network is to be used for administrative access to the overcloud nodes.
In https://review.openstack.org/#/c/264963 "Add Management Network For System Administration." (included in openstack-tripleo-heat-templates-0.8.10-1.el7ost) a new environment file "network-management.yaml" is introduced, which can be used when deploying your overcloud to enable creation of the management network/subnets and ports on each node.
As well as this new environment file you will also need to ensure the management network is created correctly by your network templates. If you are deploying with the existing (in-tree) example templates, like the "single-nic-vlans" or "multiple-nics" you will need to uncomment the provided block - see https://github.com/openstack/tripleo-heat-templates/blob/365c35cc6e1e588215ab6d63143b84bb56dce376/network/config/single-nic-vlans/controller.yaml#L140 as an example, assuming you are using the single-nic-vlans templates and wish to create the management network vlan.
Description of problem:
I was working on a customer installation of OSP Director today, and the requirement was raised for a system management network that spanned all hosts. This network would be used for SSH connectivity, monitoring, and devops work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure overcloud network
There is no option for a system management network.
This is a clear customer requirement.
We should really try to get this into 7.1, I think we're probably going to feel some pain since we won't have this in GA. Perhaps a PM should even take a look and evaluate if we need this for GA.
Upstream review to add system management network:
The original upstream patch was abandoned in favor of this newer patchset:
Patch merged in master, needs to be backported to stable liberty
Downstream review: https://code.engineering.redhat.com/gerrit/65730
We tested a multi-node overcloud deployment utilizing the management network and after getting a type error I noticed that the ManagementNetValueSpecs parameter was set to the wrong type (string instead of json).
I have already made the change in gerrit:
with a cherry pick for stable/liberty here: