CN112711469A - Cloud host migration method and device, computer equipment and storage medium - Google Patents
Cloud host migration method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112711469A CN112711469A CN202011594068.9A CN202011594068A CN112711469A CN 112711469 A CN112711469 A CN 112711469A CN 202011594068 A CN202011594068 A CN 202011594068A CN 112711469 A CN112711469 A CN 112711469A
- Authority
- CN
- China
- Prior art keywords
- cloud host
- migrated
- target
- physical server
- cloud
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The method comprises the steps of determining a target available domain of a cloud host to be migrated, wherein the target available domain comprises computing resources provided by a first physical server corresponding to a target migration region, dividing the computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain according to the computing resources of the cloud host to be migrated to obtain the target cloud host, wherein a disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to a rear-end distributed storage system of the first physical server from a rear-end distributed storage system of a second physical server, and migration of the cloud host to be migrated is completed. According to the method, the cloud host is rapidly migrated in different places by using a distributed storage and remote synchronous deployment mode, so that the migration time is greatly shortened, and the cloud migration efficiency is improved.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a cloud host migration method and apparatus, a computer device, and a storage medium.
Background
In recent years, as the cloud computing industry has expanded in size, more and more enterprises have created a demand for on-device clouds. A user can select a data center with a short distance to build a cloud host according to factors such as delay and the like to deploy cloud services. With the popularization of cloud services, the requirement of cloud host cloning or migration also comes.
In the existing scheme of migrating cloud hosts in different places, a cloud host disk file transfer mode is generally adopted to migrate cloud hosts, and the migration process includes the steps of finding out a disk file of a cloud host to be migrated in a server background, copying the disk file, creating a new cloud host on a cloud platform to be created, and then transferring the new cloud host to a disk of the cloud host to be migrated through a network.
However, the migration process of the cloud host in the cloud migration process may cause a large amount of time cost, resulting in low cloud migration efficiency.
Disclosure of Invention
Therefore, in order to solve the technical problems, it is necessary to provide a cloud host migration method, an apparatus, a computer device, and a storage medium, which can save the migration time cost of a cloud host and improve the cloud migration efficiency.
In a first aspect, an embodiment of the present application provides a cloud host migration method, where the method includes:
determining a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
according to the computing resources of the cloud host to be migrated, dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain to obtain a target cloud host; the target cloud host is a cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
In one embodiment, the back-end distributed storage system of the first physical server includes a first data pool, and the back-end distributed storage system of the second physical server includes a second data pool; the first data pool and the second data pool have the same identification;
the second data pool comprises disk files of the cloud host to be migrated;
the first data pool comprises a disk file of the target cloud host;
and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
In one embodiment, after obtaining the target cloud host, the method further includes:
and controlling the target cloud host to access the disk file of the target cloud host through the built-in access component.
In one embodiment, after obtaining the target cloud host, the method further includes:
and replacing the server information of the cloud host to be migrated with the server information of the target cloud host.
In one embodiment, before the determining that the cloud host to be migrated is in the target available domain in the target migration zone, the method further includes:
confirming whether the backup command written back to the back-end distributed storage system of the first physical server is finished or not;
if yes, executing the step of determining the target available domain of the cloud host to be migrated.
In one embodiment, the first physical server and the second physical server are both deployed with a cloud computing management platform;
and the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through a unified identity authentication component.
In one embodiment, the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form.
In a second aspect, an embodiment of the present application provides a cloud host migration apparatus, including:
the determining module is used for determining a target available domain of the cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
the migration module is used for dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain according to the computing resources of the cloud host to be migrated to obtain a target cloud host; the target cloud host is a cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
In a third aspect, an embodiment of the present application provides a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the method steps of any one of the foregoing first aspects when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method steps of any one of the embodiments in the first aspect.
According to the cloud host migration method and device, the computer equipment and the storage medium, the target available domain of the cloud host to be migrated is determined, the target available domain comprises computing resources provided by the first physical server corresponding to the target migration region, and then the computing resources which are the same as the computing resources of the cloud host to be migrated are divided in the target available domain according to the computing resources of the cloud host to be migrated to obtain the target cloud host; the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server, so that migration of the cloud host to be migrated is completed. In the method, distributed storage systems are deployed in various regions, and a distributed storage and remote synchronous deployment mode is utilized to enable the disk file of the cloud host to be migrated to be automatically backed up to the distributed storage system deployed at the rear end of a target migration region, so that disk file synchronization is performed in the form of synchronous storage log files instead of disk file transmission of the cloud host to be migrated when the cloud host to be migrated is migrated, the log files belong to small files, the problem of interruption or loss caused by network instability can be avoided through small log transmission, the integrity of data transmission is realized, meanwhile, the transmission efficiency of data in the migration process of the cloud host is improved through small file transmission, the migration time is greatly shortened, and the cloud migration efficiency is improved. And the disk file synchronization is carried out in the form of a log file, so that even if the log is hijacked in the migration process, the specific content of the disk file cannot be restored, and the safety of the transmission content is ensured. In addition, after the cloud computing management platform and the back-end distributed storage system are deployed, a multi-region mode is not used, but data of different regions are placed in different available regions in a mode of distinguishing the available regions, so that cloud hosts of different regions are logically separated, and unified management is realized.
Drawings
FIG. 1 is a diagram of an application environment for a method for cloud host migration in one embodiment;
FIG. 1a is a diagram of the internal structure of a server in one embodiment;
fig. 2 is a schematic flow chart illustrating a cloud host migration method according to an embodiment;
fig. 3 is a schematic flowchart of a cloud host migration method provided in another embodiment;
fig. 4 is a schematic flowchart of a cloud host migration method provided in another embodiment;
FIG. 5 is a schematic diagram illustrating a deployment of a cloud host migration system in different regions according to an embodiment;
fig. 6 is a schematic flowchart of a cloud host migration method provided in another embodiment;
FIG. 7 is a flow diagram of a cloud host migration process provided in one embodiment;
FIG. 7a is a diagram that illustrates the relationship between an OpenStack cluster and a Ceph cluster, according to an embodiment;
fig. 8 is a block diagram illustrating an exemplary embodiment of a cloud host migration apparatus;
FIG. 9 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The cloud host migration method provided by the application can be applied to the application environment shown in fig. 1. The application environment comprises physical servers of a plurality of regions, a cloud host is built on the physical server of each region, a management operation system cloud computing management platform with the cloud host is deployed, and a distributed storage system is deployed at the rear end of each physical server of each region. The physical servers in each region include, but are not limited to, general servers, special servers, desktop servers, rack servers, blade servers, and the like. The number of cloud hosts built on each physical server is not limited. The internal structure of each physical server can be seen in fig. 1a, and the processor in fig. 1a is used for providing computing and control capability. The memory includes a nonvolatile storage medium, an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database is used for storing relevant data during work. The network interface is used for communicating with other external devices through network connection.
At present, in a scheme of migrating cloud hosts in different places of a large public cloud operator, a mode of transferring cloud hosts by using a disk file of the cloud hosts is generally adopted. However, because the disk file of the cloud host occupies a large space, the migration of the batch clusters can cause a large amount of time cost; the transmission speed of the disk file during transmission depends on the network bandwidth, network resources are occupied during transmission, and if data is transmitted by using a public network, the risk of data leakage exists; if the express delivery is carried out by a physical medium, the risk of loss exists; in addition, when the cloud host is restored after migration is completed in the existing cloud host migration method, due to the change of the deployment environment, the related environment configuration needs to be manually adjusted, and the downtime in the migration process causes service interruption, which also reduces user experience. Based on this, embodiments of the present application provide a cloud host migration method and apparatus, a computer device, and a storage medium, which can save the migration time cost of a cloud host and improve the cloud migration efficiency. The following describes in detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems by embodiments and with reference to the drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that in the cloud host migration method provided by the present application, the execution main body in fig. 2 to fig. 9 is a console running a cloud computing management platform, which is hereinafter referred to as a cloud computing management platform for short, wherein the execution main body may also be a cloud host migration apparatus, and the apparatus may be implemented as part or all of the console running the cloud computing management platform by software, hardware, or a combination of software and hardware.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments.
In an embodiment, as shown in fig. 2, a cloud host migration method is provided, where the embodiment relates to a method in which a cloud computing management platform determines a target available domain of a cloud host to be migrated from a target migration region, and then, according to computing resources of the cloud host to be migrated, the same computing resources in a first physical server of the target migration region are divided into the target available domain, so as to obtain a target cloud host; the disk file of the target cloud host is a specific process obtained after the disk file of the cloud host to be migrated is backed up to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; this embodiment comprises the steps of:
s101, determining a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions.
For example, as shown in fig. 3, the cloud host to be migrated is a schematic diagram of migrating the cloud host to be migrated from a region (region a) to a target migration region (region B) of the cloud host to be migrated.
Available zone (available zone), i.e. a reliable, available zone. The areas may be different areas divided according to different conditions, for example, areas which are independent of each other and divided according to power and network equipment, or areas which are divided according to usage. The embodiment of the application is described by taking the division of multiple available domains according to the purpose as an example, that is, the multiple available domains are divided in advance, the cloud hosts in different regions corresponding to different available domains are allocated in the same available domain, and all the cloud hosts in the same region are allocated in the same available domain. Since the cloud host is not a physical host, and is a virtual host that is a plurality of independent hosts like virtual hosts virtualized by computing resources (CPU memory, video card resources, network resources, etc.) of physical servers of some entities, it can also be understood that an available domain is composed of computing resources provided by physical servers corresponding to one region, and the available domain is used to distinguish the computing resources of different regions, and in practical applications, one available domain includes other necessary hardware facilities or software facilities in addition to the computing resources provided by the physical servers corresponding to the region, which is not limited in this application. In the embodiment of the present application, a cloud host is used for explanation in order to simplify and clarify semantics.
As shown in fig. 4, a plurality of available domains are divided: available field 1, available field 2, available field 3, · useful field N; for example, available domain 1 includes the computing resources provided by the physical servers of region C, which are deployed as cloud hosts, and available domain 2 includes the computing resources provided by the physical servers of region C, which are deployed as cloud hosts of region D; available domain 3 includes the computing resources provided by the physical servers of region C deployed as cloud hosts for region a, and available domain N includes the computing resources provided by the physical servers of region C deployed as cloud hosts for region B. Therefore, in this step, the target available domain of the cloud host to be migrated is determined, that is, an available domain corresponding to the region (area a) to which the cloud host to be migrated belongs is determined from the set multiple available domains, that is, the target available domain (for example, available domain 3 in fig. 4). In this way, the available domain division is performed in the above manner, so that cloud hosts at different places can be effectively managed by the available domain. It should be noted that, for the available domains partitioned in the same region, although different available domains store cloud hosts of different regions, the internal networks between the available domains can be connected, and only the response time of the network may be slightly different.
S102, according to the computing resources of the cloud host to be migrated, the computing resources which are the same as the computing resources of the cloud host to be migrated are divided in a target available domain, and the target cloud host is obtained; the target cloud host is a cloud host which is migrated by the cloud host to be migrated; the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
It is explained in the foregoing that the cloud host is not a physical host, and is a virtual host that is virtualized by computing resources (CPU memory, video card resources, network resources, and the like) of some physical servers and is similar to a plurality of independent hosts, so that the cloud host migration actually partitions computing resources that are the same as the computing resources of the cloud host to be migrated in a target migration area, and then migrates a disk file (stored file) in the cloud host to be migrated to the computing resources partitioned in the target migration area, thereby completing the cloud host migration.
In the embodiment of the application, different available domains are divided, one available domain corresponds to one region, so that computing resources which are the same as the computing resources of the cloud host to be migrated need to be divided in a target available domain according to the computing resources of the cloud host to be migrated, the target available domain corresponds to a target migration region which comprises the computing resources provided by the first physical server corresponding to the target migration region, so that the computing resources which are the same as the computing resources of the cloud host to be migrated are constructed in the target migration region, and the target cloud host to be migrated is obtained.
Referring to fig. 5, taking a region a (a region to which a cloud host to be migrated belongs) and a region B (a target migration region) as examples, a physical server of the region B is referred to as a first physical server, and a physical server of the region a is referred to as a second physical server, where the first and second physical servers are only used for distinguishing different regions, and are not used for other limitations. The physical servers refer to servers having entities, and the number of the physical servers in each region is not limited, so that the first physical server may be regarded as a cluster of a plurality of physical servers, and the second physical server may also be regarded as a cluster of a plurality of physical servers.
Optionally, the first physical server and the second physical server are both deployed with a cloud computing management platform; the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through the unified identity authentication component.
The cloud computing management platform refers to a cloud operating system for managing cloud host clusters. The cloud computing management platform can be Op enaStack, and the OpenStack provides scalable and elastic cloud computing services for private clouds and public clouds. When OpenStack is deployed in the first physical server and the second physical server, a unified identity authentication component is used, namely the same keystone is used for deployment, so that when the cloud host clusters virtualized in the first physical server and the second physical server are managed, all cloud host nodes can be managed in a unified mode. Based on the deployed cloud computing management platform, the steps of the process of performing cloud host migration in the embodiment of the present application are executed by the cloud computing management platform.
In addition to the cloud computing management platform being deployed to manage the virtualized cloud host clusters in the first physical server and the second physical server, the distributed storage systems are deployed to the back ends of the first physical server and the second physical server respectively. The distributed storage system is used for storing disk files of the cloud hosts, for example, the disk files of the cloud hosts virtualized on the first physical server are stored in the back-end distributed storage system of the first physical server, and the disk files of the cloud hosts virtualized on the second physical server are stored in the back-end distributed storage system of the second physical server.
The distributed storage system may be a distributed storage system of a Ceph architecture, for example, the distributed storage system of the Ceph architecture is built by using a deployment scheme of open source software (not limited to some existing open source software), and the Ceph version is required to be above jewel. Meanwhile, a backup mechanism, for example, an RBD mirroring function module, needs to be set, so that after the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server are built, the disk files of the cloud hosts in the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server can be backed up with each other; and it should be emphasized that, after the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server are built, even if the cloud host migration operation is not performed, the disk files of the cloud hosts in the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server are always backed up with each other.
Therefore, during the migration process of the cloud host to be migrated, the disk file of the cloud host to be migrated is automatically backed up from the backend distributed storage system (region a) of the second physical server to the backend distributed storage system (region B) of the first physical server in the form of a log file. After the computing resources which are the same as the computing resources of the cloud host to be migrated are divided in the target available domain according to the computing resources of the cloud host to be migrated, the computing resources in the target available domain and the disk file of the cloud host to be migrated which is automatically backed up in the rear-end distributed storage system of the first physical server together form the target cloud host, so that the cloud host to be migrated is successfully migrated from the region a to the region B.
According to the cloud host migration method provided by the embodiment, a target available domain of a cloud host to be migrated is determined, the target available domain comprises computing resources provided by a first physical server corresponding to a target migration region, and then according to the computing resources of the cloud host to be migrated, computing resources which are the same as the computing resources of the cloud host to be migrated are divided in the target available domain to obtain the target cloud host; the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server, so that migration of the cloud host to be migrated is completed. In the method, distributed storage systems are deployed in various regions, and a distributed storage and remote synchronous deployment mode is utilized to enable the disk file of the cloud host to be migrated to be automatically backed up to the distributed storage system deployed at the rear end of a target migration region, so that disk file synchronization is performed in the form of synchronous storage log files instead of disk file transmission of the cloud host to be migrated when the cloud host to be migrated is migrated, the log files belong to small files, the problem of interruption or loss caused by network instability can be avoided through small log transmission, the integrity of data transmission is realized, meanwhile, the transmission efficiency of data in the migration process of the cloud host is improved through small file transmission, the migration time is greatly shortened, and the cloud migration efficiency is improved. And the disk file synchronization is carried out in the form of a log file, so that even if the log is hijacked in the migration process, the specific content of the disk file cannot be restored, and the safety of the transmission content is ensured. In addition, after the cloud computing management platform and the back-end distributed storage system are deployed, a multi-region mode is not used, but the data of different regions are placed in different available regions in a mode of distinguishing the available regions, the cloud hosts of the different regions are logically separated, and unified management is achieved.
Based on the above embodiments, in one embodiment, the backend distributed storage system of the first physical server includes a first data pool, and the backend distributed storage system of the second physical server includes a second data pool; the first data pool and the second data pool have the same identification; the second data pool comprises disk files of the cloud host to be migrated; the first data pool comprises a disk file of the target cloud host; and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
In the above embodiment, it is mentioned that the distributed storage system is deployed to the second physical server backend of the region a, and the distributed system is deployed to the first physical server backend of the region B. On the basis, a first data pool, such as pool (1), is divided for the back-end distributed storage system of the first physical server, a second data pool, such as pool (2), is divided for the back-end distributed storage system of the second physical server, and the first data pool and the second data pool have the same identification, that is, the names of the pool (1) and the pool (2) are consistent; the data pools of the two regions are named by the same identifier, and the identifiers are unified when the first data pool and the second data pool are in butt joint with the computer management platform, so that a unified interface is adopted between the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server and the cloud computing management platform. Based on the unified interface, when the cloud computing management platform calls the disk files of the cloud host from the first data pool and the second data pool, the generated Universal Unique Identifiers (UUIDs) are consistent, the same UUID is used by the back-end distributed storage system of the first physical server and the back-end distributed storage system of the second physical server to identify the same file, even if the cloud host is migrated from the region a to the region B, the same file name can be accurately and quickly found, and the logics are divided together in such a way, so that remote synchronization between the region a and the region B is realized.
For example, the names of the pool (1) and the pool (2) are uihoponstack, and on the premise of a preset backup mechanism (RBD mirroring), automatic backup can be implemented between the pool (1) in the backend distributed storage system of the first physical server and the pool (2) in the backend distributed storage system of the second physical server. The pool (2) comprises the disk file of the cloud host to be migrated, and the disk file of the cloud host to be migrated is automatically backed up from the pool (2) to the pool (1) and then is the disk file of the target cloud host.
Optionally, the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form. Specifically, the disk file is divided into a plurality of small spaces in the form of volumes for storage. The disk file includes a system disk and a file in a data disk, that is, the system disk and the data disk are both stored in the distributed storage system in a volume (volume) form, for example, the stored file type may be in a raw, qcw2 format.
In this embodiment, disk files of the cloud host are stored in the distributed storage system deployed at the rear ends of the two regions by establishing a data pool, and the data pools in the distributed storage system of the two regions are named by using the same identifier to form a uniform storage data pool, so that the cloud computing management platform calls the rear-end storage by using a uniform interface, the same file name can be accurately and quickly found, the storage is logically divided together, and the remote synchronization effect between the region a and the region B is realized.
Based on the deployment mode of each region, in the migration process of the cloud host to be migrated, only the cloud host to be migrated needs to be closed, and the target available domain in the target migration region is migrated. In order to ensure that the system environment of the cloud host is consistent in the migration process and achieve unaware migration, the cloud host migration in the embodiment of the present application may be performed in a cold migration (also called static migration) manner, that is, before the cloud host to be migrated is migrated, the cloud host to be migrated needs to be shut down. However, because the data backup function between the distributed storage systems deployed at the back ends of the region a and the region B also performs backup operation when the cloud host is not migrated, it is necessary to determine whether the ongoing backup operation is finished before migrating the cloud host to be migrated, so as to avoid data loss caused by the migration operation in the ongoing backup operation. Then in one embodiment, as shown in fig. 6, the method further comprises:
s201, confirming whether the backup command written back to the back-end distributed storage system of the first physical server is finished or not.
The embodiment may be performed before the foregoing determination that the cloud host to be migrated is in the target available domain in the target migration zone. The backup command refers to a signal that the back-end distributed storage system of the first physical server returns the backup completion signal to the second physical server after the data in the back-end distributed storage system of the second physical server is backed up to the back-end distributed storage system of the first physical server. For example, the distributed storage system is a Ceph-architecture distributed storage system, and a sync command is written back in Ceph journal every time a disk file is backed up once, so that the cloud computing management platform needs to confirm whether the write-back of the sync command is completed.
S202, if yes, executing the step of determining the target available domain of the cloud host to be migrated.
And if the backup command is written back completely, the cloud computing management platform starts the migration operation of the cloud host to be migrated, namely, the step of determining the target available domain of the cloud host to be migrated is executed.
In this embodiment, only after it is confirmed that the backup operation performed between the distributed storage systems is completed, the migration operation of the cloud host to be migrated is started, so that data loss caused by the migration operation in the performing backup operation is avoided, and normal migration of the cloud host to be migrated is ensured.
Optionally, after the target cloud host is obtained, the server information of the cloud host to be migrated is replaced with the server information of the target cloud host. After the migration of the cloud host to be migrated is completed, and the target cloud host is obtained, the server information of the cloud host to be migrated needs to be replaced by the server information in the available domain where the target cloud host is located. The server information includes an IP address, DNS information, and the like. Then the IP address, DNS information, etc. for the target cloud host are replaced with the available IP address, DNS information in the target available domain. However, if the migration operation of the cloud host to be migrated is an operation between internal networks, the server information of the target cloud host does not need to be changed. The server information of the migrated target cloud host is modified, and the migrated target cloud host can work normally.
Optionally, after the target cloud host is obtained, the target cloud host is controlled to access the disk file of the target cloud host through the built-in access component. After the migration operation of the cloud host to be migrated is completed, and the target cloud host can also work normally, the cloud computing management platform can control the target cloud host to access the disk file of the target cloud host through the built-in access component and execute the normal function of the cloud host. The built-in access components include but are not limited to nova and circular components, and the two components are components for calling, reading and writing data and accessing data in the virtual machine.
As shown in fig. 7, an embodiment is provided, which takes an example that the cloud computing management platform is OpenStack and the distributed storage system deployed at the back end is a distributed storage system of a Ceph architecture, and describes a process of migrating the cloud host from a region a to a region B.
S301, an OpenStack cluster is deployed to the physical servers in both areas a and B.
Specifically, the OpenStack cluster deployed by the physical servers in both region a and region B uses the same keystone (unified authentication service component), so that all nodes in the cluster can be uniformly managed. After the OpenStack cluster is deployed, a multi-region mode is not used, a plurality of available domains are divided, hosts in different regions are distinguished by the available domains, cloud hosts in different regions are logically separated, and unified management is achieved.
S302, a Ceph architecture distributed storage system is deployed at the rear end of the physical servers of the areas A and B, and the deployed Ceph cluster of the area A accesses the OpenStack cluster of the corresponding area through the same interface.
Please refer to fig. 7a, which is a schematic diagram of the relationship between OpenStack clusters and Ceph clusters in two deployed areas, area a and area B. Specifically, Ceph is adopted to deploy a distributed storage system at the rear end of physical servers in two places, namely a region A and a region B, open source software is used for building a Ceph architecture distributed storage system, and the Ceph version is required to be more than jewel, so that a Ceph cluster of the region A and a Ceph cluster of the region B are obtained. Respectively dividing a data pool on the Ceph cluster of the area A and the Ceph cluster of the area B as an access rear-end storage of the OpenStack clusters of the two areas to obtain a Ceph cluster pool A of the area A and a Ceph cluster pool B of the area B; the names of poolA and poolB are consistent (e.g., uihoponstack), and then, the poolA and poolB are configured with an RBD mirroring policy, where RBD mirroring is a mechanism for asynchronous mirroring between two clusters, so that data between the Ceph cluster poolA of a and the Ceph cluster poolB of region B are backed up with each other.
S303, the cloud host to be migrated is shut down, and the fact that the Ceph journal write-back sync command is completed is confirmed.
And S304, the OpenStack console or the command line executes migration of the cloud host, determines a target available domain to be migrated in a plurality of pre-divided available domains, and divides the same computing resources in the target available domain according to the computing resources of the cloud host to be migrated.
S305, after the migration of the cloud host to be migrated is completed, replacing the mapped floating IP before the migration of the cloud host to be migrated with the available floating IP in the target available domain after the migration, and modifying the corresponding DNS.
S306, the Ceph cluster poolB of the region B is used as the rear-end storage of the cloud host after migration is completed, correspondingly, the disk file of the cloud host after migration is the disk file backed up in the poolB, and the disk file is stored in a volume file format.
S307, the disk files stored in the data pool are accessed by using the built-in access components nova and cider.
When the OpenStack and Ceph distributed storage systems are deployed, the cloud host migration method provided by the embodiment of the application at least comprises two OpenStack clusters deployed in different regions. The OpenStack cluster comprises at least two distributed storage systems with Ceph frameworks (the Ceph version is not lower than jewel), and the distributed storage systems are respectively accessed to the OpenStack cluster in a backend storage form. And at least one cloud host created in the OpenStack cluster is included, and a system disk and a data disk of the cloud host are stored in a distributed storage system of a Ceph architecture in a volume form. The environmental configuration in the Ceph cluster involved in the deployment process can be set arbitrarily, which is not limited in the embodiment of the present application; the number of clusters to be deployed in multiple places involved in the deployment process can also be dynamically expanded according to actual requirements, which is not limited in the embodiments of the present application.
In the cloud host migration method provided in this embodiment, functions of distributed storage and different-place synchronization between different places are realized by deploying a Ceph architecture distributed storage system, and accessing a Ceph cluster of a Ceph cluster region B of a deployed region a to an OpenStack cluster of a corresponding region through the same interface. Adopting a uniform interface when OpenStack calls the back-end storage to mutually back up the remote storage to form a uniform storage data pool; the method comprises the steps of distinguishing computing resources of different regions by available domains, enabling a target available domain to be selected according to requirements when a cloud host is created, and completing migration by only turning off an original host and selecting the available domain of the region to be migrated during migration, so that system environments of the cloud host are kept consistent during migration in a cold migration mode, and unaware migration is achieved. Moreover, when the cloud host to be migrated is migrated, the disk file transmission of the cloud host does not need to be performed, the disk file synchronization is performed in a form of synchronously storing log files, the log files belong to small files, the problem of interruption or loss caused by the unstable condition of a network can be avoided through the small log transmission, and the complete data transmission is realized. And because the disk file synchronization is carried out in the form of log files, even if the log is hijacked in the migration process, the specific content of the log and the disk file cannot be restored, and the safety of the transmission content is ensured, so that the defects of time and safety brought by the transmission of the existing disk file are overcome.
In the steps of the cloud host migration method provided in this embodiment, the implementation principle and technical effect are similar to those in the foregoing cloud host migration method embodiment, and are not described herein again. The implementation manner of each step in the embodiment of fig. 7 is only an example, and is not limited to this, and the order of each step may be adjusted in practical application as long as the purpose of each step can be achieved.
It should be understood that although the various steps in the flow charts of fig. 2-7 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-7 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 8, there is provided a cloud host migration apparatus, including: a determining module 10 and a transferring module 11, wherein:
the determining module 10 is configured to determine a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
the migration module 11 is configured to divide, according to the computing resources of the cloud host to be migrated, computing resources that are the same as the computing resources of the cloud host to be migrated in the target available domain to obtain a target cloud host; the target cloud host is a cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
In one embodiment, the back-end distributed storage system of the first physical server includes a first data pool, and the back-end distributed storage system of the second physical server includes a second data pool; the first data pool and the second data pool have the same identification;
the second data pool comprises disk files of the cloud host to be migrated;
the first data pool comprises a disk file of the target cloud host;
and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
In one embodiment, the apparatus further comprises:
and the access module is used for controlling the target cloud host to access the disk file of the target cloud host through the built-in access component.
In one embodiment, the apparatus further comprises:
and the information replacement module is used for replacing the server information of the cloud host to be migrated with the server information of the target cloud host.
In one embodiment, the apparatus further comprises:
the confirmation module is used for confirming whether the backup command returned by the back-end distributed storage system of the write-back first physical server is finished or not; if yes, executing the step of determining the target available domain of the cloud host to be migrated.
In one embodiment, the first physical server and the second physical server are both deployed with a cloud computing management platform; and the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through a unified identity authentication component.
In an embodiment, the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form.
For specific limitations of the cloud host migration apparatus, reference may be made to the above limitations of the cloud host migration method, which are not described herein again. All or part of the modules in the cloud host migration device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 9. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a cloud host migration method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
determining a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
according to the computing resources of the cloud host to be migrated, dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain to obtain a target cloud host; the target cloud host is a cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
In one embodiment, the back-end distributed storage system of the first physical server includes a first data pool, and the back-end distributed storage system of the second physical server includes a second data pool; the first data pool and the second data pool have the same identification;
the second data pool comprises disk files of the cloud host to be migrated;
the first data pool comprises a disk file of the target cloud host;
and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
In one embodiment, the processor, when executing the computer program, performs the steps of:
and controlling the target cloud host to access the disk file of the target cloud host through the built-in access component.
In one embodiment, the processor, when executing the computer program, performs the steps of:
and replacing the server information of the cloud host to be migrated with the server information of the target cloud host.
In one embodiment, the processor, when executing the computer program, performs the steps of:
confirming whether the backup command written back to the back-end distributed storage system of the first physical server is finished or not;
if yes, executing the step of determining the target available domain of the cloud host to be migrated.
In one embodiment, the first physical server and the second physical server are both deployed with a cloud computing management platform; and the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through a unified identity authentication component.
In an embodiment, the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
determining a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
according to the computing resources of the cloud host to be migrated, dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain to obtain a target cloud host; the target cloud host is a cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
In one embodiment, the back-end distributed storage system of the first physical server includes a first data pool, and the back-end distributed storage system of the second physical server includes a second data pool; the first data pool and the second data pool have the same identification;
the second data pool comprises disk files of the cloud host to be migrated;
the first data pool comprises a disk file of the target cloud host;
and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
In one embodiment, the computer program when executed by a processor implements the steps of:
and controlling the target cloud host to access the disk file of the target cloud host through the built-in access component.
In one embodiment, the computer program when executed by a processor implements the steps of:
and replacing the server information of the cloud host to be migrated with the server information of the target cloud host.
In one embodiment, the computer program when executed by a processor implements the steps of:
confirming whether the backup command written back to the back-end distributed storage system of the first physical server is finished or not;
if yes, executing the step of determining the target available domain.
In one embodiment, the first physical server and the second physical server are both deployed with a cloud computing management platform; and the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through a unified identity authentication component.
In an embodiment, the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A cloud host migration method, the method comprising:
determining a target available domain of a cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
according to the computing resources of the cloud host to be migrated, dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain to obtain a target cloud host; the target cloud host is the cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; and the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
2. The method of claim 1, wherein the back-end distributed storage system of the first physical server comprises a first data pool, and the back-end distributed storage system of the second physical server comprises a second data pool; the first data pool and the second data pool have the same identification;
the second data pool comprises disk files of the cloud host to be migrated;
the first data pool comprises a disk file of the target cloud host;
and the disk file of the target cloud host is obtained after the disk file of the cloud host to be migrated is backed up to the first data pool from the second data pool according to the identification.
3. The method of claim 1 or 2, wherein after obtaining the target cloud host, the method further comprises:
and controlling the target cloud host to access the disk file of the target cloud host through a built-in access component.
4. The method of claim 1 or 2, wherein after obtaining the target cloud host, the method further comprises:
and replacing the server information of the cloud host to be migrated with the server information of the target cloud host.
5. The method according to claim 1 or 2, wherein before determining the target available domain of the cloud host to be migrated in the target migration zone, the method further comprises:
confirming whether the backup command written back to the back-end distributed storage system of the first physical server is finished or not;
if yes, executing the step of determining the target available domain of the cloud host to be migrated.
6. The method of claim 1 or 2, wherein the first physical server and the second physical server are each deployed with a cloud computing management platform;
and the cloud computing management platform manages the cloud host built on the first physical server and the cloud host built on the second physical server through a unified identity authentication component.
7. The method according to claim 1 or 2, wherein the disk file of the cloud host to be migrated and the disk file of the target cloud host are both stored in a volume form.
8. An apparatus for cloud host migration, the apparatus comprising:
the determining module is used for determining a target available domain of the cloud host to be migrated; the target available domain comprises computing resources provided by a first physical server corresponding to the target migration region; wherein different available domains are used for cloud hosts corresponding to different regions;
the migration module is used for dividing computing resources which are the same as the computing resources of the cloud host to be migrated in the target available domain according to the computing resources of the cloud host to be migrated to obtain a target cloud host; the target cloud host is the cloud host which is migrated by the cloud host to be migrated;
the disk file of the target cloud host is obtained by backing up the disk file of the cloud host to be migrated to the back-end distributed storage system of the first physical server from the back-end distributed storage system of the second physical server; and the second physical server is a physical server of the region to which the cloud host to be migrated belongs.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011594068.9A CN112711469A (en) | 2020-12-29 | 2020-12-29 | Cloud host migration method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011594068.9A CN112711469A (en) | 2020-12-29 | 2020-12-29 | Cloud host migration method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112711469A true CN112711469A (en) | 2021-04-27 |
Family
ID=75546269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011594068.9A Pending CN112711469A (en) | 2020-12-29 | 2020-12-29 | Cloud host migration method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112711469A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113949712A (en) * | 2021-10-15 | 2022-01-18 | 科大讯飞股份有限公司 | Cloud host cluster high-availability processing method and system, electronic equipment and storage medium |
| CN114157663A (en) * | 2021-11-25 | 2022-03-08 | 联想(北京)有限公司 | Cloud data access method and cloud server |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190004844A1 (en) * | 2017-06-26 | 2019-01-03 | Wangsu Science & Technology Co., Ltd. | Cloud platform construction method and cloud platform |
| CN109388478A (en) * | 2018-11-01 | 2019-02-26 | 郑州云海信息技术有限公司 | Method and apparatus for migrating virtual machine in OpenStack environment |
| US20190213030A1 (en) * | 2018-01-05 | 2019-07-11 | Boe Technology Group Co., Ltd. | Virtual host migration system and method, computer apparatus and computer readable storage medium |
| CN110209465A (en) * | 2018-04-20 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Virtual machine cross-platform migration method, device and electronic equipment |
| CN110750334A (en) * | 2019-10-25 | 2020-02-04 | 北京计算机技术及应用研究所 | Network target range rear-end storage system design method based on Ceph |
-
2020
- 2020-12-29 CN CN202011594068.9A patent/CN112711469A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190004844A1 (en) * | 2017-06-26 | 2019-01-03 | Wangsu Science & Technology Co., Ltd. | Cloud platform construction method and cloud platform |
| US20190213030A1 (en) * | 2018-01-05 | 2019-07-11 | Boe Technology Group Co., Ltd. | Virtual host migration system and method, computer apparatus and computer readable storage medium |
| CN110209465A (en) * | 2018-04-20 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Virtual machine cross-platform migration method, device and electronic equipment |
| CN109388478A (en) * | 2018-11-01 | 2019-02-26 | 郑州云海信息技术有限公司 | Method and apparatus for migrating virtual machine in OpenStack environment |
| CN110750334A (en) * | 2019-10-25 | 2020-02-04 | 北京计算机技术及应用研究所 | Network target range rear-end storage system design method based on Ceph |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113949712A (en) * | 2021-10-15 | 2022-01-18 | 科大讯飞股份有限公司 | Cloud host cluster high-availability processing method and system, electronic equipment and storage medium |
| CN113949712B (en) * | 2021-10-15 | 2024-04-30 | 科大讯飞股份有限公司 | Cloud host cluster high-availability processing method, system, electronic equipment and storage medium |
| CN114157663A (en) * | 2021-11-25 | 2022-03-08 | 联想(北京)有限公司 | Cloud data access method and cloud server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5459811B2 (en) | Method and system for virtual storage migration and virtual machine monitor | |
| US11609884B2 (en) | Intelligent file system with transparent storage tiering | |
| US10838829B2 (en) | Method and apparatus for loading data from a mirror server and a non-transitory computer readable storage medium | |
| CN109168328B (en) | Virtual machine migration method and device and virtualization system | |
| US9792150B1 (en) | Detecting site change for migrated virtual machines | |
| CN110704161B (en) | Virtual machine creation method and device and computer equipment | |
| JP6123626B2 (en) | Process resumption method, process resumption program, and information processing system | |
| US10223219B2 (en) | Managing network failure using back-up networks | |
| US10620871B1 (en) | Storage scheme for a distributed storage system | |
| JP2009237826A (en) | Storage system and volume management method therefor | |
| CN110262893B (en) | Method and device for configuring mirror image memory and computer storage medium | |
| CN111147274B (en) | System and method for creating a highly available arbitration set for a cluster solution | |
| WO2017145272A1 (en) | Data migration method and computer system | |
| CN112711469A (en) | Cloud host migration method and device, computer equipment and storage medium | |
| US11153173B1 (en) | Dynamically updating compute node location information in a distributed computing environment | |
| US8838768B2 (en) | Computer system and disk sharing method used thereby | |
| CN112804375B (en) | Configuration method for single network card and multiple IPs | |
| CN107329798B (en) | Data replication method and device and virtualization system | |
| CN111722909A (en) | Virtual machine migration method, system, equipment and storage medium | |
| KR101618992B1 (en) | System for providing virtual desktop service, control method thereof, recording medium for recording program for executing the control method, application saved in the recording medium for executing the control method being combined with hardware | |
| KR101925404B1 (en) | In-Memory redundancy-enabled Based Virtualization Service Providing System | |
| CN116615715A (en) | Method and system for combining systems using resource sets | |
| CN108334401B (en) | System and method for realizing logic roll dynamic distribution and supporting virtual machine dynamic migration | |
| CN113868679B (en) | Cluster encryption method and device | |
| CN112965790B (en) | PXE protocol-based virtual machine starting method and electronic equipment |
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 |