CN106790455B - A kind of distributed cloud management system and method based on mixed mode - Google Patents
A kind of distributed cloud management system and method based on mixed mode Download PDFInfo
- Publication number
- CN106790455B CN106790455B CN201611122409.6A CN201611122409A CN106790455B CN 106790455 B CN106790455 B CN 106790455B CN 201611122409 A CN201611122409 A CN 201611122409A CN 106790455 B CN106790455 B CN 106790455B
- Authority
- CN
- China
- Prior art keywords
- service
- workflow
- cloud
- manager
- result
- 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.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The distributed cloud management method and system based on mixed mode that the present invention relates to a kind of, belong to cloud service and computing technique field.It is most of including client service, control centre, configuration center, proxy server and cloud server terminal five.The present invention makes it have scalability and maintainable high feature for the defect for overcoming the scalability and maintainability of existing distributed cloud management system low, to promote managerial ability of the existing distributed cloud management system to cloud service, the maintainability of lifting system.
Description
Technical field
The present invention relates to a kind of distributed cloud management system and method based on mixed mode belongs to cloud service and calculates skill
Art field.
Background technique
The problem of cloud computing development is maked rapid progress, and cloud computing at present still focuses on solving individual data central interior, but with
The development of global internet, the needs that more and more enterprises have cross-region to establish branch, each region, each level number
It comes into being according to center, and these numerous data centers are in funnel-shaped construction and controlled state, this makes individually
The cloud management system of data center has the following problems: (1) multi-source, complex management is presented in cloud service.In each data
The cloud service of the heart differs greatly in way to manage, and if private clound supports the management to physical resource, and public cloud is supported to upper
The management of layer service, while the resource isomery of each data center, so that management cost is very high;(2) business degree of coupling is high.By
Different in the type of service of individual data center carrying, software and hardware system differs greatly, and physical resource and applies close coupling, business
Deployment is online, management O&M etc. operations not reusable so that maintenance cost is very high;(3) service logic description is difficult.Work as demand
Increase, when system becomes huge, service logic becomes complexity, existing service logic needs constantly modification even to redefine, and makes
The extension difficulty for the system of obtaining increases, system flexibility decline.
And distributed cloud management system can effectively solve the problem that problem above, core concept are the interoperability marks proposed between cloud
Standard, establishes unified interface, designs reasonable distributed cloud model, for across between cloud data exchange and service arrangement branch is provided
Support.Distributed cloud is just gradually becoming the focus of attention of industrial circle and academia, and Gartner report is pointed out, in dispersion building data
The heart will become one of following " the ten big subversiveness technologies for influencing data center ", and data center gradually disperses to build, rather than makees
It is established for overall structure.
Existing distribution cloud management system such as Eucalyptus, OpenStack, OpenNebula, by private clound and one
A or multiple public clouds composition mixed architecture models are with the SLA that ensures service quality, in mixed architecture, private clound and public cloud
Status is asymmetrical relationship, and private clound is occupied an leading position, and public cloud is as the standby for improving private clound response application peak demand
Resource, but mixed architecture is limited to the control ability of public cloud, can only carry out within the scope of authority resource in public cloud manufacturer
Simple control, without supporting advanced control.The distributed cloud management system such as Reservior of another aggregation scheme,
Different cloud service suppliers is regarded as the peer-to-peer of affiliate by InterCloud, when side's resource is insufficient
It is leased from other cloud service supplier, to make full use of resource, this mode has stringent want to the matching degree of cloud service interface
It asks, the degree of coupling is higher between the different product of general same cloud service supplier, is more suitable for using the mode.
Summary of the invention
The technical problem to be solved by the present invention is overcoming the deficiencies of the prior art and provide a kind of point based on mixed mode
Cloth cloud management system and method has the characteristics that scalability and maintainability are high, to promote existing distributed cloud management system
To the managerial ability of cloud service, the maintainability of lifting system.
The technical solution of the invention is as follows: a kind of distributed cloud management system based on mixed mode, including client's clothes
Business end, control centre, configuration center, proxy server and cloud server terminal;
Customer service is the interactive service on foreground, and the main body of service can be specific people and be also possible to apply, and works as client
When having demand to certain Service Source, client service initiates the request comprising service logic to control centre;
Control centre is core, including service managerZ-HU and workflow manager;Service managerZ-HU is used based on tree
The allocation models of type structure, so that multi-source heterogeneous cloud server terminal is configurable, the target object of service managerZ-HU management is difference
The cloud server terminal of type, including public cloud and private clound.For private clound, service managerZ-HU passes through configuration center deployment one
A new private clound, or an existing private clound of adapter tube, and to offering customers service;For public cloud, service management
Device obtains the access way of cloud server terminal by configuration center from proxy server, and usually the service call of http protocol connects
Mouthful, service managerZ-HU carries out unified encapsulation to these interfaces, and to offering customers service;Workflow manager uses workflow mould
Plate, so that the service logic of cloud server terminal is configurable, when control centre receives the request that client service is sent, by working
Flow manager is handled, and the request of client is converted workflow by workflow manager, and coordinates cloud by service managerZ-HU
Each serviced component of server-side executes the step in workflow, handles implementing result according to the type of workflow, when there is step
When executing generation mistake, rollback has been executed step by workflow manager, avoids the generation of redundant data;
Configuration center is responsible for the configuration file by service describing provided by cloud server terminal at unified format, when needs connect
When entering new cloud server terminal, configuration center is obtained from cloud service supplier accesses required details, including cloud service class
The information being collected into is converted unified format by type, cloud service title, cloud service version, cloud service content etc., configuration center
Configuration file, service managerZ-HU configure cloud service, mark of the configuration file as cloud server terminal service provided according to configuration file
Standard is capable of the service differences of directviewing description difference cloud, while configuration file determines which clothes service managerZ-HU provides to client
Business, the service content of cloud server terminal can be quickly adjusted to the modification of configuration file;
Proxy server is the distinctive service middle layer of public cloud, encapsulates clothes provided by public cloud service supplier
Business interface, when client service initiates the resource access request of a public cloud, workflow manager forwards the request to clothes
Business manager, service managerZ-HU reinform the request of proxy server customer in response, the side that proxy server passes through far call
Formula accesses the resource in public cloud;
Cloud server terminal is the set of the cloud service supplier referred to the accession to, and each cloud service supply commercial city externally provides one kind
Or a plurality of types of services.
Further, the service managerZ-HU includes that cloud configures interface, and the specific implementation of the interface and the interface have
The working method of body includes:
The cloud configuration interface is created, the parameter of design cloud configuration interface, the parameter includes cloud service type, cloud service
Title, cloud service version, cloud service content;
The attribute of the cloud configuration interface parameters is defined, the attribute includes the type, value range and the parameter of parameter
Whether be must parameter mark;
Call the return of cloud configuration interface corresponding as a result, that the cloud configuration interface returns the result is that an XML is indicated
Tree, the depth of tree is 3, and the 1st layer of tree i.e. root node is the authentication service of cloud, and the 2nd layer of tree is each of cloud
A kernel service, the 3rd layer of tree is the operation of cloud service, and the cloud kernel service including but not limited to calculates service, storage
Service, network service, backup services, security service, mirroring service, the operation of the cloud service including but not limited to creates,
Starting, closing, deletion, carry, unloading, configuration, enabling, connection, disconnection.
Further, the workflow manager consists of the following parts: task dispatcher, process management unit, task
Manager, service call unit and exception processing unit, in which:
Task dispatcher is responsible for receiving the request of client, and according to request type trigger process administrative unit, will finally be adjusted
Client is returned to the result of service;
Process management unit, be in charge of the management flow template, can generate workflow template according to different service logics,
It saves in xml format, in process implementation procedure, corresponding workflow template is matched according to request content, and according to template generation
Serializing event passes to task manager;
Task manager is in charge of the management and flows example, and workflow instance can be created and run according to serializing event,
And workflow instance can be terminated according to the feedback of exception processing unit, in process implementation procedure, according to serializing event creation
And workflow instance is run, the execution order of work flow step is initiated to service call unit;
Service call unit is responsible for analysis and executes order, calls corresponding service, while the result of service call being returned
To task dispatcher, in process implementation procedure, the step of record has executed, when there is step that failure occurs, exception will be triggered
It manages unit and carries out abnormality processing;
Exception processing unit is responsible for handling exception according to Exception Type, and has executed step, abnormality processing in the process that retracts
As a result it will be recorded in log, and result is fed back into task manager.
Further, the step in the same workflow template can the multiple cloud service suppliers access moneys of span
Source, to meet the needs of service logic, as that can apply for the cloud disk service in public cloud when private clound virtual machine creating.
Further, in the process management unit, it is specific as follows that workflow template is generated according to different service logics:
Creation generates the interface of workflow template, the parameter of designing workflows template interface, the workflow template interface
Parameter include workflow title, work flow step title, work flow step type, work flow step ID, work flow step source;
The attribute of workflow template parameter is defined, the attribute includes the type of workflow template parameter and indicates to be somebody's turn to do
Whether parameter is necessary mark;
It calls and generates corresponding to the return of workflow template interface as a result, returning the result the workflow mould for XML format
Plate.
The workflow template for XML format is returned the result, the format sample of the workflow template is as follows:
<? xml version=" 1.0 " encoding=" UTF-8 "?>
<workflow name=" createVmFlow ">
<list>
< setp name=" VmAllocateHostFlow " class=" sequence " id=" 1 " source=" KVM "
></step>
<setp name="VmCreateVolumeFlow"class="sync"id="2"source="KVM"></
step>
< setp name=" VmCreateDataVolumeFlow " class=" sync " id=" 2 " source=" ECS "
></step>
<setp name=" VmCreateInterfaceFlow " class=" sync " id=" 2 " source=" KVM ">
</step>
< setp name=" VmCreateOnHostFlow " class=" sequence " id=" 3 " source=" KVM "
></step>
</list>
</workflow>
The effect of the workflow template is by the step relational graph of workflow, and usually directed acyclic graph, is converted to XML
The description file of format, the content of workflow template include workflow title, work flow step title, work flow step type,
Work flow step ID, work flow step source.
Workflow title a, function point of usually corresponding client service, such as creates virtual machine;
Work flow step title, the sequence of operations of usually corresponding client service, as created in virtual machine to calculating, deposit
Storage, the selection of Internet resources;
Work flow step type is the implementation procedure essential attribute defined by workflow manager, indicates the step and its
Incidence relation between his step, such as synchronous execution, asynchronous execution, concurrently execution, sequence execution;
Work flow step ID is that the step of workflow manager is automatically generated according to work flow step type executes ID, is used
Carry out accessory ID step and executes sequence in workflow;
Work flow step source identifies the cloud service supplier of step access, usually the title of cloud service supplier.
The type that the work flow step is supported is as follows:
Further, the description of the workflow instance is recorded in database and file, when occurring for failure again
Generate example.
Further, the description content of workflow instance includes example ID, has executed step title and implementing result.
Further, the distributed cloud management method further includes the rollback operation of workflow, rollback operation will execute with
Lower step:
During workflow execution, record has executed step title and result to database, while local file is recorded;
When mistake occurs in the process of implementation for workflow, workflow, which terminates, to be executed, and has preferentially been executed from database reading
Step title and as a result, and call related service carry out workflow rollback;
When database can not access, step title has been executed and as a result, and calling related service from local file reading
Carry out workflow rollback;
Journal file is recorded in the implementing result of rollback operation.
Further, the database is deployed on the server where control centre.
Further, the XML is described on the server where file is stored in control centre.
The advantages of the present invention over the prior art are that:
(1) present invention for existing cloud management platform simultaneously manage multiple multi-sources, isomery cloud service supplier effect not
Good problem, using service managerZ-HU as the software adaptation layer of cloud server terminal, the cloud service that different cloud service suppliers are provided
Consistency configuration is carried out, and unified encapsulation is carried out to different cloud service interfaces, it can be multi-source heterogeneous with unified model management
Cloud server terminal;
(2) present invention is maintainable for the complicated business logic in user's request for existing cloud management platform and extends
Service logic in request is described as workflow using the management mode of workflow by the low problem of property, uses workflow mould
Plate and workflow instance carry out life cycle management to workflow, improve the maintainability of system;Meanwhile workflow execution step
Source is configurable, supports the resource for accessing different cloud service suppliers in workflow instance implementation procedure, improves the scalability of system.
Detailed description of the invention
Fig. 1 is the structural schematic diagram of the distributed cloud management system based on mixed mode of the embodiment of the present invention;
Fig. 2 is the structural representation of the cloud configuration of the distributed cloud management system based on mixed mode of the embodiment of the present invention
Figure;
Fig. 3 is the workflow manager process of the distributed cloud management method based on mixed mode of the embodiment of the present invention
Schematic diagram;
Fig. 4 is that the workflow rollback process of the distributed cloud management method based on mixed mode of the embodiment of the present invention is shown
It is intended to.
Specific implementation method
Below in conjunction with attached drawing of the invention, further illustrate that technical solution of the present invention, described embodiment are these
Invention a part of the embodiment, without representing whole embodiments.
For those skilled in the art, some well-known techniques may not be described in detail.
In the present embodiment, a kind of distributed cloud management system based on mixed mode, as shown in Figure 1, a kind of based on mixing
The distributed cloud management method of mode, it is characterised in that steps are as follows:
Step 101: configuration center is obtained from cloud service supplier access the cloud server terminal needed for information, including cloud service
Type, cloud service title, cloud service version, cloud service content etc.;
Step 102: service managerZ-HU calls cloud to configure interface, the information about cloud server terminal that configuration center is collected into
It is converted to the description file of XML format, configuration center will call the implementing result of cloud configuration interface to return to service managerZ-HU;
Step 103: service managerZ-HU unites service provided by cloud server terminal according to returning the result for configuration center
One encapsulation, and the service interface with other cloud service isomorphisms is provided to client service;
Step 104: client initiates the resource access request of a cloud server terminal by client service, and request is by control
The workflow manager of the heart is handled;
Step 105: request content is converted to workflow by workflow manager, and is called according to the execution step of workflow
The implementing result of interface is returned to workflow manager by the relevant interface of service managerZ-HU, service managerZ-HU, if in step
Interface calling return the result as failure, then enable workflow rollback operation, workflow manager calls returning for service managerZ-HU
Relevant interface is moved back, the implementing result for the interface that retracts is returned to workflow manager by service managerZ-HU;
Step 106: service managerZ-HU executes interface calling procedure, accesses the related resource of cloud service, and receive cloud service
Return the result.
In the present embodiment, a kind of structural schematic diagram of the cloud configuration of the distributed cloud management system based on mixed mode, such as
Shown in Fig. 2, each service and operation of cloud are expressed as a tree model, and the basic constraint of tree is: the depth of tree is 3,
The namely root node of the 1st layer of tree is the authentication service of cloud;The 2nd layer of tree is each kernel service of cloud, including is calculated
Service, storage service, network service, backup services, security service, mirroring service etc.;The 3rd layer of tree is the operation of cloud service,
Including but not limited to creation, starting, closing, deletion, carry, unloading, configuration, enabling, connection, disconnection.Cloud allocation models with
Unified model describes service and operation provided by cloud server terminal, the configurability and scalability of lifting system.
In the present embodiment, a kind of process such as Fig. 3 of the distributed cloud management method workflow manager based on mixed mode
Shown, specific implementation step is as follows:
Step 301: client submits the request comprising defined service logic in system to task dispatcher, task tune
Spend device analysis request type;
Step 302: according to request type, task dispatcher triggers corresponding process management unit;
Step 303: process management unit analysis request content matches it with existing workflow template;
Step 304: process management unit passes to task pipe as parameter according to workflow template, formation sequence event
Manage device;
Step 305: task manager receives serializing event, creates and run workflow instance, when receiving from different
When the abnormal feedback of normal processing unit, then the operating status of workflow instance is terminated immediately;
Step 306: task manager initiates the execution order of the execution step comprising workflow to service call unit;
Step 307: service call unit executes workflow according to step, calls related service, and the service refers to control
The service managerZ-HU at center encapsulates the unified of cloud server terminal service interface;
Step 308: service call unit is responsible for the implementing result of workflow returning to task dispatcher;
Step 309: task manager is responsible for submitting the workflow execution result of request to return to client client;
Step 310: when service call failure, service call unit will trigger exception processing unit and carry out abnormality processing;
Step 311: exception processing unit be responsible for executed work flow step carry out rollback operation;
Step 312: the result of abnormality processing feeds back to task manager, and task manager terminates workflow instance;
Step 313: while the result of abnormality processing is recorded in abnormal log file.
A kind of workflow backing method of the management method based on mixed mode in the present embodiment, as shown in Figure 4:
Step 401: in service calling module, workflow table is shown as specifically executing step, is held in a manner of service call
Row;
Step 402: when service call success, number is recorded in the title that step has been executed in workflow instance and result
According to library and file;
Step 403: task manager terminates the operation of workflow instance according to the feedback result of exception processing unit;
Step 404: exception processing unit reads the title that step is completed from database and as a result, for carrying out workflow
Rollback operation;
Step 405: when reading successfully from database, exception processing unit calls related service to carry out workflow rollback behaviour
Make;
Step 406: when from database read failure when, exception processing unit from file read be completed step title and
As a result, for carrying out workflow rollback operation;
Step 407: when reading successfully from file, exception processing unit calls related service to carry out workflow rollback behaviour
Make.
The description of the specific implementation method of the embodiment of the present invention is merely illustrative above, protection scope of the present invention
It is illustrated by described claims.Those skilled in the art is understanding on above explained basis, any shape of progress
The variation and change of formula are fallen within the scope of protection of the present invention.
Claims (10)
1. a kind of distributed cloud management system based on mixed mode, characterized by comprising: client service, control centre,
Configuration center, proxy server and cloud server terminal;
Customer service is the interactive service on foreground, and the main body of service is specific people or application, when client provides certain service
When there is demand in source, client service initiates the request comprising service logic to control centre;
Control centre is core, including service managerZ-HU and workflow manager;Service managerZ-HU, which uses, is based on tree-shaped knot
The allocation models of structure, so that multi-source heterogeneous cloud server terminal is configurable, the target object of service managerZ-HU management is different type
Cloud server terminal, including public cloud and private clound, for private clound, service managerZ-HU by configuration center dispose one it is new
Private clound, or an existing private clound of adapter tube, and to offering customers service;For public cloud, service managerZ-HU is logical
The access way that configuration center obtains cloud server terminal from proxy server is crossed, is the service call interface of http protocol, service pipe
Reason device carries out unified encapsulation to these interfaces, and to offering customers service;Workflow manager uses workflow template, so that cloud
The service logic of server-side is configurable, when control centre receives the request that client service is sent, by workflow manager
It is handled, the request of client is converted workflow by workflow manager, and coordinates cloud server terminal by service managerZ-HU
Each serviced component executes the step in workflow, handles implementing result according to the type of workflow, when there is step execution
When mistake, rollback has been executed step by workflow manager, avoids the generation of redundant data;
Configuration center is responsible for the configuration file by service describing provided by cloud server terminal at unified format, new when needing to access
Cloud server terminal when, configuration center is obtained from cloud server terminal access required for details, including cloud service type, cloud service
Title, cloud service version and cloud service content, configuration center convert the information being collected into the configuration file of unified format, clothes
Manager be engaged according to configuration file configuration cloud service, standard of the configuration file as cloud server terminal service provided can be intuitive
The service differences of different clouds are described, while configuration file determines which service service managerZ-HU provides to client, to configuration text
The modification of part can quickly adjust the service content of cloud server terminal;
Proxy server is the distinctive service middle layer of public cloud, encapsulates service provided by public cloud service supplier and connects
Mouthful, when client service initiates the resource access request of a public cloud, workflow manager forwards the request to service pipe
Device is managed, service managerZ-HU reinforms the request of proxy server customer in response, and proxy server is visited by way of far call
Ask the resource in public cloud;
Cloud server terminal is the set of the cloud service supplier referred to the accession to, and each cloud service supply commercial city externally provides a kind of or more
The service of seed type.
2. the distributed cloud management system according to claim 1 based on mixed mode, it is characterised in that: the service pipe
Reason device includes cloud configuration interface, and the specific implementation of the cloud configuration interface includes: with working method
The cloud configuration interface is created, the parameter of design cloud configuration interface, the parameter includes cloud service type, cloud service name
Title, cloud service version, cloud service content;
Define the attribute of cloud configuration interface parameters, the attribute include parameter type, value range and the parameter whether
For the mark of necessary parameter;
The return of calling cloud configuration interface is corresponding as a result, that the cloud configuration interface returns the result is that the tree of XML expression
Type structure, the depth of tree are 3, and the 1st layer of tree i.e. root node is the authentication service of cloud, and the 2nd layer of tree is each core of cloud
Central server, the 3rd layer of tree be cloud service operation, the cloud kernel service including but not limited to calculate service, storage service,
Network service, backup services, security service, mirroring service, the operation of the cloud service including but not limited to creates, starting,
Closing, deletion, carry, unloading, configuration, enabling, connection, disconnection.
3. the distributed cloud management system according to claim 1 based on mixed mode, it is characterised in that: the workflow
Manager includes task dispatcher, process management unit, task manager, service call unit and exception processing unit, in which:
Task dispatcher is responsible for receiving the request of client, and according to request type trigger process administrative unit, will finally call and take
The result of business returns to client;
Process management unit, be in charge of the management flow template, can generate workflow template according to different service logics, with
XML format saves, and in implementation procedure, matches corresponding workflow template according to request content, and serialize according to template generation
Event passes to task manager;
Task manager is in charge of the management and flows example, can be created according to serializing event and run workflow instance, and energy
It is enough that workflow instance is terminated according to the feedback of exception processing unit, in implementation procedure, is created according to serializing event and run work
Make stream example, the execution order of work flow step is initiated to service call unit;
Service call unit is responsible for analysis and executes order, calls corresponding service, while the result of service call being returned to and is appointed
Be engaged in scheduler, in implementation procedure, the step of record has executed, when there is step that failure occurs, will triggering exception processing unit into
Row abnormality processing;
Exception processing unit is responsible for handling exception according to Exception Type, and the stream that retracts has executed step, and abnormality processing result will be remembered
It records in log, and result is fed back into task manager.
4. the distributed cloud management system according to claim 3 based on mixed mode, it is characterised in that: the process pipe
It manages in unit, it is specific as follows to generate workflow template according to different service logics:
Creation generates the interface of workflow template, the parameter of designing workflows template interface, the ginseng of the workflow template interface
Number includes workflow title, work flow step title, work flow step type, work flow step ID;
The attribute of workflow template parameter is defined, the attribute includes the type of workflow template parameter and indicates the parameter
It whether is necessary mark;
It calls and generates corresponding to the return of workflow template interface as a result, returning the result the workflow template for XML format;
The effect of the workflow template is that the step relational graph of workflow is converted to the description file of XML format, workflow
The content of template includes workflow title, work flow step title, work flow step type, work flow step ID, workflow step
Rapid source;
Workflow title, a function point of corresponding client service, function point are creation virtual machine;
Work flow step title, the sequence of operations of corresponding client service are created in virtual machine and are provided to calculating, storage, network
The selection in source;
Work flow step type is the implementation procedure essential attribute defined by workflow manager, indicates the step and other steps
Incidence relation between rapid, incidence relation include synchronous execution, asynchronous execution, concurrently execute or sequentially execute;
Work flow step ID is that the step of workflow manager is automatically generated according to work flow step type executes ID, is used to auxiliary
Identification of steps is helped to execute sequence in workflow;
Work flow step source identifies the cloud service supplier of step access.
5. the distributed cloud management system according to claim 3 based on mixed mode, it is characterised in that: the workflow
In example, the description of workflow instance is recorded in database and file, for regenerating example when failure generation.
6. the distributed cloud management system according to claim 4 based on mixed mode, it is characterised in that: the workflow
The description content of example includes example ID, has executed step title and implementing result.
7. the distributed cloud management system according to claim 1 or 3 based on mixed mode, it is characterised in that: described time
It moves back and has executed that steps are as follows:
During workflow execution, record has executed step title and result to database, while local file is recorded;
When mistake occurs in the process of implementation for workflow, workflow, which terminates, to be executed, and has preferentially executed step from database reading
Title and as a result, and call related service carry out workflow rollback;
When database can not access, step title has been executed and as a result, and related service is called to carry out from local file reading
Workflow retracts;
Journal file is recorded in the implementing result of rollback operation.
8. a kind of distributed cloud management system based on mixed mode one of any using claim 1-7 carries out distributed cloud
Management method, it is characterised in that steps are as follows:
Step 101: configuration center is obtained from cloud service supplier access the cloud server terminal needed for information, including cloud service class
Type, cloud service title, cloud service version, cloud service content;
Step 102: service managerZ-HU calls cloud to configure interface, and the information about cloud server terminal that configuration center is collected into converts
At the description file of XML format, configuration center will call the implementing result of cloud configuration interface to return to service managerZ-HU;
Step 103: service provided by cloud server terminal is carried out unified envelope according to returning the result for configuration center by service managerZ-HU
Dress, and the service interface with other cloud service isomorphisms is provided to client service;
Step 104: client initiates the resource access request of a cloud server terminal by client service, requests by control centre
Workflow manager is handled;
Step 105: request content is converted to workflow by workflow manager, and is called and serviced according to the execution step of workflow
The implementing result of interface is returned to workflow manager by the relevant interface of manager, service managerZ-HU, if connecing in step
Mouth, which calls, to be returned the result to fail, then enables workflow rollback operation, workflow manager calls the rollback phase of service managerZ-HU
Interface is closed, the implementing result for the interface that retracts is returned to workflow manager by service managerZ-HU;
Step 106: service managerZ-HU executes interface calling procedure, accesses the related resource of cloud service, and receive returning for cloud service
Return result.
9. the distributed cloud management method according to claim 8 based on mixed mode, it is characterised in that: the workflow
The process step of manager is as follows:
Step 301: client submits the request comprising defined service logic in system to task dispatcher, task dispatcher
Analysis request type;
Step 302: according to request type, task dispatcher triggers corresponding process management unit;
Step 303: process management unit analysis request content matches it with existing workflow template;
Step 304: process management unit passes to task management as parameter according to workflow template, formation sequence event
Device;
Step 305: task manager receives serializing event, creates and run workflow instance, comes from exception when receiving
When managing the abnormal feedback of unit, then the operating status of workflow instance is terminated immediately;
Step 306: task manager initiates the execution order of the execution step comprising workflow to service call unit;
Step 307: service call unit executes workflow according to step, calls related service, and the service refers to control centre
Service managerZ-HU the unified of cloud server terminal service interface is encapsulated;
Step 308: service call unit is responsible for the implementing result of workflow returning to task dispatcher;
Step 309: task manager is responsible for submitting the workflow execution result of request to return to client client;
Step 310: when service call failure, service call unit will trigger exception processing unit and carry out abnormality processing;
Step 311: exception processing unit be responsible for executed work flow step carry out rollback operation;
Step 312: the result of abnormality processing feeds back to task manager, and task manager terminates workflow instance;
Step 313: while the result of abnormality processing is recorded in abnormal log file.
10. the distributed cloud management method according to claim 8 based on mixed mode, it is characterised in that: the work
Annealing method is flowed back to be accomplished by
Step 401: in service calling module, workflow table is shown as specifically executing step, is executed in a manner of service call;
Step 402: when service call success, database is recorded in the title that step has been executed in workflow instance and result
And file;
Step 403: task manager terminates the operation of workflow instance according to the feedback result of exception processing unit;
Step 404: exception processing unit reads the title that step is completed from database and as a result, for carrying out workflow rollback
Operation;
Step 405: when reading successfully from database, exception processing unit calls related service to carry out workflow rollback operation;
Step 406: when reading failure from database, exception processing unit reads the title and knot that step is completed from file
Fruit, for carrying out workflow rollback operation;
Step 407: when reading successfully from file, exception processing unit calls related service to carry out workflow rollback operation.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611122409.6A CN106790455B (en) | 2016-12-08 | 2016-12-08 | A kind of distributed cloud management system and method based on mixed mode |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201611122409.6A CN106790455B (en) | 2016-12-08 | 2016-12-08 | A kind of distributed cloud management system and method based on mixed mode |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106790455A CN106790455A (en) | 2017-05-31 |
CN106790455B true CN106790455B (en) | 2019-07-26 |
Family
ID=58881578
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201611122409.6A Active CN106790455B (en) | 2016-12-08 | 2016-12-08 | A kind of distributed cloud management system and method based on mixed mode |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106790455B (en) |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107846304A (en) * | 2017-09-14 | 2018-03-27 | 浙江广播电视集团 | A kind of automation engine of mixing cloud service architecture centralized management |
CN109547514A (en) * | 2017-09-22 | 2019-03-29 | 北京金山云网络技术有限公司 | A kind of task processing method, device, electronic equipment and storage medium |
CN107508923A (en) * | 2017-10-10 | 2017-12-22 | 郑州云海信息技术有限公司 | A kind of public cloud management method and system |
CN108021462B (en) * | 2017-12-08 | 2019-06-04 | 北京百度网讯科技有限公司 | Method and apparatus for calling cloud service |
CN108205440A (en) * | 2017-12-25 | 2018-06-26 | 国云科技股份有限公司 | A kind of task flow framework implementation method for supporting rollback |
CN108664289B (en) * | 2018-05-14 | 2021-05-28 | 平安科技(深圳)有限公司 | Service data processing method and terminal equipment |
CN112104697B (en) | 2018-05-31 | 2022-03-04 | 华为技术有限公司 | Data processing method, multi-cloud management system and related equipment |
CN108900482B (en) * | 2018-06-13 | 2021-04-16 | 平安科技(深圳)有限公司 | Script execution method, server management system, and storage medium |
CN109062548B (en) * | 2018-07-04 | 2020-06-30 | 中国地质大学(武汉) | Web service expansion method and system based on workflow construction |
CN109040065B (en) * | 2018-08-01 | 2021-04-23 | 杭州安恒信息技术股份有限公司 | Docking method and device for cloud security management platform and cloud platform |
CN109151045B (en) * | 2018-09-07 | 2020-05-19 | 北京邮电大学 | Distributed cloud system and monitoring method |
CN109543133A (en) * | 2018-11-29 | 2019-03-29 | 杭州涂鸦信息技术有限公司 | A kind of automation dissemination method, device, system, equipment and readable storage medium storing program for executing |
CN109669737B (en) * | 2018-12-19 | 2023-04-18 | 百度在线网络技术(北京)有限公司 | Application processing method, device, equipment and medium |
CN109819053B (en) * | 2019-03-11 | 2021-07-30 | 携程旅游信息技术(上海)有限公司 | Springboard machine system applied to mixed cloud environment and control method thereof |
CN110209484B (en) * | 2019-05-30 | 2021-10-22 | 华南理工大学 | Credible cloud task scheduling system and method based on multiple clouds and security mapping |
CN112130864A (en) * | 2019-06-25 | 2020-12-25 | 中兴通讯股份有限公司 | Deployment method and deployment device of private cloud platform service software |
CN113497814A (en) * | 2020-03-19 | 2021-10-12 | 中科星图股份有限公司 | Satellite image processing algorithm hybrid scheduling system and method |
CN112965850A (en) * | 2021-03-23 | 2021-06-15 | 上海云轴信息科技有限公司 | Method and equipment for realizing workflow in middle platform system |
CN116661771B (en) * | 2023-05-16 | 2024-04-30 | 江苏江顺精密机电设备有限公司 | Business logic compiling and executing assembly and method for logistics scheduling system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101694709A (en) * | 2009-09-27 | 2010-04-14 | 华中科技大学 | Service-oriented distributed work flow management system |
CN102307133A (en) * | 2011-03-25 | 2012-01-04 | 国云科技股份有限公司 | Virtual machine scheduling method for public cloud platform |
CN104778076A (en) * | 2015-04-27 | 2015-07-15 | 东南大学 | Scheduling method for cloud service workflow |
CN106060176A (en) * | 2016-08-04 | 2016-10-26 | 上海上大海润信息系统有限公司 | Cloud computing application architecture and cloud computing service method based on mixed cloud |
-
2016
- 2016-12-08 CN CN201611122409.6A patent/CN106790455B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101694709A (en) * | 2009-09-27 | 2010-04-14 | 华中科技大学 | Service-oriented distributed work flow management system |
CN102307133A (en) * | 2011-03-25 | 2012-01-04 | 国云科技股份有限公司 | Virtual machine scheduling method for public cloud platform |
CN104778076A (en) * | 2015-04-27 | 2015-07-15 | 东南大学 | Scheduling method for cloud service workflow |
CN106060176A (en) * | 2016-08-04 | 2016-10-26 | 上海上大海润信息系统有限公司 | Cloud computing application architecture and cloud computing service method based on mixed cloud |
Non-Patent Citations (2)
Title |
---|
云制造-面向服务的网络化制造新模式;李伯虎 等;《计算机集成制造系统》;20100131;第16卷(第1期);第1-16页 * |
工作流元模型的研究与应用;赵文 等;《软件学报》;20030623;第14卷(第6期);第1052-1059页 * |
Also Published As
Publication number | Publication date |
---|---|
CN106790455A (en) | 2017-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106790455B (en) | A kind of distributed cloud management system and method based on mixed mode | |
CN107357856B (en) | Method for realizing data integration and data service based on power grid panoramic service model | |
CN105429806B (en) | A kind of device and method of the network function virtualization based on data-driven | |
WO2018086580A1 (en) | Extensible heterogeneous cloud platform adaptation method and system thereof | |
US8904341B2 (en) | Deriving grounded model of business process suitable for automatic deployment | |
US8370814B2 (en) | Automatic test generation for reference testing | |
US9805322B2 (en) | Application blueprint and deployment model for dynamic business service management (BSM) | |
CN111176645A (en) | Power grid big data application-oriented data integration management system and implementation method thereof | |
CN103019791B (en) | Software dispositions method and software deployment system | |
CN108287756A (en) | A kind of method and device of processing task | |
CN109194506A (en) | Block chain network dispositions method, platform and computer storage medium | |
CN104202416A (en) | Service orchestration system and method under cloud operating system | |
CN102075381A (en) | Automatic test platform server and system applied to cloud storage | |
CN108400898A (en) | The management method and device of resource in cloud data management platform | |
CN102156642A (en) | Implementation method and system for universal business process management interfaces | |
CN105471662B (en) | Cloud Server, virtual network strategy centralized control system and method | |
CN106228338A (en) | A kind of distribution engineering intelligentized design integrated service system and using method | |
CN107622314A (en) | Configuring management method and its system based on automation O&M | |
CN109683911A (en) | A kind of system for realizing automation application deployment and impact analysis | |
CN107016069A (en) | Towards the metadata interchange system of intelligent transportation | |
CN111562966B (en) | Resource arrangement method of man-machine-object fusion cloud computing platform | |
CN109471730A (en) | A kind of elastic calculation service management system | |
CN109787807A (en) | Self service system based on Openstack framework cloud platform workflow | |
CN104660435A (en) | Transactional network management engine for intelligent pipeline and network management transaction processing method of transactional network management engine | |
CN104901998B (en) | integrated cloud service monitoring method |
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 | ||
GR01 | Patent grant | ||
GR01 | Patent grant |