Christian Schwede 65d38fa8de Fix networking settings for ObjectStorage role
The role name is actually "ObjectStorage", not "SwiftStorage". This
leads do failing deployments if one or more ObjectStorage nodes are
deployed on the overcloud.

Closes-Bug: 1727475
Change-Id: I96fd27bdad5d417f23550ecc3387d81fd3c5418a
2017-10-25 20:57:17 +02:00

30 lines
1.4 KiB
YAML

# ******************************************************************************
# DEPRECATED: Use tripleo-heat-templates/environments/network-isolation-v6.yaml
# and define the needed networks in your custom role file.
# ******************************************************************************
# Enable the creation of an IPv6 system management network. This
# creates a Neutron network for isolated Overcloud
# system management traffic and configures each role to
# assign a port (related to that role) on that network.
# Note that the basic sample NIC configuration templates
# do not include the management network, see the
# comments in the sample network config templates in
# network/config/ for an example.
resource_registry:
OS::TripleO::Network::Management: ../network/management_v6.yaml
# Port assignments for the controller role
OS::TripleO::Controller::Ports::ManagementPort: ../network/ports/management_v6.yaml
# Port assignments for the compute role
OS::TripleO::Compute::Ports::ManagementPort: ../network/ports/management_v6.yaml
# Port assignments for the ceph storage role
OS::TripleO::CephStorage::Ports::ManagementPort: ../network/ports/management_v6.yaml
# Port assignments for the swift storage role
OS::TripleO::ObjectStorage::Ports::ManagementPort: ../network/ports/management_v6.yaml
# Port assignments for the block storage role
OS::TripleO::BlockStorage::Ports::ManagementPort: ../network/ports/management_v6.yaml