Device migration method and system, device, computer program product, and storage medium

Abstract

Embodiments of the present disclosure provide a device migration method and system, a device, a computer program product, and a storage medium. The method comprises: objectively and quantitatively evaluating migration necessities of data processing sites, and determining, on the basis of the migration necessities, a target site requiring device migration, thereby implementing an objective data-driven decision-making mechanism; and when controlling physical devices within the target site to execute migration tasks, monitoring a migration progress, and on this basis, if it is determined, on the basis of the migration progress and a network topology corresponding to the target site, that a migration task associated with any physical device within the target site has been completed, triggering shutdown of the physical device.

Description

Device migration method, system, device, computer program product and storage medium Cross-reference to related applications

[0001] The present disclosure claims priority to Chinese Patent Application No. 202411112997.X, filed on August 13, 2024, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present disclosure relates to the technical field of cloud computing, and particularly relates to a device migration method, system, device, computer program product and storage medium. BACKGROUND

[0003] An Internet Data Center (IDC) is a globally coordinated network of specific devices used to deliver, accelerate, exhibit, compute, and store data information over the Internet infrastructure. Based on the IDC, cloud service providers can provide a variety of cloud services. Users can purchase the required cloud services as needed to meet their service needs, eliminating the need to build their own data centers, and thus effectively saving costs and improving efficiency.

[0004] With the continuous changes in cloud computing technology and user needs, IDC migration has become an important transaction in the life cycle management process of the IDC. Currently, the decision to migrate the IDC and the progress of the migration are usually made by relying on human experience. Due to the complex and staggered migration process within the IDC, this migration method relying on human experience often leads to unstable performance of the IDC. SUMMARY

[0005] Aspects of the present disclosure provide a device migration method, system, device, computer program product and storage medium to improve the performance stability of a data processing site during a device migration process.

[0006] The present disclosure provides a device migration method, comprising: determining a target site that needs to perform device migration according to a migration necessity degree evaluated for each data processing site, the data processing site being configured to provide a running environment for a physical device placed therein; monitoring a migration progress during a process of controlling a physical device in the target site to perform a migration task; and triggering the physical device to shut down if it is determined that a migration task associated with any physical device in the target site has been completed according to the migration progress and a network topology relationship corresponding to the target site.

[0007] Further, the process of evaluating the migration necessity for any data processing site comprises: calculating an evaluation value for the data processing site under a plurality of preset migration evaluation dimensions; and performing weighted summation on the calculated evaluation values according to the weights configured for different migration evaluation dimensions to obtain the migration necessity corresponding to the data processing site.

[0008] Further, the target site requiring device migration is determined according to the migration necessities evaluated for each data processing site, comprising: determining a data processing site whose migration necessity meets a preset requirement as a candidate site; evaluating the migration difficulty of the candidate site from a preset difficulty evaluation dimension; and determining a candidate site whose migration difficulty is lower than a preset standard as the target site requiring device migration.

[0009] Further, after the target site is determined, the method further comprises: formulating a migration plan for the target site; and issuing a risk prompt if the migration progress is detected to not meet any time requirement in the migration plan.

[0010] The migration plan comprises at least one time requirement, such as the migration period of the target site, the migration schedule of each machine room in the target site, and the completion time limit of each level of migration task in each machine room in the target site.

[0011] Further, the physical devices in the target site include physical servers, and the control of the physical devices in the target site to perform migration tasks comprises: creating a service-level migration task for a cloud service if it is determined according to the migration progress that an instance-level migration task for the cloud service on any physical server in the target site has been completed; and triggering the physical server to perform the service-level migration task.

[0012] Further, the method further comprises: determining the migration start time node of each physical server according to the migration priority configured for each physical server in the target site; and controlling the physical server to start performing an instance-level migration task according to the migration start time node corresponding to the physical server.

[0013] Further, the physical devices in the target site include physical servers and network devices, and the method further comprises: determining that the migration task associated with a physical server has been completed if it is determined according to the migration progress that the migration task on the physical server in the target site has been completed; and determining that the migration task associated with a network device has been completed if it is determined according to the migration progress and the network topology relationship that the downstream device connected to the network device in the target site has been shut down, wherein the downstream device includes a physical server and / or other network devices.

[0014] Further, the physical device in the target site includes a physical server, and the method further comprises: if it is monitored that the migration progress of the target site has reached a target state, checking whether the physical servers that have not been shut down in the target site are distributed in multiple machine rooms; if yes, migrating the service instances to be migrated and / or the services to be migrated on the physical servers that have not been shut down to the physical servers in a target machine room in the target site; shutting down the machine rooms in the target site that have completed device migration; continuing to control the physical servers in the target machine room to perform the migration task; and if it is monitored according to the migration progress that there is no physical server that has not been shut down in the target machine room, shutting down the target machine room.

[0015] Further, the migrating the service instances to be migrated and / or the services to be migrated on the physical servers that have not been shut down to the physical servers in a target machine room in the target site comprises: migrating the service instances to be migrated and / or the services to be migrated on the physical servers that have not been shut down to the physical servers in a target machine room in the target site in a hot migration manner; and the target machine room is any machine room in the target site.

[0016] Further, the method further comprises: formulating a resource preparation scheme for the target site, the resource preparation scheme being used to guide a construction process of the target site; the target site is a destination of each migration task; and the resource preparation scheme comprises at least one of the following: site selection of the target site, a quantity of physical devices and resource amounts required by the target site, and a source mode of the physical devices in the target site, the source mode comprising at least one of the following: inventory devices, idle devices in other data processing sites, and newly purchased devices.

[0017] The embodiments of the present disclosure further provide a device migration system, comprising: an evaluation component configured to determine a target site that needs to perform device migration according to a migration necessity degree evaluated for each data processing site; a migration management component configured to monitor a migration progress in a process of controlling physical devices in the target site to perform a migration task; and a device management component configured to trigger a physical device to shut down if it is determined according to the migration progress and a network topology relationship corresponding to the target site that a migration task associated with the physical device in the target site has been completed.

[0018] The embodiments of the present disclosure further provide a computing device, comprising a memory, a processor and a communication component; the memory is configured to store one or more computer instructions; the processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions to perform the device migration method described above.

[0019] The embodiments of the present disclosure further provide a computer readable storage medium storing a computer program, which, when executed by one or more processors, causes the one or more processors to perform the device migration method.

[0020] The embodiments of the present disclosure further provide a computer program product comprising a computer program, which, when executed by one or more processors, causes the one or more processors to perform the device migration method.

[0021] In the embodiments of the present disclosure, a migration solution from migration evaluation to migration process management is proposed. The migration necessity of each data processing site is objectively quantitatively evaluated based on data, and the migration necessity is taken as an objective basis for deciding whether the data processing site needs to be migrated, so as to realize an objective mechanism of data-driven decision making. It is further proposed to manage the migration tasks in the target site, which can effectively guarantee the controllability of the migration process. Moreover, the migration progress can be monitored in the process of executing the migration tasks by the physical devices in the target site, and on this basis, if it is determined according to the migration progress and the network topology relationship corresponding to the target site that the migration task associated with any physical device in the target site has been completed, the physical device can be triggered to shut down. In this way, based on the monitored migration progress and the network topology relationship corresponding to the data processing site, the shutdown time of each physical device in the data processing site can be reasonably managed and controlled, so that the performance stability of the data processing site in the migration process can be effectively improved. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are included to provide a further understanding of the present disclosure and constitute a part of the present disclosure, illustrate the exemplary embodiments of the present disclosure and serve to explain the present disclosure together with the descriptions. In the drawings:

[0023] FIG. 1 is a flowchart of a device migration method according to an exemplary embodiment of the present disclosure;

[0024] FIG. 2 is a logic diagram of a scheme for evaluating migration necessity according to an exemplary embodiment of the present disclosure;

[0025] FIG. 3 is a logic diagram of a scheme for evaluating migration difficulty according to an exemplary embodiment of the present disclosure;

[0026] FIG. 4 is a diagram of migration aspects involved in a device migration process according to an exemplary embodiment of the present disclosure;

[0027] FIG. 5 is a diagram of an exemplary network topology relationship according to an exemplary embodiment of the present disclosure;

[0028] Figure 6 is a logical schematic diagram of a fragmentation regularization mechanism provided by an exemplary embodiment of this disclosure;

[0029] Figure 7 is a schematic diagram of an exemplary migration link provided by an exemplary embodiment of this disclosure;

[0030] Figure 8 is a schematic diagram of the structure of a device migration system provided in another exemplary embodiment of the present disclosure;

[0031] Figure 9 is a functional logic diagram of a device migration system provided in another exemplary embodiment of this disclosure;

[0032] Figure 10 is a schematic diagram of the structure of a computing device provided in another exemplary embodiment of this disclosure. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this disclosure clearer, the technical solutions of this disclosure will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0034] Before proceeding with a detailed description of the technical solutions provided in the various embodiments of this disclosure, the following is a brief explanation of several technical concepts involved in this disclosure.

[0035] A data processing facility is a place that provides an operating environment for the physical equipment housed within it. An exemplary data processing facility can be an Internet Data Center (IDC), a globally collaborative network of specific devices used to transmit, accelerate, display, compute, and store data information over Internet infrastructure. The physical equipment within a data processing facility typically includes physical servers and various network devices. In addition to these physical devices, a data processing facility usually includes infrastructure such as power supply and distribution systems, cabling systems, air conditioning systems, server rack systems, and network systems. From a building perspective, a data processing facility may comprise one or more buildings, or a portion of a single building. The building may contain a server room, where racks can be installed, and physical servers and network equipment can be mounted on these racks.

[0036] Relocating a data processing site can be understood as shutting down the data processing site. Before shutting down, the data on the physical equipment in the data processing site needs to be migrated to the new data processing site, and the physical equipment in the data processing site also needs to be shut down (i.e., vacated).

[0037] Cloud service, which can be understood as a cloud product provided based on cloud computing technology. The cloud service is user-oriented and aims to meet the computing / storage needs of users in different scenarios.

[0038] The inventors found in the research process that the operation life of a data center is limited. With the passage of time, the basic equipment of the data center ages intensively, and the performance of various physical devices is increasingly insufficient. Therefore, it is necessary to reasonably migrate the data center. As introduced in the background, at present, the data center migration work mainly relies on manual experience. The staff in charge of the data center migration work usually decides the data center to be migrated according to personal experience, which leads to subjective decision results, and some data centers that should be migrated cannot be migrated in time. Moreover, the staff needs to promote the migration progress. However, the migration process of the data center is staggered and complicated, and the execution period is relatively long. This way of promoting by manual work may cause problems such as device failure or incomplete cloud service migration in the data center, affecting the stability of the data center.

[0039] Therefore, the embodiment proposes a device migration scheme to improve the performance stability of the data processing site in the migration process.

[0040] The device migration scheme proposed by the embodiment is a migration solution from migration evaluation to migration process control, which can guarantee the controllability, timeliness and rationality of each link on the device migration link, and can realize the standardization and systematization of the staggered and complicated migration process.

[0041] The technical solutions provided by the embodiments of the disclosure are described in detail below with reference to the accompanying drawings.

[0042] FIG. 1 is a flowchart of a device migration method provided by an example embodiment of the disclosure. The method can be executed by a device migration system, which can be implemented as software, hardware or a combination of software and hardware. The device migration system can be integrated in a computing device or a service cluster. Here, the deployment manner of the device migration system is not limited. Referring to FIG. 1, the method can include steps 100 to 102.

[0043] Step 100: Determine a target site that needs to perform device migration according to the migration necessity evaluated for each data processing site.

[0044] Step 101: Monitor the migration progress in the process of controlling the target site to perform the migration task.

[0045] Step 102: If it is determined that the migration task associated with any physical device in the target site has been completed according to the migration progress and the network topology relationship corresponding to the target site, trigger the physical device to shut down.

[0046] In this embodiment, the starting time of the device migration scheme is not limited. For example, the device migration scheme can be started periodically, such as once a month / once a week. For another example, the device migration scheme can be started manually, in which case, the user interface provided by the device migration system can include a starting control, and the staff can actively trigger the device migration scheme by clicking the starting control or the like. Of course, the user interface provided by the device migration system can also include more human-computer interaction content to support the staff to migrate the configuration more flexibly and more targeted. For example, the user interface can include a data processing site range configuration function to allow the staff to configure the data processing sites to be evaluated. Here, the human-computer interaction content in the user interface provided by the device migration system is not limited, and no more examples are given, and in actual application, the human-computer interaction content can be designed as needed.

[0047] The data processing site in this embodiment can be the data center mentioned above, and of course, can also be other types of data processing sites such as enterprise computer rooms, which are not limited here.

[0048] After the device migration scheme in this embodiment is started, a migration evaluation phase can be entered. The migration evaluation phase can be used to objectively decide the target site that needs to be migrated from multiple data processing sites.

[0049] Referring to FIG. 1, in step 100, the target site that needs to be migrated can be determined according to the migration necessity evaluated for each data processing site.

[0050] The migration necessity in this embodiment can be used to represent the necessary degree of migrating the device of the data processing site. The quantitative form of the migration necessity can be a score or the like, which is not limited here.

[0051] FIG. 2 is a logic diagram of a scheme for evaluating migration necessity according to an example embodiment of the present disclosure. Referring to FIG. 2, in this embodiment, a plurality of migration evaluation dimensions can be preset in the device migration system, based on which, a data processing site can be comprehensively evaluated from the plurality of migration evaluation dimensions to evaluate the migration necessity of the data processing site. Referring to FIG. 2, the migration evaluation dimensions in this embodiment can include, but are not limited to, a cost dimension, a benefit dimension, a stability cost dimension, and an uncontrollable factor dimension, etc. Among them, under the cost dimension, the data processing site can be evaluated according to the cost of the data processing site in terms of leasing, power, equipment idling, and operation and maintenance, etc. Under the benefit dimension, the data processing site can be evaluated according to the benefit of the data processing site in terms of revenue and market development, etc. Under the stability cost dimension, the data processing site can be evaluated according to the cost paid for ensuring that the new data processing site can meet the stability requirements of device failure rate and multi-availability zone disaster recovery after migration of the data processing site. Under the uncontrollable factor dimension, the data processing site can be evaluated according to factors such as hardware upgrade, facility upgrade, lease expiration, and failure to meet stability requirements, etc.

[0052] Referring to FIG. 2, in an actual application scheme, for any data processing site that needs to be evaluated: the evaluation value of the data processing site can be calculated under a plurality of migration evaluation dimensions; the evaluation values calculated for the data processing site are weighted and summed according to the weights configured for different migration evaluation dimensions to obtain the migration necessity corresponding to the data processing site. Among them, the weights of different migration evaluation dimensions can be configured as needed and can be flexibly adjusted, which are not limited here.

[0053] In the actual application scenario, for the aforementioned revenue dimension: the profit generated by the data processing site can be reduced by the compensation cost required for migrating the data processing site, and the evaluation value of the data processing site in the revenue dimension can be calculated according to the difference obtained, and generally, the difference is inversely proportional to the evaluation value in the revenue dimension. Of course, the capacity utilization rate of the data processing site can also be used to calculate the evaluation value of the data processing site in the revenue dimension, and generally, the capacity utilization rate is inversely proportional to the evaluation value in the revenue dimension. The capacity utilization rate can be understood as the proportion of the available capacity in the design capacity. Due to the consideration of disaster recovery and redundancy, the capacity utilization rate of the data processing site is generally not 100%, and the equipment failure rate in the data processing site and the cloud service sales situation will affect the capacity utilization rate. The power consumption cost of the data processing site is generated according to the design capacity, and the available capacity can be obtained by subtracting the loss capacity from the design capacity, and the profit is generated by the available capacity. Therefore, the higher the capacity utilization rate, the higher the revenue that the data processing site can generate, and the lower the evaluation value calculated in the revenue dimension. Here, the calculation method used to calculate the evaluation value in the revenue dimension is not limited, and any calculation method that can objectively represent the revenue of the data processing site can be used. For the aforementioned other migration evaluation dimensions, the reference data used to calculate the evaluation value can be set in the device migration system according to actual needs, which is not limited in this embodiment, and no more examples are given here.

[0054] Preferably, in the actual application scenario, the evaluation values calculated in different preset migration evaluation dimensions can be normalized before the aforementioned weighted summation operation is performed. For example, the normalization method can be to normalize the evaluation values calculated in different preset migration evaluation dimensions to a score in the 【0, 100】 interval, which is not limited here, and no more examples of normalization methods are given.

[0055] In this embodiment, the device migration system can collect the reference data required for calculating the evaluation value in each of the aforementioned migration evaluation dimensions. These reference data can come from manual input or other platform-provided data collection interfaces, etc., which are not limited here. In this way, in this embodiment, the migration necessity of each data processing site can be objectively quantitatively evaluated based on data, and the migration necessity can be used as an objective basis for deciding whether the data processing site needs to be migrated, realizing an objective mechanism of data-driven decision-making.

[0056] Further, in this embodiment, it is also proposed that migration difficulty can also be introduced as a supplementary factor to more reasonably decide the target site that needs to be migrated. Migration difficulty can be used to represent the feasibility of migrating the data processing site.

[0057] In this embodiment, the migration difficulty can be integrated into the migration decision-making process in various implementation manners. In an optional implementation manner, the data processing site whose migration necessity meets the preset requirement can be determined as a candidate site; the migration difficulty of the candidate site can be evaluated from the preset difficulty evaluation dimension; the candidate site whose migration difficulty is lower than the preset standard can be determined as the target site that needs to be migrated.

[0058] In this optional implementation manner, it is proposed that the first round of screening can be performed on each data processing site based on the migration necessity. In the first round of screening, according to the aforementioned preset requirement, each data processing site can be sorted in descending order of migration necessity; the first N data processing sites after sorting can be determined as candidate sites, and N is an integer and can be configured as needed. Alternatively, each data processing site can be sorted in descending order of migration necessity; the first m% data processing sites can be determined as candidate sites, and the m% value can be configured as needed. Alternatively, the data processing site whose migration necessity exceeds a specified threshold k can be determined as a candidate site, and the value of k can be configured as needed. In this case, the preset requirement in the first round of screening is not limited, and no more examples are given.

[0059] In this optional implementation manner, based on the result of the first round of screening, the second round of screening can be continued based on the migration difficulty. That is, from the candidate sites, the target site that needs to be migrated can be further screened out.

[0060] It can be understood that the above implementation manner is optional, and in this embodiment, other implementation manners can also be used to integrate the migration difficulty into the migration decision-making process. For example, the migration difficulty can be used as an evaluation value under a migration evaluation dimension, and the evaluation values calculated under other migration evaluation dimensions mentioned above are weighted and summed to obtain the migration necessity of the data processing site. In this implementation manner, the migration difficulty is used as a factor affecting the migration necessity to be integrated into the migration decision-making process. No more examples of implementation manners are given.

[0061] FIG. 3 is a logic diagram of a scheme for evaluating migration difficulty according to an example embodiment of the present disclosure. Referring to FIG. 3, in this embodiment, a plurality of difficulty evaluation dimensions can be preset in the device migration system, based on which, the data processing site can be evaluated from the plurality of difficulty evaluation dimensions to evaluate the migration difficulty of the data processing site. Referring to FIG. 3, the difficulty evaluation dimensions in this embodiment can include, but are not limited to, a migration capability dimension, a resource preparation difficulty dimension, and / or a stability maintenance difficulty dimension. In the migration capability dimension, the data processing site can be evaluated in terms of whether the data processing site is migratable, the migration mode that the data processing site can support when the data processing site is migratable, the migration tool that the data processing site needs to use when the data processing site is cold-migrated, the service reach requirement and service cooperation requirement that need to be met, and the like. Whether the data processing site is migratable can be determined according to whether the data processing site is a core network and whether the service instance in the data processing site is irreversible. The migration mode that the data processing site can support can include hot migration, cold migration, or cold-hot combined migration, and the like. It can be understood that, compared with non-migration, the data processing site being migratable will result in lower migration difficulty; in the case of being migratable, the higher the proportion of hot migration, the lower the migration difficulty. In the resource preparation difficulty dimension, the data processing site can be evaluated in terms of the resource requirement and the operation and maintenance cost that need to be paid when a new data processing site is built to replace the current data processing site. The resource requirement can include the quantity requirement and specification requirement of various physical devices such as infrastructure and servers, and the like. It can be understood that, the lower the resource requirement, the lower the migration difficulty; the lower the operation and maintenance cost, the lower the migration difficulty. In the stability maintenance difficulty dimension, the data processing site can be evaluated in terms of whether the new data processing site can meet the stability requirements such as multi-disaster tolerance and device failure rate required by the current data processing site when a new data processing site is built to replace the current data processing site, and the cost that needs to be paid in the case of meeting the stability requirements. It can be understood that, if the new data processing site cannot meet the stability requirements, the migration difficulty will be higher; the higher the cost that needs to be paid when meeting the stability requirements, the higher the migration difficulty.

[0062] The several preset difficulty evaluation dimensions provided above are only exemplary, and the present embodiment is not limited thereto, and no more examples are given herein. In this embodiment, the data processing site can be comprehensively evaluated from the plurality of difficulty evaluation dimensions to determine the migration difficulty of the data processing site. The comprehensive evaluation manner can also be, for example, the weighted summation mentioned above, and the like, which is not limited herein.

[0063] In this embodiment, the device migration system can collect reference data required when performing evaluation under each of the aforementioned preset difficulty evaluation dimensions. The reference data can be sourced from manual input or a data collection interface provided by another platform, without limitation. In this embodiment, migration difficulty can be introduced as a supplementary factor, and in combination with the migration necessity evaluated for each data processing site, the target site that needs to be migrated can be more reasonably and comprehensively determined.

[0064] In this embodiment, the determined target site can be one or more.

[0065] After determining the target site that needs to be migrated, the target site can be pushed to the migration stage.

[0066] FIG. 4 is a schematic diagram of a migration aspect involved in a device migration process according to an example embodiment of the present disclosure. The inventors have found in the research process that multiple migration aspects can be involved in the migration stage. Referring to FIG. 4, one migration aspect involved in the migration stage is migration of cloud services in the data processing site.

[0067] For this migration aspect, the device migration system can control the physical devices in the target site to perform migration tasks to achieve migration of cloud services, according to the present embodiment. The device migration system can monitor and control migration tasks in the target site to control the target site to perform migration tasks, according to the present embodiment.

[0068] According to the present embodiment, multiple levels of migration tasks can be set to achieve migration of cloud services. According to the present embodiment, at least instance-level migration tasks and service-level migration tasks can be set.

[0069] The instance-level migration task can be understood as a task for migrating service instances involved in cloud services. As mentioned in the background, users can purchase cloud services to meet their service needs, and users need to use service instances to use cloud services. A service instance can be understood as a service unit with specific configurations and running states created based on cloud service templates provided by a cloud service provider. Users can run their computing tasks or storage tasks in their service instances. Common service instances can include, but are not limited to, virtual machines (VMs), containers, or bare-metal servers. Service instances can be created by users themselves or created by cloud service providers for users.

[0070] In this embodiment, the instance-level migration task can be initiated by the user, and the device migration system is mainly responsible for monitoring and controlling the instance-level migration task. Of course, the instance-level migration task can also be initiated by the device migration system, without limitation.

[0071] The service-level migration task can be understood as a task for migrating the application of the cloud service itself. The cloud service itself has a plurality of applications. These applications can be used to control the generation, maintenance and death of service instances, and can also be used to regularly back up and quickly recover user data generated in the service instances, monitor performance indicators and resource usage of the cloud service, generate monitoring reports and analyze them, etc. In this embodiment, the applications of the cloud service itself are not further exemplified.

[0072] In this embodiment, the service-level migration task can be initiated by the device migration system, or the responsible party of the application can be notified by the device migration system to trigger the responsible party to initiate the corresponding service-level migration task. This is not limited.

[0073] Based on this, the embodiment proposes an exemplary scheme for controlling the physical devices in the target site to perform the migration task, which can be: if it is determined according to the migration progress that the instance-level migration task for any cloud service on any physical server in the target site has been completed, a service-level migration task for the cloud service is created; and the physical server is triggered to perform the service-level migration task.

[0074] The migration task in this embodiment is mainly performed by the physical server in the target site. It can be understood that a physical server can carry multiple cloud services, and for any cloud service, the physical server can carry multiple service instances corresponding to the cloud service, so for the cloud service, the physical server can need to carry multiple instance-level migration tasks. In this exemplary scheme, the device migration system can monitor the completion of the instance-level migration task on the physical server, and when it is monitored that the instance-level migration task corresponding to a cloud service on the physical server has been completed, it can be represented that the service instance corresponding to the cloud service has completed migration out. In this case, the device migration system in this embodiment can actively create a service-level migration task for the cloud service to trigger the migration of the application of the cloud service itself on the physical server. In this way, the device migration system can create the required service-level migration task for the physical server in a timely manner according to the completion of the instance-level migration task on the physical server, so as to control the physical server to continue migrating the application of the corresponding cloud service itself, and thus complete the migration of the cloud service. The number of service-level migration tasks created by the device migration system for the physical server can be determined according to actual needs, which is not limited herein.

[0075] In this exemplary scheme, it is also proposed that the device migration system can determine the migration start time node of each physical server according to the migration priority configured for each physical server in the target site; and for any physical server, the physical server is controlled to start performing the instance-level migration task according to the migration start time node corresponding to the physical server.

[0076] The migration priority can be used to determine the migration sequence between the physical servers, and the physical server with higher priority will start migration earlier. In actual application, the migration priority of each physical server in the target site can be determined according to parameters such as the migration mode supported by the physical server and / or the total quantity of physical servers in the computer room. For example, the physical server supporting hot migration can obtain a higher priority; the physical server in the computer room with a lower total quantity can obtain a higher migration priority, and the like. In this embodiment, the configuration strategy of the migration priority is not limited.

[0077] In this way, based on the migration priority, the migration start time of each physical server can be reasonably controlled, and then the start time of the instance-level migration task on each physical server can be controlled, so that the target site can be more finely and more reasonably controlled to perform the migration task.

[0078] On this basis, with reference to FIG. 1, in step 101, the device migration system can monitor the migration progress during the process in which the physical device in the target site performs the migration task. In this embodiment, the migration progress can be used to at least represent the completion of the migration task in the target site.

[0079] With reference to FIG. 4, the inventors have found in the research process that in the device migration stage, in addition to the migration of the cloud service as described above, another migration aspect is involved: the retirement of the physical device, or the shutdown of the physical device.

[0080] In this regard, with reference to FIG. 1, in step 102, it is proposed that if it is determined according to the migration progress and the network topology relationship corresponding to the target site that the migration task associated with any physical device in the target site has been completed, the physical device is triggered to be shut down.

[0081] In this embodiment, the network topology relationship corresponding to the target site is introduced as a basis for controlling the shutdown time of the physical device in the target site. The network topology relationship in this embodiment is used to describe the physical layout and communication relationship of the physical device in the target site.

[0082] In this embodiment, the physical device in the target site can include a physical server and various network devices, and the network device can include but is not limited to a router, a switch, a gateway, and the like, which are not exhaustively listed herein. The device migration system in this embodiment can construct the network topology relationship for the target site in advance according to the actual network architecture of the target site. If it is monitored that the network architecture of the target site changes, the device migration system can update the corresponding network topology relationship maintained by itself in a timely manner.

[0083] FIG. 5 is a schematic diagram of an exemplary network topology relationship according to an exemplary embodiment of the present disclosure. As shown in FIG. 5, according to the exemplary network topology relationship, a region is a geographical location where the target site is located. The region is intended to help users select the nearest data processing site according to its geographical location, thereby reducing network latency and improving access speed. The region can include one or more availability zones (AZs). The availability zone can be understood as a data processing site or a group of data processing sites with independent power and network. As shown in FIG. 5, the target site is located in an availability zone. As shown in FIG. 5, the target site can include one or more buildings, and the metropolitan area network core switch can be connected to the distribute layer switches (DSWs) in each building in the target site. Each building can include one or more machine rooms, and the distribute layer switches in the building can be connected to the polymerizes layer switches (PSWs) deployed in each machine room in the building. Each machine room can include a plurality of cabinets, and the polymerizes layer switches in the machine room can be connected to the access layer switches (ASWs) deployed in the plurality of cabinets in the machine room. Each cabinet can include a plurality of physical servers, and the access layer switches in the cabinet can be connected to each physical server in the cabinet.

[0084] The network topology relationship shown in FIG. 5 includes the physical layout of the target site (such as the layout relationship between the region, the availability zone, the building, the machine room, and the cabinet) and the communication relationship between the physical devices in the target site (such as the communication relationship between the layer switches and the physical servers). The inventors have found in the research process that the network architecture of the target site is usually complex, and by constructing the network topology relationship, the shutdown influence range of the physical devices in the target site can be detected. The inventors have also found that for a certain physical device, if part of the downstream devices connected to the physical device have not been shut down, the premature shutdown of the physical device will cause communication failure problems of the downstream devices.

[0085] Therefore, in addition to the network topology relationship introduced above, the migration progress monitored in step 101 is also used as a basis for controlling the shutdown time of the physical devices in the target site. On this basis, in step 102, the downstream devices connected to any physical device in the target site can be determined according to the network topology relationship, and the migration task carried by the physical device itself and the migration task carried by the downstream devices connected to the physical device are used as the migration task associated with the physical device. Whether the migration task associated with the physical device is completed can be determined by the migration progress. If it is determined that the migration task associated with the physical device is completed, the physical device can be triggered to shut down.

[0086] For example, referring to FIG. 5, for any aggregation layer switch, the downstream devices connected thereto include one or more access layer switches, and the physical servers connected to each access layer switch connected to the aggregation layer switch. That is, the physical devices in the dashed box in FIG. 5. After determining that the migration tasks on these downstream devices are completed based on the migration progress, the aggregation layer switch can be triggered to shut down.

[0087] Based on this, the shutdown of the physical devices in the target site can be timely and reasonably triggered based on the migration progress and the network topology relationship.

[0088] After the shutdown of the physical devices in the target site is completed, the target site can be shut down to complete the device migration of the target site.

[0089] In summary, the embodiment proposes a migration solution from migration evaluation to migration process control. Based on data, the migration necessity of each data processing site is objectively quantitatively evaluated, and the migration necessity is used as an objective basis for deciding whether the data processing site needs to be migrated, realizing an objective mechanism of data-driven decision-making. It is also proposed to control the migration tasks in the target site, which can effectively guarantee the controllability of the device migration process. Moreover, during the execution of the migration tasks by the physical devices in the target site, the migration progress can also be monitored, and on this basis, if it is determined that the migration tasks associated with any physical device in the target site are completed according to the migration progress and the network topology relationship corresponding to the target site, the physical device can be triggered to shut down. In this way, based on the monitored migration progress and the network topology relationship corresponding to the data processing site, the shutdown time of each physical device in the data processing site can be reasonably controlled, thereby effectively improving the performance stability of the data processing site during the migration process.

[0090] In the above or the following embodiments, different technical means can be used to determine whether the migration tasks associated with the physical devices are completed for different types of physical devices in the target site.

[0091] For physical servers: if it is determined that the migration tasks on any physical server in the target site are completed according to the migration progress, it is determined that the migration tasks associated with the physical server are completed.

[0092] After the instance-level migration task of a certain cloud service on the physical server is completed, it is indicated that the service instance under the cloud service has been migrated out; after the service-level migration task of the cloud service is also completed, it is indicated that the application program of the cloud service itself has also been migrated out, and thus the cloud service has completed migration out of the physical server. After the instance-level migration task and the service-level migration task of other cloud services on the physical server are completed, it is indicated that the other cloud services on the physical server have also completed migration out. In other words, according to the migration progress, it is determined that the migration tasks at all levels on the physical server have been completed, and thus it is indicated that the cloud services on the physical server have been migrated out, and therefore it is determined that the migration task associated with the physical server has been completed, and the physical server can be shut down.

[0093] For a network device: considering that migration tasks are usually distributed on physical servers but not on network devices, and the physical servers can be shut down in time after it is monitored that the migration tasks on the physical servers have been completed based on the migration progress, the embodiment provides that: if it is determined according to the network topology relationship that all the downstream devices connected to any network device in the target site have been shut down, it is determined that the migration task associated with the network device has been completed. It can be understood that the downstream devices connected to the network device can include physical servers and other network devices.

[0094] That is, for a network device, in the embodiment, it can be monitored whether the downstream devices connected to the network device have been shut down, and if it is determined that the downstream devices connected to the network device have been shut down, it is indicated that the network device no longer needs to undertake communication support work, and therefore it is determined that the migration task associated with the network device has been completed, and the network device can be shut down.

[0095] To sum up, in the embodiment, for different types of physical devices in the target site, based on the migration progress and the network topology relationship, appropriate technical means can be used to determine whether the physical devices can be shut down, so that the shutdown time of the physical devices can be more timely and more reasonably controlled, the migration efficiency of the data processing site can be improved, and the stability of the data processing site in the migration process can be ensured.

[0096] In the above or the following embodiments, an improved scheme for further optimizing the device migration efficiency is also provided. In the improved scheme, a fragmentation regularizing mechanism is provided. The fragmentation regularizing mechanism will be described in detail below.

[0097] In the improved scheme, if it is monitored that the migration progress of the target site has reached a target state, it is checked whether the physical servers that have not been shut down in the target site are distributed in multiple machine rooms; if yes, the to-be-migrated service instances and / or to-be-migrated services on the physical servers that have not been shut down are migrated to the physical servers in the target machine room in the target site.

[0098] The target state here could be, for example, the migration completion rate exceeding a preset threshold. This preset threshold can be set as needed and can be flexibly adjusted.

[0099] Figure 6 is a logical schematic diagram of a fragmentation consolidation mechanism provided by an exemplary embodiment of this disclosure. Referring to Figure 6, the original state of data center A, which needs to be migrated, is shown: data center A contains 3 server rooms, each containing multiple physical servers. As mentioned above, the device migration system can control the physical servers in the target location to start and execute migration tasks according to migration priority. Physical servers that support hot migration usually receive higher priority, and the migration difficulty corresponding to hot migration is also lower. Thus, physical servers with lower migration difficulty receive higher migration priority, and such physical servers can complete the migration earlier.

[0100] Based on this, referring to the intermediate state of data center A shown in Figure 6, some physical servers in data center A will complete their migration earlier (already migrated to various data centers in data center B, referring to the intermediate state of data center B), and these physical servers have been shut down; while some physical servers have not yet completed their migration due to high migration difficulty, and these physical servers have not been shut down. However, these physical servers that have not been shut down are distributed in multiple data centers, causing these data centers to still incur power consumption costs. Based on the improved scheme proposed in this embodiment, the service instances and / or services to be migrated on these physical servers that have not been shut down can be migrated to physical servers in the target data center within data center A (data center 1 in the example in Figure 6). This is equivalent to concentrating the fragmented service instances and the cloud service's own applications in the same data center. Of course, depending on actual needs, they can also be concentrated in multiple data centers, which can also achieve the effect of reducing data center power consumption.

[0101] The improved solution further proposes that after migrating the service instances and / or services to be migrated from the physical servers that have not been shut down to the physical servers in the target data center within the target site, the data centers in the target site that have already been migrated (which can be understood as data centers where all physical equipment contained therein has been shut down) can be shut down. In this way, more data centers can be shut down, thereby saving more power consumption costs during the equipment migration process.

[0102] In the above or the following embodiments, the device migration system can also divide the migration link into multiple links, in addition to the aforementioned migration evaluation link, migration control link, and device shutdown link, and the device migration system can perform control on more links.

[0103] In the improved scheme, it is also proposed that the device migration system can continue to control the un-shutdown physical servers in the target machine room to perform migration tasks; if it is determined according to the migration progress that there is no un-shutdown physical server in the target machine room, the target machine room is shut down.

[0104] Referring to the intermediate state of the data center A in FIG. 6, based on the fragmentation regularization mechanism proposed in the improved scheme, the machine room 2 and the machine room 3 in the data center A can be shut down more efficiently, so that the power consumption ends earlier, and the service instances and cloud services with long migration execution time in the data center A have been concentrated in the machine room 1. After fragmentation regularization, only the machine room 1 is still consuming power, and other machine rooms will not consume power, which can effectively save the power consumption cost of the data center A. Referring to the final state of the data center A and the final state of the data center B in FIG. 6, after a period of time, the related service instances and cloud services concentrated in the machine room 1 in the data center A have also been migrated to the data center B, and the machine room 1 can be shut down, and the data center A and the device migration are completed.

[0105] In summary, in the embodiment, the fragmentation regularization mechanism is proposed, which can concentrate the service instances and cloud services with long migration execution time in the target site into one or more machine rooms in the target site, so as to avoid the problem that too many machine rooms cannot be shut down due to the fragmentation of these service instances and cloud services, and thus the power consumption cost can be effectively saved during device migration.

[0106] In the above or the following embodiments, the device migration system can also divide the migration link into multiple links, in addition to the aforementioned migration evaluation link, migration control link, and device shutdown link, and the device migration system can perform control on more links.

[0107] FIG. 7 is a schematic diagram of an exemplary migration link provided by an exemplary embodiment of the present disclosure. Referring to FIG. 7, in the embodiment, the device migration system can also control the migration planning link.

[0108] In this regard, the embodiment proposes that the device migration system can make a migration plan for the target site; if it is detected that the migration progress in the target site does not meet any time requirement in the migration plan, a risk prompt is issued.

[0109] In the migration plan in this embodiment, at least one of the following time requirements can be included: a migration period of the target site, a migration schedule of each machine room in the target site, and a completion time limit of each level of migration task in each machine room in the target site. Of course, this is only exemplary, and the embodiment is not limited thereto.

[0110] The following provides exemplary construction schemes for the above-mentioned several exemplary time requirements: the migration period of the target site can be determined according to the remaining use time of the target site; the migration schedule between each machine room can be determined according to the estimated migration time consumption of each machine room in the target site; for any machine room in the target site, the completion time limit of each level of migration task in the machine room can be formulated according to the task amount of each level of migration task in the machine room.

[0111] The migration period can be understood as the total time consumption required for the migration of the target site. In actual application, the remaining use time of the target site can be calculated according to the lease period of the target site and other data, serving as the basis for determining the migration period. The migration schedule can be understood as the migration start time and the migration end time, used to determine the migration order between each machine room. In actual application, the migration time consumption of each machine room can be estimated according to the number of physical servers in each machine room, the number of cloud services carried, the number of service instances carried, and the like, serving as the basis for determining the migration schedule. Each machine room in the target site can perform migration in parallel to improve the migration efficiency. The parallelism between each machine room can be determined according to the device performance of the physical devices in the target site. The higher the device performance of the physical devices in the target site, the higher the parallelism between each machine room can be set. The completion time limit can be understood as the deadline of each level of migration task, which needs to be completed before the completion time limit. In actual application, the completion time limit can be determined according to the number of each level of migration task. The more the number, the later the completion time limit can be.

[0112] It should be understood that the device migration system can collect various data required in the foregoing process of constructing the migration plan. These data can be sourced from manual input or other platform-provided data collection interfaces, without limitation.

[0113] Based on the constructed migration plan, the device migration system can detect whether the migration progress in the target site meets any of the time requirements in the migration plan.

[0114] In some exemplary detection schemes: the device migration system can monitor whether the target site completes migration within a migration period in the migration plan according to the migration period in the migration plan; if not, a risk prompt can be issued; the completion time limit in the migration plan can be used to monitor whether the migration tasks at each level are completed before the corresponding completion time limit, and if not, a risk prompt can be issued; the migration schedule in the migration plan can be used to monitor whether each machine room in the target site completes migration within the migration schedule, and if not, a risk prompt can be issued. In this way, according to the migration plan, the risk identification of the migration process of the target site can be realized, and abnormal problems in the migration process can be found in time, so as to trigger the risk disposal process, for example, to promote to the manual disposal stage and the like.

[0115] With continuous reference to FIG. 7, it is proposed in the embodiment that the device migration system can also perform control on the resource preparation link.

[0116] In this regard, it is proposed in the embodiment that: a resource preparation scheme can be formulated for the target site, and the resource preparation scheme is used to guide the construction process of the target site; wherein the target site is the destination of the migration tasks at each level in the target site.

[0117] It is proposed in the embodiment that the resource preparation scheme can include at least one of the following: site selection of the target site, required physical device quantity and resource quantity of the target site, and source mode of the physical devices in the target site. The source mode can include at least one of the following: inventory devices, idle devices in other data processing sites, and newly purchased devices. Of course, the above are only exemplary, and the embodiment is not limited thereto.

[0118] Based on this, in the embodiment, the process of formulating the resource preparation scheme can include but is not limited to: determining the site selection of the target site according to the disaster recovery needs of multiple customers in the target site; estimating the required physical device quantity and resource quantity of the target site according to the physical device quantity and resource quantity in the target site; determining the source mode of the physical devices for the target site according to the physical device inventory information recorded in the device library.

[0119] After the resource preparation scheme is formulated, the scheme content in the resource preparation scheme can be pushed to the relevant person in charge through notification and the like, so as to guide the person in charge to promote the construction work of the target site. This will not be expanded and described in detail.

[0120] With reference to FIG. 7, in the embodiment, the device migration system can also perform control on the overall planning link.

[0121] To this end, the embodiment provides that the device migration system can determine a compensation strategy according to a migration mode corresponding to an instance-level migration task of a user, and push the compensation strategy to a corresponding responsible person. The device migration system can also construct a communication strategy according to a supportable compensation mode and a transaction that needs to be executed by the user in the device migration process, and push the communication strategy to the corresponding responsible person. No exhaustive control is performed on the planning and control in this aspect, and no more examples are provided.

[0122] Referring to FIG. 7, in the embodiment, the device migration system can also perform control on the device disposal link.

[0123] To this end, the embodiment provides that the device migration system can determine a disposal mode of the physical device that has been shut down according to the disposal strategy, and push the disposal mode to the corresponding responsible person. Here, the reference factors in the disposal strategy can include, but are not limited to, resource demand, device failure rate, device maintenance cost, and reconfiguration value, and no more examples are provided. The disposal mode can include, but is not limited to, relocation, reconfiguration, or scrapping, and no more examples are provided.

[0124] In summary, in the embodiment, the device migration system can divide the migration link into multiple links, and can perform control on each link, so that the device migration scenario, which is complex in evaluation and decision-making, has complicated comprehensive factors, and has a long execution period, can be standardized and automated in process steps and upstream and downstream series of systems. This makes the device migration process controllable, and can realize stability guarantee, risk identification, and progress tracking. This can effectively improve the efficiency of device migration and the stability of data processing sites in the migration process. Moreover, the data processing site with insufficient resource utilization can be more timely and more comprehensively discovered, and device migration can be performed as early as possible, so that more effective capacity management can be realized, the capacity availability of the in-use data processing site can be effectively improved, and losses can be reduced.

[0125] It should be noted that in some of the processes described in the above embodiments and the accompanying drawings, a plurality of operations appear in a specific order, but it should be clearly understood that the operations can be executed or performed in parallel or in the order in which they appear in this text. The serial numbers of the operations, such as 101, 102, etc., are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes can include more or fewer operations, and the operations can be executed in sequence or in parallel.

[0126] FIG. 8 is a structural schematic diagram of a device migration system provided by another exemplary embodiment of the present disclosure. As shown in FIG. 8, the device migration system can include an evaluation component 80, a migration management component 81, and a device management component 82.

[0127] The evaluation component 80 is configured to determine a target site that needs to be migrated according to a migration necessity degree evaluated for each data processing site.

[0128] The migration management component 81 is configured to monitor the migration progress during the process of controlling the physical devices in the target site to perform the migration task.

[0129] The device management component 82 is configured to trigger the physical device to shut down if it is determined, according to the migration progress and the network topology relationship corresponding to the target site, that the migration task associated with any physical device in the target site has been completed.

[0130] In this embodiment, the components in the device migration system cooperate with each other to control and manage each link in the migration link.

[0131] In an optional embodiment, the evaluation component 80 can be specifically configured to: calculate an evaluation value for each data processing site under a plurality of preset migration evaluation dimensions; and perform weighted summation on the calculated evaluation values according to the weights configured for different migration evaluation dimensions to obtain the migration necessity degree corresponding to the data processing site, during the process of evaluating the migration necessity degree for any data processing site.

[0132] In an optional embodiment, the evaluation component 80 can be specifically configured to: determine a data processing site whose migration necessity degree meets a preset requirement as a candidate site; evaluate the migration difficulty of the candidate site from a preset difficulty evaluation dimension; and determine a candidate site whose migration difficulty is lower than a preset standard as the target site that needs to perform device migration, during the process of determining the target site that needs to perform device migration according to the migration necessity degrees evaluated for each data processing site.

[0133] In an optional embodiment, the device migration system further includes a migration plan component 83, which can be configured to: formulate a migration plan for the target site; and issue a risk prompt if it is detected that the migration progress does not meet any time requirement in the migration plan, after the target site is determined.

[0134] The migration plan includes at least one time requirement, such as the migration period of the target site, the migration schedule of each machine room in the target site, and the completion time limit of each level of migration task in each machine room in the target site.

[0135] In an optional embodiment, the physical devices in the target site include physical servers, and the migration management component 81 can be specifically configured to: create a service-level migration task for a cloud service if it is determined, according to the migration progress, that an instance-level migration task for the cloud service on any physical server in the target site has been completed; and trigger the physical server to perform the service-level migration task.

[0136] In an optional embodiment, the migration management component 81 can be further configured to: determine a migration start time node of each physical server according to a migration priority configured for each physical server in the target site; and control each physical server to start performing an instance-level migration task according to the migration start time node of the physical server.

[0137] In an optional embodiment, the physical devices in the target site include physical servers and network devices, and the device management component 82 can be further configured to: if it is determined according to the migration progress that a migration task on any physical server in the target site has been completed, determine that a migration task associated with the physical server has been completed; and if it is determined according to the migration progress and the network topology relationship that a downstream device connected to any network device in the target site has been shut down, the downstream device including physical servers and / or other network devices, determine that a migration task associated with the network device has been completed.

[0138] In an optional embodiment, the physical devices in the target site include physical servers, and the device management component 82 can be further configured to: if it is monitored that the migration progress of the target site has reached a target state, check whether the physical servers that have not been shut down in the target site are distributed in multiple machine rooms; if yes, migrate the service instances to be migrated and / or the services to be migrated on the physical servers that have not been shut down to physical servers in a target machine room in the target site; shut down the machine room in the target site in which device migration has been completed; continue to control the physical servers in the target machine room to perform a migration task; and if it is determined according to the migration progress that there is no physical server that has not been shut down in the target machine room, shut down the target machine room.

[0139] In an optional embodiment, the device management component 82 can be specifically configured to: migrate the service instances to be migrated and / or the services to be migrated on the physical servers that have not been shut down to physical servers in a target machine room in the target site in a hot migration manner; and the target machine room is any machine room in the target site.

[0140] In an optional embodiment, a resource preparation component 84 is further included, which is configured to: formulate a resource preparation scheme for the target site, the resource preparation scheme being used to guide a construction process of the target site; wherein the target site is a destination of each migration task in the target site; and the resource preparation scheme comprises at least one of the following: a site selection of the target site, a required number of physical devices and resource quantity of the target site, and a source mode of the physical devices in the target site, the source mode comprising at least one of the following: an inventory device, an idle device in another data processing site, and a newly purchased device.

[0141] FIG. 9 is a functional logic diagram of a device migration system according to another example embodiment of the present disclosure. In addition to the functional logic provided by the components of the device migration system described above, the device migration system can further provide functional logic for overall planning and device handling, and the like. The corresponding functional logic can be referred to in FIG. 9, and will not be described in detail here.

[0142] It should be noted that the technical details described above in relation to the embodiments of the device migration system can be referred to the related descriptions in the method embodiments described above, and will not be described in detail here in order to save space, but this should not cause a loss of the protection scope of the present disclosure.

[0143] FIG. 10 is a structural diagram of a computing device according to another example embodiment of the present disclosure. The device migration system is integrated in the computing device. Referring to FIG. 10, the computing device can include a memory 10, a processor 11, and a communication component 12. The processor 11 is coupled to the memory 10 and the communication component 12, and is configured to execute a computer program in the memory 10, so as to perform each step in the method embodiments described above.

[0144] Further, as shown in FIG. 10, the computing device further includes a power supply component 13 and other components. Only some components are shown in FIG. 10, and this does not mean that the computing device only includes the components shown in FIG. 10.

[0145] It should be noted that the technical details described above in relation to the embodiments of the computing device can be referred to the related descriptions in the method embodiments described above, and will not be described in detail here in order to save space, but this should not cause a loss of the protection scope of the present disclosure.

[0146] Correspondingly, the embodiments of the present disclosure further provide a computer readable storage medium storing a computer program, which is executed to implement each step in the method embodiments described above.

[0147] Correspondingly, the embodiments of the present disclosure further provide a computer program product, which includes a computer program, which is executed to implement each step in the method embodiments described above.

[0148] The memory in FIG. 10 stores computer programs and can be configured to store other various data to support operations on the computing platform. Examples of such data include instructions for any application or method operating on the computing platform, contact data, phonebook data, messages, pictures, videos, and the like. The memory can be implemented by any type of volatile or non-volatile storage devices or a combination thereof such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic storage, flash memory, magnetic or optical disk.

[0149] The communication component in FIG. 10 is configured to facilitate wired or wireless communication between the device where the communication component resides and other devices. The device where the communication component resides can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G / LTE, 5G, or the like, or a combination thereof. In an example embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an example embodiment, the communication component also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0150] The power supply component in FIG. 10 provides power to various components of the device where the power supply component resides. The power supply component can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component resides.

[0151] Those skilled in the art will understand that embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Accordingly, the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, and the like) embodying computer-readable program code.

[0152] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0153] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks.

[0154] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0155] It should also be noted that the terms "comprising", "containing", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements in the list, but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more limitations, an element defined by the phrase "comprising a" does not exclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0156] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0157] The above merely provides an example of the present disclosure but is not intended to limit the present disclosure. The present disclosure can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A device migration method, wherein, The method comprises: determining a target site requiring device migration according to the migration necessity degree of each data processing site; monitoring the migration progress in the process of controlling the physical devices in the target site to perform migration tasks; if it is determined that the migration task associated with any physical device in the target site has been completed according to the migration progress and the network topology relationship corresponding to the target site, triggering the physical device to shut down.

2. The method of claim 1, wherein, The process of evaluating the migration necessity degree of any data processing site comprises: calculating the evaluation value of the data processing site under a plurality of preset migration evaluation dimensions respectively; performing weighted summation on the calculated evaluation values according to the weights configured for different migration evaluation dimensions to obtain the migration necessity degree corresponding to the data processing site.

3. The method of claim 1 or 2, wherein, According to the migration necessity degree evaluated for each data processing site, the target site requiring device migration is determined, which comprises: determining the data processing site whose migration necessity degree meets the preset requirement as a candidate site; evaluating the migration difficulty of the candidate site from a preset difficulty evaluation dimension; determining the candidate site whose migration difficulty is lower than the preset standard as the target site requiring device migration.

4. The method of claim 1, wherein, After the target site is determined, the method further comprises: developing a migration plan for the target site; if it is detected that the migration progress does not meet any time requirement in the migration plan, issuing a risk prompt; The migration plan comprises at least one time requirement: the migration period of the target site, the migration schedule of each computer room in the target site, and the completion time limit of each level migration task in each computer room in the target site.

5. The method of claim 1, wherein, The physical devices in the target site include physical servers, and controlling the physical devices in the target site to perform migration tasks comprises: if it is determined that the instance-level migration task for any cloud service on any physical server in the target site has been completed according to the migration progress, creating a service-level migration task for the cloud service; triggering the physical server to perform the service-level migration task.

6. The method of claim 5, wherein, Further comprising: determining the migration start time node of each physical server according to the migration priority configured for each physical server in the target site; for any physical server, controlling the physical server to start performing the instance-level migration task according to its corresponding migration start time node.

7. The method of claim 1, wherein, The physical devices in the target site include physical servers and network devices, and the method further comprises: if it is determined that the migration task on any physical server in the target site has been completed according to the migration progress, determining that the migration task associated with the physical server has been completed; if it is determined that the downstream device connected to any network device in the target site has been shut down according to the migration progress and the network topology relationship, determining that the migration task associated with the network device has been completed, wherein the downstream device includes physical servers and / or other network devices.

8. The method of claim 1, wherein, The physical devices in the target site include physical servers, and the method further comprises: If it is monitored that the migration progress of the target site has reached a target state, it is checked whether the physical servers not shut down in the target site are distributed in multiple machine rooms; If yes, the service instances and / or services to be migrated on the physical servers not shut down are migrated to the physical servers in the target machine room in the target site; The machine room in the target site in which the device migration has been completed is shut down; The physical servers in the target machine room continue to be controlled to perform the migration task; If it is monitored according to the migration progress that there is no physical server not shut down in the target machine room, the target machine room is shut down.

9. The method of claim 8, wherein, Migrating the service instances and / or services to be migrated on the physical servers not shut down to the physical servers in the target machine room in the target site comprises: Migrating the service instances and / or services to be migrated on the physical servers not shut down to the physical servers in the target machine room in the target site in a hot migration manner; The target machine room is any machine room in the target site.

10. The method of claim 1, wherein, Further comprising: Formulating a resource preparation scheme for the target site, the resource preparation scheme being used to guide the construction process of the target site; The resource preparation scheme comprises at least one of the following: the site selection of the target site, the number and resource amount of physical devices required by the target site, and the source mode of the physical devices in the target site, the source mode comprising at least one of the following: inventory devices, idle devices in other data processing sites, and newly purchased devices.

11. A device migration system, wherein, Comprising: An evaluation component configured to determine a target site requiring device migration according to the migration necessity degree evaluated for each data processing site; A migration management component configured to monitor the migration progress in the process of controlling the physical devices in the target site to perform the migration task; A device management component configured to trigger the shutdown of any physical device in the target site if it is determined according to the migration progress and the network topology relationship corresponding to the target site that the migration task associated with the physical device has been completed.

12. A computing device, wherein, Comprise a memory, a processor and a communication component; The memory is configured to store one or more computer instructions; The processor is coupled with the memory and the communication component, and is configured to execute the one or more computer instructions to perform the device migration method in any one of claims 1-10.

13. A computer readable storage medium storing a computer program, wherein, The computer program, when executed by one or more processors, causes the one or more processors to perform the device migration method in any one of claims 1-10.

14. A computer program product, wherein, The computer program, when executed by one or more processors, causes the one or more processors to perform the device migration method in any one of claims 1-10.

Images