tripleo-heat-templates

Files

James Slagle 9af3ec5865 Use parameter_defaults in env files

Switch to using parameter_defaults in environment files instead of a
parameters section. Using a parameters section to set top level
parameters breaks Tuskar based deployments because Tuskar prefixes the
name of the top level parameters with a role name and version, thus
changing the name of the parameter. When the environment file is then
used to set a top level parameter, Heat fails with an error during
template validation:

ERROR: The Parameter (NeutronExternalNetworkBridge) was not defined in template

Change-Id: I605651a8ebdbd0b2baf7bcea198c2988efb55f31

2015-07-09 11:19:43 -04:00

cinder-netapp-config.yaml

Wire in Controller pre-deployment extraconfig

2015-07-06 10:56:11 -04:00

net-bond-with-vlans.yaml

Use parameter_defaults in env files

2015-07-09 11:19:43 -04:00

net-single-nic-with-vlans.yaml

Use parameter_defaults in env files

2015-07-09 11:19:43 -04:00

network-isolation.yaml

Include Redis VIP in example environment

2015-06-25 12:03:02 -07:00

overcloud-steps.yaml

overcloud stepped deployment environment

2015-05-22 21:30:57 +01:00

puppet-ceph-devel.yaml

Add a directory for overcloud heat environments

2015-05-15 12:28:00 +02:00

puppet-pacemaker.yaml

Enable loadbalancing of the Redis VIP, defaults to False

2015-06-18 14:31:52 +02:00

puppet-tenant-vlan.yaml

Wire Neutron VLAN ranges param as array to puppet

2015-06-05 09:27:42 -04:00

README.md

Add a directory for overcloud heat environments

2015-05-15 12:28:00 +02:00

README.md

This directory contains Heat environment file snippets which can be used to enable features in the Overcloud.

Configuration

These can be enabled using the -e [path to environment yaml] option with heatclient.

Below is an example of how to enable the Ceph template using devtest_overcloud.sh:

export OVERCLOUD\_CUSTOM\_HEAT\_ENV=$TRIPLEO\_ROOT/tripleo-heat-templates/environments/ceph_devel.yaml