Derek Higgins 6e396cdedd Rename the provision subnet to match the net name ... On a tenant where several quintupleo environments exist placing the resource identifier in the subnet name will make them easier to tell apart. This will come in particularly useful on a CI cloud where we expect to have mutiple stacks defined at once.		2016-06-30 23:33:25 +01:00
..
overcloud-env	s/RDO Manager/TripleO/	2016-03-21 21:02:51 +00:00
baremetal-networks-all.yaml	Drop _net suffix from isolated network names	2016-05-04 12:53:12 -05:00
baremetal-networks-none.yaml	Create types for baremetal networking	2016-04-07 09:35:52 +12:00
baremetal-ports-all.yaml	Update default port names too	2016-05-04 15:52:50 -05:00
baremetal-ports-default.yaml	Types to create all networks for network-isolation	2016-04-07 13:06:03 +12:00
env.yaml.example	Make undercloud deploy optional in quintupleo.yaml	2016-06-28 14:20:48 -05:00
private-net-create.yaml	Add list param for dns instead one string param	2016-02-26 16:00:44 +01:00
private-net-existing.yaml	OS::OVB::PrivateNetwork which creates a network	2016-02-17 13:03:12 +13:00
quintupleo.yaml	Rename the provision subnet to match the net name	2016-06-30 23:33:25 +01:00
resource-registry.yaml	Make undercloud deploy optional in quintupleo.yaml	2016-06-28 14:20:48 -05:00
undercloud-floating-existing.yaml	Give option of using existing or no undercloud floating ip	2015-11-24 09:54:32 +13:00
undercloud-floating-none.yaml	Give option of using existing or no undercloud floating ip	2015-11-24 09:54:32 +13:00
undercloud-floating.yaml	Put undercloud floating ip into own type	2015-11-24 09:54:32 +13:00
undercloud.yaml	Make undercloud deploy optional in quintupleo.yaml	2016-06-28 14:20:48 -05:00
virtual-baremetal-servers.yaml	Types to create all networks for network-isolation	2016-04-07 13:06:03 +12:00
virtual-baremetal.yaml	Make bmc depend on baremetal instances	2016-06-09 11:34:09 -05:00