CN115643168B - Node super-fusion upgrading method, device, equipment and storage medium - Google Patents
Node super-fusion upgrading method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115643168B CN115643168B CN202211286846.7A CN202211286846A CN115643168B CN 115643168 B CN115643168 B CN 115643168B CN 202211286846 A CN202211286846 A CN 202211286846A CN 115643168 B CN115643168 B CN 115643168B
- Authority
- CN
- China
- Prior art keywords
- service
- node device
- node
- stateless
- master node
- 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.)
- Active
Links
Abstract
The application relates to a node super-fusion upgrading method, device, equipment and storage medium, and in particular relates to the technical field of cloud service. The method comprises the following steps: controlling each node device to copy each service in a control virtual manager deployed on each node device to a target container, and deploying the target container on each node device respectively; deploying load balancers on the main node equipment and the non-main node equipment respectively; controlling non-master node equipment to start a load equalizer and stateless service; the control master node device closes the control virtual manager and starts a load equalizer and a stateful service in the master node device; the control master node device initiates a stateless service on the master node device and deletes the control virtual manager. According to the scheme, on the basis that upgrade failure caused by deletion of the control virtual manager is avoided, each service is started smoothly, and service interruption time caused by service starting is reduced.
Description
Technical Field
The invention relates to the technical field of cloud services, in particular to a node super-fusion upgrading method, device, equipment and storage medium.
Background
The super fusion architecture is a new generation of laterally-expanded software defined architecture, and is composed of general hardware units integrating CPU, memory, storage, network and virtualized software platform, and has no fixed central node. The core concept of the method comprises linear lateral expansion, integration of computing capacity and storage capacity, and a server side adopts a high-speed flash memory as a storage medium.
In the existing super-fusion architecture, a super-fusion management system operates in a control virtual manager, when the automatic upgrading of the super-fusion architecture is realized, a user logs in the management system, and clicks upgrading on a web page, and at the moment, cloud management service in a background can regulate service of cloud platform life cycle management to upgrade a storage, physical machine system and the control virtual manager after receiving an upgrading instruction.
However, in the above scheme, the control virtual manager needs to be uninstalled and then installed when upgrading, which can cause that the cloud pipe cannot be logged in, and the cloud pipe is failed to upgrade.
Disclosure of Invention
The application provides a node super-fusion upgrading method, device, equipment and storage medium, which enable each service to be started smoothly on the basis of avoiding upgrading failure caused by deleting a control virtual manager, and reduce service interruption time caused by service starting.
In one aspect, a node super-fusion upgrading method is provided, and the method is applied to control equipment in a cloud service system; the cloud service system further comprises various node devices, each node device comprises a main node device and a non-main node device, and the method comprises the following steps:
controlling each node device to copy each service in a control virtual manager deployed on each node device to a target container, and deploying the target container on each node device respectively; each service comprises a stateless service and a stateful service;
deploying a load balancer on the master node device and the non-master node device respectively;
controlling the non-master node device to start the load balancer and the stateless service;
the master node equipment is controlled to close the control virtual manager, and a load equalizer and stateful service in the master node equipment are started;
and controlling the master node equipment to start stateless service on the master node equipment, and deleting the control virtual manager to complete the node super-fusion upgrading.
In still another aspect, a node super-fusion upgrade apparatus is provided, where the apparatus is configured to control devices in a cloud service system; the cloud service system further comprises each node device, each node device comprises a main node device and a non-main node device, and the device comprises:
The container deployment module is used for controlling each node device to copy each service in the control virtual manager deployed on each node device to a target container, and deploying the target container on each node device respectively; each service comprises a stateless service and a stateful service;
the load balancing deployment module is used for deploying a load balancer on the main node equipment and the non-main node equipment respectively;
a non-master node starting module, configured to control the non-master node device to start the load balancer and the stateless service;
the master node starting module is used for controlling the master node equipment to close the control virtual manager and starting a load equalizer and stateful service in the master node equipment;
and the manager deleting module is used for controlling the master node equipment to start the stateless service on the master node equipment and deleting the control virtual manager so as to complete the node super fusion upgrading.
In one possible implementation, the apparatus further includes an upgrade module;
the upgrade module is used for upgrading the distributed storage shared by the node devices and the service and operating system on the node devices.
In one possible implementation, the apparatus further includes a high availability component control module for stopping high availability components on the respective node devices; the high availability component is used for controlling the storage of each node device and controlling the switching of the virtual manager.
In one possible implementation, the manager deletion module is further configured to:
controlling the master node device to start stateless services on the master node device;
starting up high-availability components on each node device after detecting that the stateless service on the master node device is started up;
deleting the control virtual manager on each node device to complete the super-fusion upgrade of the nodes.
In one possible implementation, the high availability component control module is further configured to:
detecting the states of the node devices;
and stopping the high-availability components of each node device when the node devices are detected to be in the health state.
In one possible implementation, the high availability component control module is further configured to:
when detecting that each node device is in a health state, carrying out data backup on target data in each node device;
And stopping the high-availability components of each node device after the target data backup in each node device is detected.
In one possible implementation, the apparatus further includes:
the upgrade termination module is used for closing the stateful service and the load equalizer in the main node equipment and starting the control virtual manager when the upgrade failure condition triggered by the main node equipment is detected;
the upgrade failure condition includes at least one of:
the control virtual manager fails to close;
the load balancer fails to start;
and the stateful service fails to start.
In one possible implementation, the target container includes at least a stateful container and a stateless container;
the container deployment module is further configured to control each node device, copy the stateful services deployed on each node device into a stateful container, and copy the stateless services deployed on each node device into a stateless container;
the stateful containers and stateless containers are deployed on the respective node devices, respectively.
In yet another aspect, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, the at least one instruction loaded and executed by the processor to implement the node super fusion upgrade method described above.
In yet another aspect, a computer readable storage medium having at least one instruction stored therein is provided, the at least one instruction loaded and executed by a processor to implement the above-described node superset upgrade method.
In yet another aspect, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the node super fusion upgrading method.
The technical scheme that this application provided can include following beneficial effect:
in order to realize node supersusion, the control device can copy stateless services and stateful services in the control virtual manager into a target container, the target container is respectively deployed on each node device, the control device deploys a load balancer on each node device, and the control device controls the non-master node device to start the load balancer and the stateless services in each service; the control virtual manager of the main node equipment is controlled to be closed, and the load balancer and the stateful service in the main node equipment are started, at the moment, although the control virtual manager is closed, the load balancer can forward the service to the stateless service in the non-main node equipment when receiving the service, if the stateless service needs to access the stateful service, the stateful service in the main node equipment can be accessed, and at the moment, although the control virtual manager is closed, the substitution of the control virtual manager can be realized through the target container; the control device then controls the main node device to start the rest stateless services, and deletes the control virtual manager to complete the super-fusion upgrade of the nodes. In the scheme, the control virtual manager is replaced by the target container, and the stateful service and the stateless service in the target container are started step by step, so that each service is smoothly started on the basis of avoiding upgrade failure caused by deleting the control virtual manager, and service interruption time caused by service starting is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram illustrating a structure of a cloud service system according to an exemplary embodiment.
FIG. 2 is a method flow diagram illustrating a method of node superset upgrade, according to an example embodiment.
FIG. 3 is a method flow diagram illustrating a method of node superset upgrade, according to an example embodiment.
FIG. 4 illustrates a block flow diagram of a node superset upgrade in accordance with an embodiment of the present application.
Fig. 5 shows a logic diagram of a node before upgrade according to an embodiment of the present application.
Fig. 6 shows a container creation schematic according to an embodiment of the present application.
Fig. 7 shows a service start-up schematic of a non-master node device according to an embodiment of the present application.
Fig. 8 shows a schematic diagram of a node device after a service related to an embodiment of the present application is completely started.
Fig. 9 shows a schematic diagram of a node device after a service related to an embodiment of the present application is completely started.
Fig. 10 shows a schematic diagram of a system architecture after the upgrade according to an embodiment of the present application is completed.
Fig. 11 shows a node super-fusion upgrade apparatus according to an embodiment of the present application.
Fig. 12 is a schematic diagram of a computer device according to an exemplary embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made apparent and fully in view of the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.
In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.
In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited.
Fig. 1 is a schematic diagram illustrating a structure of a cloud service system according to an exemplary embodiment. The system includes various node devices including a master node device 110 and a non-master node device 120.
That is, in the embodiments related to the present application, each node device may be considered to include only the master node device 110 and the non-master node device 120, and the node super-fusion upgrade method described in the embodiments related to the present application is used to implement super-fusion upgrade on two nodes (that is, the master node device and the non-master node device).
Optionally, the master node device 110 and the non-master node device 120 are in a super-converged architecture, and a super-converged management system of the two node devices is deployed in a Control Virtual Manager (CVM), where services running in the CVM manage the two node devices (i.e., physical machines) through a network.
Optionally, life cycle management (hereinafter abbreviated LCM in the specification, abbreviated as LCM life cycle management in english) is disposed in the master node device 110 and the non-master node device 120, and the life cycle management LCM is responsible for upgrading, expanding, and replacing the functions of the cluster.
Optionally, the master node device 110 and the non-master node device 120 have at least one shared storage, and the data of the stateful service controlling the virtual manager CVM is stored in the shared storage, and the data of the stateless service is placed on an operating system disk of the physical machine, so that only one node of the two node devices starts to control the virtual manager CVM (i.e. the master node device) at any time. The switching of control virtual manager CVM and storage is controlled by the high availability component HA-service on each node. In the node device, the high-availability component HA-service is used for controlling storage and switching of the CVM, and when detecting a CVM failure of the master node device, the high-availability component HA-service can open the control virtual manager CVM of the non-master node device, thereby realizing switching of the control virtual manager CVM.
Optionally, the cloud service system further includes a control device (not shown in fig. 1), where the control device may monitor a state of each node device during the super-fusion upgrade process of each node device, and when detecting that the node device meets a preset condition, send a corresponding control instruction to the node device to control each node device to execute a preset operation, thereby completing the node super-fusion upgrade process.
The control device may be communicatively connected to each node device via a wired or wireless network.
Optionally, the cloud server may be a cloud server that provides basic operation and calculation services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDNs, and big data and artificial intelligence platforms.
Optionally, the cloud server 110 and the test instruction generating device 120 may be connected through a communication network. Alternatively, the communication network may be a wired network or a wireless network.
Alternatively, the wireless network or wired network described above uses standard communication techniques and/or protocols. The network is typically the internet, but may be any other network including, but not limited to, a local area network, a metropolitan area network, a wide area network, a mobile, a limited or wireless network, a private network, or any combination of virtual private networks. In some embodiments, techniques and/or formats including hypertext markup language, extensible markup language, and the like are used to represent data exchanged over a network. All or some of the links may also be encrypted using conventional encryption techniques such as secure socket layer, transport layer security, virtual private network, internet protocol security, etc. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.
FIG. 2 is a method flow diagram illustrating a method of node superset upgrade, according to an example embodiment. The method is performed by a computer device, which may be a control device in a cloud service system, the method comprising:
step 201, controlling the node devices to copy each service in the control virtual manager deployed on the node devices to a target container, and deploying the target container on the node devices respectively.
Wherein the respective services include stateless services and stateful services;
in this embodiment of the present application, the control device may first send an instruction to control each node device, and taking any node device as an example, after receiving the instruction sent by the control device, the node device may copy each service in the control virtual manager CVM deployed on the node device to a target container, and deploy the target container in the node device.
Because the target container has the functions of controlling each service in the virtual manager CVM, the target container can replace the functions of the virtual control manager CVM to a certain extent.
It should be noted that at this time, each service in the target container is not started, that is, each node device (i.e., the master node device and the non-master node device) is deployed with a target container for the non-started service.
And in the present embodiment, the respective services are further classified into stateful services and stateless services.
Stateful and stateless services are two different service architectures that differ in the handling of service states. The service state is the data required for a service request and may be a variable or a data structure. The stateless service does not record the service state, and different requests have no relation; whereas stateful services are vice versa. For the server program, whether it is a stateful service or a stateless service is determined based on whether two requests from the same initiator have a context relationship at the server side.
That is, for the stateless service, all the data that can be processed by the server side comes from the information carried by the request, and the stateless service processes a single request of the client side, and does not depend on other requests, and the information for processing the single request is contained in the request; for stateful services, the service may store data information related to the request context, and subsequent requests may be associated.
In the embodiment of the application, the data of the stateful service is placed on the distributed storage, and the data of the stateless service is placed on the operating system disk of each node device.
Step 202, deploying load balancers on the master node device and the non-master node device respectively.
After the target containers are deployed on the master node device and the non-master node device, the control device can also control the node device and the non-master node device to deploy the load balancer.
The load equalizer is responsible for traffic distribution and distributes received services, so that the quantity of the services processed by each node device is more balanced and reasonable.
Also, the load balancer deployed at this time is not started, and the load balancers which are not started are deployed in both the master node device and the non-master node device.
In step 203, the non-master node device is controlled to start the load balancer and the stateless service.
When the control device detects that the target container and the load balancer which are not started are deployed in the main node device and the non-main node device, the control device can start the load balancer and the stateless service in the non-main node device.
At this time, although the load balancer and the stateless service are started in the non-master node device, the host node device is a node device that directly receives the service, and the load balancer is not started in the master node device, so that the stateless service in the non-master node device does not process the service. At this time, the stateless service in the non-master node device and the load balancer are started in advance, so that the service interruption time is excessively long due to the fact that too many services are started at one time in the subsequent step can be prevented.
Step 204, the master node device is controlled to turn off the control virtual manager and start the load balancer and stateful services in the master node device.
After the control device detects that the load balancer and the stateless service in the non-master node device are started, the control device may send an instruction to the master node device to control the master node device to close the control virtual manager CVM and start the load balancer and the stateful service in the master node device.
At this time, although the control virtual manager CVM is turned off, after receiving the service, the master node device may split the service to the non-master node device through the load balancer, where the non-master node device determines the service first, and if the service needs to request the stateless service, directly accesses the stateless service in the non-master node device. If the service needs to request a stateful service, the service may access the stateful service in the primary node device via the vip (Virtual IP Address) address in the non-primary node device.
Through the above flow, even if the control virtual manager CVM is turned off, the stateful service and the stateless service respectively started on the master node device and the non-master node device can replace the function of the control virtual manager CVM.
Step 205, the master node device is controlled to start the stateless service on the master node device, and the control virtual manager is deleted, so as to complete the node super fusion upgrade.
And finally, the control equipment controls the main node equipment to start the stateless service on the main node equipment, and deletes the control virtual manager CVM, at the moment, the stateless service and the stateful service are started on the main node equipment, and the stateless service is started on the non-main node equipment, so that the substitution of the control virtual manager CVM is realized by the services deployed in the target container.
If a developer needs to upgrade some functions in the control virtual manager CVM, the developer can upgrade each service copied into the target container in the process of copying each service of the control virtual manager CVM into the target container, and at this time, the control virtual manager CVM is replaced by the target container, that is, the control virtual manager CVM is upgraded.
And because the stateless service is started on the main node equipment at this time, when the main node equipment receives the service, the service can be uniformly distributed to the stateless service of the main node equipment and the stateless service of the non-main node equipment, and when the service needs to access the stateful service, the stateful service on the main node equipment is accessed again.
In summary, in order to implement node supersusion, the control device may copy the stateless service and the stateful service in the CVM to the target container, and deploy the target container on each node device, and then the control device deploys the load balancer on each node device, and then the control device controls the non-master node device to start the load balancer and the stateless service in each service; the control virtual manager CVM of the master node equipment is controlled to be closed, and a load balancer and stateful services in the master node equipment are started, at the moment, although the control virtual manager CVM is closed, the load balancer can forward the service to stateless services in the non-master node equipment when receiving the service, if the stateless services need to access the stateful services, the stateful services in the master node equipment can be accessed, at the moment, although the control virtual manager CVM is closed, the substitution of the control virtual manager CVM can be realized through a target container; the control device then controls the main node device to start the rest stateless services, and deletes the control virtual manager CVM to complete the super-fusion upgrade of the nodes. In the scheme, the control virtual manager CVM is replaced by the target container, and the stateful service and the stateless service in the target container are started step by step, so that on the basis that upgrade failure caused by deletion of the control virtual manager CVM is avoided, each service is started smoothly, and service interruption time caused by service starting is reduced.
FIG. 3 is a method flow diagram illustrating a method of node superset upgrade, according to an example embodiment. The method is performed by a computer device, which may be a control device in a cloud service system, the method comprising:
step 301, the high availability components on the respective node devices are stopped.
Wherein the high availability component is used to control the storage of the respective node devices and to control the switching of the virtual manager CVM.
Before the super-fusion upgrade of the nodes is performed, the control device needs to deactivate the high-availability components on each node device, and when the Control Virtual Manager (CVM) in the master node device fails, the high-availability components can open the Control Virtual Manager (CVM) in the non-master node device, so that the switching of the Control Virtual Manager (CVM) is realized.
In the process of node supersusion upgrade, the Control Virtual Manager (CVM) in the master node equipment needs to be stopped, so that in order to avoid that the high-availability component detects service faults and controls the switching of the CVM, the high-availability component needs to be stopped before the upgrade process.
In one possible implementation, the state detection is performed on each node device;
When the respective node device is detected to be in a healthy state, the high availability component of the respective node device is stopped.
The control device also needs to detect the health state of each node device before stopping the high-availability assembly to start the node super-fusion upgrading process, and when each node device is in the health state and meets the requirement of the node super-fusion upgrading, the high-availability assembly of each node device is stopped; if at least one node device is in an unhealthy state, terminating the node super-fusion upgrading process.
In one possible implementation manner, when detecting that each node device is in a healthy state, performing data backup on target data in each node device;
and stopping the high-availability components of each node device after detecting that the target data in each node device is backed up.
Furthermore, in order to avoid the business trip in the upgrading process, the control device may first perform backup processing on the target data (such as predetermined important data) in each node device, and if an uncontrollable factor is encountered in the upgrading process to cause the upgrading failure, the control device may roll back the environment through the backup data.
Step 302, upgrade the distributed storage common to the respective node devices, as well as the services and operating systems on the respective node devices.
Before the node super fusion upgrade is performed, firstly, the distributed storage shared by all the nodes and the service and operating system on all the node devices can be upgraded. Distributed storage upgrades earlier because important data on the CVM is placed on the distributed storage, which needs to rely on the host operating system and services on the host.
That is, the storage services of the distributed storage common to the various nodes may be first performed prior to the node supersusion. The reason for the storage upgrade is that the CVM will use the storage. The distributed storage related in the embodiment of the application is a service running on 2 physical machines, forms a distributed storage cluster, and can improve functions such as block storage, object storage and file storage.
Further, in the process of upgrading the storage, the method can be realized by the following steps:
1. at the node without vip, the virtual machine running above is thermally migrated to the opposite-end server;
2. closing the storage service of the nodes without vip, wherein the storage is double-copy, and the node where vip is located can continue to operate at the moment;
3. Upgrading the storage service software package of the vip-free node;
4. starting up the vip-free node, and waiting for 2 nodes to completely and consistently update the vip node because the vip node takes over the service in the upgrading process and the data is continuously written;
5. migrating the virtual machine to a non-vip node;
6. upgrading the storage service of the vip node;
7. and starting the vip node storage service, waiting for finishing data balance, and finishing storage upgrading.
Further, the physical machines deployed by the nodes can be upgraded with operating systems, firmware, drivers and bios.
For example, in the embodiment of the present application, the upgrading process of the operating system, firmware, driver and bios of the physical machine may be implemented by the following steps:
1. at the node without vip, the virtual machine running above is thermally migrated to the opposite-end server;
2. upgrading a vip-free node operating system, taking centos as an example, wherein the upgrading method is a "yum update-y" command;
3. upgrading bios, raid drivers and the like through a web interface of an IPMI (ntelligent Platform Management Interface, intelligent platform management interface) system at a vip-free node;
4. restarting the vip-free node;
4. starting up the vip-free node, and waiting for 2 nodes to completely and consistently update the vip node because the vip node takes over the service in the upgrading process and the data is continuously written;
5. Migrating the virtual machine to a non-vip node;
6. the system and the drive for upgrading the vip node are the same as the method.
7. Starting vip node, waiting for finishing data balance and finishing upgrading.
In step 303, the respective node devices are controlled to copy the respective services in the control virtual manager CVM deployed on the respective node devices to the target containers, and the target containers are deployed on the respective node devices, respectively.
The respective services include stateless services and stateful services.
In one possible implementation, the target container includes at least a stateful container and a stateless container;
the control equipment controls each node equipment, copies the stateful service deployed on each node equipment into a stateful container, and copies the stateless service deployed on each node equipment into a stateless container;
the stateful container and the stateless container are deployed on the respective node devices, respectively.
In this embodiment of the present application, since a plurality of services are running in the CVM of the old version, both stateful services and stateless services exist, at this time, the services in the CVM may be split into two containers, that is, the stateless services are in one container, the stateful services are in one container, and when upgrading, a certain container may be independently started to implement independent starting of the stateful services or starting of the stateless services.
Step 304, deploying load balancers on the master node device and the non-master node device respectively.
In step 305, the non-master node device is controlled to start the load balancer and the stateless service.
Step 306, the master node device is controlled to turn off the control virtual manager CVM and start the load balancer and stateful services in the master node device.
Step 304 to step 306 refer to step 202 to step 204 in the embodiment shown in fig. 2, and are not described here again.
In one possible implementation, when a condition that the master node device triggers upgrade failure is detected, a stateful service and a load balancer in the master node device are closed, and the control virtual manager CVM is started; the upgrade failure condition includes at least one of:
the control virtual manager CVM fails to close;
the load balancer fails to start;
the stateful service start-up fails.
That is, in step 306, when the master node device turns off the control virtual manager CVM and starts the load balancer and the stateful service in the master node device, the control device turns off the stateful service and the load balancer when detecting that the master node device triggers the upgrade failure condition, immediately starts the old CVM, and finally informs the user of the upgrade failure through the cloud management.
In step 307, the master node device is controlled to initiate a stateless service on the master node device.
Step 308, after detecting that the stateless service on the master node device is started, starting up the high availability components on the respective node devices.
After the stateless service of the master node device is started, the master node device can process the service requiring the stateless service at the moment and can process the service requiring the stateless service; similarly, the non-master node device can process the service requesting stateless service, when the stateful service needs to be requested, the stateful service on the master node device can be requested through the vip address, so that service faults can not occur in the master node device and the non-master node device under normal conditions, and the high-availability component can be started.
Step 309, deleting the control virtual manager CVM on each node device to complete the node super fusion upgrade.
After the above steps are completed, the control device may control each node device, delete the control virtual manager CVM deployed on itself, thereby completing the node super-fusion upgrade procedure.
Referring to fig. 4, a flow chart of a node super fusion upgrade according to an embodiment of the present application is shown. As shown in fig. 4, the node super-fusion upgrade logic according to the embodiment of the present application may be as follows:
1. And carrying out health inspection and backup on important data of the environment before upgrading. The health inspection aims to discover the environmental problem in time, and if the problem is solved before upgrading, the problem is prevented from causing secondary disasters during upgrading. Important data backup is to prevent that if an upgrade process encounters an uncontrollable factor, the upgrade fails, and the environment can be rolled back through the important data.
Referring to fig. 5, a logic diagram of a node before upgrade according to an embodiment of the present application is shown. As shown in fig. 5, 2 physical machines are respectively deployed with a CVM, a high availability service HA-service, and a distributed storage service, where physical machine 1 is a master node device, and physical machine 2 is a non-master node device. Wherein CVM only the master node device is started, the CVM master-slave mode is controlled by the HA-service, and 2 nodes of the distributed storage service form a distributed storage resource pool.
2. The HA-service is stopped, and the HA-service is controlling storage and CVM switching. Because other services can be actively used in the upgrading process, the HA-service is prevented from detecting service faults and performing fault switching
3. Upgrade of the distributed storage services and operating systems on the physical machines is partly done because the important data on the CVM is placed on the distributed storage, which needs to rely on the host operating system and services on the host. The upgrade is done first to avoid a CVM upgrade.
4. Splitting the service on the previous CVM from one container into multiple containers. The split containers are created on 2 physical machines (i.e., the master node device and the non-master node device), respectively. One load balancer is deployed on each of the 2 physical machines.
Referring to fig. 6, a schematic diagram of creating a container according to an embodiment of the present application is shown. As shown in fig. 6, services in blue boxes are newly deployed at 2 nodes, respectively, and LB (LoadBalance) is a check of the load balancer, responsible for traffic distribution. Stateless services and stateful services are split up from services in the CVM. The services are deployed only but not started. In the following steps, the step is started up gradually.
5. The load balancer, stateless service is started on the non-master node. The part of services are started first, and the fast switching can be realized without perception in the subsequent switching.
Referring to fig. 7, a service start-up schematic diagram of a non-master node device according to an embodiment of the present application is shown. As shown in fig. 7, on the physical machine 1 (i.e., the master node device), the LB, stateless service, and stateful service are not started, whereas on the physical machine 2 (i.e., the non-master node device), the LB and stateful service are started, and the stateful service is not started.
6. The old CVM is started and stopped at the master node, and the stateful service and the load balancer of the node are started. If any step of the step fails, the stateful service and load equalizer is turned off, the old CVM is started immediately, and finally, a user is informed of the failure of upgrading through a cloud management, and professional support is sought after sales.
Referring to fig. 8, a service start-up schematic diagram of a master node device according to an embodiment of the present application is shown. As shown in fig. 8, the master node device (i.e., physical machine 1) stops the CVM and starts the LB service of the stateful service and the load balancer. At this time, the service accesses the LB of the master node through the vip address, and the service is split through the LB, and the LB automatically checks the service at the back end and splits the service to the physical machine 2. If stateless services need to access stateful services, traffic may access stateful services of the physical machine 1 via vip.
7. Stateless services and HA-services for 2 nodes are initiated at the master node.
Referring to fig. 9, a schematic diagram of a node device after a service related to an embodiment of the present application is completely started is shown. As shown in fig. 9, in the master node device (i.e., the physical machine 1), the LB service, the stateless service, the stateful service, and the HA-service of the load balancer are all in a started state, and the CVM is in an un-started state; in the non-master node device (i.e. the physical machine 2), the LB service, the stateless service and the HA-service of the load balancer are all in a start state; the stateful service is in an inactive state with the CVM.
8. The environment is cleaned up and old cvm and cvm images are deleted.
Referring to fig. 10, a schematic diagram of a system architecture after upgrading according to an embodiment of the present application is completed is shown. As shown in fig. 10, after cleaning up the environment, LB service, stateless service, stateful service, HA-service, and distributed storage of a load balancer are deployed in the physical machine 1; in the physical machine 2, LB services, stateless services, stateful services, HA-services, and distributed storage of the load balancer are also deployed, but the stateful services in the physical machine 2 are in an inactive state with respect to the physical machine 1.
In summary, in order to implement node supersusion, the control device may copy the stateless service and the stateful service in the CVM to the target container, and deploy the target container on each node device, and then the control device deploys the load balancer on each node device, and then the control device controls the non-master node device to start the load balancer and the stateless service in each service; the control virtual manager CVM of the master node equipment is controlled to be closed, and a load balancer and stateful services in the master node equipment are started, at the moment, although the control virtual manager CVM is closed, the load balancer can forward the service to stateless services in the non-master node equipment when receiving the service, if the stateless services need to access the stateful services, the stateful services in the master node equipment can be accessed, at the moment, although the control virtual manager CVM is closed, the substitution of the control virtual manager CVM can be realized through a target container; the control device then controls the main node device to start the rest stateless services, and deletes the control virtual manager CVM to complete the super-fusion upgrade of the nodes. In the scheme, the control virtual manager CVM is replaced by the target container, and the stateful service and the stateless service in the target container are started step by step, so that on the basis that upgrade failure caused by deletion of the control virtual manager CVM is avoided, each service is started smoothly, and service interruption time caused by service starting is reduced.
Referring to fig. 11, a node super-fusion upgrade apparatus according to an embodiment of the present application is shown. The device is arranged in control equipment in the cloud service system; the cloud service system further comprises each node device, each node device comprises a main node device and a non-main node device, and the device comprises:
a container deployment module 1101, configured to control the respective node devices to copy respective services in a control virtual manager deployed on the respective node devices to a target container, and deploy the target containers on the respective node devices respectively; each service comprises a stateless service and a stateful service;
a load balancing deployment module 1102, configured to deploy load balancers on the primary node device and the non-primary node device respectively;
a non-master node starting module 1103, configured to control the non-master node device to start the load balancer and the stateless service;
a master node starting module 1104, configured to control the master node device to close the control virtual manager, and start a load balancer and a stateful service in the master node device;
and the manager deleting module 1105 is configured to control the master node device to start a stateless service on the master node device, and delete the control virtual manager to complete node super fusion upgrade.
In one possible implementation, the apparatus further includes an upgrade module;
the upgrade module is used for upgrading the distributed storage shared by the node devices and the service and operating system on the node devices.
In one possible implementation, the apparatus further includes a high availability component control module for stopping high availability components on the respective node devices; the high availability component is used for controlling the storage of each node device and controlling the switching of the virtual manager.
In one possible implementation, the manager deletion module is further configured to:
controlling the master node device to start stateless services on the master node device;
starting up high-availability components on each node device after detecting that the stateless service on the master node device is started up;
deleting the control virtual manager on each node device to complete the super-fusion upgrade of the nodes.
In one possible implementation, the high availability component control module is further configured to:
detecting the states of the node devices;
and stopping the high-availability components of each node device when the node devices are detected to be in the health state.
In one possible implementation, the high availability component control module is further configured to:
when detecting that each node device is in a health state, carrying out data backup on target data in each node device;
and stopping the high-availability components of each node device after the target data backup in each node device is detected.
In one possible implementation, the apparatus further includes:
the upgrade termination module is used for closing the stateful service and the load equalizer in the main node equipment and starting the control virtual manager when the upgrade failure condition triggered by the main node equipment is detected;
the upgrade failure condition includes at least one of:
the control virtual manager fails to close;
the load balancer fails to start;
and the stateful service fails to start.
In one possible implementation, the target container includes at least a stateful container and a stateless container;
the container deployment module is further configured to control each node device, copy the stateful services deployed on each node device into a stateful container, and copy the stateless services deployed on each node device into a stateless container;
The stateful containers and stateless containers are deployed on the respective node devices, respectively.
In summary, in order to implement node supersusion, the control device may copy the stateless service and the stateful service in the target container, and deploy the target container on each node device, and then deploy the load balancer on each node device, and then the control device controls the non-master node device to start the load balancer and the stateless service in each service; the control virtual manager of the main node equipment is controlled to be closed, and the load balancer and the stateful service in the main node equipment are started, at the moment, although the control virtual manager is closed, the load balancer can forward the service to the stateless service in the non-main node equipment when receiving the service, if the stateless service needs to access the stateful service, the stateful service in the main node equipment can be accessed, and at the moment, although the control virtual manager is closed, the substitution of the control virtual manager can be realized through the target container; the control device then controls the main node device to start the rest stateless services, and deletes the control virtual manager to complete the super-fusion upgrade of the nodes. In the scheme, the control virtual manager is replaced by the target container, and the stateful service and the stateless service in the target container are started step by step, so that each service is smoothly started on the basis of avoiding upgrade failure caused by deleting the control virtual manager, and service interruption time caused by service starting is reduced.
Referring to fig. 12, a schematic diagram of a computer device according to an exemplary embodiment of the present application is provided, where the computer device includes a memory and a processor, and the memory is configured to store a computer program, where the computer program is executed by the processor to implement the method described above.
The processor may be a central processing unit (Central Processing Unit, CPU). The processor may also be any other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof.
The memory, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as program instructions/modules, corresponding to the methods in embodiments of the present invention. The processor executes various functional applications of the processor and data processing, i.e., implements the methods of the method embodiments described above, by running non-transitory software programs, instructions, and modules stored in memory.
The memory may include a memory program area and a memory data area, wherein the memory program area may store an operating system, at least one application program required for a function; the storage data area may store data created by the processor, etc. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some implementations, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
In an exemplary embodiment, a computer readable storage medium is also provided for storing at least one computer program that is loaded and executed by a processor to implement all or part of the steps of the above method. For example, the computer readable storage medium may be Read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), compact disc Read-Only Memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, and the like.
In an exemplary embodiment, a computer program product or a computer program is also provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions to cause the computer device to perform all or part of the steps of the method shown in any of the embodiments of fig. 2 or 3 described above.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (11)
1. The node super-fusion upgrading method is characterized by being applied to control equipment in a cloud service system; the cloud service system further comprises various node devices, each node device comprises a main node device and a non-main node device, and the method comprises the following steps:
step 1, controlling each node device to copy each service in a control virtual manager deployed on each node device to a target container, and deploying the target container on each node device respectively; each service comprises a stateless service and a stateful service;
step 2, deploying a load equalizer on the main node equipment and the non-main node equipment respectively; the load balancer is an unactuated load balancer;
step 3, controlling the non-master node equipment to start the load equalizer and the stateless service;
step 4, controlling the master node equipment to close the control virtual manager, and starting a load equalizer and stateful service in the master node equipment;
and 5, controlling the master node equipment to start stateless service on the master node equipment, and deleting the control virtual manager to complete the node super fusion upgrading.
2. The method according to claim 1, further comprising, prior to step 1:
and upgrading the distributed storage shared by the node devices and the service and operating system on the node devices.
3. The method of claim 2, wherein prior to said upgrading the distributed storage common to the respective node devices, further comprising:
stopping high availability components on the respective node devices; the high availability component is used for controlling the storage of each node device and controlling the switching of the virtual manager.
4. A method according to claim 3, wherein said step 5 comprises:
controlling the master node device to start stateless services on the master node device;
starting up high-availability components on each node device after detecting that the stateless service on the master node device is started up;
deleting the control virtual manager on each node device to complete the super-fusion upgrade of the nodes.
5. A method according to claim 3, wherein said stopping high availability components on said respective node devices comprises:
detecting the states of the node devices;
And stopping the high-availability components of each node device when the node devices are detected to be in the health state.
6. The method of claim 5, wherein the stopping the high availability component of the respective node device when the respective node device is detected to be in a healthy state comprises:
when detecting that each node device is in a health state, carrying out data backup on target data in each node device;
and stopping the high-availability components of each node device after the target data backup in each node device is detected.
7. The method according to any one of claims 1 to 6, further comprising:
step 6, when the condition that the main node equipment triggers the upgrade failure is detected, the stateful service and the load equalizer in the main node equipment are closed, and the control virtual manager is started;
the upgrade failure condition includes at least one of:
the control virtual manager fails to close;
the load balancer fails to start;
and the stateful service fails to start.
8. The method according to any one of claims 1 to 6, wherein the target container comprises at least a stateful container and a stateless container;
The step 1 comprises the following steps:
controlling each node device, copying the stateful services deployed on each node device into a stateful container, and copying the stateless services deployed on each node device into a stateless container;
the stateful containers and stateless containers are deployed on the respective node devices, respectively.
9. The node super-fusion upgrading device is characterized by being arranged in control equipment in a cloud service system; the cloud service system further comprises each node device, each node device comprises a main node device and a non-main node device, and the device comprises:
the container deployment module is used for controlling each node device to copy each service in the control virtual manager deployed on each node device to a target container, and deploying the target container on each node device respectively; each service comprises a stateless service and a stateful service;
the load balancing deployment module is used for deploying a load balancer on the main node equipment and the non-main node equipment respectively; the load balancer is an unactuated load balancer;
A non-master node starting module, configured to control the non-master node device to start the load balancer and the stateless service;
the master node starting module is used for controlling the master node equipment to close the control virtual manager and starting a load equalizer and stateful service in the master node equipment;
and the manager deleting module is used for controlling the master node equipment to start the stateless service on the master node equipment and deleting the control virtual manager so as to complete the node super fusion upgrading.
10. A computer device comprising a processor and a memory having stored therein at least one instruction that is loaded and executed by the processor to implement the node super fusion upgrade method of any of claims 1-8.
11. A computer readable storage medium having stored therein at least one instruction that is loaded and executed by a processor to implement the node super fusion upgrade method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211286846.7A CN115643168B (en) | 2022-10-20 | 2022-10-20 | Node super-fusion upgrading method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211286846.7A CN115643168B (en) | 2022-10-20 | 2022-10-20 | Node super-fusion upgrading method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115643168A CN115643168A (en) | 2023-01-24 |
| CN115643168B true CN115643168B (en) | 2023-08-04 |
Family
ID=84945444
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211286846.7A Active CN115643168B (en) | 2022-10-20 | 2022-10-20 | Node super-fusion upgrading method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115643168B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116483461B (en) * | 2023-03-09 | 2024-03-22 | 安超云软件有限公司 | Management platform control method and device of cloud primary integrated machine |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603696A (en) * | 2016-12-28 | 2017-04-26 | 华南理工大学 | High-availability system based on hyper-converged infrastructure |
| CN110912991A (en) * | 2019-11-22 | 2020-03-24 | 北京中实信息技术有限公司 | Super-fusion-based high-availability implementation method for double nodes |
| CN111935244A (en) * | 2020-07-20 | 2020-11-13 | 江苏安超云软件有限公司 | Service request processing system and super-integration all-in-one machine |
| CN112148485A (en) * | 2020-09-16 | 2020-12-29 | 杭州安恒信息技术股份有限公司 | Fault recovery method and device for super-fusion platform, electronic device and storage medium |
| CN112527325A (en) * | 2020-11-23 | 2021-03-19 | 山东乾云启创信息科技股份有限公司 | Deployment method and system applied to super-fusion architecture |
| CN113032085A (en) * | 2019-12-24 | 2021-06-25 | 中兴通讯股份有限公司 | Management method, device, server, management system and medium of cloud operating system |
| CN114020451A (en) * | 2021-10-13 | 2022-02-08 | 国网浙江省电力有限公司双创中心 | Super-fusion server control system, construction method, medium and application |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11194632B2 (en) * | 2019-06-18 | 2021-12-07 | Nutanix, Inc. | Deploying microservices into virtualized computing systems |
-
2022
- 2022-10-20 CN CN202211286846.7A patent/CN115643168B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106603696A (en) * | 2016-12-28 | 2017-04-26 | 华南理工大学 | High-availability system based on hyper-converged infrastructure |
| CN110912991A (en) * | 2019-11-22 | 2020-03-24 | 北京中实信息技术有限公司 | Super-fusion-based high-availability implementation method for double nodes |
| CN113032085A (en) * | 2019-12-24 | 2021-06-25 | 中兴通讯股份有限公司 | Management method, device, server, management system and medium of cloud operating system |
| CN111935244A (en) * | 2020-07-20 | 2020-11-13 | 江苏安超云软件有限公司 | Service request processing system and super-integration all-in-one machine |
| CN112148485A (en) * | 2020-09-16 | 2020-12-29 | 杭州安恒信息技术股份有限公司 | Fault recovery method and device for super-fusion platform, electronic device and storage medium |
| CN112527325A (en) * | 2020-11-23 | 2021-03-19 | 山东乾云启创信息科技股份有限公司 | Deployment method and system applied to super-fusion architecture |
| CN114020451A (en) * | 2021-10-13 | 2022-02-08 | 国网浙江省电力有限公司双创中心 | Super-fusion server control system, construction method, medium and application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115643168A (en) | 2023-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11449330B2 (en) | System and method for supporting patching in a multitenant application server environment | |
| US10237118B2 (en) | Efficient application build/deployment for distributed container cloud platform | |
| US10853056B2 (en) | System and method for supporting patching in a multitenant application server environment | |
| US11316800B2 (en) | Method and system for managing applications | |
| CN106991035B (en) | Host monitoring system based on micro-service architecture | |
| JP4426736B2 (en) | Program correction method and program | |
| US9753761B1 (en) | Distributed dynamic federation between multi-connected virtual platform clusters | |
| US8146073B2 (en) | Updating software while it is running | |
| CN107220100A (en) | One kind exploitation O＆M method, device and cloud computing PaaS platform | |
| US10387279B2 (en) | System and method for providing failovers for a cloud-based computing environment | |
| US11886902B2 (en) | Physical-to-virtual migration method and apparatus, and storage medium | |
| WO2016045439A1 (en) | Vnfm disaster-tolerant protection method and device, nfvo and storage medium | |
| CN111324377B (en) | Application gray level release method, system, device and storage medium | |
| CN111552489B (en) | User mode file system hot upgrading method, device, server and medium | |
| CN115643168B (en) | Node super-fusion upgrading method, device, equipment and storage medium | |
| KR102210408B1 (en) | Method for duplication of virtualization server and Virtualization control apparatus thereof | |
| CN109634638B (en) | Cluster software upgrading method, device, equipment and medium | |
| US11307842B2 (en) | Method and system for virtual agent upgrade using upgrade proxy service | |
| CN114691304A (en) | Method, device, equipment and medium for realizing high availability of cluster virtual machine | |
| CN115080176A (en) | SAAS method, SAAS platform and medium | |
| CN116527686A (en) | Bare metal opening method, device, equipment and storage medium based on intelligent network card | |
| CN116094897A (en) | Webpage configuration method, device and storage medium | |
| CN116225617A (en) | Management migration method and device for container instance, electronic equipment and storage medium | |
| CN114020292A (en) | Virtual NAS system upgrading method, device, equipment and storage medium |
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 |