Hi, 

As feature freeze is closing in I try to raise awareness of the implementation status of the support-move-ops-with-qos-ports bp [1]. 

The original goal of the bp was to support every move operations (cold migrate, resize, live-migrate, evacuate, unshelve). Today I have ready and tested (unit + functional) patches proposed for cold migrate and resize [2]. I don't think every move operations will be ready and merged in Train but I still hope that there is a chance for cold migrate and resize to land. Sure I will continue working on supporting the operations that miss the Train in the U release.

One possible complication in the current patch series is that it proposes the necessary RPC changes for _every_ move operations [3]. This might not be what we want to merge in Train if only cold migrate and resize support fill fit. So I see two possible way forwards:

a) Others also feel that cold migrate and resize will fit into Train, and then I will quickly change [3] to only modify those RPCs.

b) We agree to postpone the whole series to U. Then I will not spend too much time on reworking [3] in the Train timeframe.

A connected topic: I proposed patches [4] to add cold migrate and resize tempest coverage to the nova-grenade-multinode (renamed from nova-grenade-live-migrate) job as Matt pointed out in [3] that we don't have such coverage and that my original change in [3] would have broken a mixed-compute-version deployment.

Any feedback is appreciated. 

Cheers,

gibi

[1] https://specs.openstack.org/openstack/nova-specs/specs/train/approved/support-move-ops-with-qos-ports.html

[2] https://review.opendev.org/#/q/topic:bp/support-move-ops-with-qos-ports

[3] https://review.opendev.org/#/c/655721

[4] https://review.opendev.org/#/c/679210