From f918bdb0489963a20fe63cecb5b252378ed07f88 Mon Sep 17 00:00:00 2001 From: Jiri Stransky Date: Tue, 7 Jun 2016 12:15:04 +0200 Subject: Allow to manually disable post-puppet restarts 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 --- environments/puppet-pacemaker-no-restart.yaml | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 environments/puppet-pacemaker-no-restart.yaml (limited to 'environments/puppet-pacemaker-no-restart.yaml') diff --git a/environments/puppet-pacemaker-no-restart.yaml b/environments/puppet-pacemaker-no-restart.yaml new file mode 100644 index 00000000..67d8692d --- /dev/null +++ b/environments/puppet-pacemaker-no-restart.yaml @@ -0,0 +1,3 @@ +# use this file *in addition* to puppet-pacemaker.yaml +resource_registry: + OS::TripleO::Tasks::ControllerPostPuppetRestart: OS::Heat::None -- cgit 1.2.3-korg