Method, Apparatus, and Electronic Device for Cloud Service Migration - Patent application
The method addresses the challenges of cloud service migration by scheduling and efficiently transitioning data and configurations, reducing service interruptions and operational complexity.
Patent Information
- Application Number
- JP2020527993
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2017-11-24
- Filing Date
- 2018-11-14
- Publication Date
- 2025-01-30
- Estimated Expiration
- 2038-11-14
AI Technical Summary
Current cloud service migration technologies face challenges such as prolonged service interruptions and complex operations due to the time-consuming process of mirroring large data volumes and the lack of comprehensive solutions for reconfiguring cloud services during migration.
A method and device for cloud service migration that involves scheduling the migration process, instantiating a new instance in the target cluster, configuring resource components, and performing data operations based on priority, while terminating the original instance and copying data efficiently using techniques like data mirroring and asynchronous copying.
This approach significantly reduces service interruption time and simplifies the migration process, enabling efficient and convenient transitions of cloud services by minimizing downtime and enhancing operational efficiency.
Smart Images

Figure 0007624167000001 
Figure 0007624167000002 
Figure 0007624167000003
Abstract
Description
[Technical field]
[0001] This disclosure is a national phase entry of international application PCT / CN2018 / 115383, filed November 14, 2018, which claims priority to Chinese patent application 201711186691.9, filed November 24, 2017, both of which are incorporated by reference in their entireties herein.
[0002] The present disclosure relates to the field of cloud computing, and in particular to a method, an apparatus, and an electronic device for cloud service migration. [Background technology]
[0003] As the popularity and development of cloud computing increases, the interest in products based on cloud computing technology increases, and more kinds of cloud products are available. For example, cloud servers (e.g., Elastic Compute Service (ECS)), which are basic cloud computing services, can provide services conveniently and efficiently, such as commodity resources such as water, electricity, gas, etc., and provide various applications. However, as cloud service providers gradually expand and build new data centers, users begin to have more robust requirements for selecting geographical regions when using cloud services. Meanwhile, as the system architecture deployed based on cloud services continues to evolve and expand, it is also necessary to realign the distribution of cloud services. In addition, with the adjustment of the user service scope, it is also necessary to migrate cloud services to priority promotion regions to improve user experience.
[0004] Currently, cloud service providers have not provided a comprehensive solution to address these above-mentioned needs related to cloud service migration. For example, the cloud computing service platform AWS (Amazon Web Services) provided by Amazon, Inc. of Seattle, Washington, only provides mirrored images of disks to serve cloud services (e.g., disk mirroring). Users use these mirrored images to synchronize data through a process of copying mirrored images. Since the size of data on disks is generally hundreds of gigabytes or terabytes, it takes a long time to mirror data, resulting in a long interruption of service. Furthermore, except for the aspect of using mirroring to synchronize data, comprehensive migration of cloud services has not yet been realized. Thus, users need to handle the creation of cloud service instances, the deployment of application services, and configurations such as the configuration of IP addresses of cloud servers. All these operations require a complex migration process. Summary of the Invention
[0005] The present disclosure provides a method, apparatus, and electronic device for cloud service migration to solve the technical problems of extended service interruption time and complex operations associated with cloud service migration in the prior art.
[0006] In one embodiment, the present disclosure provides a cloud service migration method, comprising: obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; and migrating disk data associated with an original instance of the cloud service to a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. of servicesa step of migrating data operations of the original cloud service instance to a disk for the new instance, the migration of the disk data being performed based on a migration priority order of the disk data; of services The new death and configuring the data operations of the new cloud service instance.
[0007] In one embodiment, the method further comprises: Services The data operations of the cloud service on the disk for the new instance Service The method includes the steps of instantiating a new instance in the target cluster, configuring the new instance and a resource component associated with the new instance, terminating the original instance in the source cluster, and starting the new instance based on the resource component before the configuring step is performed as the data operation on the disk for the target cluster.
[0008] In one embodiment, configuring the new instance and resource components associated with the new instance includes configuring the new instance in the target cluster based on the configuration information of the original instance using the same configuration as the configuration information, or configuring the new instance based on the configuration information obtained through a pre-configured configuration interface.
[0009] In one embodiment, the resource component includes a disk, hi another embodiment, the resource component further includes at least one of a CPU, a memory, an operating system, and a network connection.
[0010] In one embodiment, configuring the new instance and resource components of the new instance includes allocating a network port in the target cluster, releasing the cloud service from a network port of the source cluster, configuring the cloud service to the network port allocated to the target cluster, and performing a routing update.
[0011] In one embodiment, configuring the new instance and the resource components of the new instance comprises: of services and stopping data operations associated with the cloud service on the disk for the new instance in the target cluster. of services and allocating the disk for the new instance. of services After the allocation of the disks for the new instance of the cloud service instantiated in the target cluster is completed, the disk data associated with the original instance of the cloud service is transferred to the new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. of services a step of transferring the original instance to a disk for of services The data operations of the cloud service on the disk for the new instance of services and configuring as a data operation on said disk for said
[0012] In one embodiment, the disk data associated with the original instance of the cloud service is transferred to a new instance of the cloud service instantiated in the target cluster. of services The step of migrating the disk data associated with the original instance to a disk for the new instance includes dividing the disk data associated with the original instance into at least one data block, and migrating the disk data associated with the original instance in the form of the data block to the disk for the new instance. of servicesa step of copying the disk data associated with the original instance to the disk for the new instance; dividing the disk data associated with the original instance into at least one data block, creating a data mirroring image corresponding to each data block, and copying the disk data associated with the original instance to the disk for the new instance through data mirroring. of services and copying the content onto the disc for use in the method.
[0013] In one embodiment, the data block is configured with a flag bit to mark whether the data block has been copied or not. The disk data associated with the original instance is copied to the new instance. of services In the process of copying to the disk for the original instance, the data already copied is compared to the disk data associated with the original instance based on the flag bits to determine the progress of copying the disk data associated with the original instance.
[0014] In one embodiment, the original instance and the new instance are each configured with a respective processing queue. of services A data request including a data operation of the cloud service on the disk for the original instance is enqueued in the processing queue of the original instance and a data request including a data operation of the cloud service on the disk for the new instance is enqueued in the processing queue of the original instance and of services A data request including a data operation of the cloud service on the disk for the new instance is enqueued in the processing queue of the new instance.
[0015] In one embodiment, the original instance of services The data operations of the cloud service on the disk for the new instance of services After the step of configuring as a data operation on the disk for the new instance of services A data request including a data operation of the cloud service on the disk for the new instance is enqueued in the processing queue of the new instance and a data request including a data operation of the cloud service on the disk for the new instance is enqueued in the processing queue of the original instance. Within Data requests that have not yet completed processing are forwarded to the processing queue of the new instance for processing.
[0016] In one embodiment, the migration priority of the disk data is determined by determining whether the data included in the data request is of services determining whether the data included in the data request exists on the disk for the new instance; of services configuring a migration priority of the data included in the data request to a high migration priority in response to determining that the data does not reside in the disk for the original instance; and configuring the disk data associated with the original instance for the new instance of the cloud service instantiated in the target cluster. of services and performing the migration in order of decreasing migration priority in the process of migrating to the disk for the first time.
[0017] In one embodiment, the processing of a data request in the processing queue of the new instance is performed by processing the data included in the data request in the processing queue of the new instance. of services and determining whether the data included in the data request is present in the disk for the new instance. of services In response to determining that the new instance exists on the disk for of services performing a data operation included in the data request on the disk for the new instance; and of services In response to determining that the data with a high migration priority is not present on the disk for of services The new instance is created from the disk. of services For the disk Transfer When the migration of the data is complete, the new instance of services For the disk death, and performing a data operation included in the data request.
[0018] In one embodiment, the source cluster and the target cluster are configured in different availability zones.
[0019] In one embodiment, the cloud service is configured as a cloud server for providing cloud computing services. In another embodiment, the source cluster includes a cloud server cluster of at least one cloud server, and the target cluster includes a cloud server cluster of at least one cloud server.
[0020] In one embodiment, the present disclosure provides a cloud service migration apparatus, the apparatus comprising: of a migration request obtaining unit configured to obtain a migration request related to a cloud service, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; and a migration request obtaining unit configured to migrate disk data associated with an original instance of the cloud service to a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. Service For 、 a disk migration unit configured to migrate the disk data to an allocated disk in the target cluster, the migration of the disk data being performed based on a migration priority order of the disk data; of services The data operations of the cloud service on the disk for the new instance of services and a data operation configuration unit configured to configure as a data operation on the disk for said data operation.
[0021] In one embodiment, the present disclosure provides an electronic device, the electronic device comprising a memory and a processor, the memory coupled to the processor, the memory being read and executed by the processor to provide to the electronic device: obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; and migrating disk data associated with an original instance of the cloud service to a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. of services a step of migrating the disk data of the original instance to a disk for which the migration of the disk data is performed based on a migration priority order of the disk data; Service The data operations of the cloud service on the disk for the new instance of services The disk for for and storing computer readable instructions for performing the steps of: manipulating data;
[0022] In one embodiment, the present disclosure provides a cloud service migration method, the method comprising: obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; and migrating disk data associated with an original instance of the cloud service to a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. Service a step of migrating the disk data to a disk for the original instance, the migration of the disk data being performed based on a migration priority of the disk data; of services The data operations of the cloud service on the disk for the new instance of servicesand configuring as a data operation on said disk for said
[0023] According to various embodiments, a cloud service migration method provides that in a process of migrating a cloud service from a source cluster to a target cluster, based on a scheduled migration time specified by a user and included in a migration request for the cloud service, disk data of the cloud service in the source cluster is migrated to the target cluster based on the scheduled migration time, and data operations of the cloud service on disks in the source cluster are reconfigured as data operations on disks in the target cluster to provide services via new instances in the target cluster. In this way, the cloud service is migrated from the source cluster to the target cluster using a simplified technique, reducing potential service interruption time caused by interruption of the cloud service provided by the cloud service instance, thereby realizing improved efficiency and convenience in service migration. [Brief description of the drawings]
[0024] [Figure 1] FIG. 1 is a flow diagram illustrating a method for cloud service migration according to some embodiments of the present disclosure.
[0025] [Diagram 2] FIG. 2 is a schematic diagram illustrating cloud server migration according to some embodiments of the present disclosure.
[0026] [Diagram 3] FIG. 2 is a schematic diagram illustrating migration of disks for services of a cloud server instance according to some embodiments of the present disclosure.
[0027] [Figure 4] FIG. 2 is a block diagram illustrating an apparatus for cloud service migration according to some embodiments of the present disclosure.
[0028] [Diagram 5] FIG. 1 is a block diagram illustrating an electronic device for cloud service migration in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] In order to facilitate a thorough understanding of the present disclosure, numerous specific details are set forth in the following description. However, the present disclosure can be implemented in many other ways than those described herein, and those skilled in the art can make similar derivations without departing from the essence of the present disclosure, and the present disclosure is not limited by the specific implementations described below.
[0030] The present disclosure provides a method, an apparatus, and an electronic device for cloud services. The following drawings are several embodiments of the present disclosure, which are described in detail below.
[0031] 1 illustrates a process for cloud service migration according to some embodiments of the present disclosure. As illustrated in FIG. 1, the process for cloud service migration includes the following steps. In the illustrated embodiment, the methods described herein may be performed by a cloud computing platform or similar system.
[0032] Step S101. Obtain a migration request related to a cloud service hosted in a source cluster.
[0033] As used herein, cloud service refers to a cloud server (e.g., Elastic Compute Service (ECS)) that provides basic cloud computing services. A user who uses a cloud server does not need to purchase hardware devices in advance. Instead, the user creates as many cloud server instances as required based on the needs of the service. During the use of the cloud server, based on the change in the actual service, the user may expand or reduce the disk volume, increase or decrease the network bandwidth, etc., for the cloud server. In some scenarios, the user may release the resources associated with the cloud server that are no longer used. As a virtual computing environment, a cloud server instance includes necessary server resource components such as CPU, memory, operating system, disk, network bandwidth, etc. A cloud server instance is an operating entity provided by the cloud server to each user, each cloud server instance being a virtual machine. A user may perform operations such as disk mounting, caching, image mirroring, environment development, etc. on the cloud server instance through the administrative privileges associated with the cloud server instance.
[0034] Generally, a geographical region is configured with one or more availability zones. As used herein, availability zone refers to one or more data centers in the same region, where infrastructure such as power supply, communication network, etc. are separated from each other. In this way, failures are separated between availability zones, and the network latency of cloud server instances is lower in the same availability zone. Whether cloud server instances are located in the same availability zone depends on the requirements of fault tolerance and network latency sensitivity. If there is an increased requirement for fault tolerance, cloud server instances are deployed in different availability zones in the same geographical region. If there is an increased requirement for network latency sensitivity, cloud server instances are deployed in the same availability zone in the same geographical region. Generally, a data center in an availability zone is a cloud server cluster of multiple cloud servers. In one example, multiple cloud server clusters deployed separately from each other are in the same availability zone.
[0035] According to various embodiments, a method of cloud service migration may be for migrating cloud servers across availability zones in the same geographic region, or for migrating cloud servers from an availability zone in one geographic region to an availability zone in another geographic region. In some embodiments, between two availability zones, a cloud server in a first cloud server cluster in a first availability zone is migrated to a second cloud server cluster in a second availability zone. In other words, the cloud server is migrated from a source cloud server cluster (source cluster) to a target cloud server cluster (target cluster).
[0036] In migrating cloud servers from a source cloud server cluster to a target cloud server cluster, the number of cloud servers for migration is not fixed, but is determined based on actual service requirements. For simplicity, only a single cloud server is shown for migration as an example, but the migration of multiple cloud servers is similar and will not be described in detail herein.
[0037] In this step, a migration request related to a cloud server hosted in a source cloud server cluster is obtained. In one embodiment, the migration request includes a scheduled migration time for migrating the cloud server from the source cloud server cluster to the target cloud server cluster. In other words, the cloud server is migrated in a pre-scheduled manner. For example, the scheduled migration time can be scheduled using a timer. When the timer is triggered (e.g., the time elapses until the current time according to the timer reaches the scheduled migration time), a migration process is executed to migrate the cloud server from the source cloud server cluster to the target cloud server cluster. As shown in FIG. 2, to migrate the cloud server from the source cloud server cluster to the target cloud server cluster at a specific time, a user schedules a migration process (201) for the cloud server to be migrated. In one embodiment, the timer is configured to expire at the scheduled migration time based on a time specified by the user. When the timer is triggered (207) (e.g., the current time according to the timer reaches the scheduled migration time), a migration process is initiated and executed (209, 211) to migrate the cloud server.
[0038] In some embodiments, after a migration process related to a cloud server is scheduled (203) (e.g., a migration time is specified by a user), the scheduled migration time may need to be modified (205) due to actual service requirements. For example, if a user service provided by a cloud service hosted by a cloud server instance is busy, the scheduled migration time needs to be postponed. In this scenario, the scheduled migration time can therefore be modified to a later time specified by the user. Similarly, if the promotion of a user service provided by a cloud service hosted by a cloud server instance exceeds the expected result, the original plan to place the cloud server in one new availability zone can therefore be adjusted to place the cloud server in multiple new availability zones. Furthermore, the migration task can also be modified to change the target cloud server cluster corresponding to the migration task from one target cloud server cluster to multiple target cloud server clusters. This is equivalent to adding a migration task to migrate the cloud server to a cloud server cluster in a newly assigned availability zone.
[0039] Step S102. Based on the scheduled migration time, the disk data associated with the original instance of the cloud service is migrated to the new instance of the cloud service instantiated in the target cluster. of services Move to disk for this purpose.
[0040] In the above step S101, a migration request for migrating a cloud server from a source cloud server cluster to a target cloud server cluster is obtained, and a migration time is determined based on a scheduled migration time included in the migration request. In step S102, disk data associated with an original instance of the cloud server in the source cloud server cluster is instantiated in the target cloud server cluster based on the scheduled migration time. Ta A new instance of a cloud server of services The files are then migrated to the disk for
[0041] In some embodiments of the present disclosure, disk data associated with an original instance of a cloud server in a source cloud server cluster is instantiated in a target cloud server cluster. Ta A new instance of a cloud server of services Before the data is migrated to the disk for
[0042] 1) Instantiate a new instance of a cloud server in the target cloud server cluster.
[0043] After obtaining a migration request for migrating a cloud server in a source cloud server cluster to a target cloud server cluster through the above step S101, during the process of migrating the cloud server from the source cloud server cluster to the target cloud server cluster, first A cloud server instance (e.g. a new instance) but , in the target cloud server cluster stomach Instantiation Be As shown in Fig. 2, after a migration request for a cloud server is obtained to migrate the cloud server from a source cloud server cluster to a target cloud server cluster at a specific scheduled migration time, a migration process for the cloud server is performed (209, 211) based on a trigger (207) associated with the scheduled migration time included in the migration request. In this example, a new instance of the cloud server is instantiated in the target cloud server cluster.
[0044] 2) Configuring a new instance of the cloud server and resource components associated with the new instance.
[0045] As explained above, a cloud server instance is a virtual computing environment that includes necessary server resource components such as CPU, memory, operating system, disk, network bandwidth, etc. In one embodiment, the resources used by a cloud server are classified into three categories: instance, network connection, and storage (e.g., disk). The following illustrates the migration process of instance resources and network resources as an example illustrating the configuration of a new instance of a cloud server instantiated in a target cloud server cluster and the configuration of the resource components of the new instance.
[0046] A new instance of a cloud server.
[0047] As used herein, a cloud server instance refers to the aggregated utilization of CPU and memory resources, and the configuration is indicated through the configuration. For example, a configuration of {core: 2, memory: 2048} indicates an instance that is configured with a CPU of 2 cores and memory of 2 gigabytes in size. The management of the cloud server is implemented by a higher-layer cloud control system that includes migration management on the cloud server as a required function. Thus, the migration of the cloud server instance is Implemented by a cloud control system, the cloud control system releases an original instance of the cloud server in a source cloud server cluster, sends an instantiation request with the same configuration based on configuration information of the original instance of the cloud server to a target cloud server cluster, and configures a new instance to be instantiated in the target cloud server cluster with the same configuration. The migration of the cloud server instance is complete once the configuration is complete (213). In some embodiments, after completing the migration, the scheduled migration time is removed (215).
[0048] Furthermore, in the implementation, as the scale of user services provided by the cloud service hosted by the cloud server instance increases, the user intends the cloud service to support the user services at a larger scale. In other words, a new instance of the cloud server providing the cloud service needs to be configured with more resources. A configuration interface is provided to configure the new instance of the cloud server, such that the configuration of the new instance of the cloud server is different from that of the original instance. In this way, the user can: Send configuration information for the self-defined new instance through the configuration interface. The configuration information sent by the user is then retrieved in the configuration interface. The new instance is configured based on the obtained configuration information to better accommodate the requirements of the user service.
[0049] b. A network of cloud servers.
[0050] In one embodiment, the network migration is implemented by a routing notification process that allocates and releases network ports associated with the cloud servers by the cloud control system. In one example, such a process includes allocating network ports for cloud servers in a target cloud server cluster, releasing cloud services from network ports in the source cloud server cluster based on network configuration information forwarded by the cloud control system, configuring cloud services to the network ports allocated in the target cloud server cluster, and completing routing updates and Address Resolution Protocol (ARP) advertisements. Thus, the terminal ports are: Via broadcast The network port associated with the cloud server is changed from the source cloud server cluster to the target cloud server cluster. Be R That You will be notified.
[0051] In one embodiment, during network migration, the user keeps the IP address before and after migration. In this way, in the geographical region of the owned network, the IP address is reachable in all availability zones in the geographical region. Alternatively, the user may choose to change the IP address. In this case, only a new relationship needs to be established to map between the IP address before migration and the IP address after migration. However, accessing the IP address from the entire geographical region sometimes leads to a decrease in the quality of network access. Therefore, in order to guarantee the network access quality, in one example, the migration of the IP address is performed only when the IP address belongs to the same geographical region, ensuring high efficiency of access to the service.
[0052] 3) Terminate the original instance in the source cloud server cluster and start a new instance that is instantiated in the target cloud server cluster based on the resource components.
[0053] In this step, after configuring the new instance and the resource components of the new instance in the above operations, the original instance of the cloud server is terminated in the source server cluster, and then a new instance of the cloud server is started based on the resource components, so that the new instance of the cloud server can provide services to users.
[0054] In one embodiment, disk data associated with an original instance of a cloud server in a source cloud server cluster is instantiated in a target cloud server cluster based on a scheduled migration time. Ta A new instance of a cloud server of services Before a file is migrated to disk for the original instance, the following steps are performed: of servicesThe operations further include stopping data operations (including read and write operations) of the cloud service to the disk for the target cloud server cluster. Okeru New Instance of services based on which disk data associated with the original instance of the cloud server in the source cloud server cluster is instantiated in the target cloud server cluster. Ta A new instance of a cloud server of services In an implementation, the original instance of the cloud server and the new instance of the cloud server each have their own processing queue. To teeth, It contains a processing queue for the original instance and a processing queue for the new instance, where the processing queue for the original instance contains: Original instance of services A data request (including a read or write request) that includes a data operation of the cloud server on a disk for the The processing queue for the new instance contains New Instance of services A read or write request that includes a data operation of the cloud server to the disk for 。
[0055] FIG. 3. Cloud service according to some embodiments of the present disclosure. of services Turning now to a flow diagram illustrating the migration of disks for the cloud server to be migrated. As shown in FIG. 3, Disk A (301) is assigned to the source server cluster to serve the cloud server to be migrated. The cloud server is configured to read data from Disk A and write data to it. When the upper layer of the cloud system issues a migration command related to Disk A (301), Disk A (301) is configured to stop all read and write processing. In addition, the processing queue of the original instance stops processing read and write requests enqueued therein. Disk A (301) is also marked as to be deleted. Cloud server of servicesA disk B (303) for the new instance is allocated in the target cloud server cluster, and then the disk B (303) is configured to start providing read and write services. For example, a read or write request including a read or write operation to the disk B (303) is enqueued in the processing queue of the new instance, and the read and write processing of the new instance is all performed to the disk B (303). When the processing queue of the original instance stops dequeuing read / write requests thereon for processing, the read / write requests that are in the processing queue of the original instance and have not yet been processed are transferred to the processing queue of the new instance for processing.
[0056] In some embodiments, disk data associated with the original instance is transferred to the new instance via a background thread running. of services In one example, a migration priority is configured for disk data during migration, and migration of disk data associated with the original instance is initiated using a low migration priority configuration. During migration, as read / write operations are performed by the new instance, data included in the data request is copied to the disk for migration to the new instance. of services It is determined whether the data exists on the disk. but A new instance of a cloud server of services In response to determining that the data in the data request does not reside on disk for the target cluster, the migration priority of the data in the data request is set to high migration priority. In this manner, the disk data associated with the original instance is transferred to the new instance of the cloud service instantiated in the target cluster. of services In the process of migrating to disk for migration, migrations are performed in descending order of migration priority.
[0057] As shown in FIG. 3, data on disk A (301) is copied to disk B (303) by the execution of a background thread. During such copying, when a read or write operation is executed on the new instance, it is determined whether data included in the read or write request including the read or write operation exists on disk B (303). In response to a determination that the data exists on disk B (303), the read or write operation included in the read or write request is executed on disk B. Otherwise, in response to a determination that the data associated with the new instance does not exist on disk B (303) (e.g., the requested data has not yet been copied to disk B 303), the migration priority of the data associated with the new instance is changed from a low migration priority to a high migration priority. Based on this, when the read or write operation included in the read or write request is completed to be executed on disk B (303), the high migration priority data (e.g., the data associated with the new instance) is copied from disk A (301) to disk B (303). This implementation is the basis of asynchronous data copy, which leads to the absence of the need to wait for data on disk A (301) to be completely copied to disk B (303) before a new instance of a cloud server can begin providing service, thereby reducing the interruption time (e.g., downtime) associated with user services.
[0058] In one embodiment, the copying of data on disk A (301) to disk B (303) is performed by dividing the data on disk A (301) associated with the original instance into at least one data block, and the data on disk A (301) associated with the original instance is copied to the new instance in the form of such data blocks. of servicesThe data on disk A (301) is then copied to disk B (303) for image mirroring. Furthermore, the data on disk A (301) is copied to disk B (303) through image mirroring. In one example, the data on disk A (301) is divided into at least one data block, and a data mirroring image corresponding to each data block is created, and the data on disk A (301) is copied to disk B (303) through data mirroring.
[0059] Further, a flag bit can be configured for the data block to mark whether the data block has been copied. In one example, if the data block has been copied to disk B (303), the flag bit of the data block is marked as 1, and if the data block has not been copied, the flag bit of the data block is marked as 0. Based on this, in the process of copying data on disk A (301) to disk B (303), the data already copied is compared with the data on disk A (301) based on the flag bit of the data block to determine the progress of the copy of the data on disk A (301). In the implementation, the comparison used to determine the progress of the copy of the data on disk A (301) is encapsulated into a migration progress query interface that allows a user to obtain the real-time copy progress of the copy of the data on disk A (301) to disk B (303).
[0060] Typically, the size of data on a disk is hundreds of gigabytes or even terabytes. Assuming that the disk data can be copied at a speed of about 100 GB / hour, the technology used by the current system takes several hours to copy the disk data that is mirrored to the mirror image for copying. In contrast, the technical solution of the present disclosure provides a service interruption time of about 2 to 3 minutes, counting from the termination of the service provided by the original instance to the resumption of the service provided after a new instance of the cloud service is started. Thus, the technical solution of the present disclosure is more efficient compared to the service interruption time of several hours or longer associated with the current migration technology.
[0061] Now, referring back to FIG. 1, the process further includes step S103. of services For disks, cloud service data operations for new instances of services This includes configuring the data operations on the disk for the purpose of
[0062] As explained above, the original instance of the cloud service and the new instance of the cloud server are each configured with their respective processing queues. In one example, a data request involving a cloud server data operation on a disk for the service of the original instance (e.g., a request involving a read or write request) is enqueued for processing in a processing queue of the original instance. New Instance of services A read or write request that includes a data operation of the cloud server to the disk for the new instance is enqueued in the processing queue of the new instance for processing.
[0063] Based on the scheduled migration time, Disk data associated with the original instance of the cloud server From the source cloud server cluster, A new instance of the cloud server to be instantiated in the target cloud server cluster. of services For discs, above Based on the above migration, the original instance of services Data operations on cloud servers for disks but , a new instance For service ofThe data operations are configured to be performed on the disks, thereby migrating the cloud services provided by the cloud servers from a source cloud server cluster to a target cloud server cluster.
[0064] Referring to FIG. 3, a cloud server (305) (e.g., an original instance of a cloud server providing a cloud service) reads data from and writes data to disk A (301). When the upper layer of the cloud system issues a migration command related to disk A (301), disk A (301) stops all read and write processing, and the processing queue of the original instance stops processing read and write requests enqueued therein. Furthermore, disk A (301) is marked as being to be deleted, and the cloud server of services For disk B(303) but , is assigned to the target cloud server cluster. Next, Disk B (303) but After being assigned, Disk B (303) Read and Write Requests Service provision for The original instance begins to process read and write requests, including read and write operations to Disk B (303), and these requests are enqueued in the processing queue of the new instance. All read and write operations of the new instance are performed to Disk B (303). After the processing queue of the original instance stops processing the read and write requests that were enqueued in it, the read and write requests that are still in the processing queue of the original instance and have not yet been processed are transferred to the processing queue of the new instance for processing.
[0065] In some embodiments, cloud servers are migrated from a source cloud server cluster to a target cloud server cluster in a "live migration" manner. In one example, compared to the above migration, the original instance For service ofA new instance is instantiated before the cloud server's read or write operations to the disk are stopped (e.g., before the original instance is taken out of service); The Instance of services The disks for the target cloud server cluster are allocated to the target cloud server cluster. Correspondingly New Instances and New Instances of services Disk for but Consists of the After completion, the new instance is started. After the new instance is started, memory data associated with the original instance is copied to memory associated with the execution of the new instance, and execution state data related to the execution state (e.g., CPU state, register state) of the original instance is further copied to the new instance until the execution state data related to the execution state of the original instance falls below a preconfigured threshold. Thereafter, the original instance is of services The cloud server's read and write operations to the disk for the new instance (e.g., disk A301) are stopped, and the remaining running state data is copied to the new instance, and the original instance is of services The cloud server data operations for the disks (e.g. disk A301) for the new instance are Service The data transfer is configured as a data operation on a disk (e.g., disk B 303) for migration of the cloud server, thereby realizing migration of the cloud server. By using the live migration technology to migrate the cloud server, the service interruption time is shorter and can be controlled within the order of milliseconds or microseconds, realizing more efficient migration of the cloud server.
[0066] According to various embodiments, a cloud service migration solution is provided in a process of migrating a cloud server from a source cloud server cluster to a target cloud server cluster based on a scheduled migration time specified by a user and included in a migration request, the cloud server is migrated from the source cloud server cluster to the target cloud server cluster based on the scheduled migration time. The data operations of the cloud service on a disk in the source cloud server cluster are reconstructed as data operations on a disk in the target cloud server cluster, and services are provided by a new instance in the target cloud server cluster. In this way, the cloud server is migrated from the source cloud server cluster to the target cloud server cluster with a simple implementation, while reducing the service interruption time caused by the interruption of the service provided by the cloud service instance, and realizing a more efficient and convenient migration.
[0067] 4 is a block diagram illustrating an exemplary apparatus for cloud service migration according to some embodiments of the present disclosure. The cloud service migration apparatus is substantially similar to the method for cloud service migration described above, and the details are not repeated here for brevity.
[0068] As shown in FIG. 4, the apparatus (400) for service migration includes a migration request obtaining unit (401), a disk migration unit (402), and a data operation configuration unit (403).
[0069] The migration request obtaining unit (401) is configured to obtain a migration request associated with a cloud service hosted in a source cluster, where the migration request includes a scheduled migration time for migrating the cloud service from the source cluster to a target cluster.
[0070] The disk migration unit (402) migrates disk data associated with the original instance of the cloud service to a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. of services The migration of disk data is configured to migrate to a disk for performing the migration of the disk data based on a migration priority order of the disk data.
[0071] The data operation configuration unit (403) of services For disks, cloud service data operations for new instances of services The data operations are configured to be performed on the disk for the purpose of the present invention.
[0072] In one embodiment, the apparatus (400) for cloud service migration further includes a new instance instantiation unit, a configuration unit, and a new instance initiation unit.
[0073] The new instance instantiation unit is configured to instantiate a new instance of the cloud service in the target server cluster.
[0074] The configuration unit is configured to configure the new instance and resource components associated with the new instance.
[0075] The new instance starting unit is configured to stop the original instance in the source server cluster and start a new instance based on the resource components.
[0076] In some embodiments, the configuration unit includes one or both of a first new instance configuration subunit and a second new instance configuration subunit.
[0077] The first new instance configuration subunit is configured to configure a new instance in the target cluster based on the configuration information of the original instance using the same configuration as the configuration information.
[0078] The second new instance configuration subunit is configured to configure the new instance based on the configuration information obtained through the pre-configured configuration interface.
[0079] In some embodiments, the resource component includes a disk, hi some other embodiments, the resource component further includes at least one of a CPU, a memory, an operating system, and a network connection.
[0080] In some embodiments, the configuration unit includes a network port allocation subunit and a network port migration subunit.
[0081] The network port allocation subunit is configured to allocate a network port in the target cluster.
[0082] The network port migration subunit is configured to release the cloud service from the network port in the source cluster, configure the cloud service to an assigned network port in the target cluster, and perform routing updates.
[0083] In some embodiments, the configuration unit includes a data manipulation termination unit and a disk allocation subunit.
[0084] The data operation stop unit is the original instance of services For disks do It is configured to stop data operations of cloud services.
[0085] The disk allocation subunit is To New Instanceof services The ESXi 5.0 server is configured to allocate disks for the virtual machine.
[0086] In some embodiments, the data manipulation configuration unit (403) includes one or both of a first copy sub-unit and a second copy sub-unit.
[0087] The first copy subunit divides the disk data associated with the original instance into at least one data block, and copies the disk data associated with the original instance to the new instance. of services The data is then copied to a disk for storage in the form of data blocks.
[0088] The second copy sub-unit divides the disk data associated with the original instance into at least one data block, creates a data mirroring image corresponding to each data block, and copies the disk data associated with the original instance to the new instance. of services The data is then copied to the disk for data mirroring.
[0089] In some embodiments, the data block is configured with a flag bit to mark whether the data block has been copied or not. of services In the process of copying to the disk for the original instance, the data already copied is compared to the disk data associated with the original instance based on the flag bits to determine the progress of copying the disk data associated with the original instance.
[0090] In some embodiments, the original instance and the new instance are each configured with their respective processing queues. of services Data requests, including data operations for the cloud service on disks for the of servicesData requests, including data operations of the cloud service against the disk for the new instance, are enqueued in the processing queue of the new instance.
[0091] In some embodiments, after the data manipulation configuration unit (403) begins execution, the new instance of services Data requests, including data operations of the cloud service on disk for the new instance, are enqueued in a processing queue of the new instance, and data requests that remain in the processing queue of the original instance and have not yet been processed are transferred to the processing queue of the new instance for processing.
[0092] In some embodiments, the migration priority of disk data is determined according to the following steps: First, the data contained in the data request but , said new instance of services The data included in the data request is used to determine whether the data exists on disk for but New Instance of services In response to determining that the requested data is not present on the disk for which the requested data is to be copied, a migration priority of the data included in the data request is configured to be a high migration priority.
[0093] Second, the disk data associated with the original instance is copied to the new instance of the cloud service instantiated in the target cluster. of services In the process of migrating to a disk for migration, migration is performed in descending order of migration priority.
[0094] In some embodiments, the apparatus (400) further includes a decision making subunit that is executed in the process of processing data requests in the processing queue of the new instance.
[0095] The decision subunit determines whether the data contained in the data request corresponds to a new instance. of services The data request is configured to determine whether the data contained in the data request exists on disk for the new instance. of servicesIn response to determining that a new instance exists on disk, the decision subunit of services The data request is configured to perform a data operation included in the data request based on the disk for which the data operation is included. or The data included in the data request is a new instance of services In response to determining that the data with high migration priority is not present on disk for the original instance, the decision subunit of services Disk for new instance of services The disks for the new instance are migrated first, and when the migration is complete, of services Based on the disk for tree, Configured to perform data operations contained in a data request. R .
[0096] In some embodiments, the source cluster and the target cluster are configured in different availability zones.
[0097] In some embodiments, the cloud service is configured as a cloud server for providing cloud computing services. In some embodiments, the source cluster is configured as a cloud server cluster of at least one cloud server, and the target cluster is configured as a cloud server cluster of at least one cloud server.
[0098] 5 is a block diagram of an exemplary electronic device for cloud service migration according to some embodiments of the present disclosure. The function of the electronic device is substantially similar to the above method for cloud service migration, and the details are not repeated here.
[0099] As shown in FIG. 5, the electronic device for cloud service migration includes a memory (501) and a processor (502).
[0100] The memory (501) is configured to store computer-executable instructions. The processor (502) is configured to read and execute the computer-executable instructions stored in the memory (501) to cause the electronic device (500) to perform operations including the following steps:
[0101] Step 1. Obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster.
[0102] Step 2. Based on the scheduled migration time, the disk data associated with the original instance of the cloud service is transferred to the new instance of the cloud service instantiated in the target cluster. of services The disk data is migrated to a disk for performing the above-mentioned operations, and the migration of the disk data is performed based on the migration priority of the disk data.
[0103] Step 3. Original Instance of services For disk operations on cloud services, the new instance of services This is configured as a data operation on the disk for the purpose of
[0104] In some embodiments, the original instance of services For disks, cloud service data operations for new instances of services Prior to configuring as a data operation to disk for the target cluster, the processor (502) is further configured to execute the computer-readable instructions including instantiating a new instance in the target cluster, configuring the new instance and a resource component associated with the new instance, stopping the original instance at the source cluster, and starting the new instance based on the resource component.
[0105] In some embodiments, configuring the new instance and resource components associated with the new instance based on the configuration information of the original instance includes: before Configuration of the above information The same configuration as or configuring the new instance based on the configuration information obtained through a pre-configured configuration interface.
[0106] In some embodiments, the resource component includes a disk, hi other embodiments, the resource component further includes at least one of a CPU, a memory, an operating system, and a network connection.
[0107] In some embodiments, configuring the new instance and resource components associated with the new instance includes allocating a network port in the target cluster, releasing the cloud service from the network port of the source cluster, configuring the cloud service to the network port allocated to the target cluster, and performing a routing update.
[0108] In some embodiments, configuring the new instance and the resource components associated with the new instance comprises configuring the original instance of services The first is to stop the cloud service from performing data operations on the disks to create new instances in the target cluster. of services The disk allocation stage for the new instance and of services After the disk allocation for the cloud service is completed, the disk data associated with the original instance of the cloud service is transferred to the new instance of the cloud service instantiated in the target cluster based on the scheduled migration time. of services Disk for the original instance ServiceFor disks, cloud service data operations for new instances of services and executing instructions that configure the data operations on the disk for the read / write operation.
[0109] In some embodiments, disk data associated with the original instance of the cloud service is transferred to a new instance of the cloud service instantiated in the target cluster. of services The step of migrating the disk data associated with the original instance to a disk for the new instance includes dividing the disk data associated with the original instance into at least one data block, and migrating the disk data associated with the original instance in the form of data blocks to a disk for the new instance. of services Copying to a disc ,or Dividing the disk data associated with the original instance into at least one data block, creating a data mirroring image corresponding to each data block, and copying the disk data of the original instance to the disk of the new instance through data mirroring. 、 It is implemented by:
[0110] In some embodiments, the data block is configured with a flag bit to mark whether the data block has been copied or not. of services In the process of copying to disk for the original instance, the data already copied is compared to the disk data associated with the original instance based on the flag bits to determine the progress of copying the disk data associated with the original instance.
[0111] In some embodiments, the original instance and the new instance are each configured with their respective processing queues. of services Data requests, including data operations for the cloud service on disks for the of servicesData requests, including data operations of the cloud service against the disk for the new instance, are enqueued in the processing queue of the new instance.
[0112] In some embodiments, the original instance of services For disks, cloud service data operations for new instances of services After the configuration stage, the new instance is of services Data requests, including data operations of the cloud service on disk for the new instance, are enqueued in the processing queue of the new instance, and data requests remaining in the processing queue of the original instance that have not yet been processed are transferred to the processing queue of the new instance for processing.
[0113] In some embodiments, the migration priority of disk data is determined by whether the data included in the data request is of services determining whether the data included in the data request is present on disk for the new instance; of services configuring a migration priority for the data included in the data request to a high migration priority in response to determining that the data does not reside in disk for the original instance; and migrating the disk data associated with the original instance to a new instance of the cloud service instantiated in the target cluster. of services and performing migration in descending order of migration priority in the process of migrating to a disk for migration.
[0114] In some embodiments, a processing queue for new instances Inside The processing of the data request includes the following operations: of services determining whether the data included in the data request exists on disk for the new instance; of services Depending on whether it is present on the disk, Data operations included in the data request New Instance of services For disks deathAt the execution stage, the data included in the data request is used to create a new instance. of services If it is determined that the file does not exist on the disk, high Migration priority data From the disks serving the original instance to the disks serving the new instance Migrate and when migration is complete, the new instance of services For disks death, and performing the data operations included in the data request.
[0115] In some embodiments, the source cluster and the target cluster are configured in different availability zones.
[0116] In some embodiments, the cloud service is configured as a cloud server for providing cloud computing services. In other embodiments, the source cluster includes a cloud server cluster of at least one cloud server and the target cluster includes a cloud server cluster of at least one cloud server.
[0117] The present disclosure is disclosed above through preferred embodiments, but is not intended to be limited thereto.Those skilled in the art can make possible variations and modifications without departing from the spirit and scope of the disclosure.Therefore, the protection scope of the present disclosure should be defined by the claims of the present disclosure.
[0118] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0119] The memory may include computer readable media in the form of non-persistent memory such as read only memory (ROM) or flash memory (Flash RAM), random access memory (RAM) or non-volatile memory, etc. The memory is an example of a computer readable medium.
[0120] Computer-readable media includes persistent and non-persistent, and movable and non-movable media that can implement information storage using any method and technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory devices, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage devices, cassette tape, magnetic tape / magnetic disk storage devices or other magnetic storage devices, or any other non-transmission media that may be used to store information accessible by a computer processing device. As defined herein, computer-readable media does not include non-transitory computer-readable media (transitory media) such as modulated data signals and carrier waves.
[0121] It should be understood by those skilled in the art that the embodiments of the present disclosure may be provided as a method, a system, or a computer program product. Thus, the present disclosure may take the form of an all-hardware embodiment, an all-software embodiment, or an embodiment that combines software and hardware. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) having computer usable program code therein. According to this specification, the configurations described in the following items are also disclosed. [Item 1] obtaining a migration request for a cloud service in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; migrating disk data of the original instance of the cloud service to a disk of a new instance of the cloud service created in the target cluster according to the scheduled migration time, wherein the migration of the disk data is performed based on a migration priority order of the disk data; configuring data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance; A cloud service migration method comprising: [Item 2] Before the step of configuring the data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance is performed, creating the new instance in the target cluster; configuring the new instance and resource components of the new instance; terminating the original instance of the source cluster; starting the new instance based on the resource component; 2. The cloud service migration method according to item 1, wherein the following is executed. [Item 3] said step of configuring said new instance and resource components of said new instance further comprising: configuring the new instance in the target cluster according to the configuration information of the original instance, according to the same configuration as the configuration information; or configuring the new instance according to configuration information obtained through a preset configuration interface; 3. The cloud service migration method according to claim 2, implemented by the method described above. [Item 4] 3. The cloud service migration method according to item 2, wherein the resource components include the disk, and the resource components further include at least one of a CPU, a memory, an operating system, and a network. [Item 5] The step of configuring the new instance and resource components of the new instance further comprises: creating a network port in the target cluster; releasing the cloud service from a network port of the source cluster; configuring the cloud service to the network port of the target cluster; performing a route update; 5. The cloud service migration method according to item 4, comprising: [Item 6] The step of configuring the new instance and resource components of the new instance further comprises: Stopping the data operations of the cloud service on the disk of the original instance; creating the disks of the new instances in the target cluster; After the creation of the disk of the new instance is complete, migrating disk data of the original instance of the cloud service to a disk of a new instance of the cloud service created in the target cluster according to the scheduled migration time; configuring data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance; and 5. The cloud service migration method according to item 4, comprising: [Item 7] The step of migrating disk data of the original instance of the cloud service to a disk of a new instance of the cloud service created in the target cluster includes: Dividing the disk data of the original instance into at least one data block and copying the disk data of the original instance in the form of the data blocks to the disk of the new instance; or dividing the disk data of the original instance into at least one data block, creating a data image corresponding to each data block, and copying the disk data of the original instance to the disk of the new instance in the form of the data image; 2. The cloud service migration method according to claim 1, implemented by the method described above. [Item 8] 8. The cloud service migration method according to item 7, wherein the data block includes a flag bit for marking whether the data block has been copied, and in a process of copying the disk data of the original instance to the disk of the new instance, the already copied data is compared with the disk data of the original instance based on the flag bit, and a progress of copying the disk data of the original instance is obtained according to a result of the comparison. [Item 9] 3. The cloud service migration method of item 2, wherein each of the original instance and the new instance includes a processing queue corresponding to the original instance and the new instance, and a data request including the data operation of the cloud service on the disk of the original instance is added to the processing queue of the original instance, and a data request including the data operation of the cloud service on the disk of the new instance is added to the processing queue of the new instance. [Item 10] 10. The cloud service migration method of claim 9, wherein after the step of configuring the data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance is performed, a data request including the data operations of the cloud service on the disk of the new instance is added to the processing queue of the new instance, and a data request for which processing has not been completed in the processing queue of the original instance is sent to the processing queue of the new instance for processing. [Item 11] The migration priority of the disk data is: determining whether data included in the data request exists within the disk of the new instance, and if not, setting a migration priority of the data included in the data request to a high migration priority; In the process of migrating the disk data of the original instance to the disk of the new instance of the cloud service created in the target cluster, performing the migration in descending order of migration priority. 2. The cloud service migration method according to claim 1, wherein the method is determined by a method. [Item 12] In processing a data request in the processing queue of the new instance, determining whether the data included in the data request exists within the disk of the new instance, and if so, tree performing a data operation included in the data request; If not, migrate the data with high migration priority from the disk of the original instance to the disk of the new instance, and upon completion of the migration, create a new instance based on the disk of the new instance. tree performing a data operation included in the data request; 12. The cloud service migration method according to item 11, wherein the following is executed. [Item 13] 13. The cloud service migration method according to any one of claims 1 to 12, wherein the source cluster and the target cluster are in different availability zones. [Item 14] 13. The cloud service migration method according to any one of claims 1 to 12, wherein the cloud service refers to a cloud server for providing a cloud computing service, the source cluster refers to a cloud server cluster consisting of at least one cloud server, and the target cluster refers to a cloud server cluster consisting of at least one cloud server. [Item 15] a migration request obtaining unit configured to obtain a migration request for a cloud service in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; a disk migration unit configured to migrate disk data of the original instance of the cloud service to a disk of a new instance of the cloud service created in the target cluster according to the scheduled migration time; a data operation configuration unit configured to configure data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance; A cloud service migration device comprising: [Item 16] A memory and a processor, The memory is configured to store computer-executable instructions, and the processor is further configured to: obtaining a migration request for a cloud service in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; Migrating disk data of the original instance of the cloud service to a disk of a new instance of the cloud service created in the target cluster according to the scheduled migration time; configuring data operations of the cloud service on the disk of the original instance as data operations on the disk of the new instance; configured to execute the computer-executable instructions, Electronic devices.
Claims
1. obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; In response to receiving the migration request, stopping data requests including data operations of the cloud service to a disk associated with an original instance in the source cluster; migrating disk data associated with the original instance of the cloud service to a disk associated with a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time and migration priority order; configuring data operations on the disks associated with the original instance after the stopping of the cloud service as data operations on the disks associated with the new instance; A method comprising: The transition step includes: during the migration, in response to determining that data included in a data request is not present on the disk associated with the new instance, changing a migration priority of the data included in the data request from a first migration priority to a second migration priority, the second migration priority causing the data included in the data request to be migrated sooner than the first migration priority; The method further comprises: enqueuing a data request, the data request including a data operation of the cloud service for the disk associated with the new instance, in a processing queue of the new instance for processing; and forwarding data requests from the processing queue of the original instance to the processing queue of the new instance for processing.
2. The transition step includes:
2. The method of claim 1, further comprising: during the migration, in response to determining that data included in a data request is present on the disk associated with the new instance, executing the data request on the disk associated with the new instance.
3. instantiating the new instance in the target cluster; configuring a resource component associated with the new instance; terminating the original instance in the source cluster; starting the new instance based on the resource components in the target cluster prior to configuring the data operations; The method of claim 1 or 2, further comprising:
4. 4. The method of claim 3, wherein configuring resource components associated with the new instance comprises configuring the new instance in the target cluster based on configuration information, the configuration information being selected from a group consisting of a configuration of the original instance and configuration information obtained via a pre-configured configuration interface.
5. Migrating disk data associated with the original instance of the cloud service to the disks associated with the new instance of the cloud service instantiated in the target cluster includes: dividing the disk data associated with the original instance into at least one data block and copying the disk data associated with the original instance in the form of the data blocks to the disk associated with the new instance; dividing the disk data associated with the original instance into at least one data block, generating a data mirroring image corresponding to each data block, and copying the disk data associated with the original instance to the disk associated with the new instance via data mirroring; The method of claim 1 , further comprising one or more of the following:
6. The data block is configured with a flag bit for marking whether the data block has been copied, the method further comprising: comparing the copied disk data associated with the new instance to the disk data associated with the original instance based on the flag bits; determining a progress of copying the disk data associated with the original instance based on the results of the comparing step; The method of claim 5 comprising:
7. The migrating step includes configuring a migration priority of the data included in the data request to a high migration priority in response to determining that the data included in the data request is not present on the disk associated with the new instance; migrating the disk data associated with the original instance to the disks associated with the new instance of the cloud service instantiated in the target cluster in order of decreasing migration priority; The method of claim 1 , comprising:
8. 8. The method of claim 7, wherein the step of migrating in descending order of migration priority includes migrating the data of the high migration priority from the disk associated with the original instance to the disk associated with the new instance, and, upon completion of the migration, performing the data operation included in the data request on the disk associated with the new instance.
9. On the computer, obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; In response to receiving the migration request, stopping data requests including data operations of the cloud service on a disk associated with an original instance in the source cluster; migrating disk data associated with the original instance of the cloud service to a disk associated with a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time and migration priority order; configuring data operations of the cloud service after the stopping step on the disk associated with the original instance as data operations on the disk associated with the new instance; A program for executing The transition procedure is as follows: during the migration, in response to determining that data included in a data request is not present on the disk associated with the new instance, changing a migration priority of the data included in the data request from a first migration priority to a second migration priority, the second migration priority causing the data included in the data request to be migrated earlier than the first migration priority; The program further includes: enqueuing a data request, the data request including a data operation of the cloud service for the disk associated with the new instance, in a processing queue of the new instance for processing; and forwarding data requests from the processing queue of the original instance to the processing queue of the new instance for processing.
10. The computer instantiating the new instance in the target cluster; configuring a resource component associated with the new instance; terminating the original instance in the source cluster; starting the new instance based on the resource components in the target cluster prior to configuring the data operation; The program according to claim 9 , further comprising:
11. 11. The program of claim 10, wherein configuring resource components associated with the new instance comprises configuring the new instance in the target cluster based on configuration information, the configuration information being selected from a group consisting of a configuration of the original instance and configuration information obtained via a pre-configured configuration interface.
12. The transition procedure is as follows: dividing the disk data associated with the original instance into at least one data block and copying the disk data associated with the original instance in the form of the data blocks to the disk associated with the new instance; dividing the disk data associated with the original instance into at least one data block, generating a data mirroring image corresponding to each data block, and copying the disk data associated with the original instance to the disk associated with the new instance via data mirroring; The program according to any one of claims 9 to 11, comprising one or more of the following:
13. The data block is configured with a flag bit for marking whether the data block has been copied, and the program causes the computer to: comparing the copied disk data associated with the new instance to the disk data associated with the original instance based on the flag bits; determining a progress of copying the disk data associated with the original instance based on a result of the comparing step; The program according to claim 12, further comprising:
14. The transition procedure is as follows: in response to determining that data included in the data request is not present on the disk associated with the new instance, configuring a migration priority of the data included in the data request to a high migration priority; migrating the disk data associated with the original instance to the disks associated with the new instance of the cloud service instantiated in the target cluster in order of decreasing migration priority; The program according to any one of claims 9 to 13, comprising:
15. A processor; a storage medium for tangibly storing thereon program logic for execution by said processor, said stored program logic comprising: logic, when executed by the processor, for obtaining a migration request associated with a cloud service hosted in a source cluster, the migration request including a scheduled migration time for migrating the cloud service from the source cluster to a target cluster; logic for, when executed by the processor, responsive to receiving the migration request, stopping data requests including data operations of the cloud service on a disk associated with an original instance in the source cluster; logic that, when executed by the processor, migrates disk data associated with the original instance of the cloud service to a disk associated with a new instance of the cloud service instantiated in the target cluster based on the scheduled migration time and migration priority order; logic that, when executed by the processor, configures data operations on the disks associated with the original instance after the shutdown of the cloud service as data operations on the disks associated with the new instance; An electronic device comprising: The logic for transitioning includes: during the migration, in response to determining that data included in a data request is not present on the disk associated with the new instance, logic to change a migration priority of the data included in the data request from a first migration priority to a second migration priority, the second migration priority causing the data included in the data request to be migrated sooner than the first migration priority; The program logic further comprises: logic for enqueuing a data request, the data request including a data operation of the cloud service for the disk associated with the new instance, in a processing queue of the new instance for processing; and logic for forwarding data requests from the processing queue of the original instance to the processing queue of the new instance for processing.
16. The stored program logic comprises: logic that, when executed by the processor, instantiates the new instance in the target cluster; logic that, when executed by the processor, configures a resource component associated with the new instance; logic that, when executed by the processor, terminates the original instance in the source cluster; logic that, when executed by the processor, starts the new instance based on the resource components in the target cluster before configuring the data operation; The electronic device of claim 15 further comprising:
17. The logic for configuring a resource component associated with the new instance comprises:
17. The electronic device of claim 16, further comprising: logic, when executed by the processor, to configure the new instance in the target cluster based on configuration information, the configuration information selected from a group consisting of a configuration of the original instance and configuration information obtained via a pre-configured configuration interface.
18. The logic for migrating disk data associated with the original instance of the cloud service to the disks associated with the new instance of the cloud service instantiated in the target cluster includes: logic that, when executed by the processor, divides the disk data associated with the original instance into at least one data block and copies the disk data associated with the original instance in the form of the data block to the disk associated with the new instance; logic that, when executed by the processor, divides the disk data associated with the original instance into at least one data block, generates a data mirroring image corresponding to each data block, and copies the disk data associated with the original instance to the disk associated with the new instance via data mirroring; 18. An electronic device according to any one of claims 15 to 17, comprising one or more of:
19. The data block is configured with a flag bit for marking whether the data block has been copied, and the stored program logic further comprises: logic that, when executed by the processor, compares the copied data to the disk associated with the new instance with the disk data associated with the original instance based on the flag bit; logic that, when executed by the processor, determines a progress of a copy of the disk data associated with the original instance based on a result of the comparison; 20. The electronic device of claim 18, comprising:
20. The logic for transitioning includes: logic that, when executed by the processor, in response to determining that data included in a data request is not present on the disk associated with the new instance, configures a migration priority of the data included in the data request to a high migration priority; logic that, when executed by the processor, migrates the disk data associated with the original instance to the disks associated with the new instance of the cloud service instantiated in the target cluster in descending order of migration priority; 20. The electronic device of claim 15, comprising:
Citation Information
Patent Citations
Backup device, backup method and backup program
JP2013196290A
Data transfer device, data transfer system, data transfer method and program
JP2014186652A
Object migration between cloud environments
US9648134B2
Data migration method and computer system
WO2017145272A1