ironic/devstack
John L. Villalovos 9d161f6922 grenade: For multi-node grenade, do not upgrade nova
Multi-node grenade jobs will fail if we upgrade nova as the minimum
required API for nova to communicate with ironic was upgraded.

Our goal for multi-node grenade is to test rolling upgrades. The
scenario we envision for rolling upgrades to be done is:

 1) Upgrade ironic-conductor services one by one. This means old
    ironic-api services communicating with new and old
    ironic-conductor services. This is what the multi-node grenade job
    tests.
 2) Upgrade ironic-api services.
 3) Upgrade nova

In this upgrade procedure we should not be running updated nova with
old ironic-api services. This patch fixes that.

Closes-Bug: #1706418
Change-Id: I85c607ae7d031e4cabcb505915aca7e88df166aa
2017-07-25 17:08:12 -07:00
..
files [Grenade]: Do not run ir-api on primary node after upgrade 2017-04-28 13:59:07 +03:00
lib Merge "py3.5:Workaround fix for forcing virtualbmc installation with pip2" 2017-07-24 20:36:36 +00:00
tools/ironic Runs the script configure_vm.py in py3.5 2017-06-08 12:22:36 +00:00
upgrade grenade: For multi-node grenade, do not upgrade nova 2017-07-25 17:08:12 -07:00
plugin.sh Ensure we install latest libivrt 2017-04-21 08:53:39 +00:00
settings Revert "Disable placement-api by default" 2017-01-06 06:28:05 -08:00