Feature Overview

The proposed enhancement aims to allow updating KVM/QEMU packages without interrupting the VMs and rebooting the OSP compute nodes. This feature will help increase the operational efficiency and reduce the downtime, which in turn will deliver a transparent operational experience to users. 

Goals

This feature is designed to benefit cloud administrators and end-users by ensuring uninterrupted service during maintenance activities.

With this feature, updates can be applied smoothly without affecting VM operations, leading to higher uptime and reliability.

Requirements

Cloud administrators will use this feature primarily during scheduled maintenance windows or when critical updates are released. It ensures that their infrastructure remains secure and up-to-date without disrupting services.

Out of Scope

This feature does not address updates to other components of the OpenStack platform or underlying hardware upgrades. It is specifically focused on KVM/QEMU package updates.

Background and Strategic Fit

This feature is crucial for maintaining high availability and reliability in a cloud environment. By enabling updates without service interruption, it aligns with the strategic goal of providing a robust and resilient cloud infrastructure.

Assumptions

• The underlying hardware supports live migration and other necessary features.
• The OSP environment is properly configured for high availability.
• Administrators have the necessary permissions and skills to perform updates.

Customer Considerations

• Customers may need to update their procedures to incorporate the new update process.
• Consideration must be given to different customer environments, including variations in hardware and software configurations.
• Upgrades must account for the new process to ensure smooth adoption.

Documentation Considerations

• Detailed documentation will be required to guide users through the update process. Customers might need access to best practices for live migration, detailed update procedures, troubleshooting guides, and rollback procedures.

 The doc impact includes New Content, Updates to existing content, and a Release Note.

Interoperability Considerations

• Interoperability test scenarios should include live migration, high availability failover, and rollback procedures.

Questions