aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud-resource-registry.yaml
diff options
context:
space:
mode:
authorDan Prince <dprince@redhat.com>2015-04-27 10:53:30 -0400
committerDan Prince <dprince@redhat.com>2015-05-22 09:08:32 -0700
commita4fd6b70b41c330f4d12da534b8a5ed92413329e (patch)
tree3435aa04e6f5a2276dbbef02baecff8cbb18aa40 /overcloud-resource-registry.yaml
parent23c329bbb9fc39f84a9397c59272bd81ab4628fe (diff)
Wire in optional network creation for overcloud
This patch enables uses to selectively enable the creation of split out networks for the overcloud traffic. These networks will be created on the undercloud's neutron instance. By default a noop network is used so that no extra networks are created. This allows our default to continue being all traffic on the control plane. Change-Id: Ied49d9458c2d94e9d8e7d760d5b2d971c7c7ed2d
Diffstat (limited to 'overcloud-resource-registry.yaml')
-rw-r--r--overcloud-resource-registry.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/overcloud-resource-registry.yaml b/overcloud-resource-registry.yaml
index 69266405..472f4b94 100644
--- a/overcloud-resource-registry.yaml
+++ b/overcloud-resource-registry.yaml
@@ -21,3 +21,12 @@ resource_registry:
OS::TripleO::BootstrapNode::SoftwareConfig: bootstrap-config.yaml
OS::TripleO::NodeUserData: firstboot/userdata_default.yaml
OS::TripleO::NodeExtraConfigPost: extraconfig/post_deploy/default.yaml
+
+ # TripleO overcloud networks
+ OS::TripleO::Network: network/networks.yaml
+
+ OS::TripleO::Network::External: network/noop.yaml
+ OS::TripleO::Network::InternalApi: network/noop.yaml
+ OS::TripleO::Network::StorageMgmt: network/noop.yaml
+ OS::TripleO::Network::Storage: network/noop.yaml
+ OS::TripleO::Network::Tenant: network/noop.yaml