Description of problem:
Customer was made aware of procedure described in [1] to migrate system from using legacy vcpu_pin_set to cpu_shared_set and cpu_dedicated_set.
Customer has more than 5300 instances in production. From customer perspective, scheduling maintenance windows and going through this procedure
in sync with every single tenant makes the procedure impractical.
A more practical solution would be required for this type of large scale deployment.
Also, please refer to BZ 2187846.
[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/framework_for_upgrades_13_to_16.2/index#updating-the-cpu-pinning-parameter-post-upgrade
How reproducible:
Steps to Reproduce:
Actual results:
Expected results:
Additional info:
Customer is currently using RHOSP 16.2, and would like to migrate to cpu_shared_set and cpu_dedicated_set
ahead of eventual upgrade to RHOSP 17.x