Bug 2216011 - [RFE] Migrating to cpu_shared_set and cpu_dedicated_set requires practical solution for large scale deployments [NEEDINFO]
Summary: [RFE] Migrating to cpu_shared_set and cpu_dedicated_set requires practical so...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-19 17:17 UTC by Francois Palin
Modified: 2023-07-13 12:06 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-13 12:06:09 UTC
Target Upstream Version:
Embargoed:
alifshit: needinfo? (fpalin)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-25890 0 None None None 2023-06-19 17:20:48 UTC

Description Francois Palin 2023-06-19 17:17:59 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.