Feature Request Overview

Currently after the OVN update completes, the rest of the services automatically update (1). This may not be what a cloud operator wants. While this may make sense in smaller environments, there may need to be more granular control over when the next update happens in larger environment.

(1) https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/updating_your_environment_to_the_latest_maintenance_release/assembly_performing-a-minor-update_preparing-minor-update#proc_updating-services-on-the-data-plane_perform-update 

Business justification

Be able to control exactly what happens when, allowing a different maintenance slot and predictable outcomes from each stage of the update process.

Functional requirements

• Be capable of turning the auto-update off. As an example, there could be a toggle for 'auto' and 'manual'. When set to manual, the flag would need to be changed to allow the update to proceed.

Describe the customer impact

This allows a customer to have complete control over what happens during the maintenance slot, ensuring predictability and the impact of failure is more closely managed. This also allows a customer to complete the planned activity and to close the maintenance slot if they choose to do so.

(Optional) Point of contact

• Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM: 
•  

(Optional) Additional links

Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.