CN106713375A - Method and device for allocating cloud resources - Google Patents

Abstract

The invention discloses a method and device for allocating cloud resources. The method is applied to a cloud platform including a first cloud domain and a second cloud domain. The method includes: acquiring resource requirements of an account in the first cloud domain; Based on the resource requirements, it is judged whether the first cloud domain provides enough resources; if the first cloud domain cannot provide enough resources, based on the resource requirements, at least Partially reallocated to the first cloud domain; wherein, the first cloud domain is a private cloud domain, and the second cloud domain is a public cloud domain; or, the first cloud domain is a public cloud domain, and the The second cloud domain is a private cloud domain.

Description

Method and device for allocating cloud resources

technical field

The present invention relates to the technical field of cloud computing, in particular to a method and device for allocating cloud resources.

Background technique

With the development of cloud computing, cloud platforms and cloud computing are used more and more frequently. Cloud resources can generally be divided into public cloud resources and private cloud resources.

Public cloud refers to standard cloud computing services provided by third-party providers for public accounts. Users can directly access the public cloud platform through the Internet to obtain the required infrastructure as a service (Infrastructure as a Service, IAAS), platform as a service (Platform as a service) -as-a-Service, PAAS) and Software as a Service (Software as a Service, SAAS). The public cloud can provide accounts with fast delivery and on-demand consumption capabilities.

The private cloud is generally deployed inside the firewall and built separately within the enterprise to provide the required IAAS, PAAS, SAAS and other resource services for various information technology systems within the unit. Private cloud has many advantages for integrating various information technology resources and improving utilization.

Public cloud and private cloud are relatively mature ways of providing cloud computing services, but the cost of building private cloud and public cloud separately is too high to effectively reduce costs and increase efficiency. In order to achieve profitability on the basis of improving the overall utilization rate of the cloud platform, more companies choose the architecture of hybrid cloud. The hybrid cloud system is based on the construction of private cloud, and provides the cloud resources corresponding to the private cloud to external users through network isolation. . However, how to allocate cloud resources to private cloud domains and public cloud domains more reasonably and how to deploy cloud resources in hybrid cloud.

Contents of the invention

In view of this, the embodiments of the present invention expect to provide a cloud resource allocation method and device, which can at least partially solve the problem of cloud resource allocation between public cloud domains and private cloud domains in a hybrid cloud.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

The first aspect of the embodiments of the present invention provides a method for allocating cloud resources. The method is applied to a cloud platform including a first cloud domain and a second cloud domain. The method includes:

Obtain resource requirements of accounts in the first cloud domain;

Based on the resource requirements, determine whether the first cloud domain provides sufficient resources;

If the first cloud domain cannot provide sufficient resources, reallocate at least part of the idle resources of the second cloud domain to the first cloud domain based on the resource requirements;

Wherein, the first cloud domain is a private cloud domain, and the second cloud domain is a public cloud domain; or, the first cloud domain is a public cloud domain, and the second cloud domain is a private cloud domain.

Based on the above scheme, the method also includes:

determining priority parameters for said resource requirements;

Based on the priority parameter, allocate resources in the first cloud domain to corresponding accounts, so as to meet the resource requirements.

Based on the above solution, the determination of the priority parameters of the resource requirements includes:

calculating an application weight for the resource requirement;

The priority parameter is calculated based on the application time of the resource requirement, the application weight, and a preset functional relationship.

Based on the above solution, the calculation of the application weight of the resource requirement includes:

The application weight is calculated based on at least one of the account level corresponding to the resource requirement, the resource type parameter required by the resource requirement, and the resource quantity parameter required by the resource requirement.

Based on the above solution, the acquisition of resource requirements of accounts in the first cloud domain includes:

Obtain the resource requirements of the account within the first specified time;

The determining whether the first cloud domain provides sufficient resources based on the resource requirements includes:

Within a second specified time, based on the resource requirements of each of the accounts, determine whether the first cloud domain provides sufficient resources;

The second specified time is later than the second specified time.

Based on the above solution, if the first cloud domain cannot provide sufficient resources, reallocating at least part of the idle resources of the second cloud domain to the first cloud domain based on the resource requirements includes:

Counting idle PAAS resources and/or SAAS resources in the second cloud domain;

Based on the resource requirements, allocate the idle PAAS resources and SAAS resources to the first cloud domain.

The second aspect of the embodiment of the present invention provides a cloud resource allocation device, the device is applied to a cloud platform including a first cloud domain and a second cloud domain, and the device includes:

An acquisition unit, configured to acquire resource requirements of accounts in the first cloud domain;

a judging unit, configured to judge whether the first cloud domain provides sufficient resources based on the resource requirements;

An allocation unit, configured to reallocate at least part of the idle resources of the second cloud domain to the first cloud domain based on the resource requirements if the first cloud domain cannot provide sufficient resources;

Wherein, the first cloud domain is a private cloud domain, and the second cloud domain is a public cloud domain; or, the first cloud domain is a public cloud domain, and the second cloud domain is a private cloud domain.

Based on the above scheme, the device also includes:

a determining unit, configured to determine a priority parameter of the resource requirement;

The allocating unit is further configured to allocate resources of the first cloud domain to corresponding accounts based on the priority parameter, so as to meet the resource requirement.

Based on the above solution, the determination unit is configured to calculate the application weight of the resource requirement; and calculate the priority parameter based on the application time of the resource requirement, the application weight and a preset functional relationship.

Based on the above solution, the determining unit specifically uses at least one of the account level corresponding to the resource requirement, the resource type parameter required by the resource requirement, and the resource quantity parameter required by the resource requirement to calculate the Application weight.

Based on the above solution, the acquiring unit is specifically configured to acquire the resource requirements of the account within the first specified time;

The judging unit is specifically configured to judge whether the first cloud domain provides sufficient resources based on the resource requirements of each of the accounts within a second specified time; the second specified time is later than the first specified time 2. Designated time.

Based on the above solution, the allocation unit is specifically configured to count idle PAAS resources and/or SAAS resources in the second cloud domain;

Based on the resource requirements, allocate the idle PAAS resources and SAAS resources to the first cloud domain.

The cloud resource allocation method and device described in the embodiments of the present invention will judge whether the first cloud domain can provide enough resources according to the resource requirements of the first cloud domain, and if not, divide the idle resources from the second cloud domain In this case, first of all, it is a dynamic resource allocation method, which obviously meets the resource requirements and utilizes resources more efficiently; Cloud resources in the cloud domain are provisioned in a unified manner.

Description of drawings

FIG. 1 is one of the schematic flow diagrams of the method for scheduling cloud resources according to an embodiment of the present invention;

FIG. 2 is the second schematic flow diagram of the cloud resource scheduling method according to the embodiment of the present invention;

3 is a schematic structural diagram of a cloud resource scheduling device according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a hybrid cloud provided by an embodiment of the present invention;

FIG. 5 is the third schematic flow diagram of the cloud resource scheduling method according to the embodiment of the present invention;

FIG. 6 is the fourth schematic flow diagram of the cloud resource scheduling method according to the embodiment of the present invention;

FIG. 7 is the fifth schematic flow diagram of the cloud resource scheduling method according to the embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a database resource provided by an embodiment of the present invention;

FIG. 9 is a schematic flowchart of database migration provided by an embodiment of the present invention.

detailed description

The technical solutions of the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Method example:

As shown in FIG. 1, this embodiment provides a method for allocating cloud resources. The method is applied to a cloud platform including a first cloud domain and a second cloud domain. The method includes:

Step S110: Obtain resource requirements of accounts in the first cloud domain;

Step S120: Based on the resource requirements, determine whether the first cloud domain provides sufficient resources;

Step S130: If the first cloud domain cannot provide enough resources, reallocate at least part of the idle resources of the second cloud domain to the first cloud domain based on the resource requirement;

Wherein, the first cloud domain is a private cloud domain, and the second cloud domain is a public cloud domain; or, the first cloud domain is a public cloud domain, and the second cloud domain is a private cloud domain.

The cloud platform described in this embodiment may be a hybrid cloud platform of a private cloud domain and a public cloud domain. The cloud platform can provide various operational resources.

The step S110 in this embodiment is obtained by receiving the expansion application of each account; it can also be obtained by monitoring the cloud service status of each account.

The account of the public cloud domain described in this embodiment is an external account. The account of the private cloud domain is a content account of the hybrid cloud platform, such as an account of each part of an enterprise provided with a hybrid cloud. According to the current work tasks of each part, the transportation resources required may change. In this embodiment, in order to better realize the unified management of cloud resources in the hybrid cloud, and at the same time rationally allocate the operation resources included in the private cloud domain and the public cloud domain, in this embodiment, when the resource requirements of a first cloud domain cannot be determined by this When the cloud resources of the cloud domain are satisfied, at least part of the idle resources in another cloud domain will be re-allocated and re-divided through dynamic allocation, so as to meet the cloud domain with resource requirements. Obviously, in this case, not only can the dynamic allocation and management of cloud resources in the private cloud domain and public cloud domain in the hybrid cloud be realized, but also the effective utilization of cloud resources can be improved.

In step S130, redeploying resources of the second cloud domain to the first cloud domain may specifically include:

Calculate resources to be re-allocated according to resource requirements and cloud resources available for allocation in the first cloud domain;

Determining idle resources available from the second cloud domain;

Determining to allocate resources based on the resources to be reallocated and the idle resources.

Calculating the re-allocated resources may include calculating the re-allocated resource type and resource quantity, and the like. Of course, determining idle resources also includes determining the type and quantity of idle resources that can be provided by the second cloud domain.

As shown in Figure 2, as a further improvement of this embodiment, the method further includes:

Step S140: determining the priority parameters of the resource requirements;

Step S150: Allocate resources of the first cloud domain to corresponding accounts based on the priority parameters, so as to meet the resource requirements.

Different resource requirements have different urgency and service requirements, which are represented by priority parameters in this embodiment. For example, different accounts in the public cloud domain correspond to different account levels. Generally, the higher the level of the account, the higher the service level it requires, and the higher the corresponding priority parameter.

Step S140 and step S150 in this embodiment may be completed after step S130, may be executed before step S130, or may be executed after step S130. For example, the first cloud domain receives multiple capacity expansion applications at the same time. The remaining unused cloud resources in the first cloud domain can meet the resource requirements in part of the expansion application. In order to improve the response speed, the remaining cloud resources currently owned in the first cloud domain can be processed before step S130 is performed. Perform deployment to achieve cloud resource provisioning response as soon as possible. In the present application, the priority parameter is also determined in step S140. Generally, the higher the priority parameter, the higher the urgency to meet the resource demand is. Therefore, when performing the step S150, priority will be given to those with higher priority parameters. Resource requirements provision cloud resources.

Specifically, as described step S140 includes:

calculating an application weight for the resource requirement;

The priority parameter is calculated based on the application time of the resource requirement, the application weight, and a preset functional relationship.

The application weight can represent the urgency of meeting the resource requirement from a non-time dimension. The application time is the time when the capacity expansion application including the resource requirement is submitted, or it may be the application time of the capacity expansion application formed after the resource management device detects the resource requirement according to the situation. Generally, the earlier the application time is, the higher priority should be met. Usually, the application time is positively correlated with the priority parameter.

In the preset functional relationship, priority parameters corresponding to resource requirements can be calculated by taking the application weight and the application time as dependent variables. In this case, the priority represents the urgency of satisfying the resource requirement from the time dimension and the non-time dimension.

In the specific implementation process, if a certain expansion application is late, although the application weight is small, it is a special emergency resource demand that needs to be adjusted in priority. In this embodiment, for this Emergency resource requirements In this embodiment, an adjustment factor is also introduced, and the priority parameter of the emergency resource requirements is increased by increasing the adjustment factor. Of course, there is also a situation where the capacity expansion application itself is pre-applied and is not in a hurry to use. At this time, the priority parameter can also be reduced through the adjustment factor.

There are many kinds of functional relationships, and a specific example is provided below:

Priority _n = X ^SLAn *time _n *weight _n

Wherein, the Priority _n is the priority parameter of the nth resource requirement; the weight _n is the application weight of the nth resource requirement; the time _n is the application time of the nth resource requirement; The ^XSLAn is an adjustment factor for the nth resource requirement. The adjustment factor can be a positive number.

In this embodiment, the calculation of the application weight of the resource requirement includes:

The application weight is calculated based on at least one of the account level corresponding to the resource requirement, the resource type parameter required by the resource requirement, and the resource quantity parameter required by the resource requirement.

Generally, the higher the account level, the higher the urgency with which the hybrid cloud needs to meet its resource requirements. In the aforementioned function, the generation account of the nth resource requirement is SLA _n .

The types of cloud resources required by the resource requirements can be classified into database resources, middleware resources and external application resources.

For example, when the resource type is the database resource, the resource type parameters for calculating the application weight may include: the recovery time objective parameter RTO required by the resource requirement, the recovery point objective parameter RPO and the backup parameter required by the resource requirement Wait. When the resource type is the database resource, the resource quantity parameters used to calculate the application weight may include: storage capacity and memory capacity.

For example, when the resource type is the middleware, the resource type parameter for calculating the application weight may include: the resource requirement requires a thread pool parameter. When the resource type is the middleware, the resource quantity parameters used to calculate the application weight may include: the number of concurrent threads and other parameters.

In order to avoid repeated changes in the cloud domain to which cloud resources belong, which is inconvenient for unified management, and at the same time to improve resource allocation strategies. In this embodiment, the step S110 may include: obtaining resource requirements of the account within a first specified time. The step S120 includes: within a second specified time, based on the resource requirements of each of the accounts, judging whether the first cloud domain provides sufficient resources; the second specified time is later than the second specified time time.

In this case, only resource requirements are obtained within the first specified time, such as only capacity expansion applications are received, and capacity expansion applications are not responded to temporarily. Start unified processing at the second designated time to obtain resource requirements in the first time. Specifically, for example, the first specified time length is 24 hours, and when the 24 hours are reached, deployment of operation resources is started to meet the resource requirements. When the resource requirement is satisfied, a cycle of obtaining the resource requirement begins.

In this embodiment, in order to implement the deployment of the cloud resources between the private cloud domain and the public cloud domain simply and dynamically, it is based on the allocation of PAAS resources and SAAS resources in this embodiment. After PAAS resources and SAAS resources are divided into cloud domains, they can be used directly without reinstalling programs and other operations, and can realize simple cloud resource allocation.

Specifically, the step S130 may include:

Counting idle PAAS resources and/or SAAS resources in the second cloud domain;

Based on the resource requirements, allocate the idle PAAS resources and PAAS resources to the first cloud domain.

When deploying the PAAS resources and the SAAS in this embodiment, if the private cloud domain and the public cloud domain belong to different virtual local area networks, it can be realized by modifying the virtual local area network to which the network protocol IP address of the resource belongs. If the private cloud domain and the public cloud domain are implemented through access control list (Access Control List, ACL) control, it can be implemented by modifying the access control list.

The deployment method of cloud resources described in this embodiment can firstly perform unified management and dynamic deployment of cloud resources in hybrid cloud domains, which breaks the limitations of static deployment in the prior art and satisfies the requirements of private cloud domains and public cloud domains. Dynamic resource requirements, while improving the effective utilization of transportation resources, and improving the overall processing efficiency of the hybrid cloud platform.

Embodiments of devices capable of implementing the above method embodiments are provided below in conjunction with the above method embodiments.

Device example:

As shown in FIG. 3 , this embodiment provides a device for allocating cloud resources. The device is applied to a cloud platform including a first cloud domain and a second cloud domain. The device includes:

An acquisition unit 110, configured to acquire resource requirements of accounts in the first cloud domain;

A judging unit 120, configured to judge whether the first cloud domain provides sufficient resources based on the resource requirement;

An allocation unit 130, configured to reallocate at least part of the idle resources of the second cloud domain to the first cloud domain based on the resource requirement if the first cloud domain cannot provide sufficient resources;

Wherein, the first cloud domain is a private cloud domain, and the second cloud domain is a public cloud domain; or, the first cloud domain is a public cloud domain, and the second cloud domain is a private cloud domain.

The device for allocating cloud resources described in this embodiment may be one or more cloud management devices or cloud management servers. The specific structure of the acquisition unit 110 may include a communication interface for receiving the expansion application including the resource requirement sent by each account or the monitoring data sent by the monitoring device. The obtaining unit 110 may further include a processor or a processing circuit, configured to obtain the resource requirement by analyzing the monitoring data.

The specific structures of the judgment unit 120 and the deployment unit 130 may include a processor or a processing circuit. The processor or processing circuit may be executed by codes to realize the above-mentioned functions of the judgment unit 120 and the allocation unit 130 and the function of the acquisition unit 110 for analyzing resource requirements.

The processor may include a central processing unit CPU, a microprocessor MCU, a digital signal processor or a programmable array PLC and the like. The processing circuit may include an application specific integrated circuit ASIC or the like.

In short, the device described in this embodiment can uniformly manage and allocate cloud resources in private cloud domains and public cloud domains, and dynamically allocate cloud resources according to the resource requirements of the two cloud domains, thereby improving the utilization efficiency of cloud resources.

The device also includes:

a determining unit, configured to determine a priority parameter of the resource requirement;

The allocating unit 130 is further configured to allocate resources of the first cloud domain to corresponding accounts based on the priority parameters, so as to meet the resource requirements.

The specific structure of the determining unit described in this embodiment may also include the above-mentioned processor or processing circuit, or a calculator with a calculation function. Through the input of variables, the priority parameter is calculated according to the preset function relationship. In this embodiment, the allocation unit 130 can determine the order of meeting multiple resource requirements according to the priority parameters, and satisfy each resource requirement in turn; thereby realizing priority satisfaction of resource requirements with high urgency, thereby improving user usage satisfaction.

The determination unit is configured to calculate the application weight of the resource requirement; and calculate the priority parameter based on the application time of the resource requirement, the application weight and a preset functional relationship.

The determining unit in this embodiment includes a calculator for calculating the application weight, which reads parameters such as application time when the resource is required, and calculates based on a preset functional relationship. For the preset functional relationship described in this embodiment, reference may be made to the foregoing method embodiments.

The determining unit specifically uses at least one of the account level corresponding to the resource requirement, the resource type parameter required by the resource requirement, and the resource quantity parameter required by the resource requirement to calculate the application weight. Here, it is further disclosed that the determining unit calculates the variables of the application weight, and these variables can accurately indicate the urgency of resource requirements, thereby improving user satisfaction.

In addition, the acquiring unit 110 is specifically configured to acquire resource requirements of accounts within a first specified time; the judging unit 120 is specifically configured to, within a second specified time, based on the resource requirements of each account, Judging whether the first cloud domain provides sufficient resources; the second specified time is later than the second specified time.

In this embodiment, the first designated time does not respond to resource requirements, that is, cloud resource allocation is not performed, and only the resource requirements are obtained, and unified response and centralized processing are performed at the second designated time. In this case, it is possible to improve Processing efficiency.

The allocation unit 130 is specifically configured to count idle PAAS resources and/or SAAS resources in the second cloud domain; and divide the idle PAAS resources and SAAS resources into the first cloud domain based on the resource requirements . In this embodiment, the allocation unit 130 includes a counter or a processor or a processing circuit with a calculation function, and determines the idle PAAS resources and/or SAAS resources available for allocation in the second cloud domain by counting.

In this embodiment, the allocation unit 130 is the result of directly allocating PAAS resources and SAAS resources, which can be realized by re-dividing the virtual local area network to which the PAAS resources and SAAS resources belong or updating the ACL when performing PAAS resources and SAAS resources; simple features.

Several specific examples are provided below in conjunction with any of the foregoing embodiments.

Example one:

As shown in FIG. 4 , a hybrid cloud to which the method described in the embodiment of the present invention can be applied is shown. The hybrid cloud shown in Figure 4 includes resource management and control devices, public cloud domain storage resources, private cloud domain storage resources, PAAS cluster 11, PAAS cluster 12, virtual machine control center vCenter, PAAS cluster 11, PAAS cluster 12 and all levels gateway device. The gateway devices at all levels here include routers and the like.

In the resource management device in the hybrid cloud shown in FIG. 4 , the hybrid cloud is divided into a private cloud domain and a public cloud domain. The private cloud domain currently includes PAAS cluster 11, PAAS cluster 12 and vCenter; the public cloud domain currently includes PAAS cluster 1 and PAAS cluster 2. The public cloud domain belongs to the virtual network-based VLAN2, and the private cloud domain belongs to the virtual local area network VLAN1. A firewall is set between VLAN1 and VLAN2. Both the private cloud domain and the public cloud domain can realize business convergence and connect to the core network, inline isolation zone DMZ, outlink DMZ, core production area, customer service system, network protocol IP private network, intrusion detection IDS equipment, data Communication Network DCN, China Internet CMNET. Of course, when the hybrid cloud is finally connected to an external network, such as CMNET, it will be connected through a firewall and an external gateway.

The specific connection structure of the hybrid cloud in this example can be referred to the figure, and will not be described in detail again.

The hybrid cloud described in FIG. 4 can implement the dynamic allocation and management of cloud resources in the private cloud domain and the public cloud domain by applying the aforementioned method embodiments. The resource management and control device in FIG. 4 can be used as the cloud resource allocation device described in the device embodiment.

As can be seen from Figure 4, in this example, a hybrid cloud is built in a domain-divided mode, and the border security is divided between private cloud domains, public cloud domains, and resource management and control devices through strict VLAN and ACL access control. In order to meet the dynamic allocation of hybrid cloud computing resources, private cloud domains and public cloud domain host resources are connected and converged to a unified business aggregation switch network. Firewalls are deployed between PAAS intelligent management and public cloud domains for port isolation and two-way access control.

In the hybrid cloud shown in Figure 4, both the public cloud domain and the private cloud domain have logically independent PAAS resource pools. When users apply for new or expand PAAS resources, they will be obtained from the public cloud domain first. If the current remaining cloud resources are insufficient When the demand is met, the intelligent resource management and control device is triggered to apply for cloud resources from the private cloud domain. The resource analysis module of the private cloud domain calculates the minimum PAAS resource unit that can be provided, and the intelligent management and control module adds this unit to the public cloud domain. The public cloud domain dynamically reorganizes various platform resources through the PAAS resource adaptation module to achieve two Resource allocation for resource domains. The minimum PAAS resource unit here is the minimum resource amount for a cloud resource scheduling. Here, this provisioning method is also applicable to private cloud domains deploying resources from public cloud domains; of course, it is also applicable to SAAS resource provisioning between public cloud domains and private cloud domains.

Example two:

As shown in Figure 5, this example can be a dynamic allocation method based on the mixed PAAS resources shown in Figure 4, specifically including:

Accounts at all levels apply for PAAS resources under the instruction of the user; and send the application for PAAS resources to the PAAS resource management and control device. After receiving the application, the PAAS resource management and control device first allocates PAAS resources in the public cloud domain. It is found that the PAAS resources in the public cloud domain cannot meet the requested resource requirements, and apply for PAAS resources in the private cloud domain. If the private cloud domain can provide unoccupied PAAS resources, deploy the PAAS resources of the original private cloud domain to the public cloud domain. Finally, based on deployment, the PAAS resources of the private cloud domain are migrated to the public cloud domain.

Example three:

Shown in Fig. 6 is the specific deployment process applicable to the cloud resources of the present invention, including:

Step S1: The resource management and control device receives n resource application tasks; the n is an integer not less than 1;

Step S2: Calculate the priority parameter of each task.

Step S3: sort the n tasks according to the priority parameters for the n task parameters;

Step S4: Process the tasks one by one based on the ranking; those with higher priority parameters are processed first.

Step S5: Return the processing result.

Based on step S1 to step S5, the following will introduce in detail.

When a user in the public cloud domain initiates a new application or PAAS resource application, the resource management and control device is responsible for resource allocation. The resource management and control device adopts a weighted timing allocation strategy based on SLA (Service Level Agreement). The allocation strategy is described as follows:

① In order to improve the allocation efficiency and improve the quality of system resource utilization, the resource management and control device regularly processes resource application requests, that is, PAAS resource allocation is performed every T time, and only PAAS resource application requests are accepted and not processed within the interval. According to production practice experience, T can be set to 24h. The T may be the first designated time in the foregoing embodiments.

② When the user initiates a PAAS resource application, the hybrid cloud system first sets the SLA according to the account level and other factors (SLA is a natural number greater than or equal to 1). The larger the SLA, the higher the service level;

③When each user initiates a PAAS resource application, the resource management and control device is equivalent to receiving a task task, which includes the SLA of the PAAS resource application, the application time time, and the application weight. For example: the application for database resources can calculate its weight based on factors such as storage space, memory, RPO, RTO, and backup; the application for middleware resources can calculate its weight based on factors such as the number of concurrency and thread pool. The larger the weight, the higher the requirements for the user's PAAS resource application;

④Assume that the resource management and control device receives 1.....n tasks within the specified interval time T, and name them task1, task2...taskn. For each task, according to its service level agreement SLA, application time Time, resource application weight and other factors are used to calculate the priority. Its calculation method is as follows:

The application time time1, time2...timen for n tasks are sorted from the back to the front,

Time1, time2....timen respectively correspond to a natural number N (1=<N<=n) as its timing value, the earlier the task application time, the greater the N value corresponding to its time;

Priority _n = X ^SLAn *time _n *weight _n

X is a natural number greater than or equal to 1, which is the adjustment factor for priority parameter calculation Priority. When calculating the priority of the same batch of tasks, X must take the same value. In the current system, X generally takes a value of 2).

⑤According to the calculation results of Priority, reorder task1, task2...taskn according to the order of Priority from large to small TASK1, TASK2...TASKm (1=<m<=n);

⑥The resource management and control device performs sequential processing on TASK1, TASK2...TASKm, and the processing method is as follows:

What is shown in FIG. 7 may be one of the processing procedures for performing tasks one by one in the step S4.

Apply for PAAS resources from the public cloud domain based on TASK. Tasks represented by TASK are sorted according to the priority parameters from high to low. For example, for the resource application of TASK1, the resource management and control device first checks whether there are enough resources in the public cloud domain for allocation, and if the public cloud domain resources meet the requirements, it will directly allocate PAAS resources from the public cloud; if the public cloud domain resources do not meet the requirements of TASK1 The demand is turned to TASK2, and so on until the task is processed or all tasks have polled the public cloud domain resources;

Determine whether the application is successful. If the application is successful, return the processing result directly. If the application is not successful, determine whether all tasks have applied for PAAS resources from the public cloud domain; the judgment result is yes to enter the follow-up operation, and if the judgment result is no, follow the priority parameter Get the next task.

Remove tasks from the remaining tasks for the applied PAAS resources to apply for PAAS resources to the private cloud domain, and record the application results.

Judging whether all tasks have applied for PAAS resources from the private cloud, if the judgment result is no, return to the previous step of operation, if the judgment result is yes, return the processing result.

In the above processing process, if the tasks have been processed, the resource management and control device directly returns all successful processing signs; if the tasks have not been processed, it means that the public cloud domain resources cannot meet the resource requirements of all tasks. The resource management and control device applies for PAAS resources to the private cloud domain one by one according to the order of the priority parameters for the remaining tasks. After the private cloud domain receives the resource application request from the resource management and control device, it first calculates the minimum PAAS unit that can be provided through its resource analysis module, and then the resource management and control device adds this unit to the public cloud domain PAAS domain. When the private cloud domain receives the public domain PAAS application, the resource analysis module calculates the smallest PAAS unit (such as a database, a virtual machine or a physical machine of a middleware platform) according to the resources of the private cloud domain, and the resource management and control device modifies the IP divides it into the VLAN of the public cloud domain, or modifies the ACL to control network access, so that the public cloud domain network can reach the PAAS resource. The PAAS resource adaptation module in the resource management and control device can dynamically adapt newly added resources to PAAS resources in the public cloud domain, and supports services such as databases, middleware, caches, and integrated environments in various modes.

Example four:

(1) When the PAAS public cloud domain receives the database (Date Base, DB) resources assigned by the private cloud domain, the intelligent control module will judge the type of DB on the demand side, and start the corresponding adaptation algorithm according to the different types. The DB implements dynamic expansion.

(2) As shown in Figure 8, there are three sets of databases (DB1, DB2, DB3) deployed under the host machine P1 of the public cloud domain. DB3 requires expansion of the CPU, data cache, backup space and modification of parameters, but the P1 host machine has no additional For hardware resources, modifying parameters will affect DB1 and DB2. At this time, the resource planning of the private cloud domain can be used to implement the expansion of DB3 through the host P2 host.

(3) When using P2 to expand the capacity and change parameters of DB3 under P1, the intelligent adaptation algorithm will calculate the influence degree Y1 of relocating DB3 and the influence degree Y2 of relocating DB1 and DB2 according to the operating factors of the three sets of databases.

The parameters in Table 1 to Table 2 will be used when calculating the above influence degree.

data capacity Operating factor F1 0-100G 1 100G-500G 2 500G-1T 3 1T-5T 4 More than 5t 5

Table 1

concurrent connections Operating factor F2 0-10 1 10-100 2 100-300 3 300 or more 4

Table 2

business continuity Operating factor F3 backup recovery 1 emergency 2 Hyperactive 3

table 3

Protection level Operating factor F4 5*8 1

7*24 2

The influence degree of DB migration Y1=F1+F2+F3+F4..., the influence degree of DB1 and DB2 relocation Y2=F1'+F2'+F3'+F4'..., when Y1<=Y2, it means that the influence of relocating DB3 is small, adopt Migrating to DB3 and vice versa.

(4) Before relocating DB3, the P2 host DB host machine has reserved the data cache and CPU resources required for DB3 expansion, and completed parameter modification. The resource management and control device restores the data through level 1 and level 0 data backup, and the data is real-time Synchronization, etc. to achieve DB3 data migration, and the application can be reconnected to complete the expansion of DB3.

(5) When Y1>Y2, implement the migration of DB1 and DB2 to the host machine P2, the migration plan is the same as step (4), the remaining resources after migration will make up for DB3, and implement parameter modification, and the application program can be reconnected to complete the DB3 expansion.

The expansion of the DB3 can be specifically shown in Figure 9, including:

Judging that P2 has available resources, if it goes to the next step, if not, apply for resources in the private cloud domain; the resources here can be database resources in PAAS resources, etc.

Calculate influence degree Y1 and influence degree Y2.

Determine whether Y1 is less than or equal to Y2.

Y1 is less than or equal to Y2, implement the migration from DB3 to P2.

Y1 is greater than Y2, and DB1 is migrated to P2.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms of.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units; Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention can be integrated into one processing module, or each unit can be used as a single unit, or two or more units can be integrated into one unit; the above-mentioned integration The unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the Including the steps of the foregoing method embodiments; and the foregoing storage medium includes: a removable storage device, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, etc. A medium on which program code can be stored.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (12)

1. a kind of cloud Resource allocation and smoothing method, it is characterised in that methods described be applied to include the first cloud domain and In the cloud platform in the second cloud domain, methods described includes：

Obtain the resource requirement of the account in the first cloud domain；

Based on the resource requirement, judge whether the first cloud domain provides enough resources；

If the first cloud domain can not provide enough resources, based on the resource requirement by second cloud The slack resources in domain are at least partly reassigned to the first cloud domain；

Wherein, the first cloud domain is private clound domain, and the second cloud domain is public cloud domain；Or, described One cloud domain is public cloud domain, and the second cloud domain is private clound domain.

2. method according to claim 1, it is characterised in that

Methods described also includes：

Determine the priority parameters of the resource requirement；

Based on the priority parameters, corresponding account is given by the resource allocation in the first cloud domain, to meet The resource requirement.

3. method according to claim 2, it is characterised in that

The priority parameters for determining the resource requirement, including：

Calculate the application weights of the resource requirement；

Application time based on the resource requirement, the application weights and preset function relation, calculate described Priority parameters.

4. method according to claim 3, it is characterised in that

The application weights for calculating the resource requirement, including：

Based on the resource type parameter needed for the corresponding account level of the resource requirement, the resource requirement and Resource quantity parameter needed for the resource requirement at least one, calculate the application weights.

5. method according to claim 1, it is characterised in that

The resource requirement of the account for obtaining the first cloud domain, including：

In the first resource requirement for specifying acquisition account in the time；

It is described to judge whether the first cloud domain provides enough resources based on the resource requirement, including：

Specified in the time second, based on the resource requirement of account each described, judge first cloud Whether domain provides enough resources；

Described second specifies the time to be later than described second specifies the time.

6. method according to claim 1, it is characterised in that

If the first cloud domain can not provide enough resources, based on the resource requirement by described The slack resources in two cloud domains are at least partly reassigned to the first cloud domain, including：

Count the second cloud domain idle PAAS resources and/or SAAS resources；

Based on the resource requirement, the idle PAAS resources and SAAS resources are allocated to described One cloud domain.

7. a kind of cloud Resource allocation and smoothing device, it is characterised in that described device be applied to include the first cloud domain and In the cloud platform in the second cloud domain, described device includes：

Acquiring unit, the resource requirement of the account for obtaining the first cloud domain；

Judging unit, for based on the resource requirement, judging whether the first cloud domain provides enough money Source；

Deployment unit, if can not provide enough resources for the first cloud domain, is needed based on the resource Ask and the slack resources in the second cloud domain are at least partly reassigned to the first cloud domain；

Wherein, the first cloud domain is private clound domain, and the second cloud domain is public cloud domain；Or, described One cloud domain is public cloud domain, and the second cloud domain is private clound domain.

8. device according to claim 7, it is characterised in that

Described device also includes：

Determining unit, the priority parameters for determining the resource requirement；

The deployment unit, is additionally operable to based on the priority parameters, by the resource allocation in the first cloud domain To corresponding account, to meet the resource requirement.

9. device according to claim 8, it is characterised in that

The determining unit, the application weights for calculating the resource requirement；Based on the resource requirement Application time, the application weights and preset function relation, calculate the priority parameters.

10. device according to claim 9, it is characterised in that

The determining unit is specific with based on the corresponding account level of the resource requirement, the resource requirement Resource quantity parameter needed for required resource type parameter and the resource requirement at least one, calculate The application weights.

11. devices according to claim 7, it is characterised in that

The acquiring unit, specifically for specifying the resource requirement that account is obtained in the time first；

The judging unit, specifically for being specified in the time second, the money based on account each described Source demand, judges whether the first cloud domain provides enough resources；Described second specified time was later than described Second specifies the time.

12. devices according to claim 7, it is characterised in that

The deployment unit, specifically for counting the idle PAAS resources in the second cloud domain and/or SAAS Resource；

Based on the resource requirement, the idle PAAS resources and SAAS resources are allocated to described One cloud domain.