[RFE] for rolling upgrades, pin the API version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Wishlist
|
Dmitry Tantsur |
Bug Description
Now that we have the rolling upgrades infrastructure in place, let's refine it! During a rolling upgrade, the new ironic-api and ironic-conductor services are pinned so that they use the same RPC vesions and IronicObject versions as the older service (thus allowing them to talk to each other without getting upset).
For the ironic-api service, we should also pin the API microversion. Pinning this would:
- make it easier for the new ironic-api services to know when/how to reject new features that the old ironic-api services cannot handle. They would return HTTP code 406 (Not Acceptable)
- change the response header so that the maximum API version would be the pinned version
This would take effect using the same [DEFAULT]
Documentation will be updated to reflect this.
description: | updated |
tags: | added: rfe |
Changed in ironic: | |
status: | New → Confirmed |
Changed in ironic: | |
assignee: | Ruby Loo (rloo) → Dmitry Tantsur (divius) |
Fix proposed to branch: master /review. openstack. org/518411
Review: https:/