CN112667205A - Development method and device for power failure editing microservice and computer equipment - Google Patents
Development method and device for power failure editing microservice and computer equipment Download PDFInfo
- Publication number
- CN112667205A CN112667205A CN202011508925.9A CN202011508925A CN112667205A CN 112667205 A CN112667205 A CN 112667205A CN 202011508925 A CN202011508925 A CN 202011508925A CN 112667205 A CN112667205 A CN 112667205A
- Authority
- CN
- China
- Prior art keywords
- power failure
- service
- micro
- arrangement
- models
- 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.)
- Granted
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to a method for developing a micro-service for power failure arrangement, which comprises the following steps: acquiring a preset power failure arrangement business process, and splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; generating a power failure arrangement business flow chart according to a plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file; generating extensible style sheet conversion language files corresponding to a plurality of target platform related meta-models; the extensible markup language file is mapped into the power failure arranging micro-service codes based on the extensible style sheet conversion language file and the code generator, the power failure arranging micro-service codes are arranged according to the power failure, the power failure arranging micro-service is generated, automatic development of the power failure arranging micro-service codes is achieved, the power failure arranging micro-service can be rapidly developed and deployed through conversion from a model to the codes, and the development efficiency of the power failure arranging micro-service is effectively improved.
Description
Technical Field
The present application relates to the field of micro-services, and in particular, to a method and an apparatus for developing a power outage orchestration micro-service, a computer device, and a storage medium.
Background
With the development of power grid technology, the range of a power grid system is increasingly expanded, and power utilization equipment is continuously increased.
In the prior art, in the operation process of a power grid, power failure management is the basis for normal development of various service works of the power grid, and in order to ensure reasonable and orderly execution of a power failure arrangement plan, related software can be developed aiming at the power failure arrangement, so that rapid and accurate power failure arrangement is realized.
However, the conventional power outage orchestration application is low in development efficiency, and rapid development of the power outage orchestration application is difficult to achieve.
Disclosure of Invention
In view of the above, it is desirable to provide a method and an apparatus for developing a power outage orchestration microservice, a computer device, and a storage medium.
A power failure editing micro-service development method is applied to a micro-service application management platform and comprises the following steps:
acquiring a preset power failure arrangement business process, and splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
generating a power failure arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and mapping the extensible markup language file into a power failure arranging micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service code.
Optionally, the method further comprises:
determining an application operating environment specification corresponding to the power failure arrangement microservice;
determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments;
and deploying the power failure arrangement micro-service in the target application running environment.
Optionally, the generating a power outage orchestration microservice according to the power outage orchestration microservice code includes:
determining codes corresponding to a plurality of functional modules from the power failure editing micro-service codes; the plurality of functional modules are used for providing different application functions when power failure arrangement occurs;
and generating a plurality of power failure arrangement microservices with different application functions according to the application codes corresponding to the functional modules.
Optionally, the method further comprises:
receiving a power failure arrangement request, and determining a plurality of target power failure arrangement micro services corresponding to the power failure arrangement request from a plurality of power failure arrangement micro services;
determining a calling sequence corresponding to the plurality of target power failure arranging microservices, and calling the plurality of target power failure arranging microservices according to the calling sequence.
Optionally, a plurality of power outage orchestration micro-services in the micro-service application management platform are respectively deployed at different service nodes, and the method further includes:
acquiring micro-service logs uploaded by service nodes corresponding to the micro-services in power failure arrangement; the micro-service log is acquired from the corresponding power failure editing micro-service through a log acquisition component on the service node;
and storing the plurality of microservice logs to a preset log storage module.
Optionally, the plurality of power outage orchestration microservices are configured to, when being mutually invoked, generate invocation information according to the expression level state conversion rule, and send the invocation information to the message middleware, so as to forward the invocation information to the invoked power outage orchestration microservices through the message middleware.
Optionally, the power outage orchestration microservice includes a microservice front-end and a microservice back-end, and the microservice front-end calls an interface gateway through an internet protocol when receiving a microservice application call request, and calls the microservice back-end through the interface gateway.
A power failure arrangement microservice development device is applied to a microservice application management platform and comprises:
the service flow acquisition module is used for acquiring a preset power failure arrangement service flow and splitting the power failure arrangement service flow according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
the service flow chart acquisition module is used for generating a power-off arrangement service flow chart according to the plurality of target platform related meta-models, and converting the power-off arrangement service flow chart into an extensible markup language file;
the file generation module is used for generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and the power failure arranging micro-service generating module is used for mapping the extensible markup language file into power failure arranging micro-service codes based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service codes.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the method as claimed in any one of the above when the computer program is executed.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of the preceding claims.
In the embodiment, by obtaining the preset power failure arrangement business process, splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models, generating a power failure arrangement business process diagram according to the plurality of target platform related meta-models, converting the power failure arrangement business process diagram into an extensible markup language file, generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models, mapping the extensible markup language file into power failure arrangement micro-service codes based on the extensible style sheet conversion language file and a code generator, generating the power failure arrangement micro-service according to the power failure arrangement micro-service codes, and realizing the automatic code development of the power failure arrangement micro-service, through the conversion from the model to the code, the power failure editing micro-service can be rapidly developed and deployed, and the development efficiency of the power failure editing micro-service is effectively improved.
Drawings
FIG. 1 is a flowchart illustrating a method for developing a blackout orchestration microservice according to one embodiment;
FIG. 2 is a flowchart illustrating the step of generating the power outage orchestration microservice according to one embodiment;
FIG. 3 is a flowchart illustrating the power outage orchestration microservice invocation step in one embodiment;
FIG. 4 is a block diagram of an embodiment of an apparatus for developing a blackout orchestration microservice;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
In an embodiment, as shown in fig. 1, a method for developing a power outage orchestration microservice is provided, and this embodiment is exemplified by applying the method to a microservice application management platform, where the microservice application management platform may be implemented by an independent server or a server cluster formed by a plurality of servers, and the microservice application management platform may manage one or more microservice applications. It is understood that the method can also be applied to a terminal, and can also be applied to a system comprising the terminal and a server, and is realized through the interaction of the terminal and the server. In this embodiment, the method may include the steps of:
As an example, the blackout arrangement business process is used for business logic describing a blackout arrangement mode for a power utilization area or power utilization equipment in a power grid, such as blackout objects arranged with blackouts, blackout start time, blackout end time, blackout frequency, power consumption triggering blackouts of the blackout objects, and the like. The service personnel can preset corresponding power failure arrangement service processes aiming at the power failure arrangement in the power grid.
In practical applications, a model library may be disposed in the micro service application management Platform, and a plurality of different Platform-related meta-models, that is, PSM (Platform-specific models) meta-models may be included in the model library. After the power failure arrangement business process is obtained, the micro-service application management platform can split the power failure arrangement business process by using platform related meta-models in the model base as a minimum unit for splitting the business process, a plurality of platform related meta-models obtained after the power failure arrangement business process is split are used as a plurality of target platform related meta-models, namely a plurality of target PSM meta-models, and the plurality of target PSM meta-models obtained after splitting can be used for describing the power failure arrangement business process.
And 102, generating a power failure arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file.
As an example, the power outage orchestration business flow diagram may be a flow diagram reflecting a power outage orchestration business flow, and the flow diagram may be built based on a UML (Unified-Modeling-Language) activity diagram. The XML file may also be referred to as an XML (Extensible Markup Language) file, which refers to a file generated by using an XML; a UML activity diagram may refer to an activity diagram generated using a unified modeling language.
After obtaining the plurality of target platform related meta-models, the power outage orchestration service flow chart may be generated based on the plurality of target platform related meta-models, and the power outage orchestration service flow chart may be converted into an extensible markup language file, for example, the power outage orchestration service flow chart in the form of a UML activity diagram may be converted into an XML file
And 103, generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models.
As an example, an extensible Stylesheet transformation Language file, which may also be referred to as an xslt (extensible Stylesheet Language transformations) file, may refer to a file generated using an extensible Stylesheet transformation Language (XML) which is a style transformation markup Language and may transform data generated based on an extensible markup Language (XML) into a file in another format.
In this embodiment, after determining the plurality of target platform related meta-models, the corresponding extensible stylesheet conversion language file may be generated for the plurality of target platform related meta-models, and specifically, for each target platform related meta-model, the extensible stylesheet conversion language file corresponding to the target platform related meta-model may be generated.
And step 104, mapping the extensible markup language file into a power failure arranging micro-service code based on the extensible style sheet conversion language file and the code generator, and arranging the micro-service code according to the power failure to obtain the power failure arranging micro-service.
Because the extensible markup language file is generated by adopting the extensible markup language, after the extensible style sheet conversion language file is obtained, the extensible markup language file can be mapped into the power failure arrangement micro-service codes based on the extensible style sheet conversion language file and the code generator, and then the power failure arrangement micro-service codes can be generated according to the obtained power failure arrangement micro-service codes.
In the embodiment, the automatic development of the codes of the blackout orchestration micro-service is realized by acquiring a preset blackout orchestration business process, splitting the blackout orchestration business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models, generating a blackout orchestration business process diagram according to the plurality of target platform related meta-models, converting the blackout orchestration business process diagram into an extensible markup language file, generating an extensible style sheet conversion language file corresponding to the plurality of target platform related meta-models, mapping the extensible markup language file into blackout orchestration micro-service codes based on the extensible style sheet conversion language file and a code generator, generating the blackout orchestration micro-service according to the blackout orchestration micro-service codes, and rapidly developing and deploying the blackout orchestration micro-service through the conversion from the model to the codes, the development efficiency of the power failure arrangement micro-service is effectively improved.
In this embodiment, the power outage orchestration microservice may be constructed based on a Model-Driven-Architecture (MDA). The model driving architecture takes UML and other industrial standards as technical support, can create a standardized model which has high abstraction degree, can be read by machine and is independent of implementation technology, can realize visualization, storage and exchange of a software development model in the software development process, emphasizes that the whole system development process is driven by the modeling behavior of a software system, and completes the work of system requirement analysis, architecture design, construction, test, deployment and operation maintenance.
In the model-driven architecture, three modeling standards, namely UML, MOF (Meta-Object-Facility) and CWM (Common-Warehouse Meta-model) can be used as the modeling bases of PIM and PSM. Secondly, the model-driven Architecture can be applied to a variety of implementation technology platforms, including public standard or private implementation technology platforms, such as CORBA (Common object request Broker Architecture), XMI (XML Metadata exchange)/XML (Extensible Markup Language), NET (microsoft operating platform), JAVA, and Web Service. The model-driven architecture may also define a plurality of Services, such as Directory Services (Directory-Services), Transaction Services (Transaction-Services), Security Services (Security-Services), and Distributed Event and Notification Services (Distributed-Event-and-Notification-Services). The model-driven architecture is flexible such that the model-driven architecture can be applied in a variety of domain environments, such as the fields of e-commerce, telecommunications, healthcare, transportation, aviation, manufacturing, finance, and the like.
In one embodiment, the method may further comprise the steps of:
determining an application operating environment specification corresponding to the power failure arrangement microservice; determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments; and deploying the power failure arrangement micro-service in the target application running environment.
In this embodiment, after the power outage orchestration micro-service is generated, the application operating environment specification corresponding to the power outage orchestration micro-service may be determined, and then a target application operating environment meeting the application operating environment specification may be determined from a plurality of preset application operating environments, and then the power outage orchestration micro-service may be deployed in the target application operating environment.
In practical application, the code data operating environment provider or the program operating environment provider can describe the application operating environment provided by the code data operating environment provider or the program operating environment provider according to a preset operating environment description specification, generate an application operating environment description file, and issue the application operating environment description file to the outside. And then the micro-service application management platform can use the application operating environment provided by the code data operating environment provider or the program operating environment provider as a plurality of preset application operating environments, and select the target application operating environment according to the plurality of application operating environment description files.
The application operation environment can be logically bound with the power failure arrangement micro-service and provides service together with the power failure arrangement micro-service, wherein the application operation environment can be separated from the power failure arrangement micro-service in a physical structure and can be independently operated; the same blackout orchestration microservice may run in different application execution environments, including application execution environments for distributed or redundant purposes.
In this embodiment, a target application running environment meeting the application running environment specification is determined from a plurality of preset application running environments, and the power outage orchestration micro-service is deployed in the target application running environment, so that the normal operation of the power outage orchestration micro-service can be ensured.
In one embodiment, as shown in fig. 2, the generating the power outage orchestration microservice according to the power outage orchestration microservice code may include the following steps:
In practical application, after the extensible markup language file is mapped into the power failure arrangement micro-service code, the obtained power failure arrangement micro-service code can be provided with a plurality of identifiers for distinguishing each functional module, and the micro-service application management platform can determine codes corresponding to the plurality of functional modules from the power failure arrangement micro-service code according to the plurality of identifiers, wherein each functional module can provide different application functions when a service worker performs power failure arrangement.
After determining the application codes corresponding to the function modules, the micro-service application management platform can generate a plurality of power failure arrangement micro-services with different application functions according to the application codes corresponding to the function modules, obtain a plurality of power failure arrangement micro-services, and deploy the plurality of power failure arrangement micro-services in the platform based on a micro-service framework.
In particular, the micro-service architecture may refer to a plurality of work units with high cohesiveness and small synergy, determined by the service scope. The micro-service architecture obviously enhances the adaptability, can make a selection of a proper tool and a proper language, then carries out program splitting, groups internal services, and can construct a perfect service by taking a specific service as a center on the premise of coordinating each service in a platform or a system and keep the service independent in the system process.
In the micro-service architecture, each micro-service corresponds to a work unit, each unit has a high degree of autonomy, and can exist in a process of a system or a platform or run in the system or the platform in an independent entity mode. Each micro service can be regarded as one component, and compared with the traditional component, each component in the micro service framework has the advantages of simplicity and convenience in operation and small occupied space. In the conventional component, although a common part of a service can be extracted, and independent service links are isolated, so that a program can be modularly used and then decoupled and multiplexed, different services have a coupling relation, and in the running process of the system, an application program changes a single system, and the service needs to be re-constructed. And the micro-service architecture can directly decompose the service in the platform or the system.
In this embodiment, a plurality of blackout orchestration micro-services having different application functions are generated according to the application codes corresponding to the function modules, and a plurality of blackout orchestration micro-services are generated, so that under the condition that the blackout orchestration micro-services of the system are coordinated with each other, a perfect service can be constructed by taking a specific service as a center, and the perfect service can be kept independent in the system process.
In one embodiment, as shown in fig. 3, the method may further include the steps of:
In practical applications, a service requester (for example, a terminal or a server) that needs to perform power outage arrangement on a power consumption device may send a power outage arrangement request to the micro-service application management platform, and after receiving the power outage arrangement request, the micro-service application management platform may determine a corresponding service requirement from the received power outage arrangement request, and further may determine a plurality of target power outage arrangement micro-services corresponding to the request from a plurality of power outage arrangement micro-services in the micro-service application management platform.
After the plurality of target power failure arranging micro services are determined, the plurality of target power failure arranging micro services can be scheduled in a scheduling sequence, the scheduling sequence of the plurality of target power failure arranging micro services is determined, and then the plurality of target power failure arranging micro services can be scheduled in sequence according to the scheduling sequence so as to respond to the power failure arranging request.
In this embodiment, by determining a calling sequence corresponding to the plurality of target power-off orchestration micro-services and calling the plurality of target power-off orchestration micro-services according to the calling sequence, combination, orchestration and integration of different power-off orchestration micro-services can be realized, each power-off orchestration micro-service in the micro-service application management platform is efficiently and orderly called, and a response is made to a relevant request.
The micro-service application management platform can schedule a plurality of micro-services to meet the service requirements of the micro-service requester. The micro-service requester can directly send service request information to the micro-service application management platform; or searching the microservices issued by a microservice application management platform or a third party in the network according to the specifications, and calling the microservices after obtaining the related search results; or, the service requirement of the user can be released in a format specified in the network, and a third party in the network sends the corresponding service request information to the micro-service application management platform.
In one embodiment, a plurality of outage orchestration micro-services in a micro-service application management platform are respectively deployed at different service nodes, and the method may further include the following steps:
acquiring micro-service logs uploaded by service nodes corresponding to the micro-services in power failure arrangement; the micro-service log is acquired from the corresponding power failure editing micro-service through a log acquisition component on the service node; and storing the plurality of microservice logs to a preset log storage module.
In a specific implementation, a plurality of power-off orchestration micro-services may be deployed on different service nodes, however, when viewing logs in the micro-services of each service node, if the logs are viewed in a manner of logging in each service node, the log viewing is too cumbersome, and for performing joint viewing analysis by associating a plurality of micro-service logs, the manner is more inconvenient. With the increase of the number of nodes and the micro-services in the platform, the positioning and viewing of the micro-service log will become more and more complex.
Based on this, in this embodiment, a log collection component may be developed and deployed on each service node, where the log collection component may be packaged in the form of log4j or Blitz4 j. The log collection component corresponding to each service node can collect logs of the power-off arrangement micro-service on the same node, and the micro-service application management platform can obtain the corresponding logs of the power-off arrangement micro-service from each service node. After obtaining the logs of the micro-service arranged in the power failure, the micro-service application management platform can store all the logs into a preset log storage module, and can uniformly manage a plurality of logs according to a pre-established log management standard, and can determine and associate a plurality of logs with association relationship from the plurality of logs.
In this embodiment, by deploying the log collection component on each service node, the micro-service logs uploaded by the service nodes corresponding to the micro-service arrangement during power failure can be obtained, and a plurality of micro-service logs are stored, so that the lookup speed of the subsequent micro-service logs is effectively increased, and the service nodes are prevented from being logged in many times when the micro-service logs are viewed.
In one embodiment, multiple blackout orchestration microservices may be invoked with respect to each other. Specifically, when calling other power outage orchestration microservices, each power outage orchestration microservice may generate calling information through a representation layer State Transfer (REST), and send the calling information to the message middleware. After receiving the calling information, the message middleware can determine a called target object, namely, a called power failure arrangement microservice, from the calling information, and further can forward the calling information to the called power failure arrangement microservice for use. In the micro-service application management platform, the isolation among micro-services arranged in power failure can be enhanced by a communication mode called by a network, and the coupling phenomenon in the operation process of the platform is prevented.
In the embodiment, through an information interaction mechanism of the message middleware, a data interaction basis is provided for mutual calling among the power failure arrangement micro services, and the cooperation efficiency among the power failure arrangement micro services is effectively improved.
In one embodiment, the power outage orchestration microservice may include a microservice front-end and a microservice back-end, and when the microservice front-end receives a microservice application call request, an interface (API) gateway may be called according to an internet protocol and the microservice back-end may be called through the interface gateway. Specifically, the interface network manager may be a hierarchical interface gateway, and when the micro-service front end calls the hierarchical interface gateway through an Http/Http protocol, the hierarchical interface gateway may determine and call the micro-service back end corresponding to the micro-service front end through the routing server.
In this embodiment, through the interface gateway, the micro service front end and the micro service back end can be distinguished, and the corresponding micro service back end is called by the micro service front end, so that front-end and back-end separation is realized, and support is provided for independent development of the front end and the back end of the power failure arrangement micro service.
In practical applications, when the micro-service application management platform is constructed, automated service implementation including automated construction, automated installation and deployment, automated testing, and automated platform release (for example, implemented by Docker) may be performed, and in the micro-service application management platform, management services and collaboration services are deployed. Aiming at the management service, the corresponding monitoring and management service and log management service can be matched according to the micro-service architecture; aiming at the cooperative service, the DevOps idea can be applied to realize the efficient communication and cooperation of development, test, operation and maintenance, so as to achieve the effect of integration of development and operation and maintenance.
In one example, the micro-service application management platform may also perform micro-service information management, micro-service transmission management, micro-service data management, micro-service resource management, network supervision.
The micro service information management can save micro service provider information, micro service requester information, micro service description information, micro service application running environment information and data running environment information in the platform. Through the micro-service transmission management, the association, call, interaction and QOS information among the micro-services in the network can be managed. Through the management of the data of the micro-services, the data source, the database and the data content information used by the micro-services in the platform can be managed. Through the management of the micro-service resources, the network resources, the system resources, the storage resources and the running environment resources related to the micro-service in the network can be managed. By network supervision, micro-service release rules, micro-service discovery rules, micro-service scheduling rules, micro-service combination rules and service networking rules in the network can be managed.
In one embodiment, for a plurality of blackout orchestration micro-services, a technology or a development language more suitable for a service itself may be selected according to characteristics of different service fields, and the micro-services may be developed without considering technology or language consistency in a service system, that is, the plurality of blackout orchestration micro-services in the micro-service application management platform may be developed based on different development languages. If a standardized technology or language is mandatory for all services in a platform or system, it is difficult to effectively support a special service scenario. In the embodiment, on the premise of not increasing the number of machines, a technology or a development language with better performance can be selected to develop the micro-service of a special service scene. In addition, different technology stacks and storage modes can be used among different micro services in the micro service application management platform.
Due to the characteristics of the micro-service mechanism, each micro-service in the micro-service application management platform can have certain elasticity, and the elasticity refers to the fault tolerance of the platform. When one micro service or one instance in the micro service application management platform fails and the platform is not paralyzed, other micro services in the micro service application management platform can still provide services normally, and the fault tolerance of the platform is effectively improved.
It should be understood that although the various steps in the flow charts of fig. 1-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-3 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 4, there is provided a development apparatus for power outage orchestration microservice, including:
the service flow acquiring module 401 is configured to acquire a preset power outage arrangement service flow, and split the power outage arrangement service flow according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
a service flow chart obtaining module 402, configured to generate a power outage arrangement service flow chart according to the multiple target platform relevant meta-models, and convert the power outage arrangement service flow chart into an extensible markup language file;
a file generating module 403, configured to generate extensible stylesheet transformation language files corresponding to the multiple target platform related meta-models;
and a power failure arrangement micro-service generation module 404, configured to map the extensible markup language file into a power failure arrangement micro-service code based on the extensible style sheet conversion language file and the code generator, and generate a power failure arrangement micro-service according to the power failure arrangement micro-service code.
In one embodiment, the apparatus may further include:
the environment specification acquisition module is used for determining an application operation environment specification corresponding to the power failure arrangement microservice;
the target application running environment determining module is used for determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments;
and the deployment module is used for deploying the power failure arranging micro-service in the target application running environment.
In one embodiment, the power outage orchestration microservice generation module 404 includes:
the functional module code determining submodule is used for determining codes corresponding to a plurality of functional modules from the power failure editing micro service codes; the plurality of functional modules are used for providing different application functions when power failure arrangement occurs;
and the functional module code conversion submodule is used for generating a plurality of power failure arrangement micro-services with different application functions according to the application codes corresponding to the functional modules.
In one embodiment, the apparatus may further include:
the target power failure arrangement micro-service determining module is used for receiving the power failure arrangement request and determining a plurality of target power failure arrangement micro-services corresponding to the power failure arrangement request from a plurality of power failure arrangement micro-services;
and the calling sequence determining module is used for determining the calling sequences corresponding to the target power failure arranging microservices and calling the target power failure arranging microservices according to the calling sequences.
In one embodiment, a plurality of outage orchestration microservices in the microservices application management platform are respectively deployed at different service nodes, and the apparatus further includes:
the micro-service log acquisition module is used for acquiring micro-service logs uploaded by service nodes corresponding to the micro-services arranged during power failure; the micro-service log is acquired from the corresponding power failure editing micro-service through a log acquisition component on the service node;
and the micro-service log storage module is used for storing a plurality of micro-service logs into a preset log storage module.
In one embodiment, the plurality of power outage orchestration micro-services are configured to generate call information through the expression level state conversion rule when the plurality of power outage orchestration micro-services are mutually called, and send the call information to the message middleware so as to forward the call information to the called power outage orchestration micro-services through the message middleware.
In one embodiment, the power outage orchestration microservice comprises a microservice front-end and a microservice back-end, wherein the microservice front-end calls an interface gateway through an internet protocol when receiving a microservice application call request, and calls the microservice back-end through the interface gateway.
For the specific definition of the development device for the blackout orchestration micro-service, refer to the above definition of the development method for the blackout orchestration micro-service, and no further description is provided herein. All or part of each module in the development device for arranging the micro-service in the power failure can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer equipment is used for storing data corresponding to the power failure arrangement business process. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method for developing a blackout orchestration microservice.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring a preset power failure arrangement business process, and splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
generating a power failure arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and mapping the extensible markup language file into a power failure arranging micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service code.
In one embodiment, the steps in the other embodiments described above are also implemented when the computer program is executed by a processor.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a preset power failure arrangement business process, and splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
generating a power failure arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and mapping the extensible markup language file into a power failure arranging micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service code.
In one embodiment, the computer program when executed by the processor also performs the steps in the other embodiments described above.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A power failure editing micro-service development method is applied to a micro-service application management platform and comprises the following steps:
acquiring a preset power failure arrangement business process, and splitting the power failure arrangement business process according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
generating a power failure arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power failure arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and mapping the extensible markup language file into a power failure arranging micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service code.
2. The method of claim 1, further comprising:
determining an application operating environment specification corresponding to the power failure arrangement microservice;
determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments;
and deploying the power failure arrangement micro-service in the target application running environment.
3. The method of claim 1, wherein generating a blackout orchestration microservice based on the blackout orchestration microservice code comprises:
determining codes corresponding to a plurality of functional modules from the power failure editing micro-service codes; the plurality of functional modules are used for providing different application functions when power failure arrangement occurs;
and generating a plurality of power failure arrangement microservices with different application functions according to the application codes corresponding to the functional modules.
4. The method of claim 3, further comprising:
receiving a power failure arrangement request, and determining a plurality of target power failure arrangement micro services corresponding to the power failure arrangement request from a plurality of power failure arrangement micro services;
determining a calling sequence corresponding to the plurality of target power failure arranging microservices, and calling the plurality of target power failure arranging microservices according to the calling sequence.
5. The method of claim 3, wherein the plurality of outage orchestration microservices in the microservices application management platform are deployed at different service nodes, respectively, the method further comprising:
acquiring micro-service logs uploaded by service nodes corresponding to the micro-services in power failure arrangement; the micro-service log is acquired from the corresponding power failure editing micro-service through a log acquisition component on the service node;
and storing the plurality of microservice logs to a preset log storage module.
6. The method of claim 1, wherein the plurality of outage orchestration microservices are configured to generate call information through the expression level state translation rules when called with each other, and send the call information to the message middleware for forwarding the call information to the called outage orchestration microservices through the message middleware.
7. The method of claim 1, wherein the power outage orchestration microservice comprises a microservice front-end and a microservice back-end, wherein the microservice front-end invokes an interface gateway via an internet protocol upon receiving a microservice application invocation request, and invokes the microservice back-end via the interface gateway.
8. A development device for arranging micro-services in power failure is applied to a micro-service application management platform, and comprises:
the service flow acquisition module is used for acquiring a preset power failure arrangement service flow and splitting the power failure arrangement service flow according to a plurality of platform related meta-models in a model library to obtain a plurality of target platform related meta-models; the plurality of target platform related meta-models are used for describing the power failure arrangement business process;
the service flow chart acquisition module is used for generating a power-off arrangement service flow chart according to the plurality of target platform related meta-models, and converting the power-off arrangement service flow chart into an extensible markup language file;
the file generation module is used for generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models;
and the power failure arranging micro-service generating module is used for mapping the extensible markup language file into power failure arranging micro-service codes based on the extensible style sheet conversion language file and the code generator, and generating the power failure arranging micro-service according to the power failure arranging micro-service codes.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011508925.9A CN112667205B (en) | 2020-12-19 | 2020-12-19 | Development method and device for power outage arrangement micro-service and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011508925.9A CN112667205B (en) | 2020-12-19 | 2020-12-19 | Development method and device for power outage arrangement micro-service and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112667205A true CN112667205A (en) | 2021-04-16 |
| CN112667205B CN112667205B (en) | 2023-10-10 |
Family
ID=75407097
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011508925.9A Active CN112667205B (en) | 2020-12-19 | 2020-12-19 | Development method and device for power outage arrangement micro-service and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112667205B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170323089A1 (en) * | 2016-05-06 | 2017-11-09 | Enterpriseweb Llc | Systems and methods for domain-driven design and execution of modular and dynamic services, applications and processes |
| US20180165604A1 (en) * | 2016-12-09 | 2018-06-14 | U2 Science Labs A Montana | Systems and methods for automating data science machine learning analytical workflows |
| US20180260745A1 (en) * | 2017-03-09 | 2018-09-13 | At&T Intellectual Property I, L.P. | System and method for designing and executing control loops in a cloud environment |
| US20190052549A1 (en) * | 2016-05-06 | 2019-02-14 | Enterpriseweb Llc | Systems and methods for domain-driven design and execution of metamodels |
| US20190220331A1 (en) * | 2018-01-16 | 2019-07-18 | Enterpriseweb Llc | Event-driven programming model-based on asynchronous, massively parallel dataflow processes for highly-scalable distributed applications |
| US10425350B1 (en) * | 2015-04-06 | 2019-09-24 | EMC IP Holding Company LLC | Distributed catalog service for data processing platform |
| CN110276592A (en) * | 2019-06-14 | 2019-09-24 | 北京科技大学 | A kind of micro services system business process variability modelling method and system |
| CN110286884A (en) * | 2019-06-21 | 2019-09-27 | 北京百度网讯科技有限公司 | Micro services method of combination, device, equipment and computer readable storage medium |
| CN111638972A (en) * | 2020-05-07 | 2020-09-08 | 北京仁科互动网络技术有限公司 | Request response method, system, equipment and storage medium based on micro-service |
| CN111736821A (en) * | 2020-06-28 | 2020-10-02 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Visual modeling analysis method, system, computer device and readable storage medium |
-
2020
- 2020-12-19 CN CN202011508925.9A patent/CN112667205B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10425350B1 (en) * | 2015-04-06 | 2019-09-24 | EMC IP Holding Company LLC | Distributed catalog service for data processing platform |
| US20170323089A1 (en) * | 2016-05-06 | 2017-11-09 | Enterpriseweb Llc | Systems and methods for domain-driven design and execution of modular and dynamic services, applications and processes |
| US20190052549A1 (en) * | 2016-05-06 | 2019-02-14 | Enterpriseweb Llc | Systems and methods for domain-driven design and execution of metamodels |
| US20180165604A1 (en) * | 2016-12-09 | 2018-06-14 | U2 Science Labs A Montana | Systems and methods for automating data science machine learning analytical workflows |
| US20180260745A1 (en) * | 2017-03-09 | 2018-09-13 | At&T Intellectual Property I, L.P. | System and method for designing and executing control loops in a cloud environment |
| US20190220331A1 (en) * | 2018-01-16 | 2019-07-18 | Enterpriseweb Llc | Event-driven programming model-based on asynchronous, massively parallel dataflow processes for highly-scalable distributed applications |
| CN110276592A (en) * | 2019-06-14 | 2019-09-24 | 北京科技大学 | A kind of micro services system business process variability modelling method and system |
| CN110286884A (en) * | 2019-06-21 | 2019-09-27 | 北京百度网讯科技有限公司 | Micro services method of combination, device, equipment and computer readable storage medium |
| CN111638972A (en) * | 2020-05-07 | 2020-09-08 | 北京仁科互动网络技术有限公司 | Request response method, system, equipment and storage medium based on micro-service |
| CN111736821A (en) * | 2020-06-28 | 2020-10-02 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | Visual modeling analysis method, system, computer device and readable storage medium |
Non-Patent Citations (3)
| Title |
|---|
| SARA HASSAN等: "Microservice Ambients: An Architectural Meta-Modelling Approach for Microservice Granularity", 《2017 IEEE INTERNATIONAL CONFERENCE ON SOFTWARE ARCHITECTURE》, pages 1 - 10 * |
| 邓禹等: "基于交互流建模语言的微服务架构建模研究", 《软件导刊》, vol. 17, no. 1, pages 165 - 168 * |
| 金镝等: "NFV网络编排器发展现状与关键技术研究", 《信息通信技术与政策》, no. 03, pages 86 - 91 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112667205B (en) | 2023-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112035228B (en) | Resource scheduling method and device | |
| US6772206B1 (en) | XML-based integrated services bridging | |
| CN101847100B (en) | Method for expanding software application and device | |
| CN111290753B (en) | Method, device, equipment and storage medium for building front-end development environment | |
| US20020087734A1 (en) | System and method for managing dependencies in a component-based system | |
| CN110752947A (en) | K8s cluster deployment method and device, and deployment platform | |
| Xie et al. | Service provisioning for HLA-based distributed simulation on the Grid | |
| CN111897541B (en) | Software interaction platform and method for automatically deploying resources in cloud environment | |
| CN112698921A (en) | Logic code operation method and device, computer equipment and storage medium | |
| Fortier et al. | Dyninka: a FaaS framework for distributed dataflow applications | |
| JP5264837B2 (en) | Remote plug-in device, robot plug-in execution engine device, and robot plug-in execution system | |
| CN116708266A (en) | Cloud service topological graph real-time updating method, device, equipment and medium | |
| CN112667205B (en) | Development method and device for power outage arrangement micro-service and computer equipment | |
| Ezenwoye et al. | A Proxy-Based Approach to Enhancing the Autonomic Behavior in Composite Services. | |
| CN114710350A (en) | Allocation method and device for callable resources | |
| CN113485894A (en) | Data acquisition method, device and equipment and readable storage medium | |
| CN113641641A (en) | Switching method, switching system, equipment and storage medium of file storage service | |
| CN113010385A (en) | Task state updating method, device, equipment and medium | |
| CN112764825A (en) | Service integration system, corresponding device and storage medium | |
| Rolland et al. | A framework for encapsulating best business practices for electricity supply industry into generic patterns | |
| CN112394947B (en) | Information system based on micro-service architecture | |
| CN115185700B (en) | High-integration single-process container management method | |
| Dünnweber et al. | Towards automatic creation of web services for grid component composition | |
| Yau et al. | An approach to adaptive distributed execution monitoring for workflows in service-based systems | |
| KR102485154B1 (en) | Power Communication Service |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230810 Address after: 518000 building 501, 502, 601, 602, building D, wisdom Plaza, Qiaoxiang Road, Gaofa community, Shahe street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: China Southern Power Grid Digital Platform Technology (Guangdong) Co.,Ltd. Address before: Room 86, room 406, No.1, Yichuang street, Zhongxin Guangzhou Knowledge City, Huangpu District, Guangzhou City, Guangdong Province Applicant before: Southern Power Grid Digital Grid Research Institute Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |