marios 2e6cc07c1a Adds Environment File for Removing Sahara during M/N upgrade ... The default path if the operator does nothing is to keep the sahara services on mitaka to newton upgrades. If the operator wishes to remove sahara services then they need to specify the provided major-upgrade-remove-sahara.yaml environment file in the stack upgrade commands. The existing migration to ha arch already removes the constraints and pcs resource for sahara api/engine so we just need to stop it from starting again if we want to remove it. This adds a KeepSaharaServiceOnUpgrade parameter to determine if Sahara is disabled from starting up after the controllers are upgraded (defaults true). Finally it is worth noting that we default the sahara services as 'on' during converge here in the resource_registry of the converge environment file; any subsequent stack updates where the deployment contains sahara services will need to include the -e /environments/services/sahara.yaml environment file. Related-Bug: 1630247 Change-Id: I59536cae3260e3df52589289b4f63e9ea0129407		2016-10-05 16:32:31 +03:00
..
all_nodes	get_param calls with multiple arguments need brackets around them	2016-09-25 22:05:00 +02:00
post_deploy	Add ExtraConfig example that always runs on update	2016-03-23 14:29:50 +00:00
pre_deploy/rhel-registration	change the default satellite tools rpm repo.	2016-03-29 12:14:22 -04:00
tasks	Adds Environment File for Removing Sahara during M/N upgrade	2016-10-05 16:32:31 +03:00