Create split out neutron networks via Heat.
authorDan Prince <dprince@redhat.com>
Mon, 27 Apr 2015 14:46:28 +0000 (10:46 -0400)
committerDan Prince <dprince@redhat.com>
Thu, 7 May 2015 01:20:24 +0000 (21:20 -0400)
commit00efb796cd3d63ecbf903c058f7647b77e6bd693
tree482019d5ea3c28c1d4ab3b479154ad8aa82364f0
parent92377361c76a612457cc147a0608d94db430a771
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
network/external.yaml [new file with mode: 0644]
network/internal_api.yaml [new file with mode: 0644]
network/networks.yaml [new file with mode: 0644]
network/noop.yaml [new file with mode: 0644]
network/storage.yaml [new file with mode: 0644]
network/storage_mgmt.yaml [new file with mode: 0644]
network/tenant.yaml [new file with mode: 0644]