| 2016-08-12 14:59:39 |
Sam Betts |
description |
It was decided at the Ironic newton midcycle that we need some form of API version negotiation between Ironic and IPA. This is required to allow Ironic to recognise that it is talking to an older ramdisk, and that newer features will not be available. |
It was decided at the Ironic newton midcycle that we need some form of API version negotiation between Ironic and IPA. This is required to allow Ironic to recognise that it is talking to an older ramdisk, and that newer features will not be available.
Notes from during midcycle:
sambetts will put up a spec for this
some people prefer semver for everything
some people think easier to use same/similar versioning as ironic's API version
N ironic with N+1 ipa, N-1 ipa, N ipa
IPA sends API Version on Lookup
Ironic uses API Version to gracefully degrade features.
Which tests cover N-1 and N+1 ?
Grenade covers master ironic with N-1 IPA
Another grenade (ipa-grenade) could cover master IPA with N-1 ironic.
src job on IPA to test IPA master against N-1 Ironic
this has a potential to break in two cases:
ironic n-1 is broken
ironic n-1 devstack plugin cannot build master IPA
we think these will be rare cases and won't work to avoid them unless we find we need to
there's a couple solutions there if we do need to
IPA devstack plugin for building IPA
run agent-master jobs on n-1 ironic patches
Normal gate tests cover master with master |
|
