VM instances resize and rebuild are currently being done as 2 distinct operations at the nova api. To simplify customer workflow, we'd like to be able to resize and rebuild in a single atomic operation . This will be also useful for cloud instances that use a rebuild for upgrades where the resource requirements of the updated stateless application differ from n to n+1
the full proposal for the resize api was rejected in favor of impormentents to the exsting api. while this will not fulfil this use-case those change would generally imporve the current UX https://etherpad.opendev.org/p/r.321f34cf3eb9caa9d87a9ec8349c3d29 the disucssion of this feature is documented on line 613-651 AGREED: new microversion auto confirming resize by default allow resizing to the same flavor to update extra_spec allow resizing shelve offloaded instances wait for the rebuild of bvf solution before we do the --image part seting dev_condtional_nack upstream,design until we have had time to reasse if this is something we still want to pursue given the upstream feedback and/or when. due to the new microversion this will not be part of osp 17 based on our currently plans to base that on wallaby as teh wallaby development cycle is now finished.
Starting with the Antelope upstream release, DFG:Compute is tracking its feature backlog in Jira. This feature request has been migrated to DFG:Compute’s new Jira backlog. The Jira tracker for this feature request can be found below. At the time of this writing, only Red Hat associates have access to the Jira tracker, but we are actively working on changing that as more and more of the OSP organization uses Jira for more things. https://issues.redhat.com/browse/OSP-284
*** Bug 1940867 has been marked as a duplicate of this bug. ***