CN112925609A - OpenStack cloud platform upgrading method and device - Google Patents
OpenStack cloud platform upgrading method and device Download PDFInfo
- Publication number
- CN112925609A CN112925609A CN202110224115.9A CN202110224115A CN112925609A CN 112925609 A CN112925609 A CN 112925609A CN 202110224115 A CN202110224115 A CN 202110224115A CN 112925609 A CN112925609 A CN 112925609A
- Authority
- CN
- China
- Prior art keywords
- environment
- containerization
- openstack
- cloud platform
- upgrading
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an OpenStack cloud platform upgrading method and device, belongs to the technical field of cloud platform upgrading, and aims to solve the technical problem of smoothly upgrading an OpenStack cloud platform running in a virtual machine to an OpenStack cloud platform managed based on container technology. The method is based on a mode of platform replacement and tenant migration, and the method is used for upgrading the OpenStack cloud platform which is not subjected to containerization deployment to the OpenStack cloud platform which is subjected to containerization deployment, and comprises the following steps: deploying a containerization environment and adjusting computing resources of the containerization environment; performing non-containerization environmental inspection; carrying out data plane upgrading; carrying out control plane upgrading; checking the version after upgrading; performing environment inspection after upgrading; carrying out client migration; and rolling back, recovering the haproxy configuration, restarting the service, and starting the OpenStack basic service and the OpenStack component service.
Description
Technical Field
The invention relates to the technical field of cloud platform upgrading, in particular to an OpenStack cloud platform upgrading method and device.
Background
OpenStack is today the most influential cloud computing management tool — managing the resource pool (servers, storage, and network) of the IaaS cloud through commands or Web-based visual control panels. OpenStack has reached a mature level in cloud platform architecture construction, and the main components of OpenStack include circuit, gloss, nova, neutron, ironic, horizons and the like, and also include components partially managed by the own platform, such as heat, ceilometer, watch and the like. In deployment, OpenStack supports virtual machine software or containers such as KVM, Xen, Lvc, Docker, and the like, and defaults to KVM. Hyper-V and VMware ESxi are also supported by installing drivers, although some functions are temporarily not supported. Since containerization fires later than the virtualization software and later than the OpenStack project began, the earliest approaches to using OpenStack were mostly virtual software based, mostly KVM.
The container technology is a kernel lightweight operating system layer virtualization technology. Compared with traditional virtualization, the container technology is launched into the market by the characteristics of light weight, second-level deployment, easiness in transplantation and elastic expansion. Currently, docker is almost a substitute for container, and the containerized deployment provided by OpenStack is also a docker-based container virtualization technology. The Docker is program software running on an operating system, and provides a container environment, so that the programs can run in the container independently, namely, components of the OpenStack can run in the container through the Docker, and the container technology has the advantages. The Docker main concept includes:
mirror Image (Image): a mirror image can be understood as a stack of static templates, the running mirror image being the container;
container (Container): when we pull a mirror image and run, a container can be run according to the mirror image, and the running container can be accessed and stopped just like our application program;
warehouse (reproducibility): where the mirror image is stored;
data volume (Volumn): the method is used for data sharing between containers of data persistence on the host machine, and simply means that the catalogue of the host machine is mapped to the catalogue in the container.
The operating principle of OpenStack deployment based on the virtual machine is as follows: the method comprises the steps of virtualizing hardware resources of a computer, distributing the hardware resources, and then virtualizing a plurality of operating systems to obtain a complete computer; the operating principle of deploying OpenStack based on docker is as follows: virtual software resources, which divide the network and storage in the computer into several virtual containers, the software runs in the containers, each container only occupies part of the resources needed by the computer, not a complete computer.
Since the OpenStack deployed in the early days is based on KVM, VMware and the like, with the popularization of container technology, the OpenStack management cloud platform is shaped by operating the OpenStack based on containerization deployment. This has led to the situation that most cloud product service companies are faced with two types of environments, which undoubtedly increases the complexity of platform product development and platform operation.
Based on the above, how to smoothly upgrade the OpenStack cloud platform running in the virtual machine to the OpenStack cloud platform managed based on the container technology is a technical problem to be solved.
Disclosure of Invention
The technical task of the invention is to provide an OpenStack cloud platform upgrading method and device aiming at the defects, so as to solve the technical problem of how to smoothly upgrade an OpenStack cloud platform running in a virtual machine to an OpenStack cloud platform managed based on a container technology.
In a first aspect, the invention provides an OpenStack cloud platform upgrading method, which is used for upgrading a non-containerized deployed OpenStack cloud platform to a containerized deployed OpenStack cloud platform based on a platform replacement and tenant migration mode, and comprises the following steps:
deploying a containerized environment and adjusting computing resources of the containerized environment, classifying all computing nodes of the non-containerized environment, wherein the containerized environment provides one computing node for each type;
performing non-containerization environment inspection, inspecting functions and nodes in the non-containerization environment, creating a virtual machine and inspecting whether the virtual machine is available;
carrying out data surface upgrading, deploying a containerized environment, backing up a database of the non-containerized environment, copying the database backed up by the non-containerized environment to a control node of the containerized environment, importing data into the containerized environment, and after the imported data is duralized, upgrading a data structure by using a db-sync process of the component in a redeployment process;
carrying out control plane upgrading, synchronizing the configuration information corresponding to the control plane of the containerization environment side to the non-containerization environment, and stopping the control plane of the non-containerization environment after the control plane of the non-containerization environment is butted with the control plane of the containerization environment;
checking the version after upgrading, and checking whether the components and the database version are upgraded to a high-version OpenStack cloud platform;
after upgrading, environment inspection is carried out, and a data plane, a control plane and functions are inspected;
carrying out client migration, and carrying out live migration testing on the virtual machines and migrating the client virtual machines;
and rolling back, recovering the haproxy configuration, restarting the service, and starting the OpenStack basic service and the OpenStack component service.
Preferably, the OpenStack cloud platform upgrade is limited to supporting cluster upgrade using distributed storage and limited to supporting adjacent version OpenStack upgrade.
Preferably, the checking of the functions in the non-containerization environment includes checking stability of an OpenStack platform, checking whether tenant side uses a normal virtual machine, and cleaning up a useless virtual machine in an error state, and the checking of the functions is covered by an OpenStack cluster, a storage cluster and a monitoring cluster.
Preferably, the nodes in the non-containerized environment are checked, including checking whether all the nodes are operating normally, whether the network is clear, and whether the time is synchronous.
Preferably, the database of the non-containerized environment is backed up by performing a database backup operation, and after the database of the non-containerized environment is backed up, the non-containerized environment does not allow a new service to be opened any more and does not allow the old service state to be changed.
Preferably, the imported data is persisted by persisted storage of the container.
Preferably, the control plane of the non-containerized environment and the control plane of the containerized environment are interfaced in a manner of: proxying an IP of a non-containerized environment to a service of a containerized environment;
by modifying the haprox service configuration mode, the service domain name of the containerization environment is analyzed to the IP of the non-containerization environment control service, so that the non-containerization environment and the containerization environment can be identified mutually, and the control surface of the non-containerization environment and the control surface of the containerization environment are communicated mutually.
Preferably, the data plane is checked, including checking the service state of the database;
checking the control surface, including checking API return difference inquiry and service state inquiry, and checking whether the service of the original non-containerization environment is normal in the containerization environment;
the functions are checked, including checking for virtual machine creation and deletion and volume creation, mount, offload, and deletion.
In a second aspect, the present invention provides apparatus comprising: at least one memory and at least one processor;
the at least one memory to store a machine readable program;
the at least one processor is configured to invoke the machine-readable program to perform the method of any of the first aspects.
In a third aspect, the present invention provides a computer readable medium having stored thereon computer instructions which, when executed by a processor, cause the processor to perform the method of any of the first aspects.
The OpenStack cloud platform upgrading method and device have the following advantages:
1. the scheme for upgrading from the OpenStack deployed in a lower version and non-containerization mode to the OpenStack deployed in a high version and a containerization mode is provided, and cloud platform operators can develop along with containerization and utilize the advantages of container technology;
2. the method supports upgrading of OpenStack large versions, and can be used as technical reference of cluster upgrading.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
The invention is further described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of an OpenStack cloud platform upgrade method according to embodiment 1;
fig. 2 is a logic block diagram of the OpenStack cloud platform upgrading method according to embodiment 1.
Detailed Description
The present invention is further described in the following with reference to the drawings and the specific embodiments so that those skilled in the art can better understand the present invention and can implement the present invention, but the embodiments are not to be construed as limiting the present invention, and the embodiments and the technical features of the embodiments can be combined with each other without conflict.
The embodiment of the invention provides an OpenStack cloud platform upgrading method and device, which are used for solving the technical problem of how to smoothly upgrade an OpenStack cloud platform running in a virtual machine to an OpenStack cloud platform based on container technology management.
Example 1:
the OpenStack cloud platform upgrading method of the invention upgrades the OpenStack cloud platform which is not arranged in a container mode to the OpenStack cloud platform which is arranged in a container mode based on the modes of platform replacement and tenant migration, and the method comprises the following steps:
s100, deploying a containerization environment, adjusting computing resources of the containerization environment, classifying all computing nodes of the non-containerization environment, and providing one computing node for each type of the containerization environment;
s200, checking a non-containerization environment, checking functions and nodes in the non-containerization environment, creating a virtual machine and checking whether the virtual machine is available;
s300, upgrading a data plane, deploying a containerized environment, backing up a database of a non-containerized environment, copying the database backed up by the non-containerized environment to a control node of the containerized environment, importing data into the containerized environment, and upgrading a data structure by using a db-sync process of the component in a redeployment process after the imported data is duralized;
s400, upgrading a control plane, synchronizing the configuration information corresponding to the control plane of the containerization environment side to the non-containerization environment, and stopping the control plane of the non-containerization environment after the control plane of the non-containerization environment is butted with the control plane of the containerization environment;
s500, checking the version after upgrading, and checking whether the components and the database version are upgraded to a high-version OpenStack cloud platform;
s600, performing environment inspection after upgrading, and inspecting a data plane, a control plane and functions;
s700, migrating the client, testing the virtual machine through live migration and migrating the client virtual machine;
and S800, rolling back, recovering haproxy configuration, restarting the service, and starting OpenStack basic service and OpenStack component service.
Wherein, platform replacement means: the control side of the OpenStack platform is upgraded firstly, the mode that platform control is docked to containerization firstly is guaranteed, host machine nodes are closed one by one if management node host machines of the original non-containerization environment need to be operated in the platform upgrading process, and the management nodes are guaranteed to meet high availability requirements and prevent the normal operation of the original non-containerization environment from being influenced. The control surface replacement and upgrade of the platform means that a set of OpenStack environments meeting the specification is deployed based on a container technology before upgrade. Because the original non-containerization environment has a running service, the upgrading strategy is completely adaptive to the containerization environment in the non-containerization environment, and therefore the containerization environment is required to meet the following requirements during the preparation: to maintain consistency of the network configuration model, to maintain consistency of the basic service configuration, to maintain consistency of the component configuration, the cluster storage operates normally and can interface to the containerization environment.
The node that this embodiment relates to includes: control nodes, computing nodes, network nodes, and are not involved in upgrading storage.
In step S100, resource preparation and limitation are required before upgrading. The embodiment upgrades the system in a mode of platform replacement and tenant migration. Before upgrading, deployment of a set of containerization environments needs to be completed, so required resources comprise all controls required by a set of standard containerization deployment, and the actual control resource scale is adjusted according to the requirements of operators and customers. Regarding the computing resource demand of the containerized environment, for a large-scale cluster, for example, a cluster with more than 20 computing nodes, the requirement of the cloud platform operator for giving resources of the same scale in the containerized environment is too high, and the requirement is also a waste of resources and an increase in complexity of upgrading. The present solution therefore proposes to classify all the compute nodes of a non-containerized environment, the containerized environment providing only one compute node for each type to ensure that the resource requirements can also be minimized by live-migration checks on the type.
The embodiment only supports cluster upgrading using distributed storage, for example, the service storage condition of the client host needs to be considered according to the actual condition when using local storage, and the service needs to be specifically analyzed according to the service type of the platform operator, so that the solution does not provide a cluster upgrading scheme using centralized storage.
In the embodiment, only the adjacent version OpenStack upgrade is supported, for example, the Queens version is upgraded to the Rocky version, and due to the limitation of community iterative development, the upgrade cannot be performed across multiple versions.
In the step S200, in the inspection before the upgrade, non-containerization environmental inspection is required before the upgrade, so as to ensure that the original environment operates normally, and the inspection contents include the following:
(1) and function checking is carried out to ensure that the original non-containerized environment function can be normally used, the platform is stable, the tenant side is normally used, and useless virtual machines in error states are cleared. Inspection coverage is not limited to: an OpenStack cluster, a storage cluster, a monitoring cluster, etc.;
(2) and (3) node checking: all nodes operate normally, the network is smooth, and the time is synchronous;
(3) and creating a test virtual machine and checking that the test virtual machine is available.
Step S300, upgrading the data plane, wherein the upgrading preparation comprises the following steps:
(1) and (3) completing empty containerization environment deployment: to finish the data surface upgrading, firstly finishing the deployment of a containerization environment, at least finishing the deployment of a containerization environment database service, and providing conditions for database backup and import;
(2) data backup: the database of the non-containerized environment is backed up by performing a database backup operation. After the backup is finished, the non-containerization environment does not allow a new service to be opened any more, and also does not allow the old service state to be changed, so that the data is prevented from changing to cause migration failure;
(3) data copying and importing: and copying the database backed up by the non-containerization environment to a control node of the containerization environment, and importing the data to the containerization environment. The data plane upgrading preparation is completed;
(4) and (3) upgrading: the upgrade of the data plane is automatically completed by re-executing the deployment. After the imported data is persisted by using the persistent storage of the container, the db-sync process of the component is used to complete the upgrading of the data structure in the redeployment process.
And when the database is upgraded, the database structure is upgraded in a backup, import and db-sync deployment mode, so that the database is adaptive to the high version.
The control plane upgrading method in step S400 includes: the containerized environment exposes the service IP, and the non-containerized environment resolves the domain name of the containerized environment by changing the proxy configuration. Attention is required in the execution process: in order to minimize modifications and service restarts on the non-containerized side, the configuration information of the control plane on the containerized environment side should be completely synchronized with the non-containerized environment.
The control surface upgrading is mainly characterized in that the control surfaces of the two environments are successfully connected, and the calculation, storage and network service of the non-containerized environment can be controlled at one side of the containerized environment. The butt joint mode is as follows: the IP of the non-containerized environment is proxied to the service of the containerized environment.
The method is characterized in that a non-containerization environment deployed in a KVM mode is identified by using a proxy of haproxy, so that a mode of modifying the configuration of the haprox service is adopted during docking, a service domain name of the containerization environment is analyzed to an IP (Internet protocol) of a non-containerization environment control service, two sets of environments can be identified mutually, and the control plane is communicated.
After the containerized environment successfully takes over the computation, storage and network service of the non-containerized environment, the control plane of the non-containerized environment is immediately stopped, because the used database is the database after the containerized environment is upgraded, and the service is in a down state due to the inconsistent data structure when the original non-containerized environment is not stopped.
Step S500, checking the version after upgrading, and after upgrading is completed, checking whether the component and the database version are successfully upgraded to the OpenStack of the high version, such as the Nova version:
Queens：17.0.X
Rocky：18.0.X
step S600, upgrading environment checking, wherein the checking content comprises:
(1) data plane: checking the service state of the database;
(2) control plane: the API returns to inquire, service state is inquired, and whether the service of the original non-containerized environment is normal or not is noticed;
(3) the functions are as follows: virtual machine creation, deletion, volume creation, mounting, uninstallation, deletion.
In the step S700, the client migration includes the following steps:
(1) the virtual machine is tested by thermal migration, and the process comprises the steps of observing whether the virtual machine is normally available after migration;
(2) migrating client virtual machines, suggesting few concurrencies;
(3) after all the migration is successful, the computing nodes and the gateway nodes of the original non-containerization environment are shut down and stop service, and the upgrading of the non-containerization environment to the containerization environment OpenStack is ended.
In the rollback process of step S800, the following contents are included:
(1) restoring the haproxy configuration and restarting the service;
(2) starting OpenStack basic service: mysql, rabbitmq;
(3) the OpenStack component service is started.
In the method for upgrading the OpenStack cloud platform, as shown in fig. 2, by taking kubernets management container environment as an example, deployment of a containerization environment needs to be completed before upgrading a control plane, and after completion, two sets of environment butt joints are completed by changing an original proxy into an IP and a domain name of a service exposed to the outside by the containerization environment, so that upgrading of the control plane is completed. The method can realize version upgrading from non-containerized deployment of OpenStack to containerized deployment of OpenStack. The method can ensure both OpenStack upgrading and containerized deployment upgrading in a non-containerized environment; the sequence of upgrading is as follows: data plane upgrading, control plane upgrading, service stopping of an original control plane and tenant service hot migration. The tenant service migration mode is thermal migration, and tenant perception is reduced.
Example 2:
an apparatus of the present invention comprises: at least one memory and at least one processor; the at least one memory for storing a machine-readable program; the at least one processor is used for calling the machine readable program and executing the method disclosed by the embodiment 1.
Example 3:
an embodiment of the present invention further provides a computer-readable medium, where computer instructions are stored on the computer-readable medium, and when the computer instructions are executed by a processor, the processor is caused to execute the method disclosed in embodiment 1. Specifically, a system or an apparatus equipped with a storage medium on which software program codes that realize the functions of any of the above-described embodiments are stored may be provided, and a computer (or a CPU or MPU) of the system or the apparatus is caused to read out and execute the program codes stored in the storage medium.
In this case, the program code itself read from the storage medium can realize the functions of any of the above-described embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.
Examples of the storage medium for supplying the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (e.g., CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW), a magnetic tape, a nonvolatile memory card, and a ROM. Alternatively, the program code may be downloaded from a server computer via a communications network.
Further, it should be clear that the functions of any one of the above-described embodiments may be implemented not only by executing the program code read out by the computer, but also by causing an operating system or the like operating on the computer to perform a part or all of the actual operations based on instructions of the program code.
Further, it is to be understood that the program code read out from the storage medium is written to a memory provided in an expansion board inserted into the computer or to a memory provided in an expansion unit connected to the computer, and then causes a CPU or the like mounted on the expansion board or the expansion unit to perform part or all of the actual operations based on instructions of the program code, thereby realizing the functions of any of the above-described embodiments.
While the invention has been shown and described in detail in the drawings and in the preferred embodiments, it is not intended to limit the invention to the embodiments disclosed, and it will be apparent to those skilled in the art that various combinations of the code auditing means in the various embodiments described above may be used to obtain further embodiments of the invention, which are also within the scope of the invention.
Claims (10)
- The OpenStack cloud platform upgrading method is characterized in that a non-containerized deployed OpenStack cloud platform is upgraded to a containerized deployed OpenStack cloud platform based on a platform replacement and tenant migration mode, and the method comprises the following steps:deploying a containerized environment and adjusting computing resources of the containerized environment, classifying all computing nodes of the non-containerized environment, wherein the containerized environment provides one computing node for each type;performing non-containerization environment inspection, inspecting functions and nodes in the non-containerization environment, creating a virtual machine and inspecting whether the virtual machine is available;carrying out data surface upgrading, deploying a containerized environment, backing up a database of the non-containerized environment, copying the database backed up by the non-containerized environment to a control node of the containerized environment, importing data into the containerized environment, and after the imported data is duralized, upgrading a data structure by using a db-sync process of the component in a redeployment process;carrying out control plane upgrading, synchronizing the configuration information corresponding to the control plane of the containerization environment side to the non-containerization environment, and stopping the control plane of the non-containerization environment after the control plane of the non-containerization environment is butted with the control plane of the containerization environment;checking the version after upgrading, and checking whether the components and the database version are upgraded to a high-version OpenStack cloud platform;after upgrading, environment inspection is carried out, and a data plane, a control plane and functions are inspected;carrying out client migration, and carrying out live migration testing on the virtual machines and migrating the client virtual machines;and rolling back, recovering the haproxy configuration, restarting the service, and starting the OpenStack basic service and the OpenStack component service.
- 2. The OpenStack cloud platform upgrade method according to claim 1, wherein the OpenStack cloud platform upgrade is limited to support only cluster upgrade using distributed storage and limited to support only adjacent version OpenStack upgrade.
- 3. The OpenStack cloud platform upgrade method according to claim 1, wherein checking functions in a non-containerized environment, including checking OpenStack platform stability, checking whether tenant side usage is normal, and cleaning up useless virtual machines in error state, is covered with OpenStack clusters, storage clusters, and monitoring clusters.
- 4. The OpenStack cloud platform upgrade method according to claim 1, wherein the checking of nodes in a non-containerized environment includes checking whether all nodes are operating normally, whether a network is clear, and whether time is synchronized.
- 5. The OpenStack cloud platform upgrade method according to claim 1, wherein the database of the non-containerization environment is backed up by performing a database backup operation, and after the database of the non-containerization environment is backed up, the non-containerization environment does not allow a new service to be opened any more and does not allow an old service state to be changed.
- 6. The OpenStack cloud platform upgrade method according to claim 1, wherein the imported data is persisted through persistent storage of a container.
- 7. The OpenStack cloud platform upgrade method according to claim 1, wherein the docking manner for docking the control plane of the non-containerized environment with the control plane of the containerized environment is: proxying an IP of a non-containerized environment to a service of a containerized environment;by modifying the haprox service configuration mode, the service domain name of the containerization environment is analyzed to the IP of the non-containerization environment control service, so that the non-containerization environment and the containerization environment can be identified mutually, and the control surface of the non-containerization environment and the control surface of the containerization environment are communicated mutually.
- 8. The OpenStack cloud platform upgrade method according to claim 1, wherein checking the data plane comprises checking a database service state;checking the control surface, including checking API return difference inquiry and service state inquiry, and checking whether the service of the original non-containerization environment is normal in the containerization environment;the functions are checked, including checking for virtual machine creation and deletion and volume creation, mount, offload, and deletion.
- 9. An apparatus, comprising: at least one memory and at least one processor;the at least one memory to store a machine readable program;the at least one processor, configured to invoke the machine readable program, to perform the method of any of claims 1 to 8.
- 10. Computer readable medium, characterized in that it has stored thereon computer instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110224115.9A CN112925609B (en) | 2021-03-01 | 2021-03-01 | OpenStack cloud platform upgrading method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110224115.9A CN112925609B (en) | 2021-03-01 | 2021-03-01 | OpenStack cloud platform upgrading method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112925609A true CN112925609A (en) | 2021-06-08 |
| CN112925609B CN112925609B (en) | 2022-03-15 |
Family
ID=76172704
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110224115.9A Active CN112925609B (en) | 2021-03-01 | 2021-03-01 | OpenStack cloud platform upgrading method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112925609B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687867A (en) * | 2021-08-24 | 2021-11-23 | 济南浪潮数据技术有限公司 | Shutdown method, system, equipment and storage medium of cloud platform cluster |
| US20230133312A1 (en) * | 2021-11-04 | 2023-05-04 | Red Hat, Inc. | Enhancing Operator Installation and Upgrade Management and Verification |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| CN108737468A (en) * | 2017-04-19 | 2018-11-02 | 中兴通讯股份有限公司 | Cloud platform service cluster, construction method and device |
| US20180343300A1 (en) * | 2017-05-26 | 2018-11-29 | Vmware Inc. | Methods and apparatus to perform data migration in a distributed environment |
| US20190163460A1 (en) * | 2017-11-29 | 2019-05-30 | Citrix Systems, Inc. | Cloud Service Automation of Common Image Management |
| US20190220271A1 (en) * | 2018-01-16 | 2019-07-18 | Nutanix, Inc. | Scheduling upgrades in distributed computing systems |
| CN110286930A (en) * | 2019-06-27 | 2019-09-27 | 腾讯科技（深圳）有限公司 | A kind of cloud platform upgrade method, device, terminal and storage medium |
| CN110445662A (en) * | 2019-08-29 | 2019-11-12 | 上海仪电（集团）有限公司中央研究院 | OpenStack control node is adaptively switched to the method and device of calculate node |
| CN111352653A (en) * | 2020-03-06 | 2020-06-30 | 中国工商银行股份有限公司 | System development method based on PaaS cloud platform server and server |
| CN111522628A (en) * | 2020-04-27 | 2020-08-11 | 上海仪电（集团）有限公司中央研究院 | Kubernets cluster building and deploying method, architecture and storage medium based on OpenStack |
| CN111880905A (en) * | 2020-08-03 | 2020-11-03 | 浪潮云信息技术股份公司 | Method for migrating virtual machine across cell by openstack |
| CN112003924A (en) * | 2020-08-20 | 2020-11-27 | 浪潮云信息技术股份公司 | Industrial internet-oriented edge cloud platform building method and system |
-
2021
- 2021-03-01 CN CN202110224115.9A patent/CN112925609B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| CN108737468A (en) * | 2017-04-19 | 2018-11-02 | 中兴通讯股份有限公司 | Cloud platform service cluster, construction method and device |
| US20180343300A1 (en) * | 2017-05-26 | 2018-11-29 | Vmware Inc. | Methods and apparatus to perform data migration in a distributed environment |
| US20190163460A1 (en) * | 2017-11-29 | 2019-05-30 | Citrix Systems, Inc. | Cloud Service Automation of Common Image Management |
| US20190220271A1 (en) * | 2018-01-16 | 2019-07-18 | Nutanix, Inc. | Scheduling upgrades in distributed computing systems |
| CN110286930A (en) * | 2019-06-27 | 2019-09-27 | 腾讯科技（深圳）有限公司 | A kind of cloud platform upgrade method, device, terminal and storage medium |
| CN110445662A (en) * | 2019-08-29 | 2019-11-12 | 上海仪电（集团）有限公司中央研究院 | OpenStack control node is adaptively switched to the method and device of calculate node |
| CN111352653A (en) * | 2020-03-06 | 2020-06-30 | 中国工商银行股份有限公司 | System development method based on PaaS cloud platform server and server |
| CN111522628A (en) * | 2020-04-27 | 2020-08-11 | 上海仪电（集团）有限公司中央研究院 | Kubernets cluster building and deploying method, architecture and storage medium based on OpenStack |
| CN111880905A (en) * | 2020-08-03 | 2020-11-03 | 浪潮云信息技术股份公司 | Method for migrating virtual machine across cell by openstack |
| CN112003924A (en) * | 2020-08-20 | 2020-11-27 | 浪潮云信息技术股份公司 | Industrial internet-oriented edge cloud platform building method and system |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113687867A (en) * | 2021-08-24 | 2021-11-23 | 济南浪潮数据技术有限公司 | Shutdown method, system, equipment and storage medium of cloud platform cluster |
| CN113687867B (en) * | 2021-08-24 | 2023-12-29 | 济南浪潮数据技术有限公司 | Shutdown method, system, equipment and storage medium of cloud platform cluster |
| US20230133312A1 (en) * | 2021-11-04 | 2023-05-04 | Red Hat, Inc. | Enhancing Operator Installation and Upgrade Management and Verification |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112925609B (en) | 2022-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062655B (en) | Containerized cloud platform and server | |
| US11556325B2 (en) | Software installation onto a client using existing resources | |
| US11416342B2 (en) | Automatically configuring boot sequence of container systems for disaster recovery | |
| US9075638B2 (en) | Efficient hosting of virtualized containers using read-only operating systems | |
| US9734019B2 (en) | Systems and methods for host image transfer | |
| US11146620B2 (en) | Systems and methods for instantiating services on top of services | |
| US9229707B2 (en) | Zero downtime mechanism for software upgrade of a distributed computer system | |
| CN112424750A (en) | Multi-cluster supply and management method on cloud platform | |
| US9703490B2 (en) | Coordinated upgrade of a cluster storage system | |
| US11385883B2 (en) | Methods and systems that carry out live migration of multi-node applications | |
| CN112424751A (en) | Cluster resource allocation and management method on cloud platform | |
| US10721125B2 (en) | Systems and methods for update propagation between nodes in a distributed system | |
| CN112925609B (en) | OpenStack cloud platform upgrading method and device | |
| CN110727653B (en) | Multi-project load balancing method and device | |
| US10715594B2 (en) | Systems and methods for update propagation between nodes in a distributed system | |
| CN110990026B (en) | Automatic deployment method and system for PaaS platform | |
| US20080256530A1 (en) | System and Method for Determining Firmware Compatibility for Migrating Logical Partitions | |
| CN112527349A (en) | Dynamic deployment strategy optimization and continuous deployment service guarantee system | |
| Oh et al. | Stateful container migration employing checkpoint-based restoration for orchestrated container clusters | |
| CN111338751B (en) | Cross-pool migration method and device for data in same ceph cluster | |
| US8930967B2 (en) | Shared versioned workload partitions | |
| CN116360834A (en) | Kubernetes cluster in-situ upgrading method and system based on OSTree | |
| Blaas et al. | Stateless provisioning: Modern practice in hpc | |
| CN115700465B (en) | Mobile electronic equipment and application method thereof | |
| US20240160354A1 (en) | Node cache migration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |