f918bdb048
Restarting services after Puppet is vital to ensure that config changes go applied. However, it can be sometimes desirable to prevent these restarts to avoid downtime, if the operator is sure that no config changes need applying. This can be a case e.g. when scaling compute nodes. Passing the puppet-pacemaker-no-restart.yaml environment file *in addition* to puppet-pacemaker.yaml should allow this. This is a stop gap solution before we have proper communication between Puppet and Pacemaker to allow selective restarts. Change-Id: I9c3c5c10ed6ecd5489a59d7e320c3c69af9e19f4 |
||
---|---|---|
.. | ||
updates | ||
README.md | ||
cinder-dellsc-config.yaml | ||
cinder-eqlx-config.yaml | ||
cinder-netapp-config.yaml | ||
config-debug.yaml | ||
docker-network-isolation.yaml | ||
docker-network.yaml | ||
docker.yaml | ||
enable-tls.yaml | ||
external-loadbalancer-vip-v6.yaml | ||
external-loadbalancer-vip.yaml | ||
inject-trust-anchor.yaml | ||
ips-from-pool-all.yaml | ||
ips-from-pool.yaml | ||
major-upgrade-pacemaker-converge.yaml | ||
major-upgrade-pacemaker-init.yaml | ||
major-upgrade-pacemaker.yaml | ||
manage-firewall.yaml | ||
mongodb-nojournal.yaml | ||
net-bond-with-vlans-no-external.yaml | ||
net-bond-with-vlans-v6.yaml | ||
net-bond-with-vlans.yaml | ||
net-multiple-nics-v6.yaml | ||
net-multiple-nics.yaml | ||
net-single-nic-linux-bridge-with-vlans.yaml | ||
net-single-nic-with-vlans-no-external.yaml | ||
net-single-nic-with-vlans-v6.yaml | ||
net-single-nic-with-vlans.yaml | ||
network-environment.yaml | ||
network-isolation-no-tunneling.yaml | ||
network-isolation-v6.yaml | ||
network-isolation.yaml | ||
network-management.yaml | ||
neutron-midonet.yaml | ||
neutron-ml2-bigswitch.yaml | ||
neutron-ml2-cisco-n1kv.yaml | ||
neutron-ml2-cisco-nexus-ucsm.yaml | ||
neutron-nuage-config.yaml | ||
neutron-opencontrail.yaml | ||
neutron-plumgrid.yaml | ||
nova-nuage-config.yaml | ||
overcloud-steps.yaml | ||
puppet-ceph-devel.yaml | ||
puppet-ceph-external.yaml | ||
puppet-pacemaker-no-restart.yaml | ||
puppet-pacemaker.yaml | ||
puppet-tenant-vlan.yaml | ||
storage-environment.yaml |
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