CN114327895A - Method and system for constructing task scheduling model - Google Patents
Method and system for constructing task scheduling model Download PDFInfo
- Publication number
- CN114327895A CN114327895A CN202111639864.4A CN202111639864A CN114327895A CN 114327895 A CN114327895 A CN 114327895A CN 202111639864 A CN202111639864 A CN 202111639864A CN 114327895 A CN114327895 A CN 114327895A
- Authority
- CN
- China
- Prior art keywords
- task
- information
- operation information
- layer
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000012545 processing Methods 0.000 claims description 41
- 238000012790 confirmation Methods 0.000 claims description 33
- 238000010276 construction Methods 0.000 claims description 12
- 238000007726 management method Methods 0.000 description 31
- 230000008569 process Effects 0.000 description 21
- 230000008859 change Effects 0.000 description 8
- 238000004590 computer program Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000013468 resource allocation Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000008520 organization Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000008846 dynamic interplay Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method and a system for constructing a task scheduling model, wherein the method comprises the following steps: constructing a complex cloud resource management platform, wherein the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds; constructing a resource request layer, a task layer and an operation layer in a complex cloud resource management platform; obtaining first request information based on a resource request layer; controlling a task layer through a resource request layer, obtaining one or more pieces of task information in the task layer, and obtaining first task information in the one or more pieces of task information; controlling the operation layer through the task layer, and obtaining a plurality of operation information in the operation layer based on the first task information; controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information; the one or more task information is completed until the first requested information is completed.
Description
Technical Field
The invention relates to the technical field of cloud services, in particular to a method and a system for constructing a task scheduling model.
Background
Cloud service computing can provide very powerful network services, and current cloud services mainly include the following three types:
a Public Cloud (Public Cloud), which is a third party's Public Cloud provider, provides users with server space in a virtual environment accessible over the internet. Users may access these servers by purchasing public cloud services such as cloud servers, data stores, and other cloud-related services.
Private Cloud (Private Cloud), which is another form of Cloud computing. It provides a dedicated cloud environment for an enterprise or organization. Private clouds may be operated internally by IT teams within a business or organization behind the organization's firewall so the organization may have better control over ITs computing resources.
Hybrid Cloud (Hybrid Cloud), a Cloud computing model that combines one or more public and private Cloud environments through a secure connection (such as a VPN connection or leased line) to allow sharing of data and applications between different Cloud environments.
In the process of selecting the cloud service by a large-scale client, not all enterprise information can be placed on the public cloud due to safety and control reasons, and various public clouds can be simultaneously selected due to different service scenes in the enterprise, so most of the enterprises applying cloud computing use a hybrid cloud mode. The hybrid cloud combines the private cloud of the local infrastructure with the public cloud through a secure connection (such as a VPN connection or leased line), and simultaneously utilizes the advantages of the private cloud and the public cloud to cope with different service scenarios.
The different cloud bottom warehouse architectures are different, and the operation and maintenance management schemes are also different. After the enterprise builds the hybrid cloud, the resources of different clouds are independent from each other, and a uniform resource management scheduling scheme cannot be formed. Enterprises typically prepare separate human and resource costs for sets of clouds, which greatly increases the difficulty of operation and maintenance management. The task scheduling of the mainstream public cloud in the current market generally uses an order mode. The allocation and change operations of resources such as CVM (cloud server), CBS (cloud hard disk), CFS (cloud network shared file storage), PDB (cloud database) and the like of the public cloud are uniformly managed through standardized orders, and a user can inquire order execution states and results through an order ID. The orders do not support decomposition and re-execution operations, and each order is an atomic operation and does not support one-time scheduling operations of multiple resources.
In the prior art, in the process of processing the same service by adopting a hybrid cloud, execution of a single service order is atomic operation, which can not be decomposed, re-executed or manually intervened, can only check the execution state and result of the order, cannot define order operation by user, and has no customizability and poor expandability. If the order execution fails, error handling is not supported, and only new orders can be resubmitted. Different cloud service operations in different clouds are different, different types of cloud resources correspond to different service scenes, a resource demand party needs to be familiar with various cloud platforms and cloud resources to correctly perform cloud service operations, the technical requirement threshold for a resource manager is high, and the technical problems of low processing efficiency and complicated management of mixed cloud services exist.
In summary, in the prior art, in the process of processing the same service by using a hybrid cloud, cloud service operations in different clouds are different, and the service cannot be decomposed and customized, so that the technical problems of low service processing efficiency and complex management exist.
Disclosure of Invention
The application provides a method and a system for constructing a task scheduling model, which are used for solving the technical problems that in the process of processing the same service by adopting a mixed cloud in the prior art, the cloud service operations in different clouds are different, the service cannot be decomposed and customized, the service processing efficiency is low, and the management is complicated.
In view of the foregoing problems, the present application provides a method and a system for constructing a task scheduling model.
In a first aspect of the present application, a method for constructing a task scheduling model is provided, where the method includes: constructing a complex cloud resource management platform, wherein the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds; constructing a resource request layer, a task layer and an operation layer in the complex cloud resource management platform; obtaining first request information based on the resource request layer; controlling the task layer through the resource request layer, obtaining one or more task information in the task layer, and obtaining first task information in the one or more task information; controlling the operation layer through the task layer, and obtaining a plurality of operation information in the operation layer based on the first task information; controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information; completing the one or more task information until the first request information is completed.
In a second aspect of the present application, a system for constructing a task scheduling model is provided, the system comprising: the system comprises a first construction unit, a second construction unit and a third construction unit, wherein the first construction unit is used for constructing a complex cloud resource management platform, and the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds; the second construction unit is used for constructing a resource request layer, a task layer and an operation layer in the complex cloud resource management platform; a first obtaining unit, configured to obtain first request information based on the resource request layer; a second obtaining unit, configured to control the task layer through the resource request layer, obtain one or more pieces of task information in the task layer, and obtain first task information in the one or more pieces of task information; a third obtaining unit configured to control the operation layer by the task layer, and obtain a plurality of pieces of operation information in the operation layer based on the first task information; the first processing unit is used for controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information; a second processing unit to complete the one or more task information until the first request information is completed.
In a third aspect of the present application, a system for constructing a task scheduling model is provided, including: a processor coupled to a memory for storing a program that, when executed by the processor, causes a system to perform the steps of the method according to the first aspect.
In a fourth aspect of the present application, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method according to the first aspect.
One or more technical solutions provided in the present application have at least the following technical effects or advantages:
according to the technical scheme, in the process of cloud service of an enterprise, a mixed cloud comprising a public cloud and/or a private cloud is built according to business requirements, in the process of service tasks by adopting the mixed cloud, a task scheduling model comprising a resource request layer, a task layer and an operation layer is built, current request information is obtained according to the resource request layer, the request information belongs to the resource request layer, one or more task information is obtained based on the request information, the task information belongs to the task layer, a plurality of operation information corresponding to the task information in the operation layer is obtained, then the operation layer is controlled based on the task layer, a plurality of operation information corresponding to the task information is executed, a plurality of task information is completed, and execution of the current request information is finally completed. The method provided by the application can decompose one service request into a plurality of tasks by constructing a task scheduling model of a resource request layer, a task layer and an operation layer in the process of service processing of a mixed cloud, then decompose each complex task into a plurality of operations, each operation can be independently executed in the processing process, and support error processing, re-execution, manual processing step interruption and the like, can uniformly convert different types of cloud resource allocation change orders into standard operation information, combines different types of operation information together through the task information for sequential scheduling execution, finally can combine a plurality of different types of task information into one request information, a user can complete one-time DEMAND resource request of each complex resource on a cloud platform at one time, and shields the allocation change implementation operation of bottom heterogeneous resources, the operation complexity is greatly simplified, the operation time cost and the labor cost are saved, the unified and standardized storage of various cloud and multi-type resource allocation changes is realized, the multi-cloud integrated management is realized, and the technical effects of improving the mixed cloud service processing efficiency and the management efficiency are achieved.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
Fig. 1 is a schematic flow chart of a method for constructing a task scheduling model according to the present application;
FIG. 2 is a schematic diagram of interface interaction in a method for constructing a task scheduling model according to the present application;
FIG. 3 is a block diagram illustrating a process of executing first task information in a method for constructing a task scheduling model according to the present application;
FIG. 4 is a structural diagram of a system for constructing a task scheduling model according to the present application;
fig. 5 is a schematic structural diagram of an exemplary electronic device of the present application.
Description of reference numerals: a first constructing unit 11, a second constructing unit 12, a first obtaining unit 13, a second obtaining unit 14, a third obtaining unit 15, a first processing unit 16, a second processing unit 17, a processor 302, a communication interface 303, and a bus architecture 304.
Detailed Description
The application provides a method and a system for constructing a task scheduling model, which are used for solving the technical problems that in the process of processing the same service by adopting a mixed cloud in the prior art, the cloud service operations in different clouds are different, the service cannot be decomposed and customized, the service processing efficiency is low, and the management is complicated.
According to the technical scheme, in the process of cloud service of an enterprise, a mixed cloud comprising a public cloud and/or a private cloud is built according to business requirements, in the process of service tasks by adopting the mixed cloud, a task scheduling model comprising a resource request layer, a task layer and an operation layer is built, current request information is obtained according to the resource request layer, the request information belongs to the resource request layer, one or more task information is obtained based on the request information, the task information belongs to the task layer, a plurality of operation information corresponding to the task information in the operation layer is obtained, then the operation layer is controlled based on the task layer, a plurality of operation information corresponding to the task information is executed, and finally resource execution requests of the current request information are completed.
Having described the basic principles of the present application, the technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments of the present application, and the present application is not limited to the exemplary embodiments described herein. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application. It should be further noted that, for the convenience of description, only some but not all of the elements relevant to the present application are shown in the drawings.
Example one
As shown in fig. 1, the present application provides a method for constructing a task scheduling model, where the method includes:
s100: constructing a complex cloud resource management platform, wherein the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds;
specifically, the complex cloud resource management platform may be a cloud resource management platform including a plurality of public clouds or a plurality of private clouds, or may be a hybrid cloud service mode having two service modes of the public clouds and the private clouds, and an enterprise may select the cloud resource management platform according to needs.
The hybrid cloud combines the private cloud of the local infrastructure with the public cloud through a secure connection (such as a VPN connection or a leased line), and simultaneously, the hybrid cloud and the public cloud have the advantages of the private cloud and the public cloud and can deal with different service scenes.
S200: constructing a resource request layer, a task layer and an operation layer in the complex cloud resource management platform;
s300: obtaining first request information based on the resource request layer;
s400: controlling the task layer through the resource request layer, obtaining one or more task information in the task layer, and obtaining first task information in the one or more task information;
s500: controlling the operation layer through the task layer, and obtaining a plurality of operation information in the operation layer based on the first task information;
s600: controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information;
s700: completing the one or more task information until the first request information is completed.
Specifically, the resource request layer, the task layer and the operation layer are respectively used for supporting different levels of functions in the complex cloud resource management platform.
In the process of using the hybrid cloud to perform the resource application service, a user may call a request of cloud resources in the resource request layer, where one resource request is a DEMAND, that is, the DEMAND is the first request information, and in the process of processing the first request information, multiple clouds in the hybrid cloud may be required to process the request.
The task layer comprises a plurality of task information, wherein, as the cloud resources are possibly stored in a plurality of private clouds or a plurality of public clouds in the mixed cloud, a plurality of clouds are simultaneously requested to complete one request information when the request is made. Thus, the first request information corresponds to one or more task information within one or more clouds. The task layer is used for executing one or more task information.
And executing one task information in the one or more task information in the cloud, namely the first task information. That is, each task information is executed corresponding to a public cloud or a private cloud. And a plurality of operation information corresponding to each task information are executed in the public cloud or the private cloud. Specifically, the first task information indicates one task (AP), and one task corresponds to a plurality of Operations (OP) required to complete the task, that is, the plurality of operation information. Therefore, in the numerical relationship, the first task information corresponds to a plurality of operation information, and the first request information corresponds to a plurality of task information.
Further, according to the number of the processed clouds, each cloud constructs one corresponding task information, that is, one first request information corresponds to a plurality of clouds, and one task information is constructed in each cloud, so that the first request information corresponds to a plurality of task information. Thus, one DEMAND for DEMAND is formed corresponding to a plurality of APs needing to be completed, and one AP corresponds to a plurality of OPs needing to be performed.
As described above, the task information belongs to the task layer, the operation information data operation layer, and the request information belongs to the resource request layer. The task scheduling model is constructed based on the method.
The following describes the construction of a task scheduling model in a specific embodiment, but the construction is not limited by the present application. According to the method, an agile development technology stack is adopted, a back-end program is based on a SpringCloud framework, Oracle and Mysql are simultaneously used for a database, Git is used for code management, Jenkins is used for continuous integration, and docker containerization deployment is carried out.
The task information and the operation information are all a set of interfaces on the implementation level, and the execution of the task is completed through various interactions and internal logics. Fig. 2 shows a schematic diagram of a possible interface interaction in the method provided by the present application.
As shown in fig. 2, TUserApp and TOperation store data required for executing operation information, and when an interrupt occurs, ApplicationBuilder and OperationBuilder provide methods for recovering an operating state from the two data objects after the interrupt. The execution of the operation information is controlled by the task information, the operation information cannot be interrupted, and the task information can schedule the execution of each operation information.
According to the method, a unified enterprise Configuration Management Database (CMDB) is realized through the design, task scheduling data of various public clouds and enterprise private clouds in a mixed cloud used by an enterprise can be uniformly adapted, and a whole set of standardized and streamlined full-life-cycle task scheduling Management framework is formed. The task scheduling model supports application, distribution and recovery of public cloud CVM, private cloud Vmware virtual machines, storage, databases and various types of software, and user-definable configuration operation is realized according to enterprise requirements.
According to the method, one resource request is decomposed into a plurality of more complex tasks, then each complex task is decomposed into a plurality of operations, each operation can be executed in a single step, error processing of steps such as re-execution of the tasks and single-step execution of errors is supported, step interruption can be manually processed, customized scripts of operation information can be customized, and customized change configuration of resources is achieved. According to the method and the device, cloud resource allocation change orders of different clouds and different types are uniformly converted into standard operation information, the operation information of different types is combined together through the task information to be scheduled and executed, and finally the task information of different types is combined into the resource request information DEMAND, so that the allocation change implementation operation of bottom heterogeneous resources is shielded, the bottom difference of different clouds is shielded, the operation complexity is greatly simplified, the operation time cost and the labor cost are saved, and the processing efficiency and the management efficiency of cloud services are improved.
Fig. 3 shows a schematic diagram of one possible processing of single task information provided by the present application. As shown in fig. 3, step S600 in the method provided by the present application includes:
s610: obtaining first operation information according to the first task;
s620: judging whether the state of the first operation information is a non-state;
s630: if the state of the first operation information is a non-state, judging whether the first operation information needs to be confirmed or not;
s640: if the first operation information needs to be confirmed, updating the first task state into a waiting confirmation state;
s650: and executing the first operation information if the first operation information does not need to be confirmed.
Specifically, the dynamic interaction logic of task information and operation information during execution is divided into a plurality of cases. The corresponding operation information is also divided into various types according to different clouds, different task information and the like.
By way of example and not limitation, after a user submits resource request information required by a certain service through a hybrid cloud, the user simultaneously requires multiple clouds to process, and then the resources are divided into a plurality of task information with a considerable number. In a certain public cloud, task information can be divided into a plurality of operation information, the operation information is distributed and separated by a CVM (composite virtual machine), and can be decomposed into 4 operation information in total, wherein the operation information can be created by the CVM, customized configuration of the CVM (initializing file systems, networks, yum sources and other customized configurations in the CV M), software installation (immediately installing software such as weblogic, MySQL and the like according to the application requirements after the CVM is created), and synchronous CMDB data (unified and centralized entry of the CVM and software data and task scheduling execution data), and each step of operation information can be independently executed in a single step.
And when the execution of the task information fails, the task information can be selected to be re-executed (automatically cleaning the executed data, restoring the state of the resource which is not executed and re-executing the task) or the failed step is broken point single step executed. If there are other custom execution steps to be added to the task information, one step of operation information can be added to the task information for implementation.
Specifically, the dynamic interaction between each OP (operation information) and the AP (task information) during the execution process is complicated, and each OP has its own state, for example, including: ST ART _ COMMIRM, END _ CONFIRM, etc. The AP schedules a decision to execute the OP or to stop waiting for CONFIRM by checking the status of the OP.
When CONFIRM ends, the operating environment before CONFIRM is resumed to continue the flow after interruption. Confreim may occur before OP execution (START _ CONFIRM) or after OP execution (END _ CONFIRM M), and thus, support may be provided for more application scenarios.
After the AP has reviewed the status of each OP and processed, the AP has completed the entire process, and the AP is finished. The AP plays a controlling role and the OP is executed passively. Of course the AP also has its own state. The typical AP-OP model is two-layered, in the application, the model is expanded into three layers, and a DEMAND layer is added outside the AP to form the DEMAND-AP-OP. The AP is equivalent to DEMAND, namely OP is equivalent to the AP, and the corresponding relation between DEMAND and AP is one-to-many.
As shown in fig. 3, when a first task is executed in a cloud, first, a state of the currently executed first operation information is obtained according to an ID of the current first task information and an operation information index of a plurality of operation information in the first task information, whether the state of the currently executed first operation information is a non-state is determined, if the state is the non-state, it is verified that no operation information is currently executed, and operation information to be started is required, whether the first operation information needs to be confirmed to start is determined, if the operation information to be started is required, the state of the first task information is updated to wait for confirmation to start, and then, the user is waited for confirmation. If the first operation information does not need to start confirmation, the operation information which does not need to wait for starting confirmation exists at present, and the operation information is further executed.
As shown in fig. 3, step S620 in the method provided by the present application further includes:
s621: if the state of the first operation information is a presence state, judging whether the state of the first operation information is waiting for starting to confirm;
s622: if the state of the first operation information is waiting for starting to confirm, executing the first operation information;
s623: and if the state of the first operation information is not the waiting starting confirmation, judging whether the state of the first operation information is the waiting ending confirmation.
Step S622 in the method provided by the present application includes:
s622-1: judging whether the first operation information is executed successfully or not;
s622-2: if the first operation information is successfully executed, judging whether the first operation information needs to be finished and confirmed;
s622-3: and if the first operation information fails to be executed, determining that the first operation information is wrongly deployed.
Specifically, if the current state of the first operation information is present, it indicates that there is currently operation information waiting for execution or in progress. And further judging whether the current first operation information is waiting for starting confirmation, if so, indicating that the operation information waiting for starting execution exists. Further, the operation information waiting for starting execution is confirmed to start execution, and the operation information is executed. If not, the current operation information does not need to be confirmed, and whether the operation information needs to be confirmed or not is judged during or after the execution.
After the execution, whether the execution of the operation information is successful is judged, if the execution is failed, the deployment is wrong, and the operation needs to be executed again or other operations are carried out. If the execution is successful, the operation information is executed completely, and whether the operation information needs to be finished and confirmed is judged.
As shown in fig. 3, step S623 of the method provided by the present application includes:
s623-1: if the state of the first operation information is waiting for the end confirmation, updating the state of the first operation information to be the completion, and judging whether the first task information has second operation information or not;
s623-2: and if the state of the first operation information is not the waiting end confirmation, determining that the state of the first operation information is an invalid state.
Specifically, if the state of the first operation information is a wait for end confirmation, which indicates that the execution of the current operation information is completed, the state of the first operation information is updated to be completed. If the first operation information is not waiting for completion confirmation, the state of the first operation information is not any of the stateless state, waiting for start confirmation, waiting for completion confirmation, and invalid operation information state, and re-execution or manual processing is required.
The method provided by the present application further includes, after step S622-2:
s622-21: if the first operation information needs to be finished and confirmed, updating the state of the first operation information into a state of waiting for finishing and confirming;
s622-22: and if the first operation information does not need to be finished and confirmed, judging whether the first task information has the second operation information.
Specifically, if the current operation information needs to be finished and confirmed after being executed, the state of the operation information is modified to be waiting for finishing and confirmed, if the operation information can be finished without finishing and confirmed, the next operation information is directly scheduled and executed, and the steps are repeated. Specifically, it is determined whether the second operation information exists after the first task information is executed.
The step of "determining whether the first task information has the second operation information" in the method provided by the present application includes:
if the first task information has the second operation information, the first task information obtains the second operation information;
and if the first task information does not have the second operation information, determining that the first task information is completely deployed.
Specifically, if the second operation information does not exist after the first operation information is executed in the current first task information, the current first task information is deployed completely. And if the second operation information exists after the first operation information is executed in the current first task information, executing the next second operation information, and repeating the steps until the first task information is deployed.
In this way, the above steps are repeated in a plurality of clouds in the mixed cloud until the deployment of a plurality of task information in one DEMAN D request is completed, and the DEMAN request is processed.
In summary, the method provided by the application can decompose a resource request service into a plurality of tasks by constructing a task scheduling model of a resource request layer, a task layer and an operation layer in the process of service processing of a hybrid cloud, then decompose each complex task into a plurality of operations, each operation can be executed independently in the processing process, and support error processing, re-execution, manual processing step interruption and the like, can uniformly convert different types of cloud resource allocation change orders into standard operation information, then combine different types of operation information together through task information for sequential scheduling execution, finally combine a plurality of different types of task information into one request information, a user can complete one-time resource request of various complex resources on a cloud platform at one time, and shield the allocation change implementation operation of bottom heterogeneous resources, the operation complexity is greatly simplified, the operation time cost and the labor cost are saved, the unified and standardized storage of various cloud and multi-type resource allocation changes is realized, the multi-cloud integrated management is realized, and the technical effects of improving the mixed cloud service processing efficiency and the management efficiency are achieved.
Example two
Based on the same inventive concept as the method for constructing the task scheduling model in the foregoing embodiment, as shown in fig. 4, the present application provides a system for constructing the task scheduling model, wherein the system includes:
the first building unit 11 is used for building a complex cloud resource management platform, and the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds;
a second constructing unit 12, where the second constructing unit 121 is configured to construct a resource request layer, a task layer, and an operation layer in the complex cloud resource management platform;
a first obtaining unit 13, where the first obtaining unit 13 is configured to obtain first request information based on the resource request layer;
a second obtaining unit 14, where the second obtaining unit 14 is configured to control the task layer through the resource request layer, obtain one or more pieces of task information in the task layer, and obtain first task information in the one or more pieces of task information;
a third obtaining unit 15, where the third obtaining unit 15 is configured to control the operation layer through the task layer, and obtain a plurality of operation information in the operation layer based on the first task information;
a first processing unit 16, where the first processing unit 16 is configured to control the operation layer based on the task layer, and control one or more of the plurality of operation information to execute corresponding operations according to the first task information, so as to complete the first task information;
a second processing unit 17, said second processing unit 17 being configured to complete said one or more task information until said first request information is completed.
Further, the system further comprises:
a fourth obtaining unit configured to obtain the first operation information according to the first task;
a first judging unit configured to judge whether a state of the first operation information is a non-state;
a second judging unit, configured to judge whether the first operation information needs to be confirmed if the state of the first operation information is a non-state;
a third processing unit, configured to update the first task state to wait for a start confirmation if the first operation information requires a start confirmation;
a fourth processing unit, configured to execute the first operation information if the first operation information does not need to start confirmation.
Further, the system further comprises:
a third judging unit, configured to judge whether the state of the first operation information is a wait for start confirmation if the state of the first operation information is a present state;
a fifth processing unit, configured to execute the first operation information if the state of the first operation information is a wait for start confirmation;
a fourth judging unit configured to judge whether the state of the first operation information is a wait end confirmation or not, if the state of the first operation information is not a wait start confirmation.
Further, the system further comprises:
a fifth judging unit, configured to judge whether the first operation information is successfully executed;
a sixth judging unit, configured to judge whether the first operation information needs to be finished and confirmed if the first operation information is successfully executed;
a sixth processing unit, configured to determine that the first operation information is deployed incorrectly if the first operation information fails to be executed.
Further, the system further comprises:
a seventh determining unit, configured to determine whether the first task information has second operation information if the state of the first operation information is a wait for end confirmation and the state of the first operation information is updated to be complete;
a seventh processing unit, configured to determine that the state of the first operation information is an invalid state if the state of the first operation information is not a wait for end confirmation.
Further, the system further comprises:
an eighth processing unit, configured to update a state of the first operation information to be a wait for end confirmation if the first operation information requires end confirmation;
an eighth determining unit, configured to determine whether the first task information has the second operation information if the first operation information does not need to be finished.
Further, the system further comprises:
a fifth obtaining unit, configured to obtain the second operation information from the first task information if the second operation information exists in the first task information;
a ninth processing unit, configured to determine that the first task information deployment is complete if the first task information does not exist in the second operation information.
EXAMPLE III
Based on the same inventive concept as the method for constructing a task scheduling model in the foregoing embodiment, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method as in the first embodiment.
Exemplary electronic device
The electronic device of the present application is described below with reference to figure 5,
based on the same inventive concept as the method for constructing the task scheduling model in the foregoing embodiment, the present application also provides a system for constructing the task scheduling model, including: a processor coupled to a memory, the memory for storing a program that, when executed by the processor, causes the system to perform the steps of the method of embodiment one.
The electronic device 300 includes: processor 302, communication interface 303, memory 301. Optionally, the electronic device 300 may also include a bus architecture 304. Wherein, the communication interface 303, the processor 302 and the memory 301 may be connected to each other through a bus architecture 304; the bus architecture 304 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus architecture 304 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
The communication interface 303 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), a wired access network, and the like.
The memory 301 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM (electrically erasable programmable read-only memory), a CD-ROM (compact-read-only memory) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor through a bus architecture 304. The memory may also be integral to the processor.
The memory 301 is used for storing computer-executable instructions for executing the present application, and is controlled by the processor 302 to execute. The processor 302 is configured to execute the computer-executable instructions stored in the memory 301, so as to implement a method for constructing a task scheduling model provided by the above-mentioned embodiments of the present application.
Those of ordinary skill in the art will understand that: the various numbers of the first, second, etc. mentioned in this application are for convenience of description and are not intended to limit the scope of this application nor to indicate the order of precedence. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one" means one or more. At least two means two or more. "at least one," "any," or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one (one ) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the present application are generated, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The various illustrative logical units and circuits described in this application may be implemented or operated through the design of a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in this application may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software cells may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be disposed in a terminal. In the alternative, the processor and the storage medium may reside in different components within the terminal. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the application and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the present application and its equivalent technology, it is intended that the present application include such modifications and variations.
Claims (10)
1. A method for constructing a task scheduling model, the method comprising:
constructing a complex cloud resource management platform, wherein the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds;
constructing a resource request layer, a task layer and an operation layer in the complex cloud resource management platform;
obtaining first request information based on the resource request layer;
controlling the task layer through the resource request layer, obtaining one or more task information in the task layer, and obtaining first task information in the one or more task information;
controlling the operation layer through the task layer, and obtaining a plurality of operation information in the operation layer based on the first task information;
controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information;
completing the one or more task information until the first request information is completed.
2. The method of claim 1, wherein each of the one or more task information corresponds to one of the public cloud or the private cloud, respectively.
3. The method of claim 1, wherein the controlling the operation layer based on the task layer, and controlling one or more of the plurality of operation information to perform corresponding operations according to the first task information comprises:
obtaining first operation information according to the first task;
judging whether the state of the first operation information is a non-state;
if the state of the first operation information is a non-state, judging whether the first operation information needs to be confirmed or not;
if the first operation information needs to be confirmed, updating the first task state into a waiting confirmation state;
and executing the first operation information if the first operation information does not need to be confirmed.
4. The method of claim 3, wherein after determining whether the state of the first operation information is stateless, further comprising:
if the state of the first operation information is a presence state, judging whether the state of the first operation information is waiting for starting to confirm;
if the state of the first operation information is waiting for starting to confirm, executing the first operation information;
and if the state of the first operation information is not the waiting starting confirmation, judging whether the state of the first operation information is the waiting ending confirmation.
5. The method of claim 4, wherein if the status of the first operation information is waiting for a start confirmation, after executing the first operation information, further comprising:
judging whether the first operation information is executed successfully or not;
if the first operation information is successfully executed, judging whether the first operation information needs to be finished and confirmed;
and if the first operation information fails to be executed, determining that the first operation information is wrongly deployed.
6. The method of claim 5, wherein if the status of the first operation information is not after waiting for a start confirmation, determining whether the status of the first operation information is after waiting for an end confirmation, further comprises:
if the state of the first operation information is waiting for the end confirmation, updating the state of the first operation information to be the completion, and judging whether the first task information has second operation information or not;
and if the state of the first operation information is not the waiting end confirmation, determining that the state of the first operation information is an invalid state.
7. The method of claim 6, wherein after determining whether the first operation information needs to be finished and confirmed if the first operation information is successfully executed, further comprising:
if the first operation information needs to be finished and confirmed, updating the state of the first operation information into a state of waiting for finishing and confirming;
and if the first operation information does not need to be finished and confirmed, judging whether the first task information has the second operation information.
8. The method of claim 7, wherein after determining whether the second operation information exists in the first task information, further comprising:
if the first task information has the second operation information, the first task information obtains the second operation information;
and if the first task information does not have the second operation information, determining that the first task information is completely deployed.
9. A system for constructing a task scheduling model, the system comprising:
the system comprises a first construction unit, a second construction unit and a third construction unit, wherein the first construction unit is used for constructing a complex cloud resource management platform, and the complex cloud resource management platform comprises a plurality of public clouds and/or private clouds;
the second construction unit is used for constructing a resource request layer, a task layer and an operation layer in the complex cloud resource management platform;
a first obtaining unit, configured to obtain first request information based on the resource request layer;
a second obtaining unit, configured to control the task layer through the resource request layer, obtain one or more pieces of task information in the task layer, and obtain first task information in the one or more pieces of task information;
a third obtaining unit configured to control the operation layer by the task layer, and obtain a plurality of pieces of operation information in the operation layer based on the first task information;
the first processing unit is used for controlling the operation layer based on the task layer, controlling one or more of the plurality of operation information to execute corresponding operations according to the first task information, and completing the first task information;
a second processing unit to complete the one or more task information until the first request information is completed.
10. A system for constructing a task scheduling model, comprising: a processor coupled to a memory for storing a program that, when executed by the processor, causes a system to perform the steps of the method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111639864.4A CN114327895A (en) | 2021-12-29 | 2021-12-29 | Method and system for constructing task scheduling model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111639864.4A CN114327895A (en) | 2021-12-29 | 2021-12-29 | Method and system for constructing task scheduling model |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114327895A true CN114327895A (en) | 2022-04-12 |
Family
ID=81016544
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111639864.4A Pending CN114327895A (en) | 2021-12-29 | 2021-12-29 | Method and system for constructing task scheduling model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114327895A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160218926A1 (en) * | 2015-01-26 | 2016-07-28 | DivvyCloud Corporation | Network Resource Management Devices Methods And Systems |
| CN111552471A (en) * | 2020-04-07 | 2020-08-18 | 电科云(北京)科技有限公司 | Task arrangement method and system under hybrid cloud environment |
| CN111797414A (en) * | 2020-06-24 | 2020-10-20 | 北京青云科技股份有限公司 | Hybrid cloud management method and system and cloud service platform |
| US20200344137A1 (en) * | 2017-12-19 | 2020-10-29 | Atos Uk International It Services Limited | Orchestrated hybrid cloud system for sap |
| CN113676537A (en) * | 2021-08-18 | 2021-11-19 | 中数通信息有限公司 | Heterogeneous cloud resource unified management platform |
-
2021
- 2021-12-29 CN CN202111639864.4A patent/CN114327895A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160218926A1 (en) * | 2015-01-26 | 2016-07-28 | DivvyCloud Corporation | Network Resource Management Devices Methods And Systems |
| US20200344137A1 (en) * | 2017-12-19 | 2020-10-29 | Atos Uk International It Services Limited | Orchestrated hybrid cloud system for sap |
| CN111552471A (en) * | 2020-04-07 | 2020-08-18 | 电科云(北京)科技有限公司 | Task arrangement method and system under hybrid cloud environment |
| CN111797414A (en) * | 2020-06-24 | 2020-10-20 | 北京青云科技股份有限公司 | Hybrid cloud management method and system and cloud service platform |
| CN113676537A (en) * | 2021-08-18 | 2021-11-19 | 中数通信息有限公司 | Heterogeneous cloud resource unified management platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10613788B2 (en) | Data migration between cloud storage systems | |
| CN109710236B (en) | Service development and implementation method, device, platform and medium based on shared service | |
| CN108694053A (en) | Build the method and terminal device of Kubernetes host nodes automatically based on Ansible tools | |
| CN110325968A (en) | System upgrade management in distributed computing system | |
| CN105005487A (en) | Continuous-service high-performance cluster operating system online upgrading method | |
| US20080244589A1 (en) | Task manager | |
| US10025630B2 (en) | Operating programs on a computer cluster | |
| CN112470119B (en) | Service upgrading method and device in distributed system and distributed system | |
| US20140156851A1 (en) | Server facility, method for providing copying service for system of server facility, and copying program for system of sever facility | |
| CN113886089A (en) | Task processing method, device, system, equipment and medium | |
| JP6668658B2 (en) | Job management method, job management device, and program | |
| CN117170803A (en) | Method for generating signal-creation operating system pipeline, electronic equipment and storage medium | |
| CN114489954A (en) | Tenant creation method based on virtualization platform, tenant access method and equipment | |
| US20240086173A1 (en) | Distributed autonomous patching system | |
| JP7439928B2 (en) | Management device, management method, management program, and management system | |
| CN117827435A (en) | Cloud host pre-allocation method in resource pool | |
| CN114327895A (en) | Method and system for constructing task scheduling model | |
| CN111984623A (en) | Database cluster automatic deployment method, device, medium and electronic equipment | |
| CN110764876A (en) | Cloud host creation method, device, equipment and readable storage medium | |
| US9471536B1 (en) | Automated firmware settings management | |
| CN115150268A (en) | Network configuration method and device of Kubernetes cluster and electronic equipment | |
| CN115277398A (en) | Cluster network configuration method and device | |
| CN114185557A (en) | Software product deployment method, device, medium and electronic equipment | |
| CN112035368A (en) | Automatic software testing method and device, electronic equipment and storage medium | |
| CN114615144B (en) | Network optimization method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |