CN115309558A

CN115309558A - Resource scheduling management system, method, computer equipment and storage medium

Info

Publication number: CN115309558A
Application number: CN202210967868.3A
Authority: CN
Inventors: 万思奇; 潘子涵; 刘伟佳; 杨超; 王天青
Original assignee: Transwarp Technology Shanghai Co Ltd
Current assignee: Transwarp Technology Shanghai Co Ltd
Priority date: 2022-08-12
Filing date: 2022-08-12
Publication date: 2022-11-08

Abstract

The invention discloses a resource scheduling management system, a resource scheduling management method, computer equipment and a storage medium. The system is integrated on a container cloud platform, and comprises: the system comprises a service access module and a resource reservation module; the service access module is used for receiving a resource pre-inspection request submitted by a front end through a provided service external access and transmitting the resource pre-inspection request to the resource reservation module; and the resource reservation module is used for performing simulated scheduling on the target component corresponding to the resource pre-detection request, performing resource pre-detection judgment according to a simulated scheduling result, and performing resource reservation and storage of simulated scheduling result information corresponding to the simulated scheduling result after the resource pre-detection is passed. The resource reservation module is added before real deployment to perform simulated scheduling on the components to be deployed, simulated scheduling result information is formed and stored in the database, and the stored simulated scheduling result information can be called when the real deployment is performed. The time for real deployment and establishment is saved, the success rate of overall product deployment is improved, and the service efficiency of the system and the platform is improved.

Description

Resource scheduling management system, method, computer equipment and storage medium

Technical Field

The present invention relates to the field of resource scheduling technologies, and in particular, to a resource scheduling management system, a resource scheduling management method, a computer device, and a storage medium.

Background

The complex big data platform usually comprises a plurality of components, the components have dependency relationship, and the distributed system can only function normally when all the components are in normal operation. With the development of distributed technology, components in a big data platform can be often deployed on a container cloud platform (such as kubernets), and normal deployment of the components on the container cloud platform is guaranteed by scheduling resources to the components through the container cloud platform.

Due to the dependency relationship among the components, each component can normally operate only after all the components of the big data platform are successfully deployed on the container cloud platform, and if the deployment of a certain component fails in the morning due to insufficient resources on the container cloud platform, the normal operation of the components on the big data platform cannot be guaranteed.

Disclosure of Invention

The invention provides a resource scheduling management system, a resource scheduling management method, computer equipment and a storage medium, which are used for realizing the management of resource scheduling.

According to a first aspect of the present invention, there is provided a resource scheduling management system integrated on a container cloud platform, including: the system comprises a service access module and a resource reservation module;

the service access module is used for receiving a resource pre-check request submitted by a front end through a provided service external access and transmitting the resource pre-check request to the resource reservation module;

the resource reservation module is used for performing simulated scheduling on the target component corresponding to the resource pre-detection request, performing resource pre-detection judgment according to the obtained simulated scheduling result, and performing resource reservation and storage of simulated scheduling result information corresponding to the simulated scheduling result after the resource pre-detection is passed;

and the stored simulation scheduling result is used for scheduling the real resources of the target component.

According to a second aspect of the present invention, there is provided a resource scheduling management method, including:

the service access module receives a resource pre-check request submitted by a front end through a provided service external access and transmits the resource pre-check request to the resource reservation module;

the resource reservation module carries out simulation scheduling on the target component corresponding to the resource pre-detection request, carries out resource pre-detection judgment according to the obtained simulation scheduling result, and carries out resource reservation and storage of simulation scheduling result information corresponding to the simulation scheduling result after the resource pre-detection is passed;

According to a third aspect of the present invention, there is provided a computer apparatus comprising:

one or more processors;

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method of resource scheduling management according to any of the embodiments of the present invention.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a resource scheduling management method according to any one of the embodiments of the present invention when the computer instructions are executed.

According to the technical scheme of the embodiment of the invention, the resource reservation module is added before the actual deployment to perform the simulated scheduling on the components to be deployed, so that the simulated scheduling result information is formed and stored in the database, and the stored simulated scheduling result information can be called when the actual deployment is performed. The time for real deployment and establishment is saved, the success rate of overall product deployment is improved, and the service efficiency of the system and the platform is improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is an exemplary diagram of a failure to deploy components under a conventional system;

FIG. 2 is an exemplary diagram of a multi-tenant deployment component failure under a conventional system;

fig. 3 is a block diagram illustrating a resource scheduling management system according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating an example of a resource scheduling management system according to an embodiment of the present invention;

fig. 5 is a flowchart of a resource scheduling management method according to a second embodiment of the present invention;

fig. 6 is a schematic structural diagram of a computer device implementing the resource scheduling management system according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It can be known that a complex distributed system usually includes several components, for example, an open source big data platform Hadoop, and usually consists of many big data components, and because there is a dependency relationship between the components, the big data platform can work normally only when all the components are running normally.

Fig. 1 is an exemplary diagram of component deployment failure in a conventional system, as shown in fig. 1, during the deployment process, a component 1, a component 2, and a component 3 have been created successfully and occupy resources, but a component 4 has failed scheduling for some reasons (e.g., resources are insufficient, affinity condition is not satisfied, etc.). At this time, the component that has been successfully created cannot function, and is in an idle state, which results in wasting resources of the cluster in this period of time. In addition, after the user deploys the big data components on the container cloud platform, the user needs to wait for the completion of the one-to-one scheduling and creation of all the components to acquire result information, which is time-consuming.

Fig. 2 is a diagram illustrating an example of failure of a multi-tenant deployment component in a conventional system, as shown in fig. 2, in a multi-tenant environment, tenants are unaware of each other. When the components are deployed at the same time, it is possible that the components 1, 2 and 3 of the product a are successfully deployed and the components 5, 6 and 7 of the product B are also successfully deployed, but the scheduling of the components 4 and 8 fails due to insufficient cluster resources, and the two products wait for each other to release resources, so that a deadlock phenomenon occurs.

When the above situation occurs, generally, a tenant needs to manually delete a certain component to release resources, and then repeatedly try to modify the configuration for many times, when the product level is large and the number of components is large, frequent deletion retry is performed, which brings many unnecessary overheads and affects the effective throughput of the scheduler. Generally, a system is adopted to perform a static reservation mode, which requires that a reserved resource amount is specified before starting, so that on one hand, the resource amount required to be reserved is difficult to define, and on the other hand, the system is required to be restarted when the reserved resource amount is adjusted, which is relatively expensive. Furthermore, the system reservation is only for system services, and the service Pod cannot use this part of the resources. Therefore, an active, dynamic reservation approach is lacking.

Example one

Fig. 3 is a block diagram of a resource scheduling management system according to an embodiment of the present invention. This embodiment is applicable to the case of managing resource scheduling, and as shown in fig. 3, the system includes: a service access module 11 and a resource reservation module 12.

The service access module 11 is configured to receive a resource pre-inspection request submitted by a front end through a provided service external access, and transmit the resource pre-inspection request to the resource reservation module 12.

It can be known that, when the target component is actually run, it cannot be determined whether the current resource is sufficient to support the running of the target component, and then the simulation scheduling can be performed before the component is actually run, so as to determine whether the target component can be run at the present stage.

In this embodiment, the front end may be understood as an end that includes a plurality of components and performs target component selection according to requirements. The resource preview request can be understood as a request for previewing resources according to information such as the resources required by the target component to be simulated to run and the size of the required resources.

Specifically, the system can provide services in a form of providing an external access, when a target component meets a simulation operation requirement, a user can send a pre-check instruction according to the target component meeting the simulation operation requirement, the front end can generate a resource pre-check request related to the target component according to the pre-check instruction, wherein the pre-check requirement can include information such as resources and resource amount required by the operation of the target component, and when a service access module 11 in the system receives the resource pre-check requirement, the resource pre-check requirement is transmitted to a resource reservation module 12.

The resource reservation module 12 is configured to perform simulated scheduling on the target component corresponding to the resource pre-inspection request, perform resource pre-inspection judgment according to the obtained simulated scheduling result, and perform resource reservation and storage of simulated scheduling result information corresponding to the simulated scheduling result after the resource pre-inspection is passed; and the stored simulation scheduling result information is used for real resource scheduling of the target component.

In this embodiment, the simulated scheduling result may be understood as a scheduling result formed after the simulated scheduling is performed on the corresponding component. The simulation scheduling result information may be understood as a form of converting a simulation scheduling result into a simulation scheduling result information, where the simulation scheduling result information may include: the reserved resource types can include resources such as a CPU, a Memory, a Storage and the like; constraints such as affinity, tolerance, tags, annotations, etc.; priority order processed at the time of analog scheduling; the number of parts required by the simulation scheduling result; a reserved time limit, when the reservation is over, the corresponding resources are released; the states of the reservation are divided into unreserved state, reserved state and overtime state; as a result of the reservation, a mapping table of a few resources is reserved on which container nodes.

Specifically, the resource reservation module 12 performs simulated scheduling according to a target component corresponding to the resource pre-inspection request, obtains a resource type, a resource amount, and the like required when the target component is used by simulation, performs resource pre-inspection determination on the scheduling result, and traverses whether container nodes meeting the scheduling result exist in all container nodes, that is, whether the resource type, the resource amount, and the like of the container nodes meet the scheduling result required by the target component. If so, the information of the container node meeting the condition is extracted through resource pre-inspection and resource reservation is carried out on the information according to a scheduling result, simulated scheduling result information is formed according to the simulated scheduling result and the corresponding container node information, and the simulated scheduling result information is stored to provide a basis for carrying out real scheduling on the subsequent target component; if not, no container node meets the conditions required by the target component scheduling, and it can be considered that the resources in the container node are not enough to support the target component to operate, the scheduling result does not pass the resource judgment, and a resource pre-inspection failure instruction can be fed back to the front end to prompt that the target component cannot operate under the current conditions.

In the resource scheduling management system provided in this embodiment, the resource reservation module is added before the real deployment to perform the simulated scheduling on the component to be deployed, so as to form simulated scheduling result information, which is stored in the database, and the stored simulated scheduling result information can be called when the real deployment is performed. The time for real deployment and establishment is saved, the success rate of overall product deployment is improved, and the service efficiency of the system and the platform is improved.

Further, the resource reservation module 12 is specifically configured to:

and carrying out format verification on the received resource pre-detection request, and if the verification is successful, determining a target component corresponding to the resource pre-detection request.

Specifically, after receiving the resource pre-check request, the resource reservation module 12 compares the format of the resource pre-check request with the format of the resource pre-check request according to the preset format requirement, and if the format of the resource pre-check request is the same as the preset format requirement, the check is considered to be successful, and when the check is successful, the target component information in the resource pre-check request can be obtained, so as to determine the target component corresponding to the resource pre-check request. When the format of the resource pre-check request is different from the preset format requirement, the check is considered to be failed, and a check failure instruction can be sent to the front end to remind the front end of the failure of the check of the target component.

And calling a preset simulation scheduling function to perform simulation scheduling on the target assembly to obtain a simulation scheduling result of the target assembly.

In the present embodiment, the simulation scheduling function may be understood as a function for simulation scheduling to pass through. The method can comprise the following steps: resource calculation function, container node selection function, data volume information detection function, storage resource simulation function, and the like.

Specifically, the resource reservation module 12 may query the stored resource data information required for operating the target component, and pass the resource data information through the simulation scheduling function, where the resource calculation function is used to simulate and calculate the resource required by the target component; the container node selection function is used for selecting the most appropriate container node; the data volume information detection function is used for detecting data volume information; the storage resource simulation function is used for simulating the storage resource. And outputting a simulation scheduling result after simulation scheduling is performed through the simulation scheduling function, wherein the simulation scheduling result may include resource reservation information, for example, information that the type of resource required by the target component may be a CPU, the optimal container node may be container node 2, and the required amount of resource may be 50M.

And analyzing the resource reservation information in the simulated scheduling result, and determining that the reserved resources corresponding to the resource reservation information are reserved through resource reservation and the control container node when the resource reservation information is determined to be successful.

In this embodiment, the resource reservation information may be understood as a basis for resource reservation.

Specifically, the corresponding container node is searched according to the resource reservation information, and the condition of the corresponding container node at the moment is judged according to the resource reservation information, for example, whether the remaining resource amount of the corresponding resource type of the container node meets the resource amount required in the resource reservation information can be judged. If the corresponding container node satisfies the resource reservation information, the resource reservation information is considered to be successful, the resource reservation is determined to pass the resource reservation, the corresponding container node is controlled to reserve the reserved resource corresponding to the resource reservation information, the resource amount of the corresponding resource type of the container node can be locked according to the resource reservation information, and the resource reservation is realized, for example, 50M resources of a CPU in the container node 2 are reserved.

After the resource pre-inspection is passed, recording a simulation scheduling result according to a set first data structure to form simulation scheduling result information, and storing the simulation scheduling result information in a database in association with a target component.

In this embodiment, the first data structure may be understood as configuration information of the simulated scheduling result information, and may include reserved resource types, such as resources of a CPU, a Memory, a Storage, and the like; constraints such as affinity, tolerance, tags, annotations, etc.; priority order processed at the time of analog scheduling; the number of parts required by the simulation scheduling result; a reserved time limit, when the reservation is over, the corresponding resources are released; the states of the reservation are divided into unreserved state, reserved state and overtime state; the result of the reservation, on which container nodes several mapping tables of resources are reserved, etc. The resource type, the reserved time limit, the priority order of processing in the simulation scheduling, and the like can be preset by a system or a front end to different target components.

Specifically, after the resource is subjected to the pre-inspection, the first data structure is called, the simulation scheduling result is identified and recorded according to the first data structure, so that simulation scheduling result information is formed, the simulation scheduling result information is associated with the target component, the simulation scheduling result information and the target component are conveniently determined mutually, and the simulation scheduling result information and the target component are stored in a database, so that the simulation scheduling result information and the target component are conveniently called in the subsequent use process. Such as: the association can be established through the form of the serial number, the simulation scheduling result information and the serial number of the target component are set as A, the corresponding simulation scheduling result information and the corresponding target component can be obtained through the serial number A, and the simulation scheduling result information and the target component are stored in the database in the naming form of the serial number A and with the timestamp of the time when the simulation scheduling result information and the target component are stored in the database.

For example, the simulation scheduling result information a of the target component a may be: the reserved resource type may be a CPU; the constraint may be affinity; the priority order in which the target component 1 is processed at the time of the simulation scheduling may be the first bit; the number of parts required by the simulation scheduling result is 1; the reserved time limit may be 20s; the current reservation is in a reserved state; the result of the reservation may be that a mapping table of 1 resource is reserved on the container node 2.

Further, the resource scheduling management system further includes: and a reserved resource control module.

A reserved resource control module configured to:

and acquiring a simulation scheduling result information list stored in a database, and carrying out time limit monitoring on the simulation scheduling result information in the simulation scheduling result information list.

In this embodiment, the simulation scheduling result information list may be understood as storing a plurality of simulation scheduling result information in a list form.

Specifically, the reserved resource control module can acquire a simulation scheduling result information list stored in the database at a set period, each simulation scheduling result information comprises set reserved time, the reserved resource control module can retrieve the timestamp of the simulation scheduling result information, the reserved time length can be acquired by subtracting the time displayed by the timestamp from the current time, and the reserved time length is compared with the set reserved time to realize time limit monitoring on the simulation scheduling result information in the simulation scheduling result information list.

And when the overtime simulated scheduling result information meeting the reserved overtime condition is monitored, deleting the overtime simulated scheduling result information and releasing the reserved resources corresponding to the reserved resource information on the container node in the overtime simulated scheduling result information.

In this embodiment, the reservation timeout condition may be understood as a condition for determining whether the already reserved time length exceeds the set reserved time.

Specifically, when it is monitored that the reserved time length of the simulated scheduling result information exceeds the set reserved time, that is, the reserved timeout condition is met, the simulated scheduling result information is determined as the timeout simulated scheduling result information, the corresponding container node is searched according to the reserved resource information in the timeout simulated scheduling result information, the locked reserved resource is released, an instruction for deleting the timeout simulated scheduling result information is sent, and the timeout simulated scheduling result information is deleted.

For example, the simulation scheduling result information B may be: the reserved resource type is CPU; the constraint may be affinity; the priority order in which the target component 1 is processed at the time of the simulation scheduling may be the first bit; the number of parts required by the simulation scheduling result is 1; the reserved time limit may be 10s; the current reservation is in a reserved state; the result of the reservation may be that a mapping table of 1 resource and the corresponding 50M resource are reserved on the container node 2. And if the set reserved time in the simulation scheduling result information B is 10s, the reserved time is 10.01s, and the reserved time is longer than the set reserved time, judging that the simulation scheduling result information B is overtime simulation scheduling result information, releasing the CPU resource with the reserved resource amount of 50M, and deleting the simulation scheduling result information B.

Further, the resource scheduling management system further includes: and reserving a binding module.

Correspondingly, the service access module is also used for receiving a resource scheduling request submitted by the front end relative to the target component through the service external access, and feeding the resource scheduling request back to the reservation binding module.

In this embodiment, the resource scheduling request may be understood as a request that needs to be actually scheduled.

Specifically, when there is a component operation demand, the user may send a resource scheduling instruction according to a target component having an operation demand, the front end may generate a resource scheduling request corresponding to the target component according to the resource scheduling instruction and send the resource scheduling request to the reservation binding module, and when the reservation binding module receives the resource scheduling request sent by the front end, the resource scheduling request is fed back to the reservation binding module.

And the reservation binding module is used for determining and storing reservation binding relationship information of the target component through the analysis of the resource scheduling request.

In this embodiment, the reservation binding relationship information may be understood as a form of converting the resource scheduling request into the reservation binding relationship information.

Specifically, the reservation binding module analyzes the resource scheduling request, determines reservation binding relationship information of the target component according to an analysis result, and stores the reservation binding relationship information in the database.

Further, the reservation binding module is specifically configured to:

and analyzing the resource scheduling request, and acquiring the reserved binding configuration information of the corresponding target component in the resource scheduling request.

In this embodiment, the reserved binding configuration information may be understood as information used for acquiring and using the previously reserved specific resource in real scheduling, and may include: the reserved name, the number of reserved resources used by the binding, component information, the state of the binding, the binding result and other information.

Specifically, the reservation binding module first determines a target component corresponding to the resource scheduling request, and searches for reservation binding configuration information corresponding to the target component, thereby obtaining the reservation binding configuration information of the target component.

And recording the reserved binding configuration information according to the second data structure to form reserved binding relationship information, and storing the reserved binding relationship information associated with the target component into a database.

In this embodiment, the second data structure may be understood as configuration information of the reserved binding relationship information, and may include: reserving a name; the binding uses the quantity of reserved resources; component information; the state in which the binding is: unbound, partially bound, and fully bound; the result of the binding, and so on.

Specifically, the second data structure is called, the reserved binding configuration information is identified and recorded according to the second data structure, so that reserved binding relationship information is formed, the reserved binding relationship information is associated with the target component, mutual determination between the reserved binding relationship information and the target component is facilitated, and the reserved binding relationship information and the target component are stored in a database, so that calling in subsequent use is facilitated. Such as: the association can be established through the form of the serial number, the reserved binding relationship information and the serial number of the target component are set to be Y1, the corresponding reserved binding relationship information and the corresponding target component can be obtained through the serial number Y1, and the reserved binding relationship information and the target component are stored in the database in the naming form of the serial number Y1 and with the timestamp of the time when the reserved binding relationship information and the target component are stored in the database.

Further, the resource scheduling management system further includes: and a resource scheduling module.

The resource scheduling module is used for deploying the target component to the determined target container node when judging that the reserved resource scheduling condition is met after receiving a resource scheduling request sent by the service access module 11 relative to the target component; and reserving reserved resources required for deploying the target component through a deployment process on the target container node.

Specifically, after receiving a resource scheduling request sent by the service access module 11 with respect to the target component, the resource scheduling module determines whether a target container node of a reserved resource corresponding to the target component meets a reserved resource scheduling condition according to the scheduling request, and when the reserved resource scheduling condition is met, the resource scheduling module may deploy the target component to the determined target container node.

Further, the resource scheduling module is specifically configured to:

after receiving a resource scheduling request sent by the service access module 11 relative to the target component, determining a deployment process type set in the resource scheduling request.

In this embodiment, the deployment process type may be understood as a processing manner for distinguishing different processes, for example, three deployment process types may be set: a normal type, a reserved type, and an analog type, wherein the normal type may be understood as not using reserved resources; the reserved type can be understood as requiring the use of reserved resources; the simulation type can be understood that the deployment process does not really exist, that is, the deployment process which needs to use the process to occupy the actual resource is simulated.

Specifically, each target component may set a deployment process type in advance and store the deployment process type in information of the target component, and when receiving the resource scheduling request, search for a deployment process type corresponding to the target component in the information corresponding to the target component, and determine the deployment process type set in the resource scheduling request.

And when the deployment process type is a reserved type, determining that a reserved resource scheduling condition is met, and determining a target container node matched with the target component according to the simulated scheduling result information and the reserved binding relationship information of the target component.

Specifically, when the resource scheduling module determines that the deployment process type set by the target component is a reserved type, the resource scheduling module acquires associated simulation scheduling result information and reserved binding relationship information. And determining the target container node of the reserved resource establishing the binding relationship with the target component according to the simulated scheduling result information and the reserved binding relationship information.

And deploying the target component to a target container node of the container cloud platform through a deployment process.

Specifically, the resource scheduling module deploys the target component to the target container node of the container cloud platform through the deployment process according to the deployment process corresponding to the target component and the target container node matched with the target component.

Further, the binding control module may be further configured to:

and acquiring a reserved binding relationship information list stored in the database, and monitoring the use condition of reserved resources associated with the reserved binding relationship information in the reserved binding relationship information list.

In this embodiment, the reserved binding relationship information list may be understood as storing a plurality of pieces of reserved binding relationship information in a form of a list.

Specifically, the binding control module may obtain a reserved binding relationship information list stored in the database, and since each reserved binding relationship information includes the set reserved resource, the use condition of the reserved resource may be determined by checking information such as the remaining amount or the scheduling condition of the reserved resource at the current time, and comparing the information with the set reserved resource, and the reserved binding relationship information is updated according to the use condition, thereby achieving the purpose of monitoring.

When the reserved resources are scheduled, determining the reserved binding relationship information associated with the scheduled reserved resources, and recording as the scheduled associated information.

In this embodiment, the scheduled association information may be understood as information generated by indicating that the reserved resource is scheduled.

Specifically, when it is monitored that the reserved resource is being used, if the reserved resource is reduced, that is, the reserved resource is scheduled corresponding to the reserved resource and already used by the target component, a search instruction may be sent to search for reservation binding relationship information associated with the scheduled reserved resource, and the reservation binding relationship information is recorded as scheduled association information to indicate that the reserved resource is being used.

And deleting the scheduled association information from the reserved binding relation information list and releasing the binding between the scheduled reserved resources on the container node and the components corresponding to the scheduled association information.

Specifically, the reserved binding relationship information list includes the non-scheduled reserved binding relationship information, when the reserved resource is scheduled, the scheduled association information is deleted, the corresponding container node, the component bound with the container node and the scheduled reserved resource are obtained according to the scheduled association information, and the binding between the scheduled reserved resource on the container node and the group price corresponding to the scheduled association information is released.

For the first time, the service access module 11 of this embodiment may be further configured to:

receiving a resource pre-check updating request or a resource pre-check deleting request submitted by a front end through a provided service external access;

correspondingly, the resource reservation module is also used for carrying out simulation scheduling again on the target assembly according to the received resource pre-inspection updating request, and updating the database by adopting the simulation scheduling result after the simulation scheduling again, namely updating the stored simulation scheduling result information; or deleting the simulation scheduling result information corresponding to the target component in the database according to the received resource pre-inspection deletion request.

It can be known that the resources and the resource amount required for the same target component may change at different times, and when the resources and the resource amount required for the target component change, the target component has already performed the simulated scheduling and formed the simulated scheduling result information, but does not perform the real scheduling according to the scheduling priority in the simulated scheduling result information, the simulated scheduling result information thereof needs to be updated. If the target assembly forms the simulation scheduling result information and reserves resources according to the simulation scheduling result information, real scheduling is not performed according to the scheduling priority in the simulation scheduling result information, and the simulation scheduling result information is deleted when the target assembly does not need to be scheduled at present.

In this embodiment, the resource preview update request may be understood as a request for performing simulated scheduling again on a component that has performed simulated scheduling. The resource pre-check deleting request can be understood as a component request for deleting simulated scheduling and reserving resources to form simulated scheduling result information.

Specifically, when the demand for the target component changes, the front end may generate a resource pre-inspection update request corresponding to the target component and send the resource pre-inspection update request to the resource reservation module, the resource reservation module receives the resource pre-inspection update request, performs re-simulation scheduling on the target component, obtains a scheduling result of the target component at the time, searches simulation scheduling result information corresponding to the target component in the stored simulation scheduling result information, updates the simulation scheduling result information corresponding to the target component according to the scheduling result, and replaces the content in the simulation scheduling result information according to the scheduling result; or, when the target component no longer needs to be operated, the front end may generate a resource pre-inspection deletion request corresponding to the target component and send the resource pre-inspection deletion request to the resource reservation module, and the resource reservation module receives the resource pre-inspection deletion request, searches for the simulated scheduling result information corresponding to the target component from the stored simulated scheduling result information, and deletes the simulated scheduling result information.

Again, the service access module 11 in this embodiment may be further configured to:

receiving a resource scheduling updating request or a resource scheduling deleting request submitted by a front end through a provided service external access;

correspondingly, the reserved binding module is used for re-determining the reserved binding configuration information of the target component according to the received resource scheduling updating request and updating the stored reserved binding relationship information by adopting the re-obtained reserved binding configuration information; or deleting the reserved binding relation information corresponding to the target component according to the received resource scheduling deletion request.

It can be known that resources and resource amounts required for the same target component may change at different times, and the reservation binding information and the reservation binding relationship information generated according to the reservation binding information also change accordingly, so that the reservation binding relationship information needs to be updated. If the target component has formed the reserved binding relationship information, but the target component does not need to be scheduled at present, the reserved binding relationship information needs to be deleted.

In this embodiment, the resource scheduling update request may be understood as updating the reserved binding relationship information of the component that has undergone the re-simulation scheduling. The resource scheduling deletion request may be understood as a target component request to delete a reserved resource and form reservation binding relationship information.

Specifically, when the demand for the target component changes, the front end may generate a resource scheduling update request corresponding to the target component and send the resource scheduling update request to the reservation binding module, the reservation binding module receives the resource scheduling update request, re-determines reservation binding configuration information according to the resource scheduling update request, searches for reservation binding relationship information corresponding to the target component in the stored reservation binding relationship information, and updates the content in the reservation binding relationship information corresponding to the target component according to the reservation binding configuration information; or, when the target component does not need to be operated any more, the front end may generate a resource scheduling deletion request corresponding to the target component and send the resource scheduling deletion request to the reservation binding module, and the reservation binding module receives the resource scheduling deletion request, searches the reservation binding relationship information corresponding to the target component in the stored reservation binding relationship information, and deletes the reservation binding relationship information.

The resource scheduling management system provided in the above preferred embodiment of the present invention can check in advance whether the component can be successfully scheduled in an overall simulation manner before actually deploying the service, and in the case of successful pre-inspection, form simulation scheduling result information for subsequent use, ensure accurate pre-inspection result, and reserve resources in advance according to the simulation scheduling result information. And when the real deployment is carried out, binding the resources and the created components according to the reserved binding relationship information and the simulated scheduling result information. It is ensured that the corresponding component can only consume the reserved resources, i.e. the "integrity" of the reserved resources. By differentiating the deployment process types, it is ensured that resources that have already been reserved are not taken up, i.e. "exclusivity" of the reserved resources. The state of the reserved resources is monitored in real time by setting time limit monitoring, two types of updating and deleting requests, and the success of scheduling of the reserved resources, namely the availability of the reserved resources, is ensured. By ensuring the integrity, exclusivity and availability of the reserved resources, the utilization rate of the resources is improved, the deployment efficiency and success rate of the system and the platform are improved, and the condition of resource deadlock is reduced.

Fig. 4 is a flowchart illustrating an example of a resource scheduling management system according to an embodiment of the present invention, and as shown in fig. 4, the resource scheduling management system may deploy components according to the following steps:

1. the service access module receives a resource pre-check request, a resource scheduling deletion request, a resource pre-check deletion request, a resource scheduling update request or a resource pre-check update request sent by a front end; 2. the resource reservation module calls a simulation scheduling function to perform simulation scheduling on the resource pre-inspection request or the resource pre-inspection updating request; 3. forming simulation scheduling result information or forming reservation binding relation information according to reservation configuration information, controlling corresponding container nodes to reserve reserved resources corresponding to the resource reservation information according to the simulation scheduling result information, and storing the simulation scheduling result information and associated target components into a database; 4. the reserved resource control module acquires a simulation scheduling result information list from the database and carries out time limit monitoring on the simulation scheduling result information in the simulation scheduling result information list; 5. the reserved resource control module deletes the overtime simulated scheduling result information and releases the reserved resources corresponding to the reserved resource information on the container nodes in the overtime simulated scheduling result information; 6. the binding control module acquires a reserved binding relationship information list from a database and monitors the use condition of reserved resources associated with the reserved binding relationship information in the list; 7. updating the use condition of the reserved resources, deleting the scheduled association information and releasing the binding between the scheduled reserved resources on the container node and the components corresponding to the scheduled association information; 8. receiving a resource scheduling request; 9. acquiring simulated scheduling result information and reserved binding relationship information according to the resource scheduling request; 10. and the resource scheduling module determines a target container node matched with the target component according to the simulated scheduling result information and the reserved binding relationship information, and deploys the target component to the node easy to be used on the cloud platform through a deployment process.

Example two

Fig. 5 is a flowchart of a resource scheduling management method according to a second embodiment of the present invention, where the method is applicable to a situation of managing resource scheduling, and may be specifically applied to a resource scheduling management system according to the foregoing embodiment of the present invention, where the resource scheduling management system may be integrated on a computer device, and the computer device may be used as a node of a container cloud platform. As shown in fig. 5, the method includes:

s110, the service access module receives a resource pre-check request submitted by a front end through a provided service external access, and transmits the resource pre-check request to the resource reservation module.

S120, the resource reservation module carries out simulation scheduling on the target component corresponding to the resource pre-detection request, carries out resource pre-detection judgment according to the obtained simulation scheduling result, and carries out resource reservation and storage of simulation scheduling result information corresponding to the simulation scheduling result after the resource pre-detection is passed.

In the resource scheduling management method provided by the second embodiment, the resource reservation module is added before the real deployment to perform the simulated scheduling on the component to be deployed, so as to form simulated scheduling result information, the simulated scheduling result information is stored in the database, and the stored simulated scheduling result information can be called when the real deployment is performed. The real deployment time is saved through the stored simulation scheduling result information, the success rate of overall product deployment is improved, and the use efficiency of the system and the platform is improved.

EXAMPLE III

FIG. 6 illustrates a block diagram of a computer device 20 that may be used to implement an embodiment of the invention. The computer device is used as a node of a container cloud platform, and the resource scheduling management system provided by the first embodiment is operated on the node. Computer devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The computer device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 6, the computer device 20 includes at least one processor 21, and a memory communicatively connected to the at least one processor 21, such as a Read Only Memory (ROM) 22, a Random Access Memory (RAM) 23, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 21 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 22 or the computer program loaded from the storage unit 28 into the Random Access Memory (RAM) 23. In the RAM 23, various programs and data necessary for the operation of the computer device 20 can also be stored. The processor 21, the ROM 22, and the RAM 23 are connected to each other via a bus 24. An input/output (I/O) interface 25 is also connected to bus 24.

A number of components in the computer device 20 are connected to the I/O interface 25, including: an input unit 26 such as a keyboard, a mouse, or the like; an output unit 27 such as various types of displays, speakers, and the like; a storage unit 28, such as a magnetic disk, optical disk, or the like; and a communication unit 29 such as a network card, modem, wireless communication transceiver, etc. The communication unit 29 allows the computer device 20 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The processor 21 may be any of various general purpose and/or special purpose processing components having processing and computing capabilities. Some examples of the processor 21 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The processor 21 performs the various methods and processes described above, such as the resource scheduling management method.

In some embodiments, the resource scheduling management method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 28. In some embodiments, part or all of the computer program may be loaded onto and/or installed onto computer device 20 via ROM 12 and/or communications unit 29. When the computer program is loaded into the RAM 23 and executed by the processor 21, one or more steps of the resource scheduling management method described above may be performed. Alternatively, in other embodiments, the processor 21 may be configured to perform the resource scheduling management method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A resource scheduling management system integrated on a container cloud platform, comprising: the system comprises a service access module and a resource reservation module;

and the stored simulation scheduling result data set is used for real resource scheduling of the target component.

2. The system of claim 1, wherein the resource reservation module is specifically configured to:

carrying out format verification on the received resource pre-detection request, and if the verification is successful, determining a target component corresponding to the resource pre-detection request;

calling a preset simulation scheduling function to perform simulation scheduling on the target assembly to obtain a simulation scheduling result of the target assembly;

analyzing the resource reservation information in the simulated scheduling result, and determining that reserved resources corresponding to the resource reservation information are reserved through resource reservation and control container nodes when the resource reservation information is determined to be successful;

and after the resource pre-inspection is passed, recording the simulation scheduling result according to a set first data structure to form simulation scheduling result information, and storing the simulation scheduling result information in a database in a manner of being associated with the target component.

3. The system of claim 1, further comprising: a module for controlling the reserved resources is provided,

the reserved resource control module is configured to:

acquiring a simulation scheduling result information list stored in a database, and carrying out time limit monitoring on simulation scheduling result information in the simulation scheduling result information list;

4. The system of claim 1, further comprising: a binding module is reserved, and the binding module is used for binding the binding module,

correspondingly, the service access module is also used for receiving a resource scheduling request submitted by a front end relative to the target component through the service external access, and feeding the resource scheduling request back to the reservation binding module;

and the reserved binding module is used for determining and storing the reserved binding relationship information of the target component through the analysis of the resource scheduling request.

5. The system according to claim 4, wherein the reservation binding module is specifically configured to:

analyzing the resource scheduling request, and acquiring reserved binding configuration information of a corresponding target component in the resource scheduling request;

and recording the reserved binding configuration information according to a second data structure to form reserved binding relationship information, and storing the reserved binding relationship information in a database in association with the target component.

6. The system of claim 4, further comprising: a resource scheduling module;

the resource scheduling module is used for deploying the target component to the determined target container node when judging that a reserved resource scheduling condition is met after receiving a resource scheduling request sent by the service access module relative to the target component;

and reserving reserved resources required for deploying the target component through the deployment process on the target container node.

7. The system of claim 6, wherein the resource scheduling module is specifically configured to:

after receiving a resource scheduling request sent by the service access module relative to the target component, determining a deployment process type set in the resource scheduling request;

when the deployment process type is a reserved type, determining that a reserved resource scheduling condition is met, and determining a target container node matched with the target component according to the simulated scheduling result information and the reserved binding relationship information of the target component;

and deploying the target component to a target container node of a container cloud platform through the deployment process.

8. The system of claim 4, further comprising: a binding control module to:

acquiring a reserved binding relationship information list stored in a database, and monitoring the use condition of reserved resources associated with the reserved binding relationship information in the reserved binding relationship information list;

when the reserved resource is scheduled, determining reserved binding relation information associated with the scheduled reserved resource and recording as scheduled associated information;

and deleting the scheduled association information from the reserved binding relation information list and releasing the binding between the scheduled reserved resource on the container node and the component corresponding to the scheduled association information.

9. The system according to any one of claims 1 to 8, wherein the service access module is further configured to receive a resource pre-check update request submitted by a front end or a resource pre-check delete request through a provided service external portal;

correspondingly, the resource reservation module is further configured to perform simulated scheduling again on the target component according to the received resource pre-inspection update request, and update the stored simulated scheduling result information by using the simulated scheduling result after the simulated scheduling again; or deleting the simulation scheduling result information corresponding to the target component according to the received resource pre-inspection deletion request.

10. The system according to any one of claims 1 to 8, wherein the service access module is further configured to receive a resource scheduling update request submitted by a front end or a resource scheduling delete request through a provided external service portal;

correspondingly, the reserved binding module is used for re-determining the reserved binding configuration information of the target component according to the received resource scheduling updating request and updating the stored reserved binding relationship information by adopting the re-obtained reserved binding configuration information; or deleting the reserved binding relationship information corresponding to the target component according to the received resource scheduling deletion request.

11. A resource scheduling management method performed by the resource scheduling management system of any one of claims 1 to 10 integrated on a container cloud platform, the method comprising:

the service access module receives a resource pre-check request submitted by a front end through a provided service external access, and transmits the resource pre-check request to the resource reservation module;

the resource reservation module carries out simulation scheduling on a target component corresponding to the resource pre-detection request, carries out resource pre-detection judgment according to an obtained simulation scheduling result, and carries out resource reservation and storage of simulation scheduling result information corresponding to the simulation scheduling result after the resource pre-detection is passed;

12. A computer device, as a node of a container cloud platform, comprising:

one or more processors;

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method of claim 11.