WO2019100984A1 - 云服务迁移方法、装置以及电子设备 - Google Patents

云服务迁移方法、装置以及电子设备 Download PDF

Info

Publication number
WO2019100984A1
WO2019100984A1 PCT/CN2018/115383 CN2018115383W WO2019100984A1 WO 2019100984 A1 WO2019100984 A1 WO 2019100984A1 CN 2018115383 W CN2018115383 W CN 2018115383W WO 2019100984 A1 WO2019100984 A1 WO 2019100984A1
Authority
WO
WIPO (PCT)
Prior art keywords
disk
data
instance
migration
cloud service
Prior art date
Application number
PCT/CN2018/115383
Other languages
English (en)
French (fr)
Inventor
苏玉滨
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to JP2020527993A priority Critical patent/JP2021504795A/ja
Priority to US16/765,755 priority patent/US11861203B2/en
Priority to EP18880836.4A priority patent/EP3716577A4/en
Publication of WO2019100984A1 publication Critical patent/WO2019100984A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G06F3/0632—Configuration or reconfiguration of storage systems by initialisation or re-initialisation of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing

Definitions

  • the present application relates to the field of cloud computing, and in particular, to a cloud service migration method.
  • the application also relates to a cloud service migration device, and an electronic device.
  • the Elastic Compute Service is a basic cloud computing service. It can be used as easily and efficiently as water, electricity, gas, etc., and is widely used.
  • ECS Elastic Compute Service
  • cloud service providers gradually expand and build new data centers, the demand for geographic area selection is stronger when users use cloud services.
  • the user system architecture based on cloud deployment is also continuously evolving and scaled up, facing the re-adjustment of cloud service distribution.
  • the user's business scope is adjusted, it is also faced with the need to migrate cloud services to key areas to improve user experience.
  • cloud service providers have not provided or released a total solution for cloud service migration for these needs of cloud service migration.
  • Amazon Web Services a cloud computing service platform provided by Amazon, only provides the cloud service disk into Mirroring, mirroring copies to synchronize data. Since disk data size is generally 100 GB or even TB level, mirror copying takes a long time, resulting in long service interruption time.
  • mirror copying takes a long time, resulting in long service interruption time.
  • the overall migration of the cloud service is not implemented. The user needs to create an instance, deploy the application service, and configure the IP address of the cloud server. The migration process is cumbersome and complicated.
  • the present invention provides a cloud service migration method to solve the problem of long service interruption time and complicated operation in the prior art.
  • the application also relates to a cloud service migration device, and an electronic device.
  • the application provides a cloud service migration method, including:
  • the migration request includes an appointment migration time of the cloud service to migrate from the source cluster to the target cluster;
  • the data operation of the cloud service for the disk of the original instance is configured as a data operation for the disk of the new instance.
  • the configuring the resource component of the new instance and the new instance is implemented as follows:
  • the resource component includes the disk, and the resource component further includes at least one of the following: a CPU, a memory, an operating system, and a network.
  • the configuring, by using the new instance and the resource component of the new instance includes:
  • the cloud service is released from the network port of the source cluster, configured to a network port of the target cluster, and route updated.
  • the configuring, by using the new instance and the resource component of the new instance includes:
  • the disk data of the original instance of the cloud service to be migrated to the disk of the new instance of the cloud service created by the target cluster is implemented as follows:
  • the data block is provided with an identifier bit for marking whether the object is copied, and in the process of copying the disk data of the original instance to the disk of the new instance, the copied data and the The disk data of the original instance is compared, and the copy progress of the disk data of the original instance is obtained according to the comparison result.
  • the original instance and the new instance are respectively set with corresponding processing queues, and a data request that includes data operations of the cloud service for the disk of the original instance is added to a processing queue of the original instance.
  • a data request containing data operations of the cloud service for the disk of the new instance is added to the processing queue of the new instance.
  • the data operation of the cloud service for the disk of the original instance is configured to be performed after the data operation step of the disk of the new instance, and the disk of the cloud service is used for the new instance.
  • the data request of the data operation is added to the processing queue of the new instance, and the data request in the processing queue of the original instance that has not been processed is sent to the processing queue of the new instance for processing.
  • the migration priority of the disk data is determined as follows:
  • the migration is performed in descending order of migration priority.
  • Determining whether data involved in the data request exists in a disk of the new instance if yes, performing a data operation included in the data request based on the disk of the new instance; if not present, prioritizing the high migration
  • the level of data is migrated from the disk of the original instance to the disk of the new instance, and the data operations contained in the data request are performed based on the disk of the new instance after the migration is completed.
  • the source cluster and the target cluster are in different Availability Zones.
  • the cloud service refers to a cloud server for providing a cloud computing service
  • the source cluster refers to a cloud server cluster composed of at least one cloud server
  • the target cluster refers to at least one cloud server.
  • the application also provides a cloud service migration device, including:
  • a migration request obtaining unit configured to acquire a migration request for a cloud service in the source cluster; the migration request includes a scheduled migration time of the cloud service to migrate from the source cluster to the target cluster;
  • a disk migration unit configured to migrate disk data of an original instance of the cloud service to a disk of a new instance of the cloud service created by the target cluster according to the scheduled migration time; and the disk data is migrated according to the disk
  • the migration order of the data is migrated in order of priority;
  • a data operation configuration unit configured to configure a data operation of the cloud service for the disk of the original instance as a data operation for a disk of the new instance.
  • the application also provides an electronic device, including:
  • Memory Memory, and processor
  • the memory is for storing computer executable instructions for executing the computer executable instructions:
  • the migration request includes an appointment migration time of the cloud service to migrate from the source cluster to the target cluster;
  • the data operation of the cloud service for the disk of the original instance is configured as a data operation for the disk of the new instance.
  • the cloud service migration method provided by the present application includes: acquiring a migration request for a cloud service in a source cluster; the migration request includes an appointment migration time of the cloud service to migrate from the source cluster to a target cluster; The reservation migration time migrates the disk data of the original instance of the cloud service to the disk of the new instance of the cloud service created by the target cluster; the migration of the disk data is migrated according to the migration priority order of the disk data. Configuring the data service of the cloud service for the disk of the original instance as a data operation for the disk of the new instance.
  • the cloud service migration solution provided by the cloud service migration method in the process of migrating the cloud service from the source cluster to the target cluster, according to the subscription migration time specified by the user included in the migration request of the cloud service, according to the scheduled migration time
  • the disk service migrates the disk data of the cloud cluster to the target cluster, and changes the data operation of the cloud service to the disk in the source cluster to a data operation for a disk in the target cluster.
  • a new instance of the target cluster is provided to provide a service, so that the migration of the cloud service from the source cluster to the target cluster is implemented, and the implementation manner is relatively simple; and the service interruption time caused by the service interruption provided by the cloud service instance is reduced. To achieve more efficient and convenient.
  • FIG. 1 is a process flow diagram of an embodiment of a cloud service migration method provided by the present application.
  • FIG. 2 is a schematic diagram of a cloud server migration provided by the present application.
  • FIG. 3 is a schematic diagram of disk migration of a cloud server instance provided by the present application.
  • FIG. 4 is a schematic diagram of an embodiment of a cloud service migration apparatus provided by the present application.
  • FIG. 5 is a schematic diagram of an embodiment of an electronic device provided by the present application.
  • the application provides a cloud service migration method, and the application further provides a cloud service migration device, and an electronic device.
  • the following is a detailed description of the embodiments of the embodiments provided herein, and the various steps of the method are explained.
  • a cloud service migration method implementation provided by the present application is as follows:
  • FIG. 1 is a process flow diagram of an embodiment of a cloud service migration method provided by the present application.
  • FIG. 2 a schematic diagram of a cloud server migration provided by the present application is shown.
  • FIG. 3 A schematic diagram of disk migration of a cloud server instance provided by the present application is shown.
  • Step S101 Acquire a migration request for a cloud service in the source cluster.
  • the cloud service in the embodiment of the present application refers to an Elastic Compute Service (ECS) for providing a basic cloud computing service.
  • ECS Elastic Compute Service
  • the cloud server can be expanded and reduced, and the network bandwidth can be increased or decreased according to the actual service changes.
  • resources can be released.
  • the cloud server instance includes basic server resource components such as CPU, memory, operating system, disk, and bandwidth.
  • the cloud server instance is the operating entity provided by the cloud server to each user.
  • a cloud server instance is equivalent to A virtual machine allows users to mount disks, create snapshots, create mirrors, and deploy environments on the cloud server instance through the management rights of the cloud server instance.
  • one geographical area can be set with one or more available areas.
  • the available area refers to one or more data centers in which power, network and other infrastructures are isolated from each other in the same area. Fault isolation can be achieved between available areas. And the network delay of the cloud server instance in the same available area is smaller. Whether the cloud server instance is placed in the same available area depends on the requirements for disaster tolerance and network delay, if the requirements for disaster tolerance are high.
  • the cloud server instance can be deployed in different Availability Zones of the same geographical area; if the network latency requirement is high, the cloud server instance can be deployed in the same Availability Zone of the same geographical area.
  • the data center in the available area is generally a cloud server cluster composed of multiple cloud servers, and multiple cloud server clusters deployed in the same Availability Zone can be isolated from each other.
  • the cloud service migration method provided by the embodiment of the present application may be that the cloud server migrates across the available area in the same geographical area, and may also migrate the cloud server from the available area of one geographical area to another for different geographical areas.
  • the available area of the geographic area Specifically, between the two available areas, the cloud server in the cloud server cluster of one of the available areas is migrated to the cloud server cluster of another available area, that is, the cloud server is clustered from the source cloud server (source cluster) ) Migrate to the target cloud server cluster (target cluster).
  • the number of migrated cloud servers is not fixed, and the number of migrations may be determined according to actual service requirements.
  • This embodiment uses a migration of a single cloud server as an example.
  • the migration of multiple cloud servers refers to the migration process of a single cloud server.
  • a migration request for the cloud server in the source cloud server cluster is obtained, where the migration request includes an appointment migration time of the cloud server from the source cloud server cluster to the target cloud server cluster, that is, adopting
  • the reservation mode implements the migration of the cloud server, for example, setting a reservation migration time by using a timer.
  • the cloud server migrates from the source cloud server cluster to the target cloud server cluster.
  • the migration operation for the cloud server is reserved by the user, according to the user-specified
  • the reservation migration time of the migration is performed, and the reservation migration time is set by using a timer. If the timer is triggered, that is, the current timing of the timer reaches the reservation migration time, the migration operation of the cloud server is triggered and executed.
  • the subscription migration time may be modified due to actual service requirements, such as cloud service support provided by the cloud server instance.
  • the user service is busy and the subscription migration time needs to be postponed.
  • the subscription migration time can be modified to the user-specified time.
  • the original plan is to deploy the cloud server in a new Availability Zone. Now it is adjusted to deploy the cloud server in multiple new Availability Zones, and the migration task can also be modified.
  • the change of the target cloud server cluster corresponding to the migration task from one to multiple is equivalent to the migration task of migrating the cloud server to the cloud server cluster of the newly added zone.
  • Step S102 The disk data of the original instance of the cloud service is migrated to the disk of the new instance of the cloud service created by the target cluster according to the scheduled migration time.
  • the step S101 obtains a migration request for migrating the cloud server in the source cloud server cluster to the target cloud server cluster, and determines a migration time according to the scheduled migration time included in the migration request, and the step is performed according to the reservation.
  • the migration time migrates the disk data of the original instance of the cloud server in the source cloud server cluster to the disk of the new instance of the cloud server in the target cloud server cluster.
  • the following operations are performed:
  • the cloud server is configured from the source cloud server cluster to the target cloud server cluster.
  • an instance ie, a new instance
  • the cloud server is first created in the target cloud server cluster.
  • the purpose of the user is to migrate the cloud server from the source cloud server cluster to the target cloud server cluster at a specified scheduled migration time
  • the cloud server instance is a virtual computing environment, which includes basic server resource components such as CPU, memory, operating system, disk, and bandwidth.
  • the resources used by the cloud server are divided into three types: an instance, a network, and a storage (disk).
  • the migration process of the instance and the network is taken as an example, and the cloud is created for the target cloud server cluster.
  • the instance of the cloud server refers to a set of CPU and memory resource usage, and the configuration of the cloud server instance can be described in a configuration manner, for example, configured as ⁇ core: 2, memory: 2048 ⁇ , indicating that one CPU is 2 An instance of a 2GB core memory size.
  • the management of the cloud server is implemented by the cloud management system of the upper layer, and the migration management of the cloud server is a basic function of the cloud management system.
  • the instance migration of the cloud server refers to the cloud management system at the source.
  • the cloud server cluster releases the original instance of the cloud server, and sends a creation request in the same configuration to the target cloud server cluster according to the configuration information of the original instance of the cloud server, where the target cloud server cluster is configured according to the same configuration.
  • the new instance created in the above configuration is configured.
  • the migration of the instance of the cloud server is completed.
  • the user hopes that the cloud service can support a larger user service scale, that is, the new cloud server that provides the cloud service.
  • the configuration of the instance is stronger.
  • a configuration interface for configuring a new instance of the cloud server may be provided.
  • the configuration information of the new instance is configured to obtain the configuration information submitted by the user through the configuration interface, and then configure the new instance according to the obtained configuration information, so as to better meet the requirements of the user service.
  • the migration of the network is actually a process of the route advertisement, and the process of creating and releasing the network port of the cloud server is implemented by the cloud management system, specifically including creating a network port of the cloud server in the target cloud server cluster, and according to the cloud
  • the network configuration information delivered by the control system is released from the network port of the source cloud server cluster, configured on the network port created by the target cloud server cluster, and the route update and the arp announcement are completed, that is, broadcasted.
  • the method is to notify each port that the network port of the cloud server is changed from the source cloud server cluster to the target cloud server cluster.
  • the user can keep the IP address before and after the migration unchanged.
  • all the available areas of the IP address in the geographical area can be connected.
  • the user can also change the IP address, and only need to establish a new mapping relationship based on the changed IP address.
  • the quality of the access may be affected. Therefore, in order to ensure network quality, it is recommended that the IP address be migrated in the same geographical area to ensure efficient service access.
  • the foregoing operations configure the new instance and the resource component of the new instance.
  • the step shuts down the original instance of the cloud server, and starts a new instance of the cloud server based on the resource component.
  • a new instance of a cloud server has the conditions to provide external services.
  • the step is to move the disk data of the original instance of the cloud server in the source cloud server cluster to the disk of the new instance of the cloud server in the target cloud server cluster according to the scheduled migration time.
  • the following operations are performed: stopping the data operation (including read and write operations) of the disk of the original instance for the disk of the original instance; creating a disk of the new instance in the target cloud server cluster; And migrating the disk data of the original instance of the cloud server in the source cloud server cluster to the disk of the new instance of the cloud server in the target cloud server cluster.
  • the original instance and the new instance of the cloud server are respectively provided with corresponding processing queues, and data requests (including read and write requests) including data operations of the cloud server for the disks of the original instance are added to the The processing queue of the original instance, the read and write request including the data operation of the cloud server for the disk of the new instance is added to the processing queue of the new instance.
  • the cloud server reads data from the disk A and can write data to the disk A.
  • the disk A stops all the read and write operations, and
  • the processing queue of the original instance stops processing the read/write request, marks the disk A as the to-be-deleted state, and creates the disk B of the cloud server in the target cloud server cluster, and starts to provide read and write after the disk B is created.
  • the service, read and write requests containing read and write operations for disk B are added to the processing queue of the new instance, and the read and write operations of the new instance occur on disk B. It should be noted that, after the processing queue of the original instance stops processing the read/write request, the read/write request that is not processed in the processing queue of the original instance is sent to the processing queue of the new instance for processing.
  • the disk data of the original instance may be copied to the disk of the new instance by a background thread.
  • a migration priority may also be set for the disk data, and the The initial migration of the disk data of the original instance is a low migration priority. If the read and write operations of the new instance are performed during the migration process, it is determined whether the data involved in the data request exists in the disk of the new instance. If not present, setting a migration priority of data involved in the data request to a high migration priority; and, a disk of a new instance of the cloud service created by the disk data of the original instance to the target cluster During the migration process, migrations are performed in descending order of migration priority. As shown in FIG.
  • the disk A data is copied to the disk B through the background thread.
  • the data related to the read/write request including the read/write operation is determined to be in the disk. Whether it exists in B, if it exists, directly perform the read and write operations included in the read/write request in the disk B; if the data involved in the new instance does not exist in the disk B, that is, has not been copied to the disk B, then The migration priority of the data involved in the new instance is changed from a low migration priority to a high migration priority, and the high migration priority data (ie, the data involved in the new instance) is copied from disk A to disk B.
  • the read and write operations included in the read/write request are performed in the disk B.
  • This implementation is an important basis for asynchronous copying of data, that is, the service is not required to wait until the disk A data is completely copied to the disk B, thereby reducing the interruption time of the user service.
  • the copying of the disk A data to the disk B is performed by splitting the disk A data of the original instance into at least one data block, and copying the original instance to the disk B of the new instance by using a data block.
  • Disk A data can be copied to the disk B by using a mirroring method. For example, after the disk A data is split into at least one data block, the data mirror corresponding to the data block is created, and the data mirroring method is adopted. Copy disk A data to disk B.
  • an identifier for marking whether it is copied may also be set for the data block, if the data block is copied to disk B, the identification bit of the data block is marked as 1; if the data block is not copied, the data block is The flag is marked as 0.
  • the copied data and the disk A data can be compared based on the flag bits of the data block, and the copy progress of the disk A data is obtained according to the comparison result.
  • the comparison of the copy progress of the disk A data can be encapsulated into a migration progress query interface, and the user can obtain the real-time copy progress of the disk A data to the disk B copy through the migration progress query interface.
  • the size of the disk data is generally 100 GB or even TB.
  • the disk of the cloud server is mirrored for copying.
  • the copying of the data takes time in hours; and the implementation provided by the embodiment stops the service from the original instance, and resumes the service provided by the new instance after the new instance of the cloud service is started. In just 2-3 minutes, it can be seen that the implementation provided by this embodiment is more efficient than the business interruption time in the prior art.
  • Step S103 configuring the cloud service for the data operation of the disk of the original instance as a data operation for the disk of the new instance.
  • the original instance and the new instance of the cloud server are respectively provided with respective corresponding processing queues, and data requests (including read and write requests) including data operations of the disk for the original instance are added.
  • data requests including read and write requests
  • the processing queue of the original instance, the read and write request including the data operation of the cloud server for the disk of the new instance is added to the processing queue of the new instance.
  • the disk data of the original instance of the cloud server in the source cloud server cluster is migrated to the disk of the new instance of the cloud server in the target cloud server cluster according to the scheduled migration time.
  • the data operation of the cloud server for the disk of the original instance is configured as a data operation for the disk of the new instance, thereby migrating the cloud service provided by the cloud server from the source cloud server cluster to the target On a cloud server cluster.
  • the cloud server reads data from the disk A and can write data to the disk A.
  • the disk A stops all the read and write operations, and
  • the processing queue of the original instance stops processing the read/write request, marks the disk A as the to-be-deleted state, and creates the disk B of the cloud server in the target cloud server cluster, and starts to provide read and write after the disk B is created.
  • the service, read and write requests containing read and write operations for disk B are added to the processing queue of the new instance, and the read and write operations of the new instance occur on disk B. It should be noted that, after the processing queue of the original instance stops processing the read/write request, the read/write request that is not processed in the processing queue of the original instance is sent to the processing queue of the new instance for processing.
  • the cloud server may be migrated by using a “hot migration” manner, and the cloud server may be migrated from the source cloud server cluster to the target cloud server cluster.
  • the difference from the above implementation manner is that the new instance is created in the target cloud server cluster before stopping the read/write operation of the original instance's disk by the cloud server, that is, before stopping the service of the original instance.
  • the disk of the instance is configured correspondingly to the new instance and the disk of the instance, and the new instance is started after the configuration is completed; and after the new instance is started, the memory data of the original instance is copied to Storing the memory of the new instance, and further copying the running state data of the original instance running state to the new instance, until the running state data of the original instance running state is less than a preset threshold, stopping the cloud server for Read and write operations of the disk of the original instance, copying remaining operating state data to the new instance, and targeting the cloud server to the original Disk configuration data manipulation operation on data of the new instance of the disk, in order to achieve migration of the cloud server.
  • the cloud server is migrated in the implementation of the "hot migration".
  • the service interruption time is shorter, and the service interruption time is controlled in the millisecond or even microsecond level. The migration of the cloud server is more efficient.
  • the cloud service migration solution provided by the cloud service migration method in the process of migrating the cloud server from the source cloud server cluster to the target cloud server cluster, according to the migration request Relocating the cloud server from the source cloud server cluster to the target cloud server cluster according to the scheduled migration time, and targeting the cloud service to the disk in the source cloud server cluster
  • the data operation is changed to a data operation for a disk in the target cloud server cluster, and a service is provided by a new instance of the target cloud server cluster, thereby implementing the cloud server from the source cloud server cluster to the target cloud server
  • the migration of the cluster is simpler to implement.
  • the service interruption time caused by the service interruption provided by the cloud service instance is reduced, and the implementation is more efficient and convenient.
  • a cloud service migration device implementation provided by the present application is as follows:
  • a cloud service migration method is provided.
  • the present application further provides a cloud service migration device, which will be described below with reference to the accompanying drawings.
  • FIG. 4 a schematic diagram of an embodiment of a cloud service migration apparatus provided by the present application is shown.
  • the application provides a cloud service migration device, including:
  • a migration request obtaining unit 401 configured to acquire a migration request for a cloud service in the source cluster; the migration request includes a scheduled migration time of the cloud service to migrate from the source cluster to the target cluster;
  • the disk migration unit 402 is configured to migrate the disk data of the original instance of the cloud service to the disk of the new instance of the cloud service created by the target cluster according to the reserved migration time; the migration of the disk data according to the The migration order of the disk data is migrated in priority order;
  • the data operation configuration unit 403 is configured to configure the data operation of the cloud service for the disk of the original instance as a data operation for the disk of the new instance.
  • the cloud service migration device includes:
  • a configuration unit configured to configure the new instance and the resource component of the new instance
  • a new instance launch unit for shutting down the original instance of the source cluster and launching the new instance based on the resource component.
  • the configuration unit includes:
  • a first new instance configuration subunit configured to configure, according to the configuration information of the original instance, the new instance according to the same configuration of the configuration information in the target cluster
  • the second new instance configuration subunit is configured to configure the new instance according to the configuration information acquired by the preset configuration interface.
  • the resource component includes the disk, and the resource component further includes at least one of the following: a CPU, a memory, an operating system, and a network.
  • the configuration unit includes:
  • a network port creation subunit configured to create a network port in the target cluster
  • a network port creation subunit configured to release the cloud service from a network port of the source cluster, configure a network port to the target cluster, and perform routing update.
  • the configuration unit includes:
  • a data operation stop subunit configured to stop data operations of the cloud service for the disk of the original instance
  • a disk creation subunit for creating a disk of the new instance in the target cluster is a disk creation subunit for creating a disk of the new instance in the target cluster.
  • the data operation configuration unit 403 includes:
  • a first copy subunit configured to split the disk data of the original instance into at least one data block, and copy the disk data of the original instance to the disk of the new instance by using a data block;
  • a second copy subunit configured to split the disk data of the original instance into at least one data block, and create a data mirror corresponding to each of the data blocks, and copy the disk to the new instance by using data mirroring The disk data of the original instance.
  • the data block is provided with an identifier bit for marking whether the object is copied, and in the process of copying the disk data of the original instance to the disk of the new instance, the copied data and the The disk data of the original instance is compared, and the copy progress of the disk data of the original instance is obtained according to the comparison result.
  • the original instance and the new instance are respectively set with corresponding processing queues, and a data request that includes data operations of the cloud service for the disk of the original instance is added to a processing queue of the original instance.
  • a data request containing data operations of the cloud service for the disk of the new instance is added to the processing queue of the new instance.
  • a data request that includes a data operation of the cloud service for the disk of the new instance is added to a processing queue of the new instance, and a processing queue of the original instance is processed.
  • the data request that has not been processed is sent to the processing queue of the new instance for processing.
  • the migration priority of the disk data is determined as follows:
  • the migration is performed in descending order of migration priority.
  • the determining subunit is configured to determine whether data involved in the data request exists in a disk of the new instance, and if yes, perform a data operation included in the data request based on the disk of the new instance; Presence that the high migration priority data is preferentially migrated from the disk of the original instance to the disk of the new instance, and the data operation included in the data request is performed based on the disk of the new instance after the migration is completed.
  • the source cluster and the target cluster are in different Availability Zones.
  • the cloud service refers to a cloud server for providing a cloud computing service
  • the source cluster refers to a cloud server cluster composed of at least one cloud server
  • the target cluster refers to at least one cloud server.
  • An electronic device implementation provided by the present application is as follows:
  • a cloud service migration method is provided.
  • the present application further provides an electronic device for implementing the cloud service migration method, which will be described below with reference to the accompanying drawings.
  • FIG. 5 a schematic diagram of an electronic device provided by this embodiment is shown.
  • the application provides an electronic device, including:
  • the memory 501 is configured to store computer executable instructions, and the processor 502 is configured to execute the computer executable instructions:
  • the migration request includes an appointment migration time of the cloud service to migrate from the source cluster to the target cluster;
  • the data operation of the cloud service for the disk of the original instance is configured as a data operation for the disk of the new instance.
  • the processor 502 is further configured to execute the following computer before the data operation of the disk of the original instance is configured to be performed on a data operation instruction of the disk of the new instance. Execution instructions:
  • the configuring the resource component of the new instance and the new instance is implemented as follows:
  • the resource component includes the disk, and the resource component further includes at least one of the following: a CPU, a memory, an operating system, and a network.
  • the configuring, by using the new instance and the resource component of the new instance includes:
  • the cloud service is released from the network port of the source cluster, configured to a network port of the target cluster, and route updated.
  • the configuring, by using the new instance and the resource component of the new instance includes:
  • the disk data of the original instance of the cloud service to be migrated to the disk of the new instance of the cloud service created by the target cluster is implemented as follows:
  • the data block is provided with an identifier bit for marking whether the object is copied, and in the process of copying the disk data of the original instance to the disk of the new instance, the copied data and the The disk data of the original instance is compared, and the copy progress of the disk data of the original instance is obtained according to the comparison result.
  • the original instance and the new instance are respectively set with corresponding processing queues, and a data request that includes data operations of the cloud service for the disk of the original instance is added to a processing queue of the original instance.
  • a data request containing data operations of the cloud service for the disk of the new instance is added to the processing queue of the new instance.
  • the configuring, by the cloud service, the data operation of the disk of the original instance as the data operation instruction for the disk of the new instance, including the disk of the cloud service for the new instance The data request of the data operation is added to the processing queue of the new instance, and the data request in the processing queue of the original instance that has not been processed is sent to the processing queue of the new instance for processing.
  • the migration priority of the disk data is determined as follows:
  • the migration is performed in descending order of migration priority.
  • the high migration priority data is migrated from the disk of the original instance to the disk of the new instance, and after the migration is completed, the data operation included in the data request is performed based on the disk of the new instance. .
  • the source cluster and the target cluster are in different Availability Zones.
  • the cloud service refers to a cloud server for providing a cloud computing service
  • the source cluster refers to a cloud server cluster composed of at least one cloud server
  • the target cluster refers to at least one cloud server.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the 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 technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include non-transitory computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开了一种云服务迁移方法、装置以及电子设备，所述方法包括：获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。所述云服务迁移方法将所述云服务从所述源集群迁移至所述目标集群，实现方式较为简单；同时降低了由于云服务实例提供的服务中断导致的业务中断时间，实现更加高效便捷。

Description

云服务迁移方法、装置以及电子设备
本申请要求2017年11月24日递交的申请号为201711186691.9、发明名称为“云服务迁移方法、装置以及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算领域，具体涉及一种云服务迁移方法。本申请同时涉及一种云服务迁移装置，以及一种电子设备。
背景技术
随着云计算的不断普及和发展，利用云计算技术开发获得的云产品得到了重视，从而使云产品的类型越来越丰富，云服务器(Elastic Compute Service，ECS)作为一种基础云计算服务，能够像使用水、电、煤气等资源一样便捷、高效的使用，应用非常广泛。但随着云服务厂商逐步拓展和新建数据中心，用户使用云服务时对地理区域选择的需求更加强烈，同时，基于云部署的用户系统架构也在持续演进和规模扩大，面临重新调整云服务分布的需求；此外，随着用户业务范围的调整，还面临将云服务迁移至重点推进的地域以提高用户体验等需求。
目前，云服务厂商尚未针对这些对云服务进行迁移的需求提供或者发布云服务迁移的整体解决方案，如亚马逊公司提供的云计算服务平台AWS(Amazon Web Services)，仅仅提供将云服务磁盘制作成镜像，通过镜像拷贝来同步数据，由于磁盘数据大小普遍为百GB甚至是TB级别，镜像拷贝所需时间较长，从而导致业务中断时间较长；同时，除提供镜像拷贝来同步数据的实现方式之外，并未实现云服务的整体迁移，用户需自行创建实例、部署应用服务以及对云服务器IP地址进行配置等，迁移过程较为繁琐复杂。
发明内容
本申请提供一种云服务迁移方法，以解决现有技术存在的业务中断时间较长和操作繁琐复杂的问题。
本申请同时涉及一种云服务迁移装置，以及一种电子设备。
本申请提供一种云服务迁移方法，包括：
获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集 群向目标集群迁移的预约迁移时间；
按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
可选的，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤执行前，执行如下操作：
在所述目标集群创建所述新实例；
对所述新实例以及所述新实例的资源组件进行配置；
关闭所述源集群的所述原实例，并基于所述资源组件启动所述新实例。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，采用如下方式实现：
根据所述原实例的配置信息，在所述目标集群按照所述配置信息的相同配置对所述新实例进行配置；
和/或，根据预设配置接口获取到的配置信息对所述新实例进行配置。
可选的，所述资源组件包括所述磁盘，且所述资源组件还包括下述至少一项：CPU、内存、操作系统以及网络。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
在所述目标集群创建网络端口；
将所述云服务从所述源集群的网络端口释放，配置到所述目标集群的网络端口并进行路由更新。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
停止所述云服务针对所述原实例的磁盘的数据操作；
在所述目标集群创建所述新实例的磁盘；
并且，在所述新实例的磁盘创建完成后执行所述按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移步骤，以及所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤。
可选的，所将将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务 的新实例的磁盘迁移，采用如下方式实现：
将所述原实例的磁盘数据拆分为至少一个数据块，采用数据块的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据；
和/或，将所述原实例的磁盘数据拆分为至少一个数据块，并创建所述数据块各自对应的数据镜像，采用数据镜像的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据。
可选的，所述数据块设置有用于标记是否被拷贝的标识位，向所述新实例的磁盘拷贝所述原实例的磁盘数据的过程中，基于所述标识位对已拷贝数据和所述原实例的磁盘数据进行比对，根据比对结果获得所述原实例的磁盘数据的拷贝进度。
可选的，所述原实例和所述新实例分别设置有各自对应的处理队列，包含所述云服务针对所述原实例的磁盘的数据操作的数据请求被加入所述原实例的处理队列，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列。
可选的，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤执行后，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列，且所述原实例的处理队列中未完成处理的数据请求，被发送至所述新实例的处理队列中进行处理。
可选的，所述磁盘数据的迁移优先级，采用如下方式确定：
判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若不存在，将所述数据请求涉及的数据的迁移优先级设为高迁移优先级；
并且，在将所述原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移的过程中，按照迁移优先级从高到低的顺序进行迁移。
可选的，在处理所述新实例的处理队列中数据请求的过程中，执行如下操作：
判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若存在，则基于所述新实例的磁盘执行所述数据请求包含的数据操作；若不存在，将所述高迁移优先级的数据从所述原实例的磁盘向所述新实例的磁盘迁移，并在迁移完成后基于所述新实例的磁盘执行所述数据请求包含的数据操作。
可选的，所述源集群和所述目标集群处于不同可用区。
可选的，所述云服务是指用于提供云计算服务的云服务器，所述源集群是指由至少一台云服务器组成的云服务器集群，所述目标集群是指由至少一台云服务器组成的云服务器集群。
本申请还提供一种云服务迁移装置，包括：
迁移请求获取单元，用于获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
磁盘迁移单元，用于按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
数据操作配置单元，用于将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
本申请还提供一种电子设备，包括：
存储器，以及处理器；
所述存储器用于存储计算机可执行指令，所述处理器用于执行所述计算机可执行指令：
获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
本申请提供的所述云服务迁移方法，包括：获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
所述云服务迁移方法提供的云服务迁移方案，将云服务从源集群迁移至目标集群的过程中，根据云服务的迁移请求中包含的用户指定的预约迁移时间，按照所述预约迁移时间将所述云服务在所述源集群的磁盘数据迁移至所述目标集群，并将所述云服务针对所述源集群中磁盘的数据操作变更为针对所述目标集群中磁盘的数据操作，由所述目标集群的新实例来提供服务，从而实现所述云服务从所述源集群至所述目标集群的迁移， 实现方式较为简单；同时降低了由于云服务实例提供的服务中断导致的业务中断时间，实现更加高效便捷。
附图说明
图1是本申请提供的一种云服务迁移方法实施例的处理流程图；
图2是本申请提供的一种云服务器迁移的示意图；
图3是本申请提供的一种云服务器实例的磁盘迁移的示意图；
图4是本申请提供的一种云服务迁移装置实施例的示意图；
图5是本申请提供的一种电子设备实施例的示意图。
具体实施方式
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其他方式来实施，本领域技术人员可以在不违背本申请内涵的情况下做类似推广，因此本申请不受下面公开的具体实施的限制。
本申请提供一种云服务迁移方法，本申请还提供一种云服务迁移装置，以及一种电子设备。以下分别结合本申请提供的实施例的附图逐一进行详细说明，并且对方法的各个步骤进行说明。
本申请提供的一种云服务迁移方法实施例如下：
参照图1，其示出了本申请提供的一种云服务迁移方法实施例的处理流程图，参照图2，其示出了本申请提供的一种云服务器迁移的示意图，参照图3，其示出了本申请提供的一种云服务器实例的磁盘迁移的示意图。
步骤S101，获取针对源集群中云服务的迁移请求。
本申请实施例所述云服务，是指用于提供基础云计算服务的云服务器(Elastic Compute Service，ECS)，用户使用云服务器时无需提前采购硬件设备，而是根据业务需要创建所需数量的云服务器实例，用户在使用云服务器的过程中，可根据实际业务变化对云服务器进行磁盘扩缩容、增减网络带宽等，对于不再使用的云服务器，也可以释放资源。云服务器实例作为一个虚拟的计算环境，包含CPU、内存、操作系统、磁盘以及带宽等基础的服务器资源组件，云服务器实例是云服务器提供给每个用户的操作实体，一个云服务器实例就相当于一台虚拟机，用户可通过云服务器实例的管理权限，在云服务器实例上进行挂载磁盘、创建快照、创建镜像和部署环境等操作。
在实际当中，一个地理区域可设置一个或者多个可用区，可用区是指在同一区域内，电力、网络等基础设施相互隔离的一个或多个数据中心，可用区之间能做到故障隔离，并且同一可用区内云服务器实例的网络延时更小，是否将云服务器实例放在同一可用区内，取决于对容灾能力和网络延时的要求，如果对容灾能力的要求较高，可将云服务器实例部署在同一地理区域的不同可用区内；如果对网络延时的要求较高，则可将云服务器实例部署在同一地理区域的同一可用区内。可用区内的数据中心一般由多台云服务器组成的云服务器集群，同一可用区内部署的多个云服务器集群可以相互隔离。本申请实施例提供的所述云服务迁移方法，可以是在同一地理区域内进行的云服务器跨可用区迁移，也可以针对不同地理区域，将云服务器从一个地理区域的可用区迁移到另一地理区域的可用区。具体是在两个可用区之间，将其中一个可用区的云服务器集群中的云服务器，迁移到另一可用区的云服务器集群，即：将所述云服务器从源云服务器集群(源集群)迁移到目标云服务器集群(目标集群)。
将所述云服务器从所述源云服务器集群迁移到所述目标云服务器集群的过程中，被迁移的所述云服务器的数目并不是固定的，迁移数目可根据实际业务需求确定。本实施例以单独一个云服务器的迁移为例进行说明，多个云服务器的迁移参照单独一个云服务器的迁移过程。本步骤中，获取针对所述源云服务器集群中云服务器的迁移请求，所述迁移请求中包含所述云服务器从所述源云服务器集群向目标云服务器集群迁移的预约迁移时间，即：采用预约方式实现所述云服务器的迁移，比如通过定时器来设置预约迁移时间，若所述定时器被触发，即所述定时器当前计时到达所述预约迁移时间，则执行迁移操作，将所述云服务器从所述源云服务器集群向所述目标云服务器集群迁移。如图2所示，如果用户的目的是在指定时间将云服务器从所述源云服务器集群迁移到所述目标云服务器集群，则由用户预约针对所述云服务器的迁移操作，根据用户指定的进行迁移的预约迁移时间，通过定时器来设置预约迁移时间，若所述定时器被触发，即所述定时器当前计时到达所述预约迁移时间，则触发并执行所述云服务器的迁移操作。
在实际当中，在预约针对所述云服务器的迁移操作之后，用户指定的所述预约迁移时间被确定之后，可能会由于实际业务需要对预约迁移时间进行修改，比如云服务器实例所提供云服务支撑的用户业务较为繁忙，需要将预约迁移时间延后，针对这种情况，可将预约迁移时间修改为用户指定的时间。类似的，如果云服务器实例所提供云服务支撑的用户业务推广超出预期，原计划在一个新可用区部署云服务器，现调整为在多个新可用区部署云服务器，同样可对迁移任务进行修改，将迁移任务对应的目标云服务器集 群从一个变更为多个，相当于增加了将云服务器迁移至新增可用区的云服务器集群的迁移任务。
步骤S102，按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移。
上述步骤S101获取到将所述源云服务器集群中的云服务器向所述目标云服务器集群迁移的迁移请求，并根据所述迁移请求中包含的预约迁移时间确定迁移时间，本步骤按照所述预约迁移时间将所述源云服务器集群中云服务器的原实例的磁盘数据向目标云服务器集群中云服务器的新实例的磁盘迁移。本申请实施例提供的一种优选实施方式中，在将所述源云服务器集群中云服务器的原实例的磁盘数据向目标云服务器集群中云服务器的新实例的磁盘迁移之前，执行如下操作：
1)在所述目标云服务器集群创建所述云服务器的新实例；
上述步骤S101获取到将所述源云服务器集群中的云服务器向所述目标云服务器集群迁移的迁移请求之后，具体在将所述云服务器从所述源云服务器集群向所述目标云服务器集群迁移的过程中，针对被迁移的所述云服务器，首先在所述目标云服务器集群创建所述云服务器的实例(即新实例)。如图2所示，如果用户的目的是在指定的预约迁移时间将云服务器从所述源云服务器集群迁移到所述目标云服务器集群，则在获取到针对所述云服务器的迁移请求之后，根据所述迁移请求中包含的所述预约迁移时间执行所述云服务器的迁移操作，此处，在所述目标云服务器集群创建所述云服务器的新实例。
2)对所述新实例以及所述新实例的资源组件进行配置；
如上所述，所述云服务器实例是一个虚拟的计算环境，包含了CPU、内存、操作系统、磁盘以及带宽等基础的服务器资源组件。本实施例中，将所述云服务器使用的资源分为实例、网络和存储(磁盘)这三类，以实例和网络二者的迁移过程为例，对所述目标云服务器集群创建所述云服务器的新实例的配置过程，以及对所述新实例的资源组件进行配置过程进行说明。
a、所述云服务器的新实例；
所述云服务器的实例是指CPU和内存资源使用的集合，可通过配置的方式来描述所述云服务器的实例的配置，比如配置为{core：2，memory：2048}，表示一个CPU为2核内存大小为2GB的实例。所述云服务器的管理通过上层的云管控系统实现，对所述云服务器的迁移管理作为云管控系统的一项基本功能，所述云服务器的实例迁移，即是指云管控系统在所述源云服务器集群释放所述云服务器的原实例，并按照所述云服务器 的原实例的配置信息在所述目标云服务器集群以相同配置下发创建请求，在所述目标云服务器集群按照相同配置对上述创建的所述新实例进行配置，配置完成后即完成所述云服务器的实例的迁移。
此外，在实际应用中，随着云服务器实例所提供云服务支撑的用户业务的规模不断增大，用户希望云服务能够支撑更大的用户业务规模，即提供云服务的所述云服务器的新实例的配置更强，面对这种所述云服务器的新实例与原实例的配置不一致的情形，可提供用于配置所述云服务器的新实例的配置接口，用户通过所述配置接口提交针对所述新实例的自定义配置信息，通过所述配置接口获得用户提交的配置信息后，按照获取到的所述配置信息对所述新实例进行配置，从而更好的满足用户业务的需求。
b、所述云服务器的网络。
网络的迁移实际是一次路由宣告的过程，通过云管控系统实现所述云服务器的网络端口的创建和释放过程，具体包括在所述目标云服务器集群创建所述云服务器的网络端口，并根据云管控系统下发的网络配置信息，将所述云服务从所述源云服务器集群的网络端口释放，配置到所述目标云服务器集群创建的网络端口上，完成路由更新和arp宣告，即通过广播的方式通知各端口所述云服务器的网络端口从所述源云服务器集群变更至所述目标云服务器集群。
在网络迁移过程中，用户可保持迁移前后的IP地址不变，在使用专有网络的地理区域内，IP地址在该地理区域内的所有可用区均可联通。当然，用户还可以变更IP地址，只需基于变更后的IP地址建立新的映射关系即可。但如果IP地址的访问跨地理区域，访问质量可能会受到影响，因此，为了确保网络质量，建议IP地址的迁移在同一地理区域内，确保业务访问的高效。
3)关闭所述源云服务器集群的所述原实例，并基于所述资源组件启动所述目标云服务器集群中创建的所述新实例。
上述操作对所述新实例以及所述新实例的资源组件进行配置，配置完成之后，本步骤关闭所述云服务器的原实例，并基于所述资源组件启动所述云服务器的新实例，所述云服务器的新实例具备对外提供服务的条件。
本申请实施例提供的一种优选实施方式中，本步骤按照所述预约迁移时间将所述源云服务器集群中云服务器的原实例的磁盘数据向目标云服务器集群中云服务器的新实例的磁盘迁移之前，执行如下操作：停止所述云服务器针对所述原实例的磁盘的数据操作(包括读写操作)；在所述目标云服务器集群创建所述新实例的磁盘；本步骤在此基 础上，将所述源云服务器集群中云服务器的原实例的磁盘数据向目标云服务器集群中云服务器的新实例的磁盘迁移。具体的，所述云服务器的原实例和新实例分别设置有各自对应的处理队列，包含所述云服务器针对所述原实例的磁盘的数据操作的数据请求(包括读写请求)被加入所述原实例的处理队列，包含所述云服务器针对所述新实例的磁盘的数据操作的读写请求被加入所述新实例的处理队列。
如图3所示，所述云服务器从磁盘A中读取数据，并能向磁盘A中写入数据，当上层下发针对磁盘A的迁移指令之后，磁盘A停止所有的读写操作，并且所述原实例的处理队列停止处理其中读写请求，将磁盘A标记为待删除状态，以及在所诉目标云服务器集群创建所述云服务器的磁盘B，完成磁盘B的创建后开始提供读写服务，包含有针对磁盘B的读写操作的读写请求被加入所述新实例的处理队列，所述新实例的读写操作都发生在磁盘B上。需要说明的是，所述原实例的处理队列停止处理其中读写请求之后，所述原实例的处理队列中未完成处理的读写请求，被发送至所述新实例的处理队列中进行处理。
在具体实施时，还可以通过后台线程将所述原实例的磁盘数据向所述新实例的磁盘拷贝，优选的，在迁移过程中，还可以针对所述磁盘数据设置迁移优先级，并且所述原实例的磁盘数据初始的迁移均为低迁移优先级，如果在迁移过程中执行所述新实例的读写操作时，判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若不存在，将所述数据请求涉及的数据的迁移优先级设为高迁移优先级；并且，在将所述原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移的过程中，按照迁移优先级从高到低的顺序进行迁移。如图3所示，通过后台线程将磁盘A数据向磁盘B拷贝，在拷贝过程中，执行所述新实例的读写操作时，判断包含所述读写操作的读写请求涉及的数据在磁盘B中是否存在，如果存在，则直接在磁盘B中执行所述读写请求包含的读写操作；如果所述新实例涉及的数据在磁盘B中不存在，即尚未拷贝到磁盘B，则将所述新实例涉及的数据的迁移优先级从低迁移优先级变更为高迁移优先级，并将所述高迁移优先级的数据(即所述新实例涉及的数据)从磁盘A拷贝到磁盘B，拷贝完成后在磁盘B中执行所述读写请求包含的读写操作。这一实现方式是数据异步拷贝的重要基础，即无需等待此磁盘A数据完全拷贝到磁盘B后才提供服务，从而减少了用户业务的中断时间。
优选的，上述将磁盘A数据向磁盘B拷贝，是通过将所述原实例的磁盘A数据拆分为至少一个数据块，采用数据块的方式向所述新实例的磁盘B拷贝所述原实例的磁盘A 数据。除此之外，还可以采用镜像的方式将磁盘A数据向磁盘B拷贝，比如将磁盘A数据拆分为至少一个数据块之后，创建所述数据块各自对应的数据镜像，采用数据镜像的方式向磁盘B拷贝磁盘A数据。
此外，还可以针对所述数据块设置用于标记其是否被拷贝的标识位，如果数据块被拷贝至磁盘B，数据块的标识位被标记为1；如果数据块未被拷贝，数据块的标识位被标记为0。基于此，在将磁盘A数据向磁盘B拷贝的过程中，可基于数据块的标志位对已拷贝数据和磁盘A数据进行比对，根据比对结果获得磁盘A数据的拷贝进度。在实际应用中，可将磁盘A数据的拷贝进度的比对封装为迁移进度查询接口，用户通过迁移进度查询接口可获得磁盘A数据向磁盘B拷贝的实时拷贝进度。
一般而言，磁盘数据的大小一般为百GB甚至TB级别的大小，按照1小时100G左右的磁盘数据拷贝速度，采用现有技术提供的实现方式，将云服务器的磁盘制作成镜像进行拷贝，磁盘数据的拷贝需要花费以小时为单位的时间；而本实施例提供的实现方案，从所述原实例停止提供服务，至所述云服务的新实例启动之后恢复对外提供的服务，业务中断的时间仅仅需要2-3分钟，可见，相比现有技术动辄以小时计的业务中断时间，本实施例提供的实现方案更加高效。
步骤S103，将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
如上所述，所述云服务器的原实例和新实例分别设置有各自对应的处理队列，包含所述云服务器针对所述原实例的磁盘的数据操作的数据请求(包括读写请求)被加入所述原实例的处理队列，包含所述云服务器针对所述新实例的磁盘的数据操作的读写请求被加入所述新实例的处理队列。
上述步骤S102按照所述预约迁移时间将所述源云服务器集群中云服务器的原实例的磁盘数据向目标云服务器集群中云服务器的新实例的磁盘迁移，在此基础上，本步骤中，将所述云服务器针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作，从而将所述云服务器对外提供的云服务从所述源云服务器集群迁移到所述目标云服务器集群上。
如图3所示，所述云服务器从磁盘A中读取数据，并能向磁盘A中写入数据，当上层下发针对磁盘A的迁移指令之后，磁盘A停止所有的读写操作，并且所述原实例的处理队列停止处理其中读写请求，将磁盘A标记为待删除状态，以及在所诉目标云服务器集群创建所述云服务器的磁盘B，完成磁盘B的创建后开始提供读写服务，包含有针对 磁盘B的读写操作的读写请求被加入所述新实例的处理队列，所述新实例的读写操作都发生在磁盘B上。需要说明的是，所述原实例的处理队列停止处理其中读写请求之后，所述原实例的处理队列中未完成处理的读写请求，被发送至所述新实例的处理队列中进行处理。
除本实施例提供的上述实现方式之外，还可以采用“热迁移”的方式对所述云服务器进行迁移，将所述云服务器从所述源云服务器集群迁移至所述目标云服务器集群，与上述实现方式的区别在于：在停止所述云服务器针对所述原实例的磁盘的读写操作之前，即停止所述原实例的服务之前，在所述目标云服务器集群创建所述新实例以及所述实例的磁盘，并对所述新实例以及所述实例的磁盘进行相应配置，配置完成后启动所述新实例；以及，所述新实例启动后，将所述原实例的内存数据拷贝至所述新实例的内存，并进一步将所述原实例运行态的运行态数据拷贝至所述新实例，直至所述原实例运行态的运行态数据小于预设阈值，则停止所述云服务器针对所述原实例的磁盘的读写操作，将剩余运行态数据拷贝至所述新实例，并将所述云服务器针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作，从而实现所述云服务器的迁移。采用这种“热迁移”的实现方式对所述云服务器进行迁移，业务中断时间更短，业务中断时间控制在毫秒甚至是微秒级别，对所述云服务器的迁移更加高效。
综上所述，所述云服务迁移方法提供的云服务迁移方案，将所述云服务器从所述源云服务器集群迁移至所述目标云服务器集群的过程中，根据所述迁移请求中包含的用户指定的预约迁移时间，按照所述预约迁移时间将所述云服务器从所述源云服务器集群迁移至所述目标云服务器集群，并将所述云服务针对所述源云服务器集群中磁盘的数据操作变更为针对所述目标云服务器集群中磁盘的数据操作，由所述目标云服务器集群的新实例来提供服务，从而实现所述云服务器从所述源云服务器集群至所述目标云服务器集群的迁移，实现方式较为简单；同时降低了由于云服务实例提供的服务中断导致的业务中断时间，实现更加高效便捷。
本申请提供的一种云服务迁移装置实施例如下：
在上述的实施例中，提供了一种云服务迁移方法，与之相对应的，本申请还提供了一种云服务迁移装置，下面结合附图进行说明。
参照图4，其示出了本申请提供的一种云服务迁移装置实施例的示意图。
由于装置实施例基本相似于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本申请提供一种云服务迁移装置，包括：
迁移请求获取单元401，用于获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
磁盘迁移单元402，用于按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
数据操作配置单元403，用于将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
可选的，所述云服务迁移装置，包括：
新实例创建，用于在所述目标集群创建所述新实例；
配置单元，用于对所述新实例以及所述新实例的资源组件进行配置；
新实例启动单元，用于关闭所述源集群的所述原实例，并基于所述资源组件启动所述新实例。
可选的，所述配置单元，包括：
第一新实例配置子单元，用于根据所述原实例的配置信息，在所述目标集群按照所述配置信息的相同配置对所述新实例进行配置；
第二新实例配置子单元，用于根据预设配置接口获取到的配置信息对所述新实例进行配置。
可选的，所述资源组件包括所述磁盘，且所述资源组件还包括下述至少一项：CPU、内存、操作系统以及网络。
可选的，所述配置单元，包括：
网络端口创建子单元，用于在所述目标集群创建网络端口；
网络端口创建子单元，用于将所述云服务从所述源集群的网络端口释放，配置到所述目标集群的网络端口并进行路由更新。
可选的，所述配置单元，包括：
数据操作停止子单元，用于停止所述云服务针对所述原实例的磁盘的数据操作；
磁盘创建子单元，用于在所述目标集群创建所述新实例的磁盘。
可选的，所述数据操作配置单元403，包括：
第一拷贝子单元，用于将所述原实例的磁盘数据拆分为至少一个数据块，采用数据块的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据；
第二拷贝子单元，用于将所述原实例的磁盘数据拆分为至少一个数据块，并创建所述数据块各自对应的数据镜像，采用数据镜像的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据。
可选的，所述数据块设置有用于标记是否被拷贝的标识位，向所述新实例的磁盘拷贝所述原实例的磁盘数据的过程中，基于所述标识位对已拷贝数据和所述原实例的磁盘数据进行比对，根据比对结果获得所述原实例的磁盘数据的拷贝进度。
可选的，所述原实例和所述新实例分别设置有各自对应的处理队列，包含所述云服务针对所述原实例的磁盘的数据操作的数据请求被加入所述原实例的处理队列，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列。
可选的，所述数据操作配置单元403运行后，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列，且所述原实例的处理队列中未完成处理的数据请求，被发送至所述新实例的处理队列中进行处理。
可选的，所述磁盘数据的迁移优先级，采用如下方式确定：
判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若不存在，将所述数据请求涉及的数据的迁移优先级设为高迁移优先级；
并且，在将所述原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移的过程中，按照迁移优先级从高到低的顺序进行迁移。
可选的，在处理所述新实例的处理队列中数据请求的过程中，运行判断子单元；
所述判断子单元，用于判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若存在，则基于所述新实例的磁盘执行所述数据请求包含的数据操作；若不存在，优先将所述高迁移优先级的数据从所述原实例的磁盘向所述新实例的磁盘迁移，并在迁移完成后基于所述新实例的磁盘执行所述数据请求包含的数据操作。
可选的，所述源集群和所述目标集群处于不同可用区。
可选的，所述云服务是指用于提供云计算服务的云服务器，所述源集群是指由至少一台云服务器组成的云服务器集群，所述目标集群是指由至少一台云服务器组成的云服务器集群。
本申请提供的一种电子设备实施例如下：
在上述的实施例中，提供了一种云服务迁移方法，此外，本申请还提供了一种用于实现所述云服务迁移方法的电子设备，下面结合附图进行说明。
参照图5，其示出了本实施例提供的一种电子设备的示意图。
本申请提供的所述电子设备实施例描述得比较简单，相关的部分请参见上述提供的所述云服务迁移方法实施例的对应说明即可。下述描述的实施例仅仅是示意性的。
本申请提供一种电子设备，包括：
存储器501，以及处理器502；
所述存储器501用于存储计算机可执行指令，所述处理器502用于执行所述计算机可执行指令：
获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
可选的，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作指令执行前，所述处理器502还用于执行下述计算机可执行指令：
在所述目标集群创建所述新实例；
对所述新实例以及所述新实例的资源组件进行配置；
关闭所述源集群的所述原实例，并基于所述资源组件启动所述新实例。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，采用如下方式实现：
根据所述原实例的配置信息，在所述目标集群按照所述配置信息的相同配置对所述新实例进行配置；
和/或，根据预设配置接口获取到的配置信息对所述新实例进行配置。
可选的，所述资源组件包括所述磁盘，且所述资源组件还包括下述至少一项：CPU、内存、操作系统以及网络。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
在所述目标集群创建网络端口；
将所述云服务从所述源集群的网络端口释放，配置到所述目标集群的网络端口并进行路由更新。
可选的，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
停止所述云服务针对所述原实例的磁盘的数据操作；
在所述目标集群创建所述新实例的磁盘；
并且，在所述新实例的磁盘创建完成后执行所述按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移指令，以及所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作指令。
可选的，所将将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移，采用如下方式实现：
将所述原实例的磁盘数据拆分为至少一个数据块，采用数据块的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据；
和/或，将所述原实例的磁盘数据拆分为至少一个数据块，并创建所述数据块各自对应的数据镜像，采用数据镜像的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据。
可选的，所述数据块设置有用于标记是否被拷贝的标识位，向所述新实例的磁盘拷贝所述原实例的磁盘数据的过程中，基于所述标识位对已拷贝数据和所述原实例的磁盘数据进行比对，根据比对结果获得所述原实例的磁盘数据的拷贝进度。
可选的，所述原实例和所述新实例分别设置有各自对应的处理队列，包含所述云服务针对所述原实例的磁盘的数据操作的数据请求被加入所述原实例的处理队列，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列。
可选的，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作指令执行后，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列，且所述原实例的处理队列中未完成处理的数据请求，被发送至所述新实例的处理队列中进行处理。
可选的，所述磁盘数据的迁移优先级，采用如下方式确定：
判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若不存在，将所述数据请求涉及的数据的迁移优先级设为高迁移优先级；
并且，在将所述原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移的过程中，按照迁移优先级从高到低的顺序进行迁移。
可选的，在处理所述新实例的处理队列中数据请求的过程中，执行如下操作：
判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若存在，则基于所 述新实例的磁盘执行所述数据请求包含的数据操作；
若不存在，将所述高迁移优先级的数据从所述原实例的磁盘向所述新实例的磁盘迁移，并在迁移完成后基于所述新实例的磁盘执行所述数据请求包含的数据操作。
可选的，所述源集群和所述目标集群处于不同可用区。
可选的，所述云服务是指用于提供云计算服务的云服务器，所述源集群是指由至少一台云服务器组成的云服务器集群，所述目标集群是指由至少一台云服务器组成的云服务器集群。
本申请虽然以较佳实施例公开如上，但其并不是用来限定本申请，任何本领域技术人员在不脱离本申请的精神和范围内，都可以做出可能的变动和修改，因此本申请的保护范围应当以本申请权利要求所界定的范围为准。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。

Claims (16)

  1. 一种云服务迁移方法，其特征在于，包括：
    获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
    按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；所述磁盘数据的迁移按照该磁盘数据的迁移优先级顺序进行迁移；
    将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
  2. 根据权利要求1所述的云服务迁移方法，其特征在于，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤执行前，执行如下操作：
    在所述目标集群创建所述新实例；
    对所述新实例以及所述新实例的资源组件进行配置；
    关闭所述源集群的所述原实例，并基于所述资源组件启动所述新实例。
  3. 根据权利要求2所述的云服务迁移方法，其特征在于，所述对所述新实例以及所述新实例的资源组件进行配置，采用如下方式实现：
    根据所述原实例的配置信息，在所述目标集群按照所述配置信息的相同配置对所述新实例进行配置；
    和/或，根据预设配置接口获取到的配置信息对所述新实例进行配置。
  4. 根据权利要求2所述的云服务迁移方法，其特征在于，所述资源组件包括所述磁盘，且所述资源组件还包括下述至少一项：
    CPU、内存、操作系统以及网络。
  5. 根据权利要求4所述的云服务迁移方法，其特征在于，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
    在所述目标集群创建网络端口；
    将所述云服务从所述源集群的网络端口释放，配置到所述目标集群的网络端口并进行路由更新。
  6. 根据权利要求4所述的云服务迁移方法，其特征在于，所述对所述新实例以及所述新实例的资源组件进行配置，包括：
    停止所述云服务针对所述原实例的磁盘的数据操作；
    在所述目标集群创建所述新实例的磁盘；
    并且，在所述新实例的磁盘创建完成后执行所述按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移步骤，以及所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤。
  7. 根据权利要求1所述的云服务迁移方法，其特征在于，所将将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移，采用如下方式实现：
    将所述原实例的磁盘数据拆分为至少一个数据块，采用数据块的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据；
    和/或，将所述原实例的磁盘数据拆分为至少一个数据块，并创建所述数据块各自对应的数据镜像，采用数据镜像的方式向所述新实例的磁盘拷贝所述原实例的磁盘数据。
  8. 根据权利要求7所述的云服务迁移方法，其特征在于，所述数据块设置有用于标记是否被拷贝的标识位，向所述新实例的磁盘拷贝所述原实例的磁盘数据的过程中，基于所述标识位对已拷贝数据和所述原实例的磁盘数据进行比对，根据比对结果获得所述原实例的磁盘数据的拷贝进度。
  9. 根据权利要求2所述的云服务迁移方法，其特征在于，所述原实例和所述新实例分别设置有各自对应的处理队列，包含所述云服务针对所述原实例的磁盘的数据操作的数据请求被加入所述原实例的处理队列，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列。
  10. 根据权利要求9所述的云服务迁移方法，其特征在于，所述将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作步骤执行后，包含所述云服务针对所述新实例的磁盘的数据操作的数据请求被加入所述新实例的处理队列，且所述原实例的处理队列中未完成处理的数据请求，被发送至所述新实例的处理队列中进行处理。
  11. 根据权利要求1所述的云服务迁移方法，其特征在于，所述磁盘数据的迁移优先级，采用如下方式确定：
    判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若不存在，将所述 数据请求涉及的数据的迁移优先级设为高迁移优先级；
    并且，在将所述原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移的过程中，按照迁移优先级从高到低的顺序进行迁移。
  12. 根据权利要求11所述的云服务迁移方法，其特征在于，在处理所述新实例的处理队列中数据请求的过程中，执行如下操作：
    判断所述数据请求涉及的数据在所述新实例的磁盘中是否存在，若存在，则基于所述新实例的磁盘执行所述数据请求包含的数据操作；
    若不存在，将所述高迁移优先级的数据从所述原实例的磁盘向所述新实例的磁盘迁移，并在迁移完成后基于所述新实例的磁盘执行所述数据请求包含的数据操作。
  13. 根据权利要求1至12任意一项所述的云服务迁移方法，其特征在于，所述源集群和所述目标集群处于不同可用区。
  14. 根据权利要求1至12任意一项所述的云服务迁移方法，其特征在于，所述云服务是指用于提供云计算服务的云服务器，所述源集群是指由至少一台云服务器组成的云服务器集群，所述目标集群是指由至少一台云服务器组成的云服务器集群。
  15. 一种云服务迁移装置，其特征在于，包括：
    迁移请求获取单元，用于获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
    磁盘迁移单元，用于按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；
    数据操作配置单元，用于将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的数据操作。
  16. 一种电子设备，其特征在于，包括：
    存储器，以及处理器；
    所述存储器用于存储计算机可执行指令，所述处理器用于执行所述计算机可执行指令：
    获取针对源集群中云服务的迁移请求；所述迁移请求中包含所述云服务从所述源集群向目标集群迁移的预约迁移时间；
    按照所述预约迁移时间将所述云服务的原实例的磁盘数据向所述目标集群创建的所述云服务的新实例的磁盘迁移；
    将所述云服务针对所述原实例的磁盘的数据操作配置为针对所述新实例的磁盘的 数据操作。
PCT/CN2018/115383 2017-11-24 2018-11-14 云服务迁移方法、装置以及电子设备 WO2019100984A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2020527993A JP2021504795A (ja) 2017-11-24 2018-11-14 クラウドサービス移行のための方法、装置、及び電子デバイス
US16/765,755 US11861203B2 (en) 2017-11-24 2018-11-14 Method, apparatus and electronic device for cloud service migration
EP18880836.4A EP3716577A4 (en) 2017-11-24 2018-11-14 CLOUD SERVICE MIGRATION METHOD AND DEVICE AND ELECTRONIC DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711186691.9A CN109842636A (zh) 2017-11-24 2017-11-24 云服务迁移方法、装置以及电子设备
CN201711186691.9 2017-11-24

Publications (1)

Publication Number Publication Date
WO2019100984A1 true WO2019100984A1 (zh) 2019-05-31

Family

ID=66630886

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115383 WO2019100984A1 (zh) 2017-11-24 2018-11-14 云服务迁移方法、装置以及电子设备

Country Status (5)

Country Link
US (1) US11861203B2 (zh)
EP (1) EP3716577A4 (zh)
JP (1) JP2021504795A (zh)
CN (1) CN109842636A (zh)
WO (1) WO2019100984A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021033852A (ja) * 2019-08-28 2021-03-01 富士ゼロックス株式会社 情報処理装置、情報処理システム、及び情報処理プログラム

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324184B (zh) * 2019-06-26 2021-06-25 深圳前海微众银行股份有限公司 服务扩容与迁移方法、装置、系统、设备及可读存储介质
US11748130B2 (en) * 2019-06-28 2023-09-05 Intel Corporation Virtualization and multi-tenancy support in graphics processors
CN110825494A (zh) * 2019-11-01 2020-02-21 北京京东尚科信息技术有限公司 物理机调度方法及装置、计算机可存储介质
CN111813760B (zh) * 2020-05-29 2024-03-26 阿里巴巴集团控股有限公司 数据迁移方法以及装置
CN112286904A (zh) * 2020-09-30 2021-01-29 北京大米科技有限公司 集群迁移方法、装置及存储介质
CN114442907A (zh) * 2020-11-04 2022-05-06 华为技术有限公司 数据迁移方法和装置、服务器、网络系统
CN112565431A (zh) * 2020-12-08 2021-03-26 西藏宁算科技集团有限公司 基于用户访问量的跨地域集群迁移方法、装置及电子设备
CN112698792B (zh) * 2021-01-14 2021-09-10 腾讯科技（深圳）有限公司 分布式存储系统的数据迁移方法、装置及电子设备
CN113093995B (zh) * 2021-04-12 2023-05-26 深圳软通动力信息技术有限公司 一种云盘数据的迁移方法和系统
CN113128909A (zh) * 2021-05-13 2021-07-16 瑞麟天下节能技术(北京)有限公司 一种基于电力资源的服务器管理方法
CN114615263A (zh) * 2022-02-10 2022-06-10 深圳市小满科技有限公司 集群在线迁移方法、装置、设备及存储介质
CN114338692B (zh) * 2022-02-17 2023-11-10 上海玄翎科技有限公司 一种基于分片集群扩容的数据平衡方法与设备
CN116319354B (zh) * 2023-01-30 2023-11-28 杭州优云科技有限公司 基于云实例迁移的网络拓扑更新方法
KR102543749B1 (ko) * 2023-02-17 2023-06-14 주식회사 헤카톤에이아이 데이터 레이크 이관을 위한 인공지능 기반 자동화 시스템
CN116582453B (zh) * 2023-07-06 2023-09-15 北京志凌海纳科技有限公司 一种多业务集群场景下的监控数据迁移方法和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090300719A1 (en) * 2008-05-29 2009-12-03 James Michael Ferris Systems and methods for management of secure data in cloud-based network
CN103297492A (zh) * 2012-02-07 2013-09-11 国际商业机器公司 用于在联网计算环境之间迁移数据的方法和系统
CN107018193A (zh) * 2017-04-01 2017-08-04 济南浪潮高新科技投资发展有限公司 一种基于共享存储的vtpm迁移系统及方法

Family Cites Families (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5680640A (en) * 1995-09-01 1997-10-21 Emc Corporation System for migrating data by selecting a first or second transfer means based on the status of a data element map initialized to a predetermined state
US20070234107A1 (en) * 2006-03-31 2007-10-04 International Business Machines Corporation Dynamic storage data protection
GB0606639D0 (en) * 2006-04-01 2006-05-10 Ibm Non-disruptive file system element reconfiguration on disk expansion
US8738872B2 (en) * 2009-04-03 2014-05-27 Peter Chi-Hsiung Liu Methods for migrating data in a server that remains substantially available for use during such migration
JP5284905B2 (ja) * 2009-08-12 2013-09-11 富士通株式会社 データ移行方法、及びプログラム
US8984269B2 (en) * 2011-02-28 2015-03-17 Red Hat, Inc. Migrating data among cloud-based storage networks via a data distribution service
JP5942511B2 (ja) * 2012-03-19 2016-06-29 富士通株式会社 バックアップ装置，バックアップ方法，およびバックアッププログラム
US9292330B2 (en) * 2012-11-29 2016-03-22 International Business Machines Corporation Replacing virtual machine disks
CN103139221B (zh) * 2013-03-07 2016-07-06 中国科学院软件研究所 一种可信虚拟平台及其构建方法、平台之间数据迁移方法
US20140280977A1 (en) 2013-03-15 2014-09-18 Servicemesh, Inc. Systems and methods for evaluating computing resources
JP6186787B2 (ja) * 2013-03-25 2017-08-30 富士通株式会社 データ転送装置、データ転送システム、データ転送方法及びプログラム
US9201606B1 (en) 2013-05-20 2015-12-01 Ca, Inc. System and method for automating data migrations between heterogeneous architectures
WO2014189481A1 (en) * 2013-05-20 2014-11-27 Empire Technology Development, Llc Object migration between cloud environments
CN103458050A (zh) * 2013-09-16 2013-12-18 浪潮电子信息产业股份有限公司 一种基于云计算的电子阅览室搭建方法
CN103581331B (zh) * 2013-11-13 2018-04-03 中国科学院计算技术研究所 虚拟机在线迁移方法与系统
CN103605561A (zh) * 2013-11-28 2014-02-26 中标软件有限公司 一种云计算集群系统及其在线迁移物理服务器的方法
CN105095317B (zh) * 2014-05-23 2018-09-21 中国银联股份有限公司 分布式数据库服务管理系统
US9542108B2 (en) * 2014-06-30 2017-01-10 Scale Computing, Inc. Efficient migration of virtual storage devices to a remote node using snapshots
CN104283951B (zh) * 2014-09-29 2018-03-27 华为技术有限公司 一种实例迁移的方法、装置及系统
CN105528368B (zh) * 2014-09-30 2019-03-12 北京金山云网络技术有限公司 一种数据库迁移方法及装置
US9672054B1 (en) * 2014-12-05 2017-06-06 Amazon Technologies, Inc. Managing virtual machine migration
JP6979264B2 (ja) * 2014-12-30 2021-12-08 エヌエイチエヌ コーポレーション クラウドサービス提供方法およびシステム
US9600320B2 (en) 2015-02-11 2017-03-21 International Business Machines Corporation Mitigation of virtual machine security breaches
US9575797B2 (en) 2015-03-20 2017-02-21 International Business Machines Corporation Virtual machine migration between hypervisor virtual machines and containers
CN104750541B (zh) * 2015-04-22 2018-01-16 成都睿峰科技有限公司 一种虚拟机迁移方法
CN106302623B (zh) 2015-06-12 2020-03-03 微软技术许可有限责任公司 承租人控制的云更新
US9612865B2 (en) 2015-06-15 2017-04-04 International Business Machines Corporation Managed services coordinator
US20170024260A1 (en) 2015-07-21 2017-01-26 Cisco Technology, Inc. Workload migration across cloud providers and data centers
US9600331B1 (en) 2015-08-24 2017-03-21 International Business Machines Corporation Virtual machine placement in a cloud computing environment based on factors including optimized processor-memory affinity
AU2016310529B2 (en) 2015-08-27 2020-12-17 Johnson Controls Tyco IP Holdings LLP Edge intelligence platform, and internet of things sensor streams system
US10514986B2 (en) 2015-09-30 2019-12-24 Commvault Systems, Inc. Dynamic triggering of block-level backups based on block change thresholds and corresponding file identities in a data storage management system
US9832277B2 (en) * 2015-11-13 2017-11-28 Western Digital Technologies, Inc. Systems and methods for adaptive partitioning in distributed cache memories
US20170235647A1 (en) 2016-02-12 2017-08-17 Commvault Systems, Inc. Data protection operations based on network path information
US10684924B2 (en) 2016-02-18 2020-06-16 Commvault Systems, Inc. Data restoration operations based on network path information
WO2017145272A1 (ja) * 2016-02-24 2017-08-31 株式会社日立製作所 データ移行方法及び計算機システム
US10592350B2 (en) 2016-03-09 2020-03-17 Commvault Systems, Inc. Virtual server cloud file system for virtual machine restore to cloud operations
CN105897866B (zh) * 2016-03-29 2019-03-29 新浪网技术(中国)有限公司 一种基于IaaS云平台的云主机迁移方法及装置
JP6819131B2 (ja) 2016-08-18 2021-01-27 富士通株式会社 情報処理装置、情報処理方法、情報処理プログラムおよび情報処理システム
US10587700B2 (en) 2016-09-16 2020-03-10 Oracle International Corporation Cloud operation reservation system
CN106790713B (zh) * 2017-03-08 2019-09-20 中国人民解放军国防科学技术大学 云计算环境下的跨数据中心虚拟机迁移方法
US10776329B2 (en) 2017-03-28 2020-09-15 Commvault Systems, Inc. Migration of a database management system to cloud storage

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090300719A1 (en) * 2008-05-29 2009-12-03 James Michael Ferris Systems and methods for management of secure data in cloud-based network
CN103297492A (zh) * 2012-02-07 2013-09-11 国际商业机器公司 用于在联网计算环境之间迁移数据的方法和系统
CN107018193A (zh) * 2017-04-01 2017-08-04 济南浪潮高新科技投资发展有限公司 一种基于共享存储的vtpm迁移系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3716577A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021033852A (ja) * 2019-08-28 2021-03-01 富士ゼロックス株式会社 情報処理装置、情報処理システム、及び情報処理プログラム
JP7375375B2 (ja) 2019-08-28 2023-11-08 富士フイルムビジネスイノベーション株式会社 情報処理装置、情報処理システム、及び情報処理プログラム

Also Published As

Publication number Publication date
US11861203B2 (en) 2024-01-02
EP3716577A4 (en) 2021-06-23
EP3716577A1 (en) 2020-09-30
JP2021504795A (ja) 2021-02-15
CN109842636A (zh) 2019-06-04
US20200293216A1 (en) 2020-09-17

Similar Documents

Publication Publication Date Title
WO2019100984A1 (zh) 云服务迁移方法、装置以及电子设备
US11553034B2 (en) Server computer management system for supporting highly available virtual desktops of multiple different tenants
US10379893B2 (en) Container synchronization
EP2965200B1 (en) Method and system for providing a roaming remote desktop
WO2018077079A1 (zh) 一种应用的扩容方法、装置和系统
US10013189B1 (en) Storage volume backup management for multi-tenant environments
JP6450756B2 (ja) パーティションベースのデータストリーム処理フレームワーク
US8756599B2 (en) Task prioritization management in a virtualized environment
US8473692B2 (en) Operating system image management
WO2017012381A1 (zh) 一种生命周期管理方法及装置
JP2016540298A (ja) 大規模データストリームの取得、記憶、及び消費のための管理型サービス
US20170220661A1 (en) On-demand subscribed content library
US20200026786A1 (en) Management and synchronization of batch workloads with active/active sites using proxy replication engines
WO2015176636A1 (zh) 分布式数据库服务管理系统
WO2016165472A1 (zh) 一种创建虚拟机的方法和装置
JP6123626B2 (ja) 処理再開方法、処理再開プログラムおよび情報処理システム
JPWO2019100984A5 (zh)
WO2017041650A1 (zh) 用于扩展分布式一致性服务的方法和设备
US20150154048A1 (en) Managing workload to provide more uniform wear among components within a computer cluster
CN111465920B (zh) 远程复制操作期间通过总线接口被写入存储控制器的数据的管理
JP2015108899A (ja) 制御プログラム、制御装置及び制御方法
US10417254B2 (en) Intelligent content synchronization between content libraries
US11726885B2 (en) Efficient method and system of intelligent deploying file level restore agent in multicloud
US11704334B2 (en) System and method for hyperconvergence at the datacenter
US20230221977A1 (en) Efficient mass virtual machine (vm) cloning

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18880836

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020527993

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018880836

Country of ref document: EP

Effective date: 20200624