Allow to enable fencing, pass through fencing config
authorJiri Stransky <jistr@redhat.com>
Thu, 4 Jun 2015 14:20:52 +0000 (16:20 +0200)
committerJiri Stransky <jistr@redhat.com>
Wed, 1 Jul 2015 11:54:00 +0000 (13:54 +0200)
commit1787fbc7ca58f9965cd5d64b685c1f9beed4cb9b
tree3b535f75d170cab13208d8442f8bb2a09ef4cc91
parent5d1738f6e3fcdd73bb3fa1c64df9bb295bb42184
Allow to enable fencing, pass through fencing config

Add two new parameters: EnableFencing and FencingConfig.

FencingConfig is a json with an expected structure documented in the
templates. It gets passed further to puppet-tripleo, which configures
the fencing devices.

Fencing is configured and enabled in the last step after all pacemaker
resources and constraints have been created, which should be a more
stable approach than the other way round.

Change-Id: Ifd432bfd2443b6d13e7efa006d4120bb0eaa2554
Depends-On: I819fc8c126ec47cd207c59b3dcf92ff699649c5a
Depends-On: I8b7adff6f05f864115071c51810b41efad887584
controller.yaml
overcloud-without-mergepy.yaml
puppet/controller-post-puppet.yaml
puppet/controller-puppet.yaml
puppet/manifests/overcloud_controller_pacemaker.pp