CN111897654A - Method and device for migrating application to cloud platform, electronic equipment and storage medium - Google Patents

Abstract

The application relates to the technical field of computers, in particular to a method, a device, electronic equipment and a storage medium for migrating an application to a cloud platform, which are used for improving the accuracy of resource estimation and enabling the cloud-up process of application migration to be more convenient and efficient, wherein the method comprises the following steps: acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform; determining the application level of each application to be migrated according to the resource use information of each application to be migrated; acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to the migration strategy corresponding to the application level of each application to be migrated; and migrating each application to be migrated to the cloud platform after corresponding resources are created and reserved on the cloud platform according to the acquired number of the physical servers. According to the application, the application to be migrated is divided into different application levels according to the resource use information, and the resources required in the migration process are accurately estimated by adopting different migration strategies, so that the migration is more efficient.

Description

Method and device for migrating application to cloud platform, electronic equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for migrating an application to a cloud platform, an electronic device, and a storage medium.

Background

In cloud computing products, full stack cloud is a new solution, which is generally beneficial to providing a virtual machine for the virtualization capability of a cloud platform, then deploying a cloud native platform on the virtual machine, and after the cloud native platform hatches a container, transforming an application program into container service to provide service for an end user, so that the application program has both good isolation performance brought by the virtual machine and lightweight expansion and contraction capability brought by the container.

Because the virtual machine and the container service exist and the whole deployment form is relatively complex, the consumption of the application resources does not have global statistics at present, which brings great difficulty to resource estimation in the cloud application migration process. At present, after resource estimation is directly carried out according to experience values, an application is migrated to a cloud platform, and how to well estimate the use condition of the resource in the process of migrating the application to a full stack cloud is a problem to be considered.

Disclosure of Invention

The embodiment of the application migration method and device, the electronic device and the storage medium is used for improving the accuracy of resource estimation and enabling the cloud migration process to be more convenient and efficient.

The first method for migrating the application to the cloud platform provided by the embodiment of the application comprises the following steps:

acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

determining the application level of each application to be migrated according to the resource use information of each application to be migrated;

acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to a migration strategy corresponding to the application level of each application to be migrated;

and migrating each application to be migrated to the cloud platform after corresponding resources are created and reserved on the cloud platform according to the acquired number of the physical servers.

The first device for migrating an application to a cloud platform provided by the embodiment of the application comprises:

the information acquisition unit is used for acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

the grade dividing unit is used for determining the application grade of each application to be migrated according to the resource use information of each application to be migrated;

the pre-estimation unit is used for acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to the migration strategy corresponding to the application level of each application to be migrated;

and the migration unit is used for creating and reserving corresponding resources on the cloud platform according to the acquired number of the physical servers and then migrating each application to be migrated to the cloud platform.

Optionally, the resource in the migration policy includes a physical server or a virtual machine; the estimation unit is specifically configured to:

if the migration position is a physical server, acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of physical servers required for each database preset in the migration strategy;

if the migration position is a virtual machine, obtaining the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of virtual machines required by each database preset in the migration strategy and the reduced number corresponding to a first preset specification of the virtual machine, wherein the reduced number corresponding to the first preset specification is obtained according to a mapping relation between the preset virtual machine specification and the reduced number.

Optionally, the resources in the migration policy include a container service, and the migration policy further includes resource consumption of the container service; the estimation unit is specifically configured to:

estimating resource consumption required by all container services according to the number of the container services in the migration strategy corresponding to the application to be migrated and the resource consumption of each container service;

determining the number of virtual machines of a second preset specification required for migrating the application to be migrated to the cloud platform according to the estimated resource consumption required by all container services;

and acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the determined number of the required virtual machines and the reduced number corresponding to a second preset specification of the virtual machines, wherein the reduced number corresponding to the second preset specification is acquired according to a mapping relation between the preset virtual machine specification and the reduced number.

Optionally, the mapping relationship between the virtual machine specification and the reduced number is configured in advance according to the specification of the physical server, and the reduced number refers to the number of virtual machines of each specification that can be supported by the physical server of the target specification.

An electronic device provided in an embodiment of the present application includes a processor and a memory, where the memory stores program code, and when the program code is executed by the processor, the processor is caused to execute any one of the above steps of the method for migrating an application to a cloud platform.

An embodiment of the present application provides a computer-readable storage medium, which includes program code, when the program code runs on an electronic device, the program code is configured to cause the electronic device to perform any one of the steps of the method for migrating an application to a cloud platform.

Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of any one of the above methods for migrating an application to a cloud platform.

The beneficial effect of this application is as follows:

according to the method, the device, the electronic equipment and the storage medium for migrating the application to the cloud platform, in the embodiment of the application, before the application to be migrated is migrated to the cloud platform, the use condition of the application resource is analyzed through the obtained resource use information of each application to be migrated, different application grades are divided for the application to be migrated, different migration strategies are formulated for the applications to be migrated with different application grades, different resources are distributed, the use condition of the resource can be well estimated in the whole migration cloud-up process, the resource can be conveniently estimated in the whole migration cloud-up process, guidance is provided for the application migration cloud-up, the application migration cloud-up process is more convenient and efficient, and the method, the device, the electronic equipment and the storage medium can be further used for subsequent data center cluster expansion.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is an alternative schematic diagram of an application scenario in an embodiment of the present application;

FIG. 2 is a flowchart of a method for migrating an application to a cloud platform in an embodiment of the present application;

FIG. 3 is a flowchart of a method for calculating the number of physical servers in an embodiment of the present application;

fig. 4 is an architecture diagram of a full stack cloud platform in the embodiment of the present application;

fig. 5A is a schematic diagram of an architecture of a Region cluster in an embodiment of the present application;

fig. 5B is a schematic architecture diagram of a cloud-native service cluster in an embodiment of the present application;

FIG. 6 is a schematic diagram illustrating an alternative interactive implementation timing sequence in the embodiments of the present application;

fig. 7 is a schematic structural diagram illustrating an apparatus for migrating an application to a cloud platform in an embodiment of the present application;

fig. 8 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the technical solutions of the present application. All other embodiments obtained by a person skilled in the art without any inventive step based on the embodiments described in the present application are within the scope of the protection of the present application.

Some concepts related to the embodiments of the present application are described below.

Virtual Machine (Virtual Machine): in the context of computer science, the term "architecture" refers to a special software that creates an environment between a computer platform and an end user who operates the software based on the environment created by the software. In computer science, a virtual machine refers to a software implementation of a computer that can run a program like a real machine. In the embodiment of the present application, a virtual machine refers to a virtual device running on a physical host, and is used for deploying a cloud native platform.

Host machine: the virtual machine is installed on the host machine and can only be operated on the host machine, and the host machine is a host. In the embodiment of the present application, a host refers to a physical host, which may also be referred to as a physical machine or a physical server, and is used for providing a hardware environment for a virtual machine to run the virtual machine.

A container: typically located within the application server, which is responsible for loading and maintenance. One container can only exist within one application server, and one application server can establish and maintain multiple containers. The containers generally comply with the configurable principle that the user of the container can achieve its own usage requirements by configuring the parameters of the container without modifying the code of the container. Briefly, a container contains the complete runtime environment: all dependencies, class libraries, other binaries, configuration files, etc. required by the application, except the application itself, are uniformly typed into a package called a container image. By containerizing the application itself, and the differences that are made by its dependencies, operating system releases and other underlying environments, are abstracted away.

Container service: the cloud server instance cluster management system is a highly extensible high-performance container management service, and can easily run application programs on the hosted cloud server instance cluster. The user can split the big application into different micro-services, and each micro-service provides atomic functions and is connected with each other. Each microservice consists of a set of containers that mirror the same configuration. The micro service is a concept of a container service, and one or more services constitute an application of the container service.

Resource usage information: the parameters indicating the usage of the application resources may be an application concurrency amount, a CPU (Central Processing Unit) usage rate, a memory usage rate, and the like. The concurrency means the number of people accessed by the website at the same time, and the larger the number of people, the higher the instantaneous bandwidth requirement.

Cloud-native: the method is a method for constructing and running the application program, and is a set of technical system and methodology. Cloud Native (cloudlive) is a compound word, Cloud + Native. Cloud represents applications located in the Cloud, rather than a traditional data center; native represents that the application program is originally designed for the cloud from the beginning of design in consideration of the cloud environment, runs on the cloud in an optimal posture, and fully utilizes and exerts the elasticity and the distributed advantage of the cloud platform. In the embodiment of the present application, an application deployed on a cloud native platform may be referred to as a cloud native application, and the cloud native application has three features: 1) containerized packaging: based on the container, the overall development level is improved, codes and components are reused, and maintenance of the cloud native application program is simplified. The application and the process are run in the container and serve as independent units for application deployment, and high-level resource isolation is achieved. 2) Dynamic management: the dynamic management and scheduling are realized by a centralized scheduling system. 3) Micro service oriented: the dependencies between the explicit services are decoupled from each other.

IaaS (Infrastructure as a Service): meaning that the consumer can obtain services from a sophisticated computing infrastructure via the Internet. The services provided to the consumer are the utilization of all of the computing infrastructure, including processing CPU, memory, storage, networking and other basic computing resources, and the user is able to deploy and run any software, including operating systems and applications. Consumers do not manage or control any cloud computing infrastructure, but can control operating system selection, storage space, deployed applications, and possibly limited network components (e.g., routers, firewalls, load balancers, etc.). In the embodiment of the application, the cloud computing platform in the IaaS service mode is referred to as the IaaS cloud platform for short.

A middleware: the basic software is a basic software applied to a distributed system, is positioned between an application and the operating system as well as between the application and the database, and provides a platform for development, operation and integration for upper-layer application software. The middleware solves the common problems of software interconnection, interoperation and the like in a heterogeneous network environment, provides a standard interface and a standard protocol, and provides a reusable standard component for sharing resources among application software.

HA (High Available, High availability): by combining redundant hardware and software, fault detection and correction can be managed without human intervention. The main implementation mode of the HA is to configure two identical devices at the same location of the network. The equipment is divided into a main equipment and a backup equipment. The main device is in active state, transmits message, and transmits all network and configuration information and current session information to the backup device. When the main device fails, the backup device takes over the main device to work and forwards the message.

JVM (Java Virtual Machine): the specification is used for computing equipment, is a fictitious computer and is realized by simulating various computer functions on an actual computer. After the Java language virtual machine is introduced, the Java language does not need to be recompiled when running on different platforms. The Java language masks information related to a specific platform using a Java virtual machine, so that a Java language compiler can be executed on a variety of platforms without modification by only generating object codes (bytecodes) to be executed on the Java virtual machine.

Polling (Polling): the method is a way for the CPU to decide how to provide peripheral device services, and is also called Programmed input/output (Programmed I/O). The concept of the polling method is: the CPU sends out inquiry at regular time to inquire each peripheral equipment whether it needs its service or not in sequence, if so, the peripheral equipment gives service, and after the service is over, the peripheral equipment asks the next peripheral equipment, and then the process is repeated.

Cloud computing (cloud computing): the method is a computing mode, and distributes computing tasks on a resource pool formed by a large number of computers, so that various application systems can acquire computing power, storage space and information services according to needs. The network that provides the resources is referred to as the "cloud". Resources in the "cloud" appear to the user as being infinitely expandable and available at any time, available on demand, expandable at any time, and paid for on-demand.

As a basic capability provider of cloud computing, a cloud computing resource pool (called as an ifas (Infrastructure as a Service) platform for short is established, and multiple types of virtual resources are deployed in the resource pool and are selectively used by external clients.

According to the logic function division, a Platform as a Service (PaaS) layer can be deployed on the IaaS layer, a Software as a Service (SaaS) layer is deployed on the PaaS layer, and the SaaS layer can be directly deployed on the IaaS layer. PaaS is a platform on which software runs, such as a database, a Web container, and the like. SaaS is a variety of business software, such as web portal, sms, and mass texting. Generally speaking, SaaS and PaaS are upper layers relative to IaaS.

The following briefly introduces the design concept of the embodiments of the present application:

the close integration of cloud computing and 5G (5th-Generation, fifth Generation mobile communication technology) and AI (artificial intelligence) technologies is rapidly changing the industrial patterns of various industries and promoting global digital transformation into deep water areas. Enterprises need a brand-new cloud infrastructure, transparently integrate any resource, and guarantee dynamic migration of workload, so that the enterprises are helped to release data potential, novel full-factor productivity is improved, and a foundation is laid for continuous business innovation and upgrade. The full-stack cloud infrastructure enables enterprises to simply and quickly support application development and delivery on a full-stack cloud layer through unified intelligent monitoring management of cross-multi-cloud, core and edge architectures, and quickly integrates and releases multi-cloud or edge computing resources. Based on a full-stack cloud virtualization technology, a plurality of virtual machines can be created on a physical server to serve as application servers to improve the energy efficiency problem of a data center, so that migration of application programs is achieved, and the resource utilization rate is improved.

However, before the application is migrated to the cloud, since the consumption of the application resources does not have global statistics, the resource estimation in the process of migrating to the cloud is very difficult. In the related art, the application is generally migrated to the cloud platform after resource pre-estimation is performed according to an empirical value, and the method can only roughly estimate the resources required for migrating to the cloud.

In view of this, the embodiment of the application provides a method, an apparatus, an electronic device, and a storage medium for migrating an application to a cloud platform, where resource usage of applications to be migrated is analyzed, application levels of the applications to be migrated are divided according to resource usage information of the applications to be migrated, and different migration strategies are formulated for different application levels, so that a total resource consumption of a server that migrates the applications to be migrated to the cloud platform can be estimated more accurately, and the usage of the resources can be estimated well in advance in a full-stack cloud migration process. And then corresponding resources can be created and reserved on the cloud platform according to the estimated total resource consumption of the server, preparation is made for migration, and on the basis, the applications to be migrated can be more convenient and efficient when being migrated to the cloud platform.

The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it should be understood that the preferred embodiments described herein are merely for illustrating and explaining the present application, and are not intended to limit the present application, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

As shown in fig. 1, the application scenario diagram of the embodiment of the present application includes a unified cloud pipe, a cloud native platform, an IaaS cloud platform, a virtual resource pool, and an infrastructure.

The unified cloud management is a unified management platform of data center resources, and can manage a plurality of open-source or heterogeneous cloud computing technologies or products.

In the embodiment of the application, the IaaS cloud platform refers to a platform capable of providing IaaS cloud service; the cloud native platform is a PaaS platform which provides application hosting and micro-service management capabilities for enterprises, can help the enterprises to simplify application life cycle management work such as deployment, monitoring, operation and maintenance and the like, and simultaneously provides micro-service management and operation and maintenance capabilities such as service registration, service management, service monitoring and call chains and the like. The virtual resource pool is a pool formed by resources abstracted from a bare computer of a host in the cloud platform and comprises a computing resource pool, a storage resource pool, a network resource pool and the like; where the computing resource pool includes the servers shown in fig. 1, virtualization of services may be implemented, and the storage resource pool is used to implement storage virtualization, such as the storage pool shown in fig. 1. In addition, the network resource pool is used to implement network virtualization, which is not shown in fig. 1. At the bottom of fig. 1, an infrastructure layer is provided, and the main deployed infrastructure refers to hardware, including hardware related to machine rooms, refrigeration, power supply and the like.

In the embodiment of the application, the virtual machine is provided by utilizing the virtualization capability of the cloud platform, the application program is transformed into the container service by deploying the cloud native platform on the virtual machine, for example, the cloud native platform hatching container, the service is provided for the final user, and the application program can be migrated to the cloud.

It should be noted that, the application in the embodiment of the present application refers to an application located on a PC (Personal Computer) terminal or a mobile terminal, where the mobile terminal includes a mobile phone, a tablet Computer, a notebook, an e-book reader, and the like, and is not limited specifically herein.

Referring to fig. 2, an implementation flow chart of a method for migrating an application to a cloud platform according to an embodiment of the present application is shown, and a specific implementation flow of the method is as follows:

s21: acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

the resource usage information refers to parameters indicating the resource usage of the application to be migrated, such as application concurrency, CPU usage, memory usage, and the like.

S22: determining the application level of each application to be migrated according to the resource use information of each application to be migrated;

in the embodiment of the application, the resource use information of each application to be migrated, such as the CPU use rate, the memory use rate, the application concurrency amount, and the like of the application to be migrated, is collected in real time, and the application level is divided for each application to be migrated according to the collected information. In the embodiment of the present application, migration policies corresponding to different application levels are different, and accordingly, situations of resource allocation are also different.

In an optional implementation manner, when analyzing the application level of each application to be migrated, first, a usage interval to which resource usage information of each application to be migrated belongs needs to be analyzed, in the embodiment of the present application, a plurality of usage intervals are divided in advance according to a preset threshold, and different usage intervals correspond to different application levels; further, the application level corresponding to the use interval to which the resource use information of each application to be migrated belongs is used as the application level of each application to be migrated.

When determining the use interval to which the resource use information of one application to be migrated belongs, the use interval to which the peak value of the resource use information of each application to be migrated in a preset time period belongs can be used as the use interval to which the resource use information of each application to be migrated belongs.

Taking the resource usage information as the application concurrency amount as an example, assume that three usage intervals related to the application concurrency amount are divided in advance according to a preset threshold, and are respectively [0, 100 ], [100, 1000], (1000, + ∞).

The correspondence between the usage intervals and the application levels can be seen in table 1.

TABLE 1

Usage interval	Application level
		(1000，+∞)	Height of
[100，1000]	In
		[0，100)	Is low in

As can be seen from table 1, if the peak value of the concurrency amount of an application to be migrated in a preset time period is greater than 1000, the application level of the application is high; when the peak value of the application concurrency is between 100 and 1000, the application level of the application is middle; when the peak value of the application concurrency amount is less than 100, the application level of the application is low. The above-listed gradations are also merely examples, and are not specifically limited herein.

Taking the resource usage information as the CPU usage as an example, assume that three usage intervals regarding the CPU usage are divided in advance according to a preset threshold, and are [0, 10%, [ 10%, 50% ], and (50%, 100% ], respectively.

The correspondence between the usage intervals and the application levels can be seen in table 2.

TABLE 2

Usage interval	Application level
		(80％，100％]	Height of
[10％，80％]	In
		[0，10％)	Is low in

As can be seen from table 2, if the peak value of the CPU utilization of a certain application to be migrated is above 80% in a preset time period, the application level of the application is high; when the peak value of the CPU utilization rate is between 10% and 80%, the application grade of the application is medium; when the peak value of the CPU usage is less than 10%, the application level of the application is low. Similarly, when the resource usage information is the memory usage rate, the resource usage information may be ranked in a similar manner.

In addition, the resource usage information may further include multiple types of the application concurrency amount, the CPU usage rate, and the memory usage rate listed above, in this case, when determining the application level of the application to be migrated, it is first necessary to determine a usage interval to which a peak value of each type of resource usage information belongs, and at this time, it is determined, according to the usage interval to which the peak value of each type of resource usage information belongs, each application level obtained when dividing the application level according to the usage interval to which each type of resource usage information belongs, respectively. Comprehensively considering each application level, the application level with the largest occurrence frequency in the application levels corresponding to the various resource use information can be used as the application level of the application to be migrated; or the highest application level in all application levels corresponding to the various resource use information may be used as the application level of the application to be migrated.

For example, for a certain application to be migrated, the peak value of the CPU utilization rate in the preset time period is 90%, the corresponding application level is high in the usage interval (80%, 100%), the peak value of the memory utilization rate is 70%, the corresponding application level is medium in the usage interval [ 10%, 80%), the peak value of the application concurrency amount reaches 1500, the corresponding application level is high in the usage interval (1000, + ∞).

Wherein, each application grade respectively obtained according to the three resource use information is as follows: high, medium, and high, wherein the application level with the highest occurrence number is high, and thus the application level of the application to be migrated is finally determined to be high. If the highest application level of the three application levels is taken as the application level of the application to be migrated, the application level of the application to be migrated is still high.

Optionally, the application level of the application to be migrated may also be determined by means of weighted summation or the like. Firstly, determining a use interval to which a peak value of each type of resource use information belongs, determining use scores corresponding to each type of resource use information according to the use interval to which the peak value belongs, and determining the application grade of the application to be migrated according to a final score obtained by weighting and summing each use score. When determining the application level of the application to be migrated according to the final score, two thresholds may be set, a first threshold being 10 and a second threshold being 70. If the final score is lower than a first threshold, confirming that the application grade is low; if the final score is between the first threshold and the second threshold, confirming that the application grade is medium; if the final score is above a second threshold, the application level is confirmed to be high.

For example, when the peak value of the CPU utilization rate of the application to be migrated is 90% in the preset time period and belongs to the use interval (80%, 100%), the corresponding use score is 90 and the weight is 30%, when the peak value of the memory utilization rate is 70% and belongs to the use interval [ 10%, 80% ], the corresponding use score is 70 and the weight is 30%, when the peak value of the application concurrency amount reaches 1500, and belongs to the use interval (1000, + ∞), the corresponding use score is 80 and the weight is 40%, the three use scores are subjected to weighted summation, the obtained final score is 80 and is higher than the second threshold, and therefore the final application level of the application to be migrated is high.

It should be noted that, the above listed manners of determining the usage interval to which the resource usage information belongs according to the peak value of the resource usage information in the preset time period and further determining the application level of the application to be migrated are only examples, and any manner of determining the application level of the application to be migrated according to the peak value of the resource usage information in the preset time period is applicable to the embodiment of the present application, and is not specifically limited herein.

In the following, the application concurrency is mainly exemplified as the resource usage information of the application, but the same reasoning is true when the resource usage information is other parameters, and the limitation is not repeated here.

S23: acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to the migration strategy corresponding to the application level of each application to be migrated;

the migration policy includes resources and resource quantity allocated to the application to be migrated, and the resources or resource quantity in the migration policies corresponding to different application levels are different.

In this embodiment of the present application, the resources included in the migration policy may be any one or more of physical servers, virtual machines, or container services, and the number of resources refers to the number of physical servers, the number of virtual machines, or the number of container services. The different application levels correspond to different migration strategies, and resources or the number of the resources allocated to the application to be migrated in the different migration strategies are different.

S24: and migrating each application to be migrated to the cloud platform after corresponding resources are created and reserved on the cloud platform according to the acquired number of the physical servers.

In the embodiment of the application, before the application to be migrated is migrated to the cloud platform, the resource use condition of the application to be migrated is analyzed through the acquired resource use information of each application to be migrated, the application to be migrated is divided into different application levels, different migration strategies are formulated for the applications to be migrated at different application levels, and different resources are allocated, so that the use condition of the resources can be well estimated in advance in the full-stack cloud migration process, the resources can be conveniently estimated in the whole cloud migration process, guidance is provided for cloud migration of the application, and the method can be used for subsequent data center cluster expansion.

A process of acquiring the number of physical servers required to migrate each application to be migrated to the cloud platform according to the migration policy is described in detail below.

In the embodiment of the present application, different application levels correspond to different migration policies, where a migration policy is mainly used to specify resources and the number of resources required for migrating an application to be migrated, and the number of resources refers to the number of physical servers, the number of virtual machines, or the number of container services, which are required. In addition, the establishment of the migration strategy has a certain association with the splitting of the application, and in the embodiment of the application, the splitting of the application to be migrated is divided into two different modes, namely a front-end mode, a back-end mode and a front-end mode, a middleware mode and a back-end mode. For example, applications such as office systems and mailbox systems are generally in a front-end + back-end + database mode, and applications such as announcement systems and presentation systems are generally in a front-end + middleware + back-end mode.

The migration policy used for the applications in different modes is different, specifically, the resources allocated to the applications to be migrated in the migration policy are different. For the application to be migrated in the front-end + back-end + database mode, the resources allocated in the migration policy are physical servers or virtual machines, and for the application to be migrated in the mode, the resources in the migration policies corresponding to different application levels may be the same or different, and in addition, the number of resources in the migration policies corresponding to different application levels is also different, and generally, the higher the application level is, the more the number of corresponding resources is.

And aiming at the application to be migrated in the front-end mode, the middleware mode and the back-end mode, resources distributed in the migration strategy serve the container. For the application to be migrated in this mode, resources in the migration policies corresponding to different application levels are all container services, and resource consumption of each container service may be different.

In the two enumerated modes, when the number of physical servers required for migrating each application to be migrated to the cloud platform is determined according to the migration policy, for any one application to be migrated, the following discussion is respectively given:

if the application to be migrated is in a front-end + back-end + database mode, determining the number of physical servers required for migrating the database of the application to be migrated to the cloud platform according to the migration position and the resource number of the database in the migration policy corresponding to the application to be migrated, wherein the migration position represents resources occupied when the database of the application to be migrated is migrated to the cloud platform.

For the application in this mode, the migration policy is mainly used to define what resources the database should be deployed on when the application to be migrated is migrated to the cloud platform, and since the resources in the migration policy include a physical server or a virtual machine, the corresponding migration location also refers to the physical server or the virtual machine, where the physical server is the physical machine. When different migration strategies are formulated, the migration positions preset in the migration strategies are determined according to the application levels of the applications to be migrated. Specifically, when the application level is higher, the migration position preset in the migration policy is the physical server, that is, the database of the application to be migrated is directly deployed on the physical server; when the application level is low, the migration position preset in the migration policy is the virtual machine, that is, the database of the application to be migrated needs to be deployed on the virtual machine.

For example, the database of the application with high concurrency is directly deployed on the physical machine, while the database of the application with low concurrency or medium concurrency is deployed on the virtual machine, and the number of the required physical servers needs to be further reduced according to the number of the virtual machines.

In the embodiment of the application, the higher the application concurrency is, the higher the application level is, and according to the corresponding migration policy, the resource is preferentially allocated to the application to be migrated at the higher level as the physical server, so that the stability of the application system in the emergency situation can be ensured. In addition, under the condition that the physical servers are not sufficiently allocated, virtual machines can be further allocated to the application to be migrated.

Optionally, if the migration position in the migration policy is a physical server, the resource data in the migration policy is the number of physical servers required by each database, so that the number of physical servers required to migrate the application to be migrated to the cloud platform can be obtained according to the number of physical servers required by each database preset in the migration policy. That is to say, for the application to be migrated with high concurrency, the migration policy specifies that the migration position of the database is a physical server, and in addition, the migration policy also sets the number of physical servers required by each database, so that the sum of the number of physical servers required by all databases, that is, the number of physical servers required when the application to be migrated with high concurrency is migrated to the cloud platform.

If the migration position in the migration policy is a virtual machine, the resource data in the migration policy, that is, the number of virtual machines required by each database, is migrated, so that the number of physical servers required for migrating all databases in the application to be migrated to the cloud platform can be obtained according to the number of virtual machines required by each database preset in the migration policy and the reduced number corresponding to the first preset specification of the virtual machine, where the ratio of the number of virtual machines to the reduced number is the number of physical servers required.

It should be noted that, in the embodiment of the present application, the converted number corresponding to the first preset specification is obtained according to a mapping relationship between the virtual machine specification and the converted number configured in advance, and in the embodiment of the present application, a mapping relationship between the virtual machine specification and the converted number needs to be preset and established, so that the number of the physical servers needed can be converted based on the number of the virtual machines and the specification according to the virtual machine specification and the number preset in the migration policy and the mapping relationship. After the converted number corresponding to the first preset specification is determined from the mapping relation, the ratio of the number of the virtual machines to the converted number is the number of physical servers required by migrating all databases in the application to be migrated to the cloud platform. In the following, taking the resource usage information as the application concurrency amount as an example, the migration policies corresponding to various application levels under different application concurrency amounts will be described in detail for example.

If the application to be migrated is an application in a front-end + middleware + rear-end mode, the number of the container services, which is resource data in a migration policy corresponding to the application, is determined, when the number of the physical servers is calculated, the number of the physical servers required for migrating the application to be migrated to the cloud platform needs to be determined according to the number of the container services in the migration policy corresponding to the application to be migrated, wherein the number of the container services indicates the number of the container services required for migrating the application to be migrated to the cloud platform, and the higher the application level of the application to be migrated is, the larger the number of the container services in the migration policy corresponding to the application level is.

It should be noted that, in the case that the resource in the migration policy includes a container service, the migration policy may further include resource consumption required by the container service. Referring to fig. 3, which is a flowchart of a method for calculating the number of physical servers in this embodiment of the application, when determining the number of physical servers required to migrate the application to be migrated to the cloud platform according to the number of container services in the migration policy corresponding to the application to be migrated, specifically including the following steps:

in step S31, estimating resource consumption required by all container services according to the number of container services in the migration policy corresponding to the application to be migrated and resource consumption of each container service;

the migration policy may specify the number of container services, and the migration policies corresponding to different application levels have different specified numbers of container services, for example, the higher the application level is, the higher the number of corresponding container services is. The resource consumption of the container service specifically includes CPU consumption and JVM consumption, the resource consumption required by the container service specified in the migration policy corresponding to different application levels is also different, and the higher the application level is, the higher the resource consumption required by each container service specified in the corresponding migration policy is.

For example, the number of container services specified in the migration policy corresponding to the high concurrency application level is 30, and the resource consumption is: the CPU is 4-8 cores, and the size of the JVM is 8-16G; the number of container services specified in the migration policy corresponding to this application level in concurrency is 24, and the resource consumption is respectively: the CPU is 2-4 cores, and the size of the JVM is 4-8G; the number of container services specified in the migration policy corresponding to this application level of low concurrency is 18, and the resource consumption is: the CPU is 1-2 cores, and the size of the JVM is 2-4G. In the following, taking the resource usage information as the application concurrency amount as an example, a detailed example of the migration policy corresponding to various application levels under different application concurrency amounts will be described.

In step S32, determining the number of virtual machines of a second preset specification required for migrating the application to be migrated to the cloud platform according to the estimated resource consumption required for all the container services;

the second preset specification is the specification of the virtual machine specified in the migration policy, specifically, the CPU size and the JVM size, so that the number of virtual machines of the second preset specification required for migrating the application to be migrated to the cloud platform can be determined according to the ratio of the sum of resource consumption of all container services to the second preset specification of the virtual machine.

In step S33, the number of physical servers required for migrating the application to be migrated to the cloud platform is obtained according to the determined number of required virtual machines and the reduced number corresponding to the second preset specification of the virtual machines, where the reduced number corresponding to the second preset specification is obtained according to the mapping relationship between the preset virtual machine specification and the reduced number.

The mapping relation between the virtual machine specification and the converted number is configured in advance according to the specification of the physical server, and the converted number refers to the number of virtual machines of each specification which can be supported by the physical server of the target specification.

The step is also similar in principle, the conversion number corresponding to the second preset specification of the virtual machine can be determined based on the mapping relation, and then the ratio of the determined number of the required virtual machines to the conversion number is calculated, namely the number of the physical servers required for migrating the application to be migrated to the cloud platform.

In the embodiment of the present application, the specification of the physical server may be various, for example, the target specification is: the number of CPUs of each physical server is 64 cores, and the memory assumes that each physical server is 256G. Considering that the virtual machine is a process of the operating system of the physical machine, and there may be a case that the operating system of the virtual machine and the operating system of the physical machine robs resources, the CPU reserved for the operating system and the virtual machine is 4 cores, and the memory is 16G, and in addition, the number of CPU cores that can be provided is (64-4) ═ 60 cores, and the memory is (256-16) ═ 240G.

Assuming that the virtual machine specification is 8U16G specification (different specifications can be customized), the number of virtual machines that a physical server of one target specification can support is: 60/8 ═ 7; according to the memory calculation, the number of virtual machines which can be supported by a physical server with a target specification is as follows: 240/16 ═ 15. Therefore, one physical server can support 7 virtual machines of 8U16G specification. Similarly, virtual machines of other specifications may also perform computations in a similar manner.

By the above method, the number of virtual machines of different specifications that can be supported by the physical server of the target specification can be obtained, and based on this, a mapping relationship between the virtual machine specification and the reduced number is established, which indicates how many virtual machines can be supported by one physical server for different virtual machine specifications, for example, table 3, which is a mapping relationship table listed in the embodiment of the present application:

TABLE 3

Specification of	Reduced number of
		4U8G	15
8U16G	7
		16U32G	3
…	…

As can be seen from table 3, when the specification of the virtual machine is 4U8G, one physical server can support 15 virtual machines of the specification, and the reduced number is 15; when the specification of the virtual machine is 8U16G, one physical server can support 7 virtual machines with the specification, and the reduced number is 7; when the specification of a virtual machine is 16U32G, one physical server can support 3 virtual machines of that specification, the reduced number is 3, and so on.

The following describes in detail migration policies corresponding to different application levels in different modes, with reference to the manner of dividing application levels listed in table 1. Firstly, introducing migration strategies corresponding to different application levels in a front-end + back-end + database mode, wherein for applications to be migrated in the mode, resources in the migration strategies include physical servers or virtual machines, and the number of the resources is the number of the physical servers or the number of the virtual machines:

high concurrency:

when the application concurrency amount of the application to be migrated is above 1000, the application level of the application to be migrated is high, that is, high concurrency. In this case, the migration policy specifies that the highly-concurrent database to be migrated is directly deployed on the physical server, which indicates that the migration position in the migration policy is the physical server, and in addition, the database is set to be read-write separated, each database needs 4 physical servers, 1 write and 3 read indicate that the number of resources in the migration policy is 4. The physical servers in the embodiments of the present application are all physical servers of the target specification. When the application to be migrated only has one database, the number of physical servers required for migrating the application to be migrated to the cloud platform is 4.

And (II) concurrent generation:

when the application concurrency amount of the application to be migrated is between 100 and 1000, the application level of the migration application is medium, that is, medium concurrency. In this case, the migration policy specifies that the databases to be concurrently migrated and applied are directly deployed on the virtual machines, the migration position in the migration policy is the virtual machine, and in addition, read-write separation is also set, each database needs 4 16U32G virtual machines, 1 read and 3 write indicates that the number of resources in the migration policy is 4, where the specification of the virtual machine is 16U32G, i.e., a first preset specification, which is determined based on the migration policy, and when the migration policy specifies and deploys the databases to be concurrently migrated and applied on the virtual machines, the specification and number of the virtual machines needed by one database, so the number of the needed physical servers can be converted according to the specification and number of the virtual machines preset in the migration policy.

For example, when the relationship between the virtual machine specification and the reduced number is shown in table 3, as can be seen from table 3, since one physical server can reduce 3 virtual machines with the specification of 16U32G, when 4 virtual machines with the specification of 16U32G need to be occupied by one database, the number of physical servers needed is 2(4/3 ≈ 1.33 ≈ 2). That is, when the application to be migrated has only one database, the number of physical servers required to migrate the application to be migrated to the cloud platform is 2.

(III) low concurrency:

when the application concurrency amount of the application to be migrated is less than 100, the application level of the migration application is low, that is, the concurrency is low. In this case, the migration policy specifies that the database used by the low-concurrency application to be migrated is deployed on the virtual machine, which indicates that the migration position in the migration policy is the virtual machine, and in addition, the virtual machine is set as the host and backup HA, so that each database needs 2 virtual machines of 16U32G, 1 host and 1 backup indicates that the number of resources in the migration policy is 2. Based on the specification and number of virtual machines preset in the migration policy, the number of physical servers required can be converted by referring to the mapping relationship table shown in table 3.

Wherein, the number of the required physical servers is as follows: 2/3 ≈ 0.67 ≈ 1. That is, when the application to be migrated has only one database, the number of physical servers required to migrate the application to be migrated to the cloud platform is 1.

It should be noted that the above listed migration policies for the application database to be migrated are also only examples, and the specification of the virtual machines, the number of virtual machines, and the like specified in the migration policies may be determined according to actual situations, and are not specifically limited herein. It can be known from the above embodiments that the higher the application level is, the more the amount of physical server resources that need to be consumed when the application to be migrated is migrated to the cloud platform is.

In this embodiment of the present application, depending on application conditions, application splitting needs to introduce a migration policy corresponding to different application levels in a front-end + middleware + back-end mode, where for an application to be migrated in this type of mode, resources in the migration policy include container services, and a resource number is a number of container services:

high concurrency:

when the application concurrency amount of the application to be migrated is above 1000, the application level of the application to be migrated is high, that is, high concurrency. Where each application component, such as a front end, may be served by multiple containers, polling is provided through load balancing. Assuming that under the high concurrency condition, each high concurrent application to be migrated can be specified in the migration policy to be highly available by using 10 duplicate containers, that is, 10 containers provide front-end services, a total of 30 container services are required in the mode that the application is divided into front-end + middleware + backend, which means that resources in the migration policy are container services, and the number of the resources is 30.

It should be noted that, when the resources in the migration policy include a container service, the migration policy also includes resource consumption of the container service. Assuming that a critical high-concurrency application with a large access amount is taken as an example, the resource consumption of the container service of one high-concurrency application preset in the migration policy is as follows: the CPU is 4-8 cores, and the size of the JVM is 8-16G. According to the number of the container services in the migration policy and the resource consumption of each container service, it can be determined that the sizes of the CPUs and the memories required by 30 container services are about:

a CPU: 30 × 4-8 nuclei, up to 240 nuclei;

JVM: 30 × 8-16G, the maximum is 480G, and the actual container internal storage is about 500G.

Because the virtual machine needs to leave a certain amount of CPU and memory overhead for the operating system itself, each application needs 15 16C32G virtual machines, where 16C32G is the second predetermined specification specified in the migration policy. The number of the required virtual machines can be estimated according to the number of the systems, and the number of the required physical servers can be converted.

Assuming that the application concurrency in the cloud platform project is more than 1000, there are 3 mechanisms and 24 application systems, so that 24 × 15-360 virtual machines are required in total, and 360/3-120 physical servers are required in total. Wherein, the organization refers to the department to which the application system belongs, or the tenant. Typically, a department will have multiple applications. Here, it is explained that 8 application systems are provided in one department, and one application system corresponds to one application.

Therefore, for an application to be migrated, the number of physical servers required to migrate the application to be migrated to the cloud platform is as follows: 15/3 ═ 5.

And (II) concurrent generation:

when the application concurrency amount of the application to be migrated is between 100 and 1000, the application level of the migration application is medium, that is, medium concurrency. In this case, it is specified in the migration policy that each concurrent application to be migrated can adopt 8 copies with high availability, and then under the mode that the application is divided into front-end + middleware + back-end, 24 container services are required in total, which means that resources in the migration policy are container services, and the number of the resources is 24.

Assuming that a concurrent application is taken as an example, the resource consumption of the container service of the concurrent application in one preset migration policy is as follows: the CPU is 2-4 cores, and the size of the JVM is 4-8G. The CPU and memory size required for this 24 container service is about:

a CPU: 24 × 2-4 nuclei, up to 96 nuclei;

JVM: 30 × 4-8G, the maximum is 192G, and the actual container memory is about 200G.

Because the virtual machine needs to leave a certain amount of CPU and memory overhead for the operating system itself, each application needs 6 16C32G virtual machines, where 16C32G is the second predetermined specification specified in the migration policy. The application concurrency in the cloud platform project is more than 100-1000, and the cloud platform project comprises 7 mechanisms and 28 application systems, wherein one mechanism comprises 4 application systems, so that 28 × 6-168 virtual machines are required, and 168/3-56 physical servers are required.

For an application to be migrated, the number of physical servers required for migrating the application to be migrated to the cloud platform is as follows: 6/3 ═ 2.

(III) low concurrency:

when the application concurrency amount of the application to be migrated is above 1000, the application level of the application to be migrated is high, that is, high concurrency. In this case, it is specified in the migration policy that each low-concurrent application to be migrated employs 6-copy high availability, and then under the mode that the application is divided into front-end + middleware + back-end, a total of 18 container services are required, which means that resources in the migration policy are container services, and the number of resources is 18.

Assuming that the low-concurrency application is taken as an example, the resource consumption of the container service of one low-concurrency application preset in the migration policy is as follows: the CPU is 1-2 cores, and the size of the JVM is 2-4G. The CPU and memory size required for this time 18 container services is about:

a CPU: 18 × 1-2 nuclei, up to 36 nuclei;

JVM: 18 x (2-4) G, the maximum is 72G, and the actual container internal storage is about 100G.

Because the virtual machine needs to leave a certain amount of CPU and memory overhead for the operating system itself, each application needs 3 16C32G virtual machines, where 16C32G is the second predetermined specification specified in the migration policy. Assuming that the application concurrency is lower than 100, there are 15 mechanisms and 30 application systems, wherein one mechanism has 2 application systems, so that 30 × 3-90 virtual machines are needed, and 90/3-30 physical servers are needed.

For an application to be migrated, the number of physical servers required for migrating the application to be migrated to the cloud platform is as follows: 3/3 is equal to 1.

It should be noted that the above listed migration policies for the application database to be migrated are also only examples, and the number of container services, the virtual machine specification, and the like specified in the migration policies may be determined according to actual situations, and are not limited specifically herein. It can also be seen from the foregoing embodiments that the higher the application level is, the greater the amount of physical server resources that need to be consumed when the application to be migrated is migrated to the cloud platform.

In the above embodiments, it is listed that the number of required physical servers can be calculated according to the concurrency condition of the application to be migrated, and planning and estimation of the support capacity can be supported. In addition, the number of the required physical servers can also be calculated according to the CPU usage, the content usage, and the like of the application to be migrated, and the specific calculation manner is similar to the above process, and is not repeatedly limited herein.

In an optional implementation manner, after the applications to be migrated are migrated to the cloud platform, the latest resource usage information of each application to be migrated can be continuously collected in real time; and then dynamically adjusting the resources allocated to each application to be migrated on the cloud platform before according to the collected new resource use information.

Specifically, when the resources allocated to each application to be migrated on the cloud platform before are dynamically adjusted according to the collected new resource usage information, the resource allocated to the application to be migrated with the changed application level is adjusted. Therefore, the application level of each application to be migrated needs to be determined again according to the use interval to which the collected new resource use information belongs; if the application level of the application to be migrated changes, adjusting the resources allocated to the application to be migrated on the cloud platform according to the migration policy corresponding to the changed application level, for example, the number of the resources in the migration policy changes before and after the application level changes.

In the embodiment of the present application, the resource may be periodically adjusted according to the collected new resource usage information. That is, when new collected resource usage information is used, the peak value of the resource usage information in a certain period is counted, and the application level of each application to be migrated is re-determined according to the usage interval to which the resource usage information in the period belongs. After the application level is changed, the allocation of resources is specifically adjusted according to the migration policy corresponding to the changed application level.

For example, when the application concurrency amount of the application 1 to be migrated is reduced from low concurrency to medium concurrency in a certain period, the number of physical servers allocated to the application 1 to be migrated needs to be increased. Specifically, for an application to be migrated 1, which is a front-end + back-end + database mode, before the change, the resources in the migration policy are virtual machines, and the number of the resources is 2, that is, each database needs 2 virtual machines, and the corresponding 2 virtual machines need 1 physical server; after the change, the resources in the migration policy are virtual machines, the number of the resources is 4, that is, each database needs 4 virtual machines, and the corresponding 4 virtual machines need 2 physical servers, so that the number of the physical servers allocated to the application 1 to be migrated needs to be increased from 1 to 2.

Through the above process, the application level of each application to be migrated may change, and a new application may be added to the cloud platform, so that the capacity of the cloud platform may be expanded according to the method in the embodiment of the present application, in addition to dynamically adjusting the resources allocated to each application to be migrated.

Fig. 4 is a schematic diagram of an architecture of a full-stack cloud platform in the embodiment of the present application, which specifically includes a unified cloud pipe, a cloud native platform, and a plurality of Region clusters.

In a general case, a full stack cloud is divided into a plurality of Region clusters, and assuming that each Region tentatively has 200 physical server capacities, the plurality of regions share a unified cloud pipe and a cloud native platform.

The unified cloud management system comprises a unified cloud management platform, a plurality of cloud management nodes and monitoring nodes, wherein the unified cloud management is a unified portal platform and mainly comprises the plurality of cloud management nodes and the monitoring nodes; the cloud native platform comprises a plurality of monitoring nodes and management nodes, and further comprises a maintenance node.

In the embodiment of the application, a cloud platform management and control node, referred to as a cloud management node for short, is a cluster management node and is responsible for managing machines in a Region; the monitoring node refers to a resource monitoring report platform and is used for monitoring cloud platform resources; the management node is used for managing the cloud originality and is a management and control node for managing the cloud originality; and the maintenance node is responsible for the state maintenance of cloud originality.

Referring to fig. 5A, which is a Region part in fig. 4, in each Region cluster, a cluster controller (cloud platform management node) is required, and a plurality of additional computing nodes are required. The computing nodes, namely the cloud platform computing node part in fig. 5A, here include a plurality of computing nodes, which are nodes hatched by the host; the cloud platform management node, that is, the physical and chemical deployment part of the cloud platform management node in fig. 5A, is located on the left side of the cloud platform computing node part, and includes a plurality of management nodes and middleware. The middleware refers to a database and a message queue node of cluster management.

In addition, the system further includes a cloud native service cluster part, specifically referring to fig. 5B, in this embodiment, the cloud native service cluster part is mainly used for transforming the application program into a container service, where the cloud native service cluster is deployed on the virtual machine. As shown in fig. 5B, the application mainly includes a front end, a back end, and a DB (Data base) of the application, where the DB includes a master DB and a slave DB, which are all directly or indirectly deployed on the virtual machine. Wherein the storage pool is used for providing storage capacity for the cloud native container service; node (Node) refers to a Node for hatching a cloud native container service; the Master (control Node) refers to a cloud native cluster management Node, the specification of which is 16C32G, and the cloud native service cluster shown in fig. 4, 5A and 5B is composed of 3 masters and a plurality of Node nodes, wherein each Node runs a plurality of Pod, each Pod is abstracted to represent a group of application containers, and the Pod also has resources shared by the containers. . Each Node is managed by a Master, and meanwhile the Master automatically schedules Pod on the cloud native service cluster. The automatic scheduling of the Master takes into account the available resources on each Node.

According to the business condition of a user department, the tenants are divided, virtual machines under each tenant form cloud native business clusters, each department has at least one business cluster, the number of virtual machines of management nodes required by each tenant can be estimated according to the business condition, and the number of required physical servers is further converted.

In the embodiment of the application, the required virtual machines can be calculated according to different migration strategies corresponding to the concurrency condition and the like of the application, and the number of the required physical servers can be calculated according to the virtualization capacity of the physical servers; and then calculating the cluster control number according to the divided Region number, and finally adding a uniform cloud pipe and a cloud native pipe control node to obtain the total resource consumption of the physical server of the migrated full-stack cloud. After the total resource consumption is estimated, corresponding resources are created and reserved according to the estimated resources, and preparation is made for cloud migration, so that subsequent cloud migration is realized.

Referring to fig. 6, a flowchart of a complete method for migrating an application to a cloud platform is shown. The specific implementation flow of the method is as follows:

step S61: acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

step S62: determining a use interval to which a peak value of resource use information of each application to be migrated belongs within a preset time period;

step S63: respectively taking the application grade corresponding to the use interval to which each resource use information belongs as the application grade of each application to be migrated;

step S64': for the applications to be migrated in the front-end + back-end + database mode, determining the number of physical servers required for migrating each application to be migrated to the cloud platform according to the migration position and the resource number of the database in the migration strategy corresponding to the application to be migrated;

step S64 ″: for the applications to be migrated in the front-end mode, the middleware mode and the back-end mode, determining the number of physical servers required for migrating each application to be migrated to the cloud platform according to the number of container services in the migration strategy corresponding to each application to be migrated;

step S65: establishing and reserving corresponding resources on the cloud platform according to the obtained number of the physical servers;

step S66: and migrating each application to be migrated to the cloud platform.

As shown in fig. 7, which is a schematic structural diagram of an apparatus 700 for migrating an application to a cloud platform in an embodiment of the present application, the apparatus may include:

an information obtaining unit 701, configured to obtain resource usage information of each application to be migrated that needs to be migrated to the cloud platform;

a ranking unit 702, configured to determine an application rank of each application to be migrated according to resource usage information of each application to be migrated;

an estimating unit 703, configured to obtain, according to a migration policy corresponding to an application level of each application to be migrated, the number of physical servers required to migrate each application to be migrated to the cloud platform;

a migration unit 704, configured to create and reserve corresponding resources on the cloud platform according to the obtained number of the physical servers, and migrate each application to be migrated to the cloud platform.

According to the embodiment of the application, before the application to be migrated is migrated to the cloud platform, the service condition of the application resources is analyzed through the acquired resource use information of each application to be migrated, different application levels are divided for the application to be migrated, different migration strategies are formulated for the applications to be migrated at different application levels, and different resources are allocated, so that the service condition of the resources can be well estimated in advance in the full-stack cloud migration process, the resources can be conveniently estimated in the whole cloud migration process, guidance is provided for the cloud migration process of the application, the cloud migration process of the application is more convenient and efficient, and the method can be further used for subsequent data center cluster expansion.

Optionally, the ranking unit 702 is specifically configured to:

determining a use interval to which resource use information of each application to be migrated belongs, wherein the use interval is divided in advance according to a preset threshold;

and respectively taking the application level corresponding to the use interval to which each piece of resource use information belongs as the application level of each application to be migrated, wherein the larger the range of the use interval is, the higher the application level corresponding to the use interval is.

Optionally, the ranking unit 702 is specifically configured to:

and respectively taking the use interval in which the peak value of the resource use information of each application to be migrated is located in the preset time period as the use interval to which the resource information of each application to be migrated belongs.

Optionally, the migration policy includes resources and resource quantity allocated to the application to be migrated, and the resources or resource quantity in the migration policies corresponding to different application levels are different; the estimation unit 703 is specifically configured to:

if the resources in the migration strategy comprise physical servers or virtual machines, determining the number of the physical servers required for migrating the application to be migrated to the cloud platform according to the migration position and the number of the resources of the database in the migration strategy corresponding to the application to be migrated, wherein the migration position represents the resources occupied when the database of the application to be migrated is migrated to the cloud platform; or

If the resources in the migration policy include container services, determining the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of the container services in the migration policy corresponding to the application to be migrated, wherein the number of the container services represents the number of the container services required for migrating the application to be migrated to the cloud platform, and the higher the application level of the application to be migrated is, the larger the number of the container services in the migration policy corresponding to the application level is.

Optionally, the resource in the migration policy includes a physical server or a virtual machine; the estimation unit 703 is specifically configured to:

if the migration position is a physical server, acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of physical servers required for each database preset in the migration strategy;

if the migration position is a virtual machine, the number of the physical servers required for migrating the application to be migrated to the cloud platform is obtained according to the number of the virtual machines required by each database preset in the migration strategy and the conversion number corresponding to the first preset specification of the virtual machine, wherein the conversion number corresponding to the first preset specification is obtained according to the mapping relation between the preset virtual machine specification and the conversion number.

Optionally, the resources in the migration policy include container services, and the migration policy further includes resource consumption of the container services; the estimation unit 703 is specifically configured to:

estimating resource consumption required by all container services according to the number of the container services in the migration strategy corresponding to the application to be migrated and the resource consumption of each container service;

determining the number of virtual machines of a second preset specification required for migrating the application to be migrated to the cloud platform according to the estimated resource consumption required by all container services;

and acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the determined number of the required virtual machines and the converted number corresponding to the second preset specification of the virtual machines, wherein the converted number corresponding to the second preset specification is acquired according to a mapping relation between the preset virtual machine specification and the converted number.

Optionally, the mapping relationship between the virtual machine specification and the reduced number is configured in advance according to the specification of the physical server, and the reduced number refers to the number of virtual machines of each specification that can be supported by the physical server of the target specification.

Optionally, the apparatus further comprises:

an updating unit 705, configured to collect new resource usage information of each application to be migrated in real time;

re-determining the application level of each application to be migrated according to the use interval to which the collected new resource use information belongs;

and if the application level of the application to be migrated is changed, adjusting resources allocated to the application to be migrated on the cloud platform according to a migration strategy corresponding to the changed application level.

For convenience of description, the above parts are separately described as modules (or units) according to functional division. Of course, the functionality of the various modules (or units) may be implemented in the same one or more pieces of software or hardware when implementing the present application.

Having described the method and apparatus for migrating an application to a cloud platform according to an exemplary embodiment of the present application, an electronic device according to another exemplary embodiment of the present application is described next.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

Fig. 8 is a block diagram illustrating an electronic device 800 according to an example embodiment, the apparatus comprising:

a processor 810;

a memory 820 for storing instructions executable by the processor 810;

wherein the processor 810 is configured to execute instructions to implement the steps of the method of migrating an application to a cloud platform in an embodiment of the present disclosure, such as the steps shown in fig. 2.

In an exemplary embodiment, a storage medium comprising instructions, such as the memory 820 comprising instructions, executable by the processor 810 of the electronic device 800 to perform the above-described method is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, for example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an alternative embodiment, the present application further provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for migrating the application to the cloud platform provided in the various optional implementation manners in the above embodiments.

In some alternative embodiments, various aspects of the method for migrating an application to a cloud platform provided by the present application may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of the method for migrating an application to a cloud platform according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the steps as shown in fig. 2.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product of embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a computing device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with a command execution system, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with a command execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (15)

1. A method of migrating an application to a cloud platform, the method comprising:

acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

determining the application level of each application to be migrated according to the resource use information of each application to be migrated;

acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to a migration strategy corresponding to the application level of each application to be migrated;

and migrating each application to be migrated to the cloud platform after corresponding resources are created and reserved on the cloud platform according to the acquired number of the physical servers.

2. The method according to claim 1, wherein the determining the application level of each application to be migrated according to the resource usage information of each application to be migrated specifically includes:

determining a use interval to which the resource use information of each application to be migrated belongs, wherein the use interval is divided in advance according to a preset threshold;

and respectively taking the application level corresponding to the use interval to which each piece of resource use information belongs as the application level of each to-be-migrated application, wherein the larger the range of the use interval is, the higher the application level corresponding to the use interval is.

3. The method according to claim 2, wherein the determining the usage interval to which the resource usage information of each application to be migrated belongs specifically includes:

and respectively taking the use interval in which the peak value of the resource use information of each application to be migrated is located in a preset time period as the use interval to which the resource information of each application to be migrated belongs.

4. The method according to claim 1, wherein the migration policy includes resources and resource quantity allocated to the application to be migrated, and the resources or resource quantity in the migration policy corresponding to different application levels are different; when the number of physical servers required for migrating each application to be migrated to the cloud platform is obtained according to the migration policy corresponding to the application level of each application to be migrated, the method specifically includes, for any one application to be migrated:

if the resources in the migration policy comprise physical servers or virtual machines, determining the number of the physical servers required for migrating the application to be migrated to the cloud platform according to the migration position and the number of the resources of the database in the migration policy corresponding to the application to be migrated, wherein the migration position represents the resources occupied when the database of the application to be migrated is migrated to the cloud platform; or

If the resources in the migration policy include container services, determining the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of the container services in the migration policy corresponding to the application to be migrated, where the number of the container services represents the number of the container services required for migrating the application to be migrated to the cloud platform, and the higher the application level of the application to be migrated is, the larger the number of the container services in the migration policy corresponding to the application level is.

5. The method of claim 4, wherein the resources in the migration policy comprise physical servers or virtual machines;

the determining, according to the migration position of the database in the migration policy corresponding to the application to be migrated, the number of physical servers required to migrate the application to be migrated to the cloud platform includes:

if the migration position is a physical server, acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of physical servers required for each database preset in the migration strategy;

if the migration position is a virtual machine, obtaining the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of virtual machines required by each database preset in the migration strategy and the reduced number corresponding to a first preset specification of the virtual machine, wherein the reduced number corresponding to the first preset specification is obtained according to a mapping relation between the preset virtual machine specification and the reduced number.

6. The method of claim 4, wherein the resources in the migration policy include container services, the migration policy further including resource consumption of the container services;

the determining, according to the number of container services in the migration policy corresponding to the application to be migrated, the number of physical servers required to migrate the application to be migrated to the cloud platform includes:

estimating resource consumption required by all container services according to the number of the container services in the migration strategy corresponding to the application to be migrated and the resource consumption of each container service;

determining the number of virtual machines of a second preset specification required for migrating the application to be migrated to the cloud platform according to the estimated resource consumption required by all container services;

and acquiring the number of physical servers required for migrating the application to be migrated to the cloud platform according to the determined number of the required virtual machines and the reduced number corresponding to a second preset specification of the virtual machines, wherein the reduced number corresponding to the second preset specification is acquired according to a mapping relation between the preset virtual machine specification and the reduced number.

7. The method according to claim 5 or 6, wherein the mapping relationship between the virtual machine specification and the reduced number is configured in advance according to the specification of the physical server, and the reduced number refers to the number of virtual machines of each specification that can be supported by the physical server of the target specification.

8. The method of any one of claims 1 to 6, further comprising:

collecting new resource use information of each application to be migrated in real time;

re-determining the application level of each application to be migrated according to the use interval to which the collected new resource use information belongs;

if the application level of the application to be migrated changes, adjusting resources allocated to the application to be migrated on the cloud platform according to a migration strategy corresponding to the changed application level.

9. An apparatus for migrating an application to a cloud platform, comprising:

the information acquisition unit is used for acquiring resource use information of each application to be migrated, which needs to be migrated to the cloud platform;

the grade dividing unit is used for determining the application grade of each application to be migrated according to the resource use information of each application to be migrated;

the pre-estimation unit is used for acquiring the number of physical servers required for migrating each application to be migrated to the cloud platform according to the migration strategy corresponding to the application level of each application to be migrated;

and the migration unit is used for creating and reserving corresponding resources on the cloud platform according to the acquired number of the physical servers and then migrating each application to be migrated to the cloud platform.

10. The apparatus of claim 9, wherein the ranking unit is specifically configured to:

determining a use interval to which the resource use information of each application to be migrated belongs, wherein the use interval is divided in advance according to a preset threshold;

and respectively taking the application level corresponding to the use interval to which each piece of resource use information belongs as the application level of each to-be-migrated application, wherein the larger the range of the use interval is, the higher the application level corresponding to the use interval is.

11. The apparatus of claim 10, wherein the ranking unit is specifically configured to:

and respectively taking the use interval in which the peak value of the resource use information of each application to be migrated is located in a preset time period as the use interval to which the resource information of each application to be migrated belongs.

12. The apparatus according to claim 9, wherein the migration policy includes resources and resource quantity allocated to the application to be migrated, and the resources or resource quantity in the migration policy corresponding to different application levels are different; the estimation unit is specifically configured to:

if the resources in the migration policy comprise physical servers or virtual machines, determining the number of the physical servers required for migrating the application to be migrated to the cloud platform according to the migration position and the number of the resources of the database in the migration policy corresponding to the application to be migrated, wherein the migration position represents the resources occupied when the database of the application to be migrated is migrated to the cloud platform; or

If the resources in the migration policy include container services, determining the number of physical servers required for migrating the application to be migrated to the cloud platform according to the number of the container services in the migration policy corresponding to the application to be migrated, where the number of the container services represents the number of the container services required for migrating the application to be migrated to the cloud platform, and the higher the application level of the application to be migrated is, the larger the number of the container services in the migration policy corresponding to the application level is.

13. The apparatus of any of claims 9 to 12, further comprising:

the updating unit is used for collecting new resource use information of each application to be migrated in real time;

re-determining the application level of each application to be migrated according to the use interval to which the collected new resource use information belongs;

if the application level of the application to be migrated changes, adjusting resources allocated to the application to be migrated on the cloud platform according to a migration strategy corresponding to the changed application level.

14. An electronic device, comprising a processor and a memory, wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 8.

15. A computer-readable storage medium, characterized in that it comprises program code for causing an electronic device to perform the steps of the method of any of claims 1-8, when said program code is run on the electronic device.

Images