1. CentOS update suspension crisis
Since 1993, Red Hat Linux has been accompanying developers on a journey of nearly 30 years. As an open source operating system based on Red Hat Enterprise Linux (RHEL), CentOS has been widely used in enterprise servers and cloud computing platforms. But in December 2020, CentOS announced that it would stop maintenance! CentOS Linux 8 has stopped updating and releasing on December 31, 2021; CentOS Linux 7 will also cease service on June 30, 2024.
This will mean that users will no longer be able to obtain official patch installation support and system upgrades. Domestic enterprises and developers are important user groups of CentOS. The cessation of maintenance of CentOS will undoubtedly bring huge challenges and risks to enterprise business operations and digital transformation: for example, the current version will not be able to obtain technological evolution and version upgrades in the future, resulting in product interruptions that cannot be continued. ; Enterprises will face huge security vulnerabilities and other problems. Security vulnerabilities have no one to manage and repair them, and data security is threatened; they will no longer be able to obtain professional help from upstream communities and technical service information; newly launched software and hardware systems are no longer compatible with the original ones. Operating systems and system construction are restricted...
But even if CentOS is about to be discontinued, Linux still occupies an absolute leading position in China's server operating system market, with a market share of 79.2%. In mainstream industries such as telecommunications and energy, RHEL and CentOS account for more than half. How should existing CentOS Linux operating system users respond? What strategies and practical experiences can we learn from?
It is crucial to migrate existing CentOS systems as quickly as possible to avoid security vulnerabilities and missing functionality.
2. About Inspur Information KeyarchOS
Based on this situation, Inspur Information X2Keyarch migration tool came into being;
As one of the leading cloud computing and data center service providers, Inspur Information began to develop its own server operating system as early as 2008. The product name at that time was K-UX. After more than ten years of continuous iterative updates, in December 2022 Inspur information publishing server operating system KeyarchOS (Chinese name Yunluan, referred to as KOS). Compared with K-UX, which is mainly targeted at key application hosts and supports Power architecture; KeyarchOS is mainly targeted at general server operating systems and supports x86 and ARM architectures.
X2Keyarch is a tool developed by Inspur Information specifically for business migration. It can assist customers to quickly and efficiently migrate data from other systems to the Inspur Information operating system. The tool provides a variety of migration solutions to meet the needs of different business scenarios and data structures. It supports batch migration, incremental migration, batch migration and other methods, and can verify and clean the migrated data to ensure the accuracy and completeness of the data.
X2Keyarch contains four major functional modules, as follows:
| Host management | Migration assessment | Migration implementation | Log management |
|---|---|---|---|
| Migrate host management Cluster management |
Risk Assessment System Assessment Hardware Assessment Application Assessment |
Batch migration System restore System backup Single-step migration |
Operation Log Evaluation Log Implementation Log |
Next, we use actual migration operation cases to get started and experience each functional module of the X2Keyarch migration tool.
3. Inspur Information KeyarchOS License application migration practice
In this case, we will carry out the practical operation of KeyarchOS License application migration.
Step 1: Verification before migration
First, connect to the server to be migrated. The server IP address is: 82.156.143.200. A complete License application has been deployed on this server;
Next, start the front-end and back-end services respectively;
# 启动数据库
systemctl start mariadb
# 启动后端服务
cd /data/snms/official/
sh snmsstart.sh
# 启动前端服务
cd /data/snms/official/inspurnode/kos/bin
sh start.sh &
After the service is started, go to the browser to access the server IP to open the login page;
Username: admin
Password: Inspur1!
After entering the user name and password, enter the backend of the Inspur Information Serial Number Management System;
It can be seen that the migrated server connection is normal so far, the front-end and back-end services are started normally, and the system and data are accessed normally;
Verification completed before migration.
Step 2: Migrate
In this step, you need to use the migration server (note that this server is used for migration operations, not the migrated server), and the browser accesses the IP 182.92.82.159 to enter Inspur operating system control Panel;
Username: admin
Password: 123456a?
Open the host management page and find the host with IP 82.156.143.200, which is the migrated server we verified in the first step;
Select "Operating System Migration"–>"Migration Assessment" to assess migration risks;
The evaluation here is mainly to evaluate whether there are risks in this migration. The system evaluation is to evaluate whether the system configuration information is compatible with the KOS system. The hardware evaluation is to evaluate whether the hardware under the system is compatible with the KOS system.
Wait for the assessment to be completed;
Awaiting assessment results;
High-risk items do not need attention and will not affect migration. Only the inhibitor option will affect migration.
Select Operating System Migration–>Migration Implementation to start the migration. Fill in the server information to be migrated;
Wait for the migration to complete;
After the migration is officially started, the migration status will change to Running, and then progress will begin;
I found an exception during the operation. The migration status was always "running" and it took too long.
The migration is completed and the system version has changed to kos5.8.
Step 3: Post-migration verification
After the migration is completed, log in to the migrated server again and start the front-end and back-end programs;
Enter the page: https://82.156.143.200:8443/snms/login.html;
Username: admin
Password: Inspur1!
login successful;
Open the authorization query page, enter the order number AS000106666777778889, click Authorization Query, and you can see the query results;
The result is correct, there are no exceptions in the migration, and the migration operation is completed.
4. Write at the end
By using Inspur X2Keyarch migration tool this time to migrate KeyarchOS License applications, X2Keyarch’s overall performance in migrating KeyarchOS License applications is excellent.
First of all, from the perspective of the entire interface of the tool, the overall interface is friendly and easy to operate. As can be seen from the above practical operation, the entire migration is actually a process of evaluation + migration. The user only needs to configure the server address, and the rest is basically a matter of clicking a button. There are only a few simple steps, even if it is the first time to get started. You can also get started quickly. In addition, during the entire migration process, the application system ran smoothly and the data was accurate, making it truly efficient, accurate and easy to use.
I also encountered a problem during the operation, that is, the "in progress" status lasted too long after the official start of the migration (the migration started on the first night and was still in progress on the second night). Later, I reported feedback to the official staff and they received timely feedback. solved the problem. I analyzed that this may be a status update problem. The application has been migrated long ago, but the update status has not been updated, and users cannot perform other operations if the status remains unchanged.
Generally speaking, the Inspur Information X2Keyarch migration tool is a very good migration tool. Regarding the lack of efficient one-stop migration tools, X2Keyarch has undoubtedly filled this gap very well. Although there are still some details that need to be improved, overall I am very satisfied with this use.