Michele Baldessari 066a360ee5 Allow the IHA OCF and fencing resource to be moved to the nova service user ... Currently both nova evacuate and fence compute in the Instance HA setup of tripleo user the keystone admin user in order to query nova, evacuate instances, disable/enable the nova-compute service and call the nova force-down API. With this patch we introduce the keystone_tenant parameter which is needed when moving to the nova service user as it is different than keystone_admin in that case. Tested as follows: 1. Deployed a normal unpatched OSP13 with IHA 2. Run a redeploy with the following addition: parameter_defaults: ExtraConfig: tripleo::profile::base::pacemaker::instance_ha::keystone_password: "%{hiera('nova::keystone::authtoken::password')}" tripleo::profile::base::pacemaker::instance_ha::keystone_admin: 'nova' tripleo::profile::base::pacemaker::instance_ha::keystone_tenant: 'service' 3. Observe the following: 3.1. Both the fence_compute and nova evacuate resources have updated attributes 3.2. IHA still works correctly Change-Id: If6b19ad05e0f91425f93a1c123947e92cf2ba949		2019-10-11 22:18:43 +02:00
..
instance_ha.pp	Allow the IHA OCF and fencing resource to be moved to the nova service user	2019-10-11 22:18:43 +02:00