Why is this Epic required for deployment and adoption support for the 17.1 OSP feature set, except for 17.1 functionality that has been intentionally re-prioritized to 18-Feature Release-1 or later, and in-place update to post-18.0.0 releases.

sbauza@redhat.com smooney@redhat.com can keep me honest here, but I believe this was requested by VZ. Also, it's just generally good optics to show off the ability to save power by turning off unused CPUs.

Do you have capacity to complete the work, testing and documentation required for this Epic and is all the remaining work captured in Jira stories?

Yes, all that remains is to enable the existing tests in component CI, and write docs. Both have Stories.

What is the probability and severity of the issue? I.e. the overall risk

NA (no issue at stake here)

Does this affect specific configurations, hardware, environmental factors, etc.?

The feature is opt-in, but we'd like to make it enabled by default in OSP.

Are any partners relying on this functionality in order to ship an ecosystem product?

No.

What proportion of our customers could hit this issue?

Given that we're proposing to make this the default, 100%.

Does this happen for only a specific use case?

On by default, affects everyone.

What proportion of our CI infrastructure, automation, and test cases does this issue impact?

None.

Is this a regression in supported functionality from a previous release?

No, this is a new OSP 18 feature.

Is there a clear workaround?

NA.

Is there potential doc impact?

Yes, this will need documentation.

If this is a UI issue

NA

Overall context and effort – is the overall impact bigger/worse than the bug in isolation?

NA (not a bug)