aboutsummaryrefslogtreecommitdiffstats
path: root/network/networks.yaml
diff options
context:
space:
mode:
authorDan Prince <dprince@redhat.com>2015-04-27 10:46:28 -0400
committerDan Prince <dprince@redhat.com>2015-05-06 21:20:24 -0400
commit00efb796cd3d63ecbf903c058f7647b77e6bd693 (patch)
tree482019d5ea3c28c1d4ab3b479154ad8aa82364f0 /network/networks.yaml
parent92377361c76a612457cc147a0608d94db430a771 (diff)
Create split out neutron networks via Heat.
This patch adds a new abstraction for network creation within Heat. This (optional) set of templates may be disabled if you wish to create Neutron networks for the undercloud via Heat templates... instead of using os-cloud-config JSON to do so. Creating networks with Heat has the benefit of being parameter driven so that users can quickly enable networks using the resource registry and parameters. There are 5 networks to start with which are roughly modeled around networks an Overcloud user might want to use to isolate their traffic. The intent is to make these opt-in and configurable for end users. The networks.yaml template can be used to create all of the networks using parameters in the resource registry. Change-Id: I5f2b3356378eb263d90d428cc83c7f5b141957e1
Diffstat (limited to 'network/networks.yaml')
-rw-r--r--network/networks.yaml20
1 files changed, 20 insertions, 0 deletions
diff --git a/network/networks.yaml b/network/networks.yaml
new file mode 100644
index 00000000..7d36707d
--- /dev/null
+++ b/network/networks.yaml
@@ -0,0 +1,20 @@
+heat_template_version: 2014-10-16
+
+description: Create networks to split out Overcloud traffic
+
+resources:
+
+ ExternalNetwork:
+ type: OS::TripleO::Network::External
+
+ InternalNetwork:
+ type: OS::TripleO::Network::InternalApi
+
+ StorageMgmtNetwork:
+ type: OS::TripleO::Network::StorageMgmt
+
+ StorageNetwork:
+ type: OS::TripleO::Network::Storage
+
+ TenantNetwork:
+ type: OS::TripleO::Network::Tenant