OS Version Change Overview
OS version change is a functional module that focuses on host OS upgrade management in COC. It provides convenient and efficient OS version change capabilities for hosts. With this function, you can easily create an OS version change task to upgrade multiple hosts in batches, greatly improving the OS upgrade efficiency.
After an OS version change task is created, the system automatically generates an upgrade service ticket. The service ticket records the upgrade progress of each instance in detail, including the current upgrade phase and whether there are any exceptions. In this way, you can learn about the overall upgrade status in real time. In addition, if an issue arises during the upgrade, you can retry the instance based on the actual requirements in the service ticket. If the instance has an incompatibility issue after the upgrade, you can roll back the instance to the status before the upgrade to ensure stable running of the system.
Key Features
- Task creation: Create an OS version change task on the function page. You need to specify the task name, select the target OS version, and select the host instances to be upgraded. You can select different types of hosts (such as ECSs and BMSs) at the same time to implement batch operations.
- Change service ticket: Service tickets are created for task execution, and the OS version change service ticket synchronizes the upgrade status of each instance in real time. The upgrade statuses from preparation, upgrade, to upgrade completion or failure are clearly recorded by the ticket, and detailed operation logs are provided for troubleshooting.
- Operation options: Two key operations are provided: retry and rollback. If an instance fails to be upgraded, you can retry the upgrade. If there is a service adaptation issue after the upgrade, you can roll back the instance to the version and status before the upgrade.
Advantages
- Efficient batch upgrade: Version change tasks can be started for multiple hosts at the same time. This feature is especially suitable for unified OS upgrade of a large-scale host cluster, greatly reducing the operation time and manpower input.
- Controllable and traceable process: The upgrade progress of each instance is monitored in real time through the upgrade service ticket. All operations are recorded in logs. This helps you detect and handle exceptions in a timely manner and provides a complete basis for subsequent audit and review.
- Comprehensive security assurance: The retry function reduces the impacts of a single upgrade failure, and the rollback function helps you roll back an upgrade to avoid risks generated after the upgrade, ensuring system stability and service continuity during the OS version change.
Benefits
- Improved upgrade efficiency: If you have a large number of hosts, the batch upgrade function helps you shorten the upgrade time from several days to a short time by eliminating the need to perform operations one by one. That is, this function greatly improves O&M efficiency.
- Reduced operation risks: The comprehensive progress monitoring and rollback mechanism enables you to handle various problems during the upgrade in a timely manner. This reduces service interruption risks caused by upgrade failures or version incompatibility and ensures stable running of core services.
- Unified management: Centralized task creation and service ticket management implement unified planning and control of all host OS version changes, ensuring system environment consistency and reducing management difficulties caused by version disorder. For example, before launching a new service system, an enterprise can use this function to upgrade OS versions of all related hosts to the target version where required operations can be performed to ensure smooth service deployment.
Constraints
Currently, only Red Hat Linux is supported. Only ECSs and IDC offline resources are supported. Only minor version upgrades are allowed (upgrade path: From Red Hat 7.4/7.6 to Red Hat 7.9). The architecture type can only be x86_64. Batching is not supported.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot