Vasyl Saienko fdf6f89a23 [Grenade]: Do not run ir-api on primary node after upgrade ... Ironic upgrade process has pre-requirement that ironic-conductors should be upgraded before ironic-api. Grenade is launched on primary node, where we have ir-api and ir-cond runnning. Do not start ir-api on primary node after upgrade to avoid situation when we have new ir-api (primary) and old ir-cond (subnode) as it is not allowed by upgrade procedure. Instead redirect all requests destinied to ir-api on primary node to subnode. Depends-On: I026121121059768aa74389add7eee6e63fdb214d Change-Id: I9e496353a1d3d6547e4881f96fb187e488cff83f		2017-04-28 13:59:07 +03:00
..
debs	Ensure we install latest libivrt	2017-04-21 08:53:39 +00:00
hooks	Devstack: Create a "no ansi" logfile for the baremetal console logs	2017-01-26 13:15:33 -08:00
rpms	Add Ironic standalone tests	2017-03-15 16:54:45 +02:00
apache-ipxe-ironic.template	Add wsgi handling to ironic-api in devstack	2017-03-09 16:55:34 +02:00
apache-ironic-api-redirect.template	[Grenade]: Do not run ir-api on primary node after upgrade	2017-04-28 13:59:07 +03:00
apache-ironic-api.template	Add /baremetal path instead of port 6385	2017-04-18 11:03:22 +03:00