CN112398668B - IaaS cluster-based cloud platform and node switching method - Google Patents
IaaS cluster-based cloud platform and node switching method Download PDFInfo
- Publication number
- CN112398668B CN112398668B CN201910749798.2A CN201910749798A CN112398668B CN 112398668 B CN112398668 B CN 112398668B CN 201910749798 A CN201910749798 A CN 201910749798A CN 112398668 B CN112398668 B CN 112398668B
- Authority
- CN
- China
- Prior art keywords
- node
- application
- application program
- availability layer
- layer
- 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
- 238000000034 method Methods 0.000 title claims abstract description 13
- 239000003795 chemical substances by application Substances 0.000 claims description 12
- 238000005516 engineering process Methods 0.000 claims description 6
- 239000003818 cinder Substances 0.000 claims description 4
- 238000013500 data storage Methods 0.000 claims description 3
- 238000012546 transfer Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 4
- 230000036541 health Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a cloud platform and node switching method based on an IaaS cluster. Wherein, the cloud platform based on IaaS cluster includes: an application high availability layer and a data high availability layer, wherein the application high availability layer is connected with the data high availability layer. On one hand, the application program high availability layer and the data high availability layer are matched for use together, when the fact that a node in the application program high availability layer fails is detected, the high availability of the program is achieved, on the other hand, the deployment of the cluster application can be achieved through a single node deployment mode, and the cluster application deployment efficiency is improved.
Description
Technical Field
The embodiment of the invention relates to a cloud computing technology, in particular to a cloud platform and node switching method based on an IaaS cluster.
Background
In recent years, cloud computing technology has been developed, which allows users to access a dynamically configurable pool of shared computing resources (including network devices, servers, storage, applications, and services) via a ubiquitous, convenient network, and enables rapid distribution of these configurable computer resources with minimal administrative overhead or service provider interaction complexity. Based on the above advantages, enterprises need to consider whether to go to cloud, how to go to cloud, and the like.
In the prior art, in a conventional cluster application, a deployment mode is a multi-node deployment program, and a back-end storage used by the program may be a cluster, so that a cluster-in-cluster mode can be formed. This model is robust, but due to its complex composition structure, the maintenance cost is multiplied, the deployment process is very complex, and as applications become more and more, clusters are also increasing, and these cluster applications have entered a state that is difficult to maintain and difficult to migrate.
Disclosure of Invention
The embodiment of the invention provides a cloud platform and node switching method based on an IaaS cluster, which changes the existing cluster application deployment mode, improves the cluster application deployment efficiency, and realizes high availability of application and storage.
In a first aspect, an embodiment of the present invention provides an IaaS cluster-based cloud platform, where the cloud platform includes: the system comprises an application program high-availability layer and a data high-availability layer, wherein the application program high-availability layer is connected with the data high-availability layer;
the application program high-availability layer runs on an infrastructure as a service (IaaS) cluster and comprises a plurality of nodes; a storage volume is arranged in the node, and the node is used for managing application programs running on the node through the storage volume;
the data high-availability layer is used for storing storage volumes of all nodes running the application programs in the application program high-availability layer;
the application program high-availability layer is used for selecting a new node from the application program high-availability layer when a fault node is detected; acquiring a storage volume corresponding to the failed node from the data high-availability layer, and deploying the storage volume in the new node; and the application program running on the failed node is redeployed on the new node, so that the application program running on the failed node is transferred to run on the new node.
In a second aspect, an embodiment of the present invention provides a method for switching a node, where the method includes:
when the application program high-availability layer detects a fault node, selecting a new node from the application program high-availability layer;
the high-availability layer of the application program acquires a storage volume corresponding to the failed node from the high-availability layer of the data and deploys the storage volume in the new node;
and the application program high-availability layer redeployes the application program running on the failed node on the new node so as to transfer the application program running on the failed node to run on the new node.
In the technical solution of the embodiment of the present invention, the cloud platform based on the IaaS cluster includes: the application program high-availability layer and the data high-availability layer are used together, when the fact that a node in the application program high-availability layer fails is detected, a new node is reselected from the application program high-availability layer, a storage volume corresponding to the failed node is obtained from the data high-availability layer and is deployed in the new node, and finally the application program running on the failed node is redeployed on the new node, so that the application program running on the failed node is transferred to the new node to run.
Drawings
Fig. 1 is a schematic structural diagram of an IaaS cluster-based cloud platform according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a cloud platform based on an IaaS cluster in the second embodiment of the present invention;
fig. 3 is a flowchart of a node handover method in a third embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic structural diagram of an IaaS cluster-based cloud platform in an embodiment of the present invention, where the technical solution of this embodiment is suitable for a case where a high-availability cluster application is created in an IaaS cluster, the IaaS cluster-based cloud platform includes an application high-availability layer 1 and a data high-availability layer 2, and the application high-availability layer 1 is connected to the data high-availability layer 2.
The application program high-availability layer 1 runs on an infrastructure as a service (IaaS) cluster and comprises a plurality of nodes; the node is internally provided with a storage volume and is used for managing the application programs running on the node through the storage volume.
Among them, Infrastructure as a Service (IaaS) is the bottom layer of cloud Service, and mainly provides some basic resources for users, such as processing, storage, network and other basic computing resources, which can be used to deploy and execute an operating system or an application program.
In this embodiment, a virtual machine cluster for supporting a specific service is first created on an IaaS cluster, and then an application high-availability layer 1 and a data high-availability layer 2 are constructed on the created virtual machine cluster. The application high availability layer 1 comprises a plurality of nodes, each node runs an application deployed in the node, meanwhile, each node is mounted with a storage volume for storing data information related to the application running in the node, the storage volume can exist in the corresponding node in a form independent of the application high availability layer 1, the life cycle of the storage volume is irrelevant to the mounted node, and after the current node is down, the data volume is not deleted, but can be mounted to other nodes for data storage.
Optionally, the application high availability layer is implemented by a container cluster, and the data high availability layer is implemented by a storage cluster.
Optionally, the container cluster uses Swarm or Kubernetes.
In the two optional embodiments, a specific manner for implementing the high availability layer of the application program and the high availability layer of the data is provided, and the high availability of the application program may be implemented by using the functions of detecting and managing a plurality of nodes of the container cluster, and at the same time, the high availability of the data may be implemented by using the storage cluster. In addition, to accommodate such an IaaS cluster-based cloud platform, when high availability of applications is achieved with container clusters, health checks of the container clusters should be configured to be highly sensitive, that is, to provide a higher frequency of health checks on the basis of the original health checks.
The Swarm and Kubernets are cluster management tools and are used for abstracting a virtual machine cluster into a whole and uniformly managing containerized applications on a plurality of hosts in a cloud platform. For example, after the cluster management tool detects that a certain node in the container cluster is down, the application program running on the node may be redeployed to other nodes to continue running.
And the data high-availability layer 2 is used for storing the storage volume of each node running the application program in the application program high-availability layer 1.
The data high-availability layer 2 is also established in a virtual machine cluster for supporting specific services in the IaaS cluster, storage spaces in multiple devices are aggregated into a storage pool capable of providing a unified access interface and a management interface for an application server, data can be stored and read from multiple storage devices according to a certain rule, and the performance of the storage devices and the utilization rate of a disk are fully exerted. In this embodiment, the data high availability layer 2 is used to store and read the storage volume mounted in each node in the application program high availability layer 1, and the reading and the storing of the storage volume mounted in the node can be realized through the communication connection between the application program high availability layer 1 and the data high availability layer 2.
It should be noted that, in this embodiment, the data high availability layer 2 is also deployed in a virtual machine cluster supporting a specific service in the IaaS cluster, and in some other cases, the data high availability layer 2 may also be deployed independently from the IaaS cluster.
The application program high-availability layer 1 is used for selecting a new node from the application program high-availability layer 1 when a fault node is detected; acquiring a storage volume corresponding to the failed node from the data high-availability layer 2, and deploying the storage volume in the new node; and the application program running on the failed node is redeployed on the new node, so that the application program running on the failed node is transferred to run on the new node.
In this embodiment, when the high-availability layer 1 of the application detects that a node running a certain application program fails, a new node is reselected to replace the failed node to continue running the application program, specifically, after the new node is selected, the storage volume mounted on the failed node is read from the high-availability layer 2 of the data, and is re-mounted on the selected new node, and then the application program running on the failed node is redeployed to the new node, and in the new node, the application program is rerun according to the data stored in the storage volume, thereby realizing high availability of the application.
In the technical solution of the embodiment of the present invention, the cloud platform based on the IaaS cluster includes: the application program high-availability layer and the data high-availability layer are used together, when the fact that a node in the application program high-availability layer fails is detected, a new node is reselected from the application program high-availability layer, a storage volume corresponding to the failed node is obtained from the data high-availability layer and is deployed in the new node, and finally the application program running on the failed node is relocated on the new node, so that the application program running on the failed node is transferred to the new node to run, the structural separation of the application program high-availability layer and the data high-availability layer is achieved, and the high availability of the application program is further achieved.
Example two
Fig. 2 is a schematic structural diagram of an IaaS cluster-based cloud platform in an embodiment of the present invention, where this embodiment is applicable to a case where a high-availability cluster application is created in an IaaS cluster, and further detailed on the basis of the above embodiment, and a detailed explanation is performed on a cloud platform structure based on an IaaS cluster.
The application program high-availability layer 1 runs on an infrastructure as a service (IaaS) cluster and comprises a plurality of nodes; the node is internally provided with a storage volume and is used for managing the application programs running on the node through the storage volume.
Optionally, the plurality of nodes specifically include: at least one host node 11 and at least one compute node 12;
the primary node 11 is internally provided with an agent 111, and is configured to deploy at least one application created on the cloud platform on the primary node and/or the computing node by running the agent 111.
In this alternative embodiment, the application high availability layer 1 includes a plurality of nodes, and the nodes are divided into two categories, namely, a master node 11 and a compute node 12, where the master node 11 refers to a node in which an agent 111 is embedded, and the agent 111 is used to deploy an application in each node. Illustratively, as shown in fig. 2, the node containing the agent in the application high availability layer 1 is a master node 11, and both the computing node B and the computing node C are computing nodes 12.
It is understood that the agent 111 only plays a role of deploying the application during the deployment of the application, and after each node starts to run the application, the agent 111 does not play a role any more, and at this time, the above-mentioned master node 11 also plays the same role as the other computing nodes 12 for running the application deployed thereon.
Optionally, the cloud platform further includes: at least one customer premise equipment (3), wherein the customer premise equipment (3) is connected with a master node (11) in the application program high-availability layer (1);
the client device 3 is internally provided with a management program 31, and is configured to execute the management program 31, fill the application template according to the received application parameter input by the user, and provide the filled application template to the agent 111, so as to publish at least one application program on the cloud platform;
the agent program 111 is specifically configured to parse the filled application template sent by the management program 31 to obtain an executable code; providing the executable code to the application high availability layer 1 such that the application high availability layer 1 creates the at least one application by executing the executable code.
In this optional embodiment, the cloud platform further includes at least one user end device 3, and the user may input the application parameter of the application program to be deployed through the user end device 3, and send the application parameter to the high availability layer 1 of the application program for corresponding processing, so as to finally implement deployment of the application program. Specifically, the user end device 3 is internally provided with a management program 31, the management program 31 perfects a preset application template according to application parameters of the deployment application program input by a user, and finally sends the application template including the application parameters to the agent 111 internally provided in the host node, where the application template is a configuration file including basic parameters of the application program and can be analyzed by a preset driver to obtain an executable code. After receiving the application template including the application parameters, the agent 111 may compile the application template into an executable code of the application high availability layer 1 through a preset driver, and further send the executable code to the application high availability layer 1, where the application high availability layer 1 creates at least one application program in each node by running the executable code.
Optionally, the user end device 3 further includes a Web program 32, configured to receive an application parameter input by a user, and send the application parameter to the management program 31, so as to fill the application template according to the application parameter.
Optionally, the management program 31 and the agent program 111 are communicatively connected by a message queue.
Optionally, the message queue adopts a RabbitMQ system.
In both alternative embodiments, the manager 31 may send the template containing the application parameters to the agent 111 by means of a message queue, for example, using the RabbitMQ system.
And the data high-availability layer 2 is used for storing the storage volume of each node running the application program in the application program high-availability layer 1.
Optionally, the storage of the application high availability layer 1 uses a Cinder volume, and the Cinder volume uses a Ceph system to realize multi-copy storage.
Optionally, the application high availability layer 1 and the data high availability layer 2 are in communication connection through a Rexray plug-in.
Connection between the data volume mounted by each node and the data high availability layer circular volume can be realized by using a Rexray plug-in.
The shader is an abstraction of a layer of 'logical storage volume' introduced between the virtual machine and the specific storage device, and manages corresponding back-end storage by calling drive interfaces of different storage back-end types, so that a storage interface for unified volume-related operations is provided for a user. The Ceph is a distributed file system and can realize multi-copy storage, that is, the application of each node in the high availability layer 1 of the application program actually uses one storage volume, but the actual storage back end of the storage volume is in a multi-copy mode by using the Ceph system. Illustratively, as shown in fig. 2, the actual data high availability layer 2 includes three storage nodes A, B and C, i.e., the 3-copy storage of the back end is realized by the Ceph system.
The application program high-availability layer 1 is used for selecting a new node from the application program high-availability layer 1 when a fault node is detected; acquiring a storage volume corresponding to the failed node from the data high-availability layer 2, and deploying the storage volume in the new node; and the application program running on the failed node is redeployed on the new node, so that the application program running on the failed node is transferred to run on the new node.
The technical scheme of this embodiment, a cloud platform based on an IaaS cluster includes: on one hand, the application program high-availability layer and the data high-availability layer are used together, when a node in the application program high-availability layer is detected to have a fault, the application program running on the node can be redeployed to other nodes to continue running, so that the high availability of the application is realized, on the other hand, when the application program is deployed, a user side only needs to receive related application parameters input by a user and fills the related application parameters into an application template stored in a management program, and finally the template is sent to an agent program built in a main node of the application program high-availability layer, so that the deployment of the high-availability cluster application can be realized, the existing cluster application deployment mode is changed, and the cluster application deployment efficiency is improved.
EXAMPLE III
Fig. 3 is a flowchart of a node switching method in a third embodiment of the present invention, where the technical solution in this embodiment is suitable for a case where a high-availability cluster application is created in an IaaS cluster, and the method may be applied to the IaaS cluster-based cloud platform, and specifically includes the following steps:
and step 310, when the application program high-availability layer detects a fault node, selecting a new node from the application program high-availability layer.
In this embodiment, after detecting that a node running a certain program is down, the high-availability layer of the application program determines that the node is a failed node, and then reselects a new node from the high-availability layer of the application program to replace the failed node, so as to continue to execute the application program running the failed node, thereby achieving high availability of the application program. For example, the failure of the node may be a power failure of the node or a system crash, which is not specifically limited in this embodiment.
And step 320, the application program high-availability layer acquires the storage volume corresponding to the failed node from the data high-availability layer and deploys the storage volume in the new node.
In this embodiment, after the high availability layer of the application program determines a new node that replaces the failed node, the storage volume mounted by the failed node may be acquired from the high availability layer of the data through RexRay, and the storage volume is mounted on the new node again, so as to provide the new node with data information related to the application program run by the failed node.
And step 330, the application program high-availability layer redeploys the application program running on the failed node on the new node, so that the application program running on the failed node is transferred to run on the new node.
In this embodiment, after the storage volume corresponding to the failed node is mounted to the new node, the application program running on the failed node is deployed to the new node by the application program high availability layer, so that the application program can continue to run in the application program high availability layer.
Optionally, the redeploying, by the application high availability layer, the application running on the failed node on the new node, so that the application running on the failed node is transferred to the new node to run, further comprising:
the application program high-availability layer dispatches the virtual IP corresponding to the application program running on the failed node to the new node;
and the high-availability layer of the application program adopts an Ingress technology to forward the flow corresponding to the fault node to the new node.
Where a virtual IP address is an IP address that is not connected to a particular computer or network interface card in a computer, one virtual IP address may be used by another node in the event of a failure of the current node. Illustratively, each node has a particular physical IP address, and also has a virtual IP address, which is a working IP address. Illustratively, the physical IP address of the node 1 is 200.10.10.1, the physical IP address of the node 2 is 200.10.10.2, at this time, there is a virtual IP address of 200.10.10.3, when an application program runs on the node 1, the node 1 uses the virtual IP address, that is, the working IP address of the node 1 under normal working condition is 200.10.10.3, when the node 1 fails, the node 2 is handed over to continue to run the program running in the node 1, at this time, the virtual IP address also drifts to the node 2, at this time, the working IP address of the node 2 is 200.10.10.3.
In this optional embodiment, after a node running a certain application program fails, the application program high-availability layer deploys the application program running on the failed node to a new node to continue running, and accordingly, the virtual IP address corresponding to the failed node also drifts to the new node, and meanwhile, the application program high-availability layer correspondingly forwards the traffic corresponding to the failed node to the new node by using an Ingress technology, so as to implement load balancing.
According to the technical scheme, when the high-availability layer of the application program detects a fault node, a new node is selected from the high-availability layer of the application program, the storage volume corresponding to the fault node is obtained from the high-availability layer of the data, the storage volume is deployed in the new node, and finally the application program running on the fault node is re-deployed on the new node, so that the application program running on the fault node is transferred to the new node to run, and the high availability of the application program is realized.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A cloud platform based on an IaaS cluster, comprising: the system comprises an application program high-availability layer and a data high-availability layer, wherein the application program high-availability layer is connected with the data high-availability layer;
the application program high-availability layer runs on an infrastructure as a service (IaaS) cluster and comprises a plurality of nodes; a storage volume is arranged in the node, and the node is used for managing application programs running on the node through the storage volume;
the data high-availability layer is used for storing storage volumes of all nodes running the application programs in the application program high-availability layer;
the application program high-availability layer is used for selecting a new node from the application program high-availability layer when a fault node is detected; acquiring a storage volume corresponding to the failed node from the data high-availability layer, and deploying the storage volume in the new node; redeploying the application program running on the failed node on the new node so that the application program running on the failed node is transferred to run on the new node;
the storage volume exists in the corresponding node in a form independent of a high available layer of an application program, the life cycle of the storage volume is irrelevant to the mounted node, and after the current node is down, the storage volume cannot be deleted, but is mounted to other nodes for data storage.
2. The cloud platform of claim 1, wherein the application high availability layer is implemented by a container cluster and the data high availability layer is implemented by a storage cluster.
3. The cloud platform of claim 1, wherein the plurality of nodes specifically comprise: at least one master node and at least one compute node;
and the main node is internally provided with an agent program and is used for deploying at least one application program created on the cloud platform on the main node and/or the computing node by running the agent program.
4. The cloud platform of claim 3, wherein the cloud platform further comprises: at least one customer premise equipment, wherein the customer premise equipment is connected with the main node in the high-availability layer of the application program;
the client device is internally provided with a management program and used for filling an application template according to received application parameters input by a user by operating the management program and providing the filled application template for the agent program so as to release at least one application program on the cloud platform;
the agent program is specifically configured to parse the filled application template sent by the management program to obtain an executable code; providing the executable code to the application high availability layer such that the application high availability layer creates the at least one application by executing the executable code.
5. The cloud platform of claim 1, wherein said application high availability layer and said data high availability layer are communicatively connected via a RexRay plug-in.
6. The cloud platform of claim 1, wherein the storage of the application high availability layer uses a Cinder volume, while the Cinder volume uses Ceph technology to implement multi-copy storage.
7. The cloud platform of claim 4, wherein the hypervisor and the agent are communicatively coupled via a message queue.
8. The cloud platform of claim 2, wherein said container cluster employs Swarm or kubernets.
9. A node switching method applied to the IaaS cluster-based cloud platform according to any one of claims 1 to 8, comprising:
when the application program high-availability layer detects a fault node, selecting a new node from the application program high-availability layer;
the high-availability layer of the application program acquires a storage volume corresponding to the failed node from the high-availability layer of the data and deploys the storage volume in the new node;
the application program high-availability layer redeploys the application program running on the fault node on the new node so as to transfer the application program running on the fault node to the new node to run;
the storage volume exists in the corresponding node in a form independent of a high available layer of an application program, the life cycle of the storage volume is irrelevant to the mounted node, and after the current node is down, the storage volume cannot be deleted, but is mounted to other nodes for data storage.
10. The method of claim 9, wherein the application high availability layer redeploys the application running on the failed node to the new node to cause the application running on the failed node to migrate to run on the new node, further comprising:
the application program high-availability layer allocates the virtual IP corresponding to the application program running on the failed node to the new node;
and the high-availability layer of the application program adopts an Ingress technology to forward the flow corresponding to the fault node to the new node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910749798.2A CN112398668B (en) | 2019-08-14 | 2019-08-14 | IaaS cluster-based cloud platform and node switching method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910749798.2A CN112398668B (en) | 2019-08-14 | 2019-08-14 | IaaS cluster-based cloud platform and node switching method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112398668A CN112398668A (en) | 2021-02-23 |
| CN112398668B true CN112398668B (en) | 2022-08-23 |
Family
ID=74602739
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910749798.2A Active CN112398668B (en) | 2019-08-14 | 2019-08-14 | IaaS cluster-based cloud platform and node switching method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112398668B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022227059A1 (en) * | 2021-04-30 | 2022-11-03 | 西门子（中国）有限公司 | Method and apparatus for deploying application, computing device, and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107707393A (en) * | 2017-09-26 | 2018-02-16 | 赛尔网络有限公司 | More live systems based on Openstack O version characteristics |
| CN108632057A (en) * | 2017-03-17 | 2018-10-09 | 华为技术有限公司 | A kind of fault recovery method of cloud computing server, device and management system |
| CN109522145A (en) * | 2018-11-14 | 2019-03-26 | 江苏鸿信系统集成有限公司 | A kind of virtual-machine fail automatic recovery system and its method |
| CN109634716A (en) * | 2018-12-04 | 2019-04-16 | 武汉烽火信息集成技术有限公司 | The OpenStack virtual machine High Availabitity management end device and management method of anti-fissure |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10929195B2 (en) * | 2017-08-07 | 2021-02-23 | Dynavisor, Inc. | Method and system for cloud virtualization |
-
2019
- 2019-08-14 CN CN201910749798.2A patent/CN112398668B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108632057A (en) * | 2017-03-17 | 2018-10-09 | 华为技术有限公司 | A kind of fault recovery method of cloud computing server, device and management system |
| CN107707393A (en) * | 2017-09-26 | 2018-02-16 | 赛尔网络有限公司 | More live systems based on Openstack O version characteristics |
| CN109522145A (en) * | 2018-11-14 | 2019-03-26 | 江苏鸿信系统集成有限公司 | A kind of virtual-machine fail automatic recovery system and its method |
| CN109634716A (en) * | 2018-12-04 | 2019-04-16 | 武汉烽火信息集成技术有限公司 | The OpenStack virtual machine High Availabitity management end device and management method of anti-fissure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112398668A (en) | 2021-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103368768B (en) | The method of the auto zoom network coverage, device and equipment in mixed cloud environment | |
| US10050850B2 (en) | Rack awareness data storage in a cluster of host computing devices | |
| CN104052789B (en) | Method and system for the load balance of virtual networking system | |
| US10289441B1 (en) | Intelligent scale-out federated restore | |
| US9244817B2 (en) | Remote debugging in a cloud computing environment | |
| US9582221B2 (en) | Virtualization-aware data locality in distributed data processing | |
| US7793298B2 (en) | Facilitating access to input/output resources via an I/O partition shared by multiple consumer partitions | |
| US9135189B2 (en) | Delivering GPU resources across machine boundaries | |
| US10540211B2 (en) | Elasticity for highly available applications | |
| CN106528327B (en) | A data processing method and backup server | |
| US8856585B2 (en) | Hardware failure mitigation | |
| KR20170110708A (en) | Opportunistic Resource Migration for Resource Deployment Optimization | |
| CN105912389A (en) | Technique for implementing virtual machine transition system in hybrid cloud environment on basis of data virtualization | |
| JP5855724B1 (en) | Virtual device management apparatus, virtual device management method, and virtual device management program | |
| CN114615268B (en) | Service network, monitoring node, container node and equipment based on Kubernetes cluster | |
| CN105183588A (en) | Rebuilding method and device of virtual machines | |
| CN112398668B (en) | IaaS cluster-based cloud platform and node switching method | |
| CN116010111B (en) | Cross-cluster resource scheduling method, system and terminal equipment | |
| CN110870275B (en) | Method and apparatus for shared memory file transfer | |
| CN112015515A (en) | Virtual network function instantiation method and device | |
| CN114546644A (en) | Cluster resource scheduling method, device, software program, electronic device and storage medium | |
| CN115811549B (en) | Cloud-side resource management scheduling method and system supporting hybrid heterogeneous runtime | |
| CN120295789A (en) | CPU resource allocation method for DPU centralized service grid | |
| CN114721815A (en) | Method, apparatus, program, device and medium for determining the maximum number of copies available | |
| US10223019B1 (en) | Policy-driven volume expansion |
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 |