CN114327855A - Service method and system for downtime migration of edge node - Google Patents
Service method and system for downtime migration of edge node Download PDFInfo
- Publication number
- CN114327855A CN114327855A CN202111209188.7A CN202111209188A CN114327855A CN 114327855 A CN114327855 A CN 114327855A CN 202111209188 A CN202111209188 A CN 202111209188A CN 114327855 A CN114327855 A CN 114327855A
- Authority
- CN
- China
- Prior art keywords
- server
- virtual server
- server instance
- virtual
- instance
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000005012 migration Effects 0.000 title abstract description 12
- 238000013508 migration Methods 0.000 title abstract description 12
- 230000004044 response Effects 0.000 claims abstract description 11
- 238000004590 computer program Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 4
- 230000002085 persistent effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000002355 dual-layer Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
Images
Abstract
A service method and system for marginal node down migration are disclosed. A first virtual server instance is run on a first server disposed at an edge node. Virtual server instance-related data associated with the operation of the first virtual server instance is stored in a storage device that is physically separate from the first server. And in response to the unavailability of the first server, running a second virtual server instance on a second server arranged in the cloud based on the virtual server instance-related data stored in the storage device to provide the service provided by the first virtual server instance. Thus, the service can resume operation without feeling.
Description
Technical Field
The present disclosure relates to the field of information processing technologies, and in particular, to a service method and system for performing downtime migration on an edge node.
Background
As public clouds are increasingly extended to the edge, miniaturized edge nodes can be deployed in customer data centers or machine rooms of partners to provide services for customers by using server resources arranged on the edge nodes. The edge nodes are small in scale and can support the requirements of customers on low application delay or data compliance.
However, since the resource pool of the computing server of the edge node is small, when a server failure occurs easily, the service provided by the affected server cannot be recovered in a short time because there is no idle server resource locally. This is because it takes a long time, typically in days, to replenish server resources at the edge nodes.
Therefore, a solution capable of rapidly recovering a service provided by a server provided at an edge node when the server fails is required.
Disclosure of Invention
One technical problem to be solved by the present disclosure is to provide a solution capable of quickly recovering a service provided by a server when the server disposed at an edge node fails.
According to a first aspect of the present disclosure, there is provided a service method including: running a first virtual server instance on a first server disposed at an edge node; storing virtual server instance-related data associated with the operation of the first virtual server instance in a storage device that is physically separate from the first server; and in response to the first server not being available, running a second virtual server instance on a second server arranged in the cloud based on the virtual server instance-related data stored in the storage device to provide the service provided by the first virtual server instance.
Optionally, the method further comprises: and migrating the second virtual server instance to the first server in response to the first server recovering from the unavailable state to the available state, and releasing the resources occupied by the second virtual server instance in the second server.
Optionally, the storage device is a cloud disk disposed at an edge node and logically associated with the first virtual server instance.
Optionally, the method further comprises: responding to the unavailability of the first server, judging whether an edge node has a third server which can support the running of the first virtual server instance by available resources, wherein if the edge node has the third server, a second virtual server instance is run on the third server based on the relevant data of the virtual server instance stored in the storage equipment so as to provide the service provided by the first virtual server instance; and if the third server does not exist in the edge node, executing the step of running a second virtual server instance on a second server arranged in the cloud.
Optionally, the step of running the second virtual server instance on the second server disposed in the cloud based on the data related to the virtual server instance stored in the storage device includes: configuring a second server to configure the second server as a server cluster logically belonging to the edge node; the second server starts and runs the second virtual server instance by accessing the data related to the virtual server instance stored in the storage device.
Optionally, the method further comprises: the second virtual server instance accesses the virtual private network used by the edge node and communicates with the client of the edge node and/or other virtual server instances other than the first virtual server instance over the virtual private network.
According to a second aspect of the present disclosure, there is provided a service system including: the first server is arranged on the edge node, and a first virtual server instance runs on the first server; the cloud disk is arranged on the edge node and logically associated with the first virtual server instance and used for storing virtual server instance related data associated with the operation of the first virtual server instance; the second server is arranged at the cloud end; and the management and control device is used for responding to the unavailability of the first server, and running a second virtual server instance on a second server based on the storage virtual server instance related data stored in the storage equipment so as to provide the service provided by the first virtual server instance.
Optionally, the management and control device is further configured to determine, in response to that the first server is unavailable, whether a third server exists in other servers disposed in the edge node, where the third server is capable of supporting the operation of the first virtual server instance, and if it is determined that the third server exists, run the third virtual server instance on the third server based on the storage virtual server instance-related data stored in the storage device, so as to provide the service provided by the first virtual server instance; and if the third server does not exist, running the second virtual server instance on the second server based on the storage virtual server instance related data stored in the storage equipment.
Optionally, the second virtual server instance accesses a virtual private network used by the edge node, and communicates with clients of the edge node and/or other virtual server instances other than the first virtual server instance via the virtual private network.
Optionally, the management and control device is disposed in the cloud.
According to a third aspect of the present disclosure, there is provided a computing device comprising: a processor; and a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform a method according to the first aspect of the disclosure.
According to a fourth aspect of the present disclosure, there is provided a computer program product comprising executable code which, when executed by a processor of an electronic device, causes the processor to perform the method according to the first aspect of the present disclosure.
According to a fifth aspect of the present disclosure, there is provided a non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of an electronic device, causes the processor to perform the method according to the first aspect of the present disclosure.
Thus, by running the second virtual server instance on the second server disposed in the cloud based on the virtual server instance-related data stored in the storage device physically independent from the first server when the first server disposed in the edge node is unavailable, the present disclosure effectively equates to transferring the first virtual server instance from the first server to the second server, which allows the service to recover the service provided by the unavailable first server without perceiving such a change, i.e., allowing the service to recover operation thereof without perceiving it.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.
Fig. 1 shows a schematic flow chart of a service method according to an embodiment of the present disclosure.
Fig. 2 shows a schematic flow chart of a service method according to another embodiment of the present disclosure.
Fig. 3 shows a schematic structural diagram of a service system according to an embodiment of the present disclosure.
FIG. 4 shows a schematic flow diagram of a server tamper-time restore service located at an edge node.
FIG. 5 shows a schematic structural diagram of a computing device according to one embodiment of the present disclosure.
Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The virtual server instance on the edge unavailable server is transferred to the cloud end available server from the bottom angle when the server arranged on the edge node is unavailable (such as downtime), so that the virtual server instance running on the cloud end available server can provide the service provided by the virtual server instance running on the edge unavailable server, and meanwhile, the service cannot sense the change, and the effect of quickly and invisibly recovering the service is achieved.
Further details relating to the present disclosure are described below in conjunction with the appended drawings.
Fig. 1 shows a schematic flow chart of a service method according to an embodiment of the present disclosure.
Referring to fig. 1, in step S110, a first virtual server instance is run on a first server provided at an edge node.
The first Virtual server instance refers to a Virtual server, such as a Virtual Machine (Virtual Machine), created on the first server using the resources of the first server. The runtime environment of the first virtual server instance is provided by the first server. One or more first virtual server instances may be run on the first server, the first virtual server instances providing services. The first server is unavailable and the first virtual server instance running on the first server will no longer be running.
In step S120, virtual server instance related data associated with the operation of the first virtual server instance is stored in a storage device physically separate from the first server.
A storage device physically separate from the first server for storing virtual server instance related data associated with the operation of the first virtual server instance as a storage device for the first virtual server instance. The storage device may be a block storage device. When the first server is unavailable, the data associated with the virtual server instance stored in the storage device is still available.
The storage device may form a computing and storage separate architecture from the first server. That is, the first server may refer to a computing server in the architecture for providing computing resources, and the storage device may refer to a storage server in the architecture for providing storage resources.
The storage device may be disposed in the edge node, may also be disposed in the cloud, or may also be disposed in other locations. As a preferred embodiment, the storage device may be a cloud disk disposed at the edge node and logically associated with the first virtual server instance to store virtual server instance related data associated with the operation of the first virtual server instance.
The virtual server instance related data may include data that needs to be read when the virtual server instance is started, that is, data on which the virtual server instance is started, such as system disk data of the virtual machine.
The virtual server instance related data may also include data related to a service provided by the virtual server instance. The services provided by the virtual server instance may refer to, but are not limited to, any one or more combinations of applications running in the virtual server instance, functions implemented by the virtual server instance, and tasks performed by the virtual server instance.
In step S130, in response to the first server not being available, a second virtual server instance is run on a second server disposed in the cloud based on the data related to the virtual server instance stored in the storage device, so as to provide the service provided by the first virtual server instance.
And running the second virtual server instance on the second server arranged in the cloud based on the virtual server instance related data, wherein the operation is equivalent to the effect of transferring the first virtual server instance from the first server to the second server. I.e. it is equivalent to pull (restore) the first virtual server instance on the second server based on the virtual server instance related data.
The second server may start and run the second virtual server instance on the second server by reading the virtual server instance related data stored in the storage device. The underlying resources of the second virtual server instance are the same as the first virtual server instance (e.g., IP address, system disk used, etc.) or similar (e.g., the second virtual server instance has a higher configuration and is downward compatible than the first virtual server instance). Thus, starting and running the second virtual server instance on the second server is equivalent to resuming the running of the first virtual server instance on the second server.
The second server may also be a computing server in a compute, storage split architecture for providing computing resources.
Fig. 2 shows a schematic flow chart of a service method according to another embodiment of the present disclosure.
Referring to fig. 2, in response to the first server being unavailable, step S210 may be performed first to determine whether there is a third server whose available resources can support the operation of the first virtual server instance.
If the edge node has a third server whose available resources can support the operation of the first virtual server instance, step S220 is executed to operate a second virtual server instance on the third server based on the storage virtual server instance related data stored in the storage device, so as to provide the service provided by the first virtual server instance. I.e., equivalent to migrating the virtual server instance on the first server to the other local servers.
If the edge node does not have a third server whose available resources can support the operation of the first virtual server instance, step S230 is executed to operate a second virtual server instance on a second server based on the data related to the virtual server instance stored in the storage device, so as to provide the service provided by the first virtual server instance. I.e., equivalent to migrating the virtual server instance on the first server to a server on the cloud.
The second Virtual server instance may access a Virtual Private Network (VPN) used by the edge node, and communicate with clients of the edge node and/or other Virtual server instances outside the first Virtual server instance via the VPN.
The second server may be a completely idle server selected from the cloud, and the cloud disk may be located at the edge node. To enable migration of the first virtual server instance onto the second server, the second server may be configured to configure the second server as a cluster of servers logically belonging to the edge node. That is, the second server is logically joined to the server cluster in the edge node, so that the second server can directly use the cloud disk in the edge node to access the data related to the virtual server instance therein, and accordingly generate the virtual server instance (i.e., the second virtual server instance) with the required specification.
The second server logically belongs to the server cluster of the edge node, and means that the second server is still arranged at the cloud end in the physical way, but not arranged at the edge node; the second server is able to communicate with other servers or other devices, such as clients, in the edge node's server cluster through the virtual private network such that the second server appears to be located in the edge node's server cluster.
After configuration, the second server may start and run the second virtual server instance by accessing data associated with the virtual server instance stored in the storage device.
As described above, the virtual server instance related data may include data that needs to be read when the virtual server instance is started, as well as data related to the service provided by the virtual server instance. The second server may first access data that needs to be read at the start of the virtual server instance to start the second virtual server instance and then enable the second virtual server instance to provide the service provided by the first virtual server instance based on the data related to the service provided by the virtual server instance.
In response to the first server reverting from the unavailable state to the available state, the second virtual server instance may be migrated to the first server and resources occupied by the second virtual server instance in the second server are released.
When the second virtual server instance is migrated to the first server, because the second server is in an available state, live migration without shutdown can be performed, and shutdown migration can also be performed.
The specific implementation manner of migrating the second virtual server instance to the first server may refer to the implementation manner of migrating the first virtual server instance to the second server, and other implementation manners may also be used, for example, the second virtual server instance may be migrated to the first server through data transmission between the first server and the second server.
Fig. 3 shows a schematic structural diagram of a service system according to an embodiment of the present disclosure.
As shown in fig. 3, the service system may include a first server 110 disposed at an edge node, a cloud disk 120 disposed at the edge node, a second server 130 disposed at a cloud end, and a management apparatus 140. The management device 140 may be disposed in the cloud.
At least one first virtual server instance is running on the first server 110.
The cloud disk 120 is logically associated with the first virtual server instance for storing virtual server instance related data associated with the operation of the first virtual server instance.
The cloud disk 120 may form a computing and storage separated architecture with the first server 110. That is, the first server 110 may refer to a computing server in the architecture for providing computing resources, and the cloud disk 120 may refer to a storage server in the architecture for providing storage resources.
The management apparatus 140 may be connected to the first server 110, the cloud disk 120, and the third server 130, respectively.
In response to that the first server is unavailable, the management and control device 140 may first determine whether a third server exists among other servers disposed in the edge node, where available resources can support the operation of the first virtual server instance, and if it is determined that the third server exists, run the third virtual server instance on the third server based on the storage virtual server instance related data stored in the cloud disk 120 to provide the service provided by the first virtual server instance.
If the edge node does not have a third server whose available resources can support the operation of the first virtual server instance, the management and control apparatus 140 may execute the second virtual server instance on the second server based on the storage virtual server instance related data stored in the cloud disk, so as to provide the service provided by the first virtual server instance.
The second virtual server instance may access a virtual private network used by the edge node, and communicate with clients of the edge node and/or other virtual server instances other than the first virtual server instance over the virtual private network.
As indicated by the dashed box in the figure, running the second virtual server instance on the second server is equivalent to transferring the first virtual server instance running on the first server to the second server, thereby enabling the service to recover the service provided by the unavailable first server without perceiving the change, i.e. enabling the service to recover quickly and imperceptibly.
Application example
As shown in fig. 4, when a server 1 in the computing server cluster of the edge node is rammed, all cloud server instances (e.g., VM1, VM2 shown in the figure) on the server 1 will stop running. The cloud server instance is also the first virtual server instance mentioned above.
After the cloud management system detects a tamper event of the server 1, it may determine whether there are enough idle resources on other local servers to place the affected cloud server instances (i.e., VM1, VM 2).
If the other local servers have enough idle resources, all the resources are migrated to the other local servers.
If some of the cloud server instances have no resources to place, then a migration to a server on the cloud is initiated.
The migration procedure to the servers on the cloud is as follows.
The management and control system selects a completely idle server from a computing server cluster of a central Region, configures the server and adds the server into a server cluster in an edge node logically, thereby being capable of producing the required cloud server specification, directly using a cloud disk (block storage) cluster in the edge node to access a cloud disk example therein, accessing a virtual private network (VPC) used by the edge node
The management and control system initiates a downtime migration instruction, cloud server instances which cannot be recovered due to insufficient local resources are pulled up on the newly configured computing servers on the cloud, the instances use various resources such as a cloud disk and an IP of the instances, and can still be communicated with other cloud server instances in the same VPC through the VPC (no matter whether the cloud servers are on the cloud or on the edge), so that user applications cannot sense changes, and the operation can be recovered senslessly.
After the edge nodes supplement the resources of the computing servers, the management and control system can initiate shutdown migration or non-shutdown live migration, migrate the cloud server instances temporarily running in the servers on the cloud back to the edge nodes, and then release the temporarily borrowed computing servers on the cloud.
When the computing server of the edge node is down and other local servers have no resources to place the affected cloud server instance, the central Region on the cloud temporarily borrows the server and logically adds the server to the computing server cluster or the resource pool in the edge node, so that the cloud server instance affected by the down can be migrated to the borrowed server to be recovered to operate, data and behaviors such as a cloud disk and an IP (Internet protocol) are kept unchanged, the service (such as user application) can be recovered to operate in an insensitive mode, and the time for affecting the service (such as user application) is greatly shortened.
According to the method and the device, the operation of the cloud server instance in the edge server affected by the fault is recovered by temporarily using the abundant server resources on the cloud, so that the problem that the local server resources are limited can be solved, and the influence of the downtime of the server on a client is reduced.
Fig. 5 shows a schematic structural diagram of a computing device that can be used to implement the service method according to an embodiment of the present disclosure.
Referring to fig. 5, computing device 500 includes memory 510 and processor 520.
The processor 520 may be a multi-core processor or may include a plurality of processors. In some embodiments, processor 520 may include a general-purpose host processor and one or more special coprocessors such as a Graphics Processor (GPU), a Digital Signal Processor (DSP), or the like. In some embodiments, processor 520 may be implemented using custom circuitry, such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA).
The memory 510 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions for the processor 520 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. Further, the memory 510 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic and/or optical disks, may also be employed. In some embodiments, memory 510 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a digital versatile disc read only (e.g., DVD-ROM, dual layer DVD-ROM), a Blu-ray disc read only, an ultra-dense disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disk, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.
The memory 510 has stored thereon executable code, which when processed by the processor 520, causes the processor 520 to perform the service methods mentioned above.
The service method, computing device and system according to the present disclosure have been described in detail above with reference to the accompanying drawings.
Furthermore, the method according to the present disclosure may also be implemented as a computer program or computer program product comprising computer program code instructions (e.g. executable code) for performing the above-mentioned steps defined in the above-mentioned method of the present disclosure, which, when executed by a processor of an electronic device, cause said processor to perform the steps of the above-mentioned method according to the present disclosure.
Alternatively, the present disclosure may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) which, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the various steps of the above-described method according to the present disclosure.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (13)
1. A method of servicing, comprising:
running a first virtual server instance on a first server disposed at an edge node;
storing virtual server instance-related data associated with the operation of the first virtual server instance in a storage device that is physically separate from the first server; and
and in response to the first server not being available, running a second virtual server instance on a second server arranged in the cloud based on the virtual server instance related data stored in the storage device to provide the service provided by the first virtual server instance.
2. The method of claim 1, further comprising:
and responding to the first server recovering from the unavailable state to the available state, migrating the second virtual server instance to the first server, and releasing the resources occupied by the second virtual server instance in the second server.
3. The method of claim 1, wherein,
the storage device is a cloud disk which is arranged at an edge node and is logically associated with the first virtual server instance.
4. The method of claim 1, further comprising:
determining, in response to the first server not being available, whether there is a third server of the edge node having available resources capable of supporting the operation of the first virtual server instance,
if the third server exists in the edge node, running a second virtual server instance on the third server based on the data related to the virtual server instance stored in the storage device so as to provide the service provided by the first virtual server instance;
and if the third server does not exist in the edge node, executing the step of running a second virtual server instance on a second server arranged in the cloud.
5. The method of claim 1, wherein the step of running the second virtual server instance on the cloud-disposed second server based on the virtual server instance-related data stored in the storage device comprises:
configuring the second server to configure the second server as a server cluster logically belonging to the edge node;
and the second server starts and runs the second virtual server instance by accessing the data related to the virtual server instance stored in the storage equipment.
6. The method of claim 5, further comprising:
the second virtual server instance accesses a virtual private network used by the edge node, and communicates with clients of the edge node and/or other virtual server instances other than the first virtual server instance through the virtual private network.
7. A service system, comprising:
the first server is arranged on the edge node, and a first virtual server instance runs on the first server;
a cloud disk disposed at an edge node and logically associated with the first virtual server instance, for storing virtual server instance-related data associated with the operation of the first virtual server instance;
the second server is arranged at the cloud end; and
and the management and control device is used for responding to the unavailability of the first server, and running a second virtual server instance on a second server based on the storage virtual server instance related data stored in the storage equipment so as to provide the service provided by the first virtual server instance.
8. The system of claim 7, wherein,
the management and control device is further configured to determine, in response to the first server not being available, whether there is a third server in other servers disposed in an edge node, where available resources can support the operation of the first virtual server instance, where,
if the third server exists, running a third virtual server instance on the third server based on the storage virtual server instance related data stored in the storage device to provide the service provided by the first virtual server instance;
and if the third server does not exist, running a second virtual server instance on a second server based on the storage virtual server instance related data stored in the storage equipment.
9. The system of claim 7, wherein,
the second virtual server instance accesses a virtual private network used by the edge node, and communicates with clients of the edge node and/or other virtual server instances other than the first virtual server instance through the virtual private network.
10. The system of claim 7, wherein,
the management and control device is arranged at the cloud end.
11. A computing device, comprising:
a processor; and
a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any of claims 1 to 6.
12. A computer program product comprising executable code which, when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1 to 6.
13. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111209188.7A CN114327855A (en) | 2021-10-18 | 2021-10-18 | Service method and system for downtime migration of edge node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111209188.7A CN114327855A (en) | 2021-10-18 | 2021-10-18 | Service method and system for downtime migration of edge node |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114327855A true CN114327855A (en) | 2022-04-12 |
Family
ID=81044664
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111209188.7A Pending CN114327855A (en) | 2021-10-18 | 2021-10-18 | Service method and system for downtime migration of edge node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114327855A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115250227A (en) * | 2022-06-02 | 2022-10-28 | 苏州思萃工业互联网技术研究所有限公司 | Scheduling system for realizing fault migration in edge computing scene |
| CN115543971A (en) * | 2022-11-29 | 2022-12-30 | 天津南大通用数据技术股份有限公司 | Method for realizing high availability of MPP database |
-
2021
- 2021-10-18 CN CN202111209188.7A patent/CN114327855A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115250227A (en) * | 2022-06-02 | 2022-10-28 | 苏州思萃工业互联网技术研究所有限公司 | Scheduling system for realizing fault migration in edge computing scene |
| CN115543971A (en) * | 2022-11-29 | 2022-12-30 | 天津南大通用数据技术股份有限公司 | Method for realizing high availability of MPP database |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11855904B2 (en) | Automated migration of compute instances to isolated virtual networks | |
| US11329885B2 (en) | Cluster creation using self-aware, self-joining cluster nodes | |
| US10404795B2 (en) | Virtual machine high availability using shared storage during network isolation | |
| US9104645B2 (en) | System and method of replicating virtual machines for live migration between data centers | |
| US9632813B2 (en) | High availability for virtual machines in nested hypervisors | |
| US10474484B2 (en) | Offline management of virtualization software installed on a host computer | |
| US11809901B2 (en) | Migrating the runtime state of a container between two nodes | |
| CN114327855A (en) | Service method and system for downtime migration of edge node | |
| US11418566B2 (en) | Adding and removing virtual disks remotely to a streaming machine | |
| US20140109095A1 (en) | Seamless extension of local computing power | |
| US11593234B2 (en) | Cloud restart for VM failover and capacity management | |
| US10860375B1 (en) | Singleton coordination in an actor-based system | |
| CN112256393B (en) | Resource management method and equipment for bare metal server | |
| JP5998566B2 (en) | Movement control program, movement control method, and control apparatus | |
| CN110515697A (en) | A kind of virtual machine migration method, device, storage medium and computer equipment | |
| CN111459619A (en) | Method and device for realizing service based on cloud platform | |
| CN113157392B (en) | High-availability method and equipment for mirror image warehouse | |
| US20220129292A1 (en) | Fast virtual machine resume at host upgrade | |
| US9348672B1 (en) | Singleton coordination in an actor-based system | |
| US20160203016A1 (en) | Methods, systems, and computer readable media for virtual machine (vm) deployment | |
| US11853783B1 (en) | Identifying hosts for dynamically enabling specified features when resuming operation of a virtual compute instance | |
| EP4068091A1 (en) | Hybrid approach to performing a lazy pull of container images | |
| US11579912B2 (en) | Integrity-preserving cold migration of virtual machines | |
| US20230093925A1 (en) | Offloaded container execution environment | |
| US20240028441A1 (en) | Propagating fault domain topology to nodes in a distributed container orchestration system |
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 |