CN112667205B - Development method and device for power outage arrangement micro-service and computer equipment - Google Patents
Development method and device for power outage arrangement micro-service and computer equipment Download PDFInfo
- Publication number
- CN112667205B CN112667205B CN202011508925.9A CN202011508925A CN112667205B CN 112667205 B CN112667205 B CN 112667205B CN 202011508925 A CN202011508925 A CN 202011508925A CN 112667205 B CN112667205 B CN 112667205B
- Authority
- CN
- China
- Prior art keywords
- service
- micro
- arrangement
- outage
- power outage
- 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
-
- 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
Landscapes
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application relates to a development method of a power failure arrangement micro-service, which comprises the following steps: acquiring a preset outage scheduling service flow, and splitting the outage scheduling 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; generating a power outage arrangement business flow chart according to a plurality of target platform related meta-models, and converting the power outage 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; based on the extensible style sheet conversion language file and the code generator, the extensible markup language file is mapped into a power outage arrangement micro-service code, and the power outage arrangement micro-service is generated according to the power outage arrangement micro-service code, so that automatic development of the code of the power outage arrangement micro-service is realized, the power outage arrangement micro-service can be rapidly developed and deployed through conversion from a model to the code, and the development efficiency of the power outage arrangement micro-service is effectively improved.
Description
Technical Field
The present application relates to the field of micro services, and in particular, to a method, an apparatus, a computer device, and a storage medium for developing a micro service for arranging power failure.
Background
With the development of power grid technology, the range of a power grid system is increasingly expanded, and electric equipment is continuously increased.
In the prior art, in the running process of the power grid, power outage management is the basis for normal development of various business work of the power grid, and for ensuring reasonable and orderly execution of power outage arrangement plans, relevant software development can be carried out aiming at power outage arrangement, so that quick and accurate power outage arrangement is realized.
However, the existing power outage arrangement application has low development efficiency, and the quick development of the power outage arrangement application is difficult to realize.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, and a storage medium for developing a blackout orchestration microservice.
A method of developing a outage orchestration micro-service for a micro-service application management platform, the method comprising:
acquiring a preset outage scheduling service flow, and splitting the outage scheduling 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 target platform related meta-models are used for describing the outage arrangement business process;
generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power outage arrangement business flow chart into an extensible markup language file;
Generating extensible style sheet conversion language files corresponding to the target platform related meta-models;
and mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
Optionally, the method further comprises:
determining an application running environment specification corresponding to the power outage arrangement micro-service;
determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments;
and deploying the outage scheduling micro-service in the target application running environment.
Optionally, the generating the outage arrangement micro-service according to the outage arrangement micro-service code includes:
determining codes corresponding to a plurality of functional modules from the power outage arrangement micro-service codes; the functional modules are used for providing different application functions when power failure is scheduled;
and generating a plurality of outage arrangement micro-services with different application functions according to the application codes corresponding to the functional modules.
Optionally, the method further comprises:
receiving a power outage arrangement request, and determining a plurality of target power outage arrangement micro-services corresponding to the power outage arrangement request from a plurality of power outage arrangement micro-services;
And determining the calling sequence corresponding to the plurality of target outage scheduling micro-services, and calling the plurality of target outage scheduling micro-services according to the calling sequence.
Optionally, the plurality of outage orchestration micro services in the micro service application management platform are deployed at different service nodes respectively, and the method further comprises:
obtaining micro-service logs uploaded by service nodes corresponding to the micro-service arranged in power outage; the micro service log is acquired from the corresponding power outage arrangement micro service through a log acquisition component on the service node;
and storing the plurality of micro service logs into a preset log storage module.
Optionally, the plurality of outage arrangement micro-services are used for generating call information through expressing the layer transformation rule when the plurality of outage arrangement micro-services are mutually called, and sending the call information to the message middleware so as to forward the call information to the called outage arrangement micro-service through the message middleware.
Optionally, the outage scheduling micro-service includes a micro-service front end and a micro-service back end, and when the micro-service front end receives a micro-service application calling request, the micro-service front end calls an interface gateway through an internet protocol, and calls the micro-service back end through the interface gateway.
A development device for orchestrating micro-services in a power outage, applied to a micro-service application management platform, the device comprising:
the business process acquisition module is used for acquiring a preset power outage arrangement business process, and splitting the power outage arrangement business process according to a plurality of platform related meta-models in the model library to obtain a plurality of target platform related meta-models; the target platform related meta-models are used for describing the outage arrangement business process;
the business flow chart acquisition module is used for generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models and converting the power outage arrangement business 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 target platform related meta-models;
the power outage arrangement micro-service generation module is used for mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
A computer device comprising a memory storing a computer program and a processor implementing the steps of any one of the methods described above when the computer program is executed by the processor.
A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method as claimed in any one of the preceding claims.
In this embodiment, by obtaining a preset outage arrangement business process and splitting the outage arrangement business process according to a plurality of platform related meta-models in a model library, obtaining a plurality of target platform related meta-models, generating a outage arrangement business process diagram according to the plurality of target platform related meta-models, converting the outage arrangement business process diagram into an extensible markup language file, and generating extensible style sheet conversion language files corresponding to the plurality of target platform related meta-models, mapping the extensible markup language file into outage arrangement micro-service codes based on the extensible style sheet conversion language files and a code generator, and generating outage arrangement micro-service codes according to the outage arrangement micro-service codes, automatic development of codes of the outage arrangement micro-service is realized, the outage arrangement micro-service can be rapidly developed and deployed through conversion from the model to the codes, and development efficiency of the outage arrangement micro-service is effectively improved.
Drawings
FIG. 1 is a flow diagram of a method of developing outage orchestration micro-services, according to one embodiment;
FIG. 2 is a flow chart illustrating steps for generating a micro-service for outage orchestration in one embodiment;
FIG. 3 is a flow chart illustrating steps for scheduling micro-service invocation in a blackout in one embodiment;
FIG. 4 is a block diagram of an apparatus for developing outage orchestration micro-services, according to one embodiment;
fig. 5 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
In one embodiment, as shown in fig. 1, a method for developing a micro service for arranging power failure is provided, and this embodiment is exemplified by the method being applied to a micro service application management platform, where the micro service application management platform may be implemented by using an independent server or a server cluster formed by a plurality of servers, and the micro service application management platform may manage one or more micro service applications. It will be appreciated that the method may also be applied to a terminal, and may also be applied to a system comprising a terminal and a server, and implemented by interaction of the terminal and the server. In this embodiment, the method may include the steps of:
Step 101, acquiring a preset power outage arrangement business process, and splitting the power outage 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 outage orchestration business process.
As an example, a blackout orchestration business process is used to describe business logic of a blackout orchestration manner for a power utilization area or a powered device in a power grid, such as a blackout object for which blackout is orchestrated, a blackout start time, a blackout end time, a blackout frequency, a power utilization amount for triggering blackout of the blackout object, and the like. Service personnel can preset corresponding power outage arrangement service flows aiming at power outage arrangement in a power grid.
In practical applications, a model library may be provided in the micro service application management Platform, and a plurality of different Platform-related metamodels, i.e., PSM (Platform-specific models) metamodels may be included in the model library. When the outage scheduling business process is obtained, the micro-service application management platform can be used as a platform related meta-model in a model library, the outage scheduling business process is split as a minimum unit for splitting the business process, a plurality of platform related meta-models obtained after the outage scheduling 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 the splitting can be used for describing the outage scheduling business process.
And 102, generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power outage arrangement business flow chart into an extensible markup language file.
As an example, the outage orchestration business flow chart may be a flow chart reflecting outage orchestration business flow, which may be a flow chart built based on UML (Unified-Modeling-Language) activity charts. The extensible markup language file may also be called an XML (extensible markup language ) file, which refers to a file generated by using an extensible markup language; the UML activity diagram may refer to an activity diagram generated in a unified modeling language.
After obtaining the plurality of target platform related meta-models, a blackout orchestration business flow chart may be generated based on the plurality of target platform related meta-models and converted into an extensible markup language file, e.g., a blackout orchestration business flow chart in the form of a UML activity diagram, into an XML file
And step 103, generating extensible style sheet conversion language files corresponding to the target platform related meta-models.
As an example, an extensible style sheet conversion language file may also be referred to as a XSLT (Extensible Stylesheet Language Transformations) file, and may refer to a file generated using an extensible style sheet conversion language as one type of style conversion markup language, which may convert data generated based on extensible markup language (XML) into a file of another format.
In this embodiment, after determining a plurality of target platform related meta-models, corresponding extensible style sheet conversion language files may be generated for the plurality of target platform related meta-models, and specifically, for each target platform related meta-model, extensible style sheet conversion language files corresponding to the target platform related meta-model may be generated.
And 104, mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and obtaining the power outage arrangement micro-service according to the power outage arrangement micro-service code.
Because the extensible markup language file is a file generated by adopting an extensible markup language, after the extensible style sheet conversion language file is obtained, the extensible markup language file can be mapped into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and further the power outage arrangement micro-service can be generated according to the obtained power outage arrangement micro-service code.
In this embodiment, a power outage arrangement business process is obtained by obtaining a preset power outage arrangement business process, splitting the power outage arrangement business process according to a plurality of platform related meta-models in a model library, obtaining a plurality of target platform related meta-models, generating a power outage arrangement business process diagram according to the plurality of target platform related meta-models, converting the power outage 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 a power outage arrangement micro-service code based on the extensible style sheet conversion language files and a code generator, generating a power outage arrangement micro-service according to the power outage arrangement micro-service code, realizing automatic development of the code of the power outage arrangement micro-service, enabling the power outage arrangement micro-service to be rapidly developed and deployed through conversion from the model to the code, and effectively improving development efficiency of the power outage arrangement micro-service.
In this embodiment, the construction of the outage orchestration microservices may be performed based on Model-Driven Architecture (MDA). The model driving architecture takes UML and other industrial standards as technical supports, can create a standardized model which is high in abstraction degree, machine-readable and independent of implementation technology, can realize visualization, storage and exchange of a software development model in a software development process, emphasizes that the whole system development process is driven by modeling behaviors of a software system, and completes system demand analysis, architecture design, construction, testing, deployment and operation maintenance work.
In the model driven architecture, three modeling standards of UML, MOF (Meta-Object-Facility) and CWM (Common repository Meta-model) can be used as modeling bases of PIM and PSM. Second, the model driven architecture may be applied to a variety of implementation technology platforms, including publicly standard or proprietary implementation technology platforms, such as CORBA (public object request broker architecture, common ObjectRequest Broker Architecture), XMI (XML metadata interchange )/XML (extensible markup language, extensible Markup Language),. NET (microsoft operations platform), JAVA, and Web Service. The model driven architecture may also define various Services, such as Directory Services (Directory-Services), transaction-Services (Transaction-Services), security-Services (Security-Services), distributed Event and Notification Services (Distributed-Event-and-Notification-Services). Model driven architecture flexibility such that the model driven architecture may be applied in a variety of field environments, such as 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 running environment specification corresponding to the power outage arrangement micro-service; determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments; and deploying the outage scheduling micro-service in the target application running environment.
In this embodiment, after the outage arrangement micro-service is generated, an application running environment specification corresponding to the outage arrangement micro-service may be determined, and further, a target application running environment meeting the application running environment specification may be determined from a plurality of preset application running environments, and further, the outage arrangement micro-service may be deployed in the target application running environment.
In practical application, the code data running environment provider or the program running environment provider can describe the application running environment provided by the code data running environment provider or the program running environment provider according to a preset running environment description specification, generate an application running environment description file and issue the application running environment description file to the outside. And the micro-service application management platform can take the application running environment provided by the code data running environment provider or the program running environment provider as a plurality of preset application running environments and select a target application running environment according to the plurality of application running environment description files.
The application running environment can be logically bound with the outage arrangement micro-service and provide services together with the outage arrangement micro-service, wherein the application running environment can be separated from the outage arrangement micro-service in physical structure and can be operated independently; the same outage orchestration micro-service may run in different application operating environments, including application operating environments that are for distributed or redundancy purposes.
In this embodiment, from a plurality of preset application operating environments, a target application operating environment meeting the application operating environment specification is determined, and the outage scheduling micro-service is deployed in the target application operating environment, so that normal operation of the outage scheduling micro-service can be ensured.
In one embodiment, as shown in fig. 2, the generating the outage arrangement micro-service according to the outage arrangement micro-service code may include the following steps:
step 201, determining codes corresponding to a plurality of functional modules from the outage arrangement micro-service codes; the plurality of functional modules are used for providing different application functions when power failure is scheduled.
In practical application, after mapping the extensible markup language file into a power outage arrangement micro-service code, the obtained power outage 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 functional modules from the power outage arrangement micro-service code according to the identifiers, wherein each functional module can provide different application functions when a service person performs power outage arrangement.
Step 202, generating a plurality of outage arrangement micro-services with different application functions according to application codes corresponding to the functional modules.
After determining the application codes corresponding to the functional modules, the micro-service application management platform can generate a plurality of outage arrangement micro-services with different application functions aiming at the application codes corresponding to the functional modules to obtain a plurality of outage arrangement micro-services, and deploy the plurality of outage arrangement micro-services in the platform based on a micro-service architecture.
In particular, a micro-service architecture may refer to a plurality of units of work with high cohesiveness and small synergy, as determined by the service scope. The micro service architecture obviously enhances the suitability, can make a suitable choice of tools and languages, then split programs, group internal services, and can construct perfect services with specific services as the center and keep the perfect services independent in the system process on the premise that all services in a platform or a system are coordinated and matched with each other.
In the micro-service architecture, each micro-service corresponds to a working unit, and each unit has higher autonomy and can exist in the process of a system or a platform or run in the system or the platform in the form of independent entities. Each micro-service can be regarded as a component, and each component in the micro-service architecture has the advantages of simplified operation and small space occupation compared with the traditional component. In the conventional component, although a common part of the service can be extracted, and independent service links are isolated, so that the program can be used in a modularized mode, and then decoupled and multiplexed, however, different services have a coupling relationship, in the running process of the system, an application program changes a single system, and the service needs to be re-constructed. While micro-service architecture may directly break down services in a platform or system.
In this embodiment, according to the application codes corresponding to the respective functional modules, a plurality of outage arrangement micro-services with different application functions are generated, and a plurality of outage arrangement micro-services are generated, so that a perfect service can be built with a specific service as a center under the condition that the outage arrangement micro-services of the system are coordinated and matched with each other, and the perfect service can be kept independent in the system process.
In one embodiment, as shown in fig. 3, the method may further comprise the steps of:
step 301, receiving a outage arrangement request, and determining a plurality of target outage arrangement micro-services corresponding to the outage arrangement request from a plurality of outage arrangement micro-services.
In practical application, a service requester (for example, a terminal or a service end) needing to schedule power failure of electric equipment can send a power failure scheduling request to a micro-service application management platform, after receiving the power failure scheduling request, the micro-service application management platform can determine corresponding service requirements from the received power failure scheduling request, and then can determine a plurality of target power failure scheduling micro-services corresponding to the request from a plurality of power failure scheduling micro-services in the micro-service application management platform.
Step 302, determining the calling sequence corresponding to the plurality of target outage scheduling micro-services, and calling the plurality of target outage scheduling micro-services according to the calling sequence.
After determining the plurality of target outage arrangement micro-services, the plurality of target outage arrangement micro-services can be arranged in a calling sequence, and the calling sequence of the plurality of target outage arrangement micro-services is determined, so that the plurality of target outage arrangement micro-services can be sequentially called according to the calling sequence to respond to the outage arrangement request.
In this embodiment, by determining the calling sequence corresponding to the plurality of target outage arrangement micro-services and calling the plurality of target outage arrangement micro-services according to the calling sequence, the combination, arrangement and integration of different outage arrangement micro-services can be realized, and each outage arrangement micro-service in the micro-service application management platform can be efficiently and orderly called to respond to the related 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; the micro-service application management platform or the micro-service issued by a third party in the network can be searched according to the specification, and the related search result is called after the related search result is obtained; or, the service requirement of the micro-service application management platform can be issued in a format specified in the network, and a third party in the network sends corresponding service request information to the micro-service application management platform.
In one embodiment, the plurality of outage orchestration micro services in the micro service application management platform are deployed at different service nodes, respectively, and the method may further comprise the steps of:
obtaining micro-service logs uploaded by service nodes corresponding to the micro-service arranged in power outage; the micro service log is acquired from the corresponding power outage arrangement micro service through a log acquisition component on the service node; and storing the plurality of micro service logs into a preset log storage module.
In a specific implementation, a plurality of outage arrangement microservices can be deployed on different service nodes, however, when checking logs in each service node microservices, if log checking is performed by logging in each service node, the log checking is too complicated, and when joint checking analysis is performed for a plurality of microservices logs to be associated, the above-mentioned mode is more inconvenient. As the number of nodes and micro services in the platform increase, the positioning and viewing of micro service logs 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 outage arrangement micro-service on the same node, and then the micro-service application management platform can obtain the logs of the outage arrangement micro-service corresponding to each service node. After the logs of each power outage arrangement micro service are obtained, the micro service application management platform can store all the logs into a preset log storage module, can uniformly manage the plurality of logs according to a pre-established log management specification, and can determine and correlate the plurality of logs with association relations from the plurality of logs.
In this embodiment, by disposing the log collection component on each service node, the micro service log uploaded by the service node corresponding to each micro service scheduled by each power outage can be obtained, and the log is stored for a plurality of micro service logs, so that the speed of consulting the subsequent micro service log is effectively improved, and multiple logging in the service node when the micro service log is checked is avoided.
In one embodiment, a plurality of outage orchestration microservices may be invoked with respect to each other. Specifically, each outage orchestration micro-service may generate invocation information by expressing the layer transformation rules (i.e., representational State Transfer, REST) when invoking other outage orchestration micro-services, and send the invocation information to the message middleware. After receiving the call information, the message middleware can determine the called target object, namely the called outage arrangement micro-service, from the call information, and then can forward the call information to the called outage arrangement micro-service. In the micro-service application management platform, the communication mode of network call can enhance the isolation between the micro-services of each power outage arrangement and prevent the coupling phenomenon in the operation process of the platform.
In the embodiment, a data interaction basis is provided for the mutual call between the power outage arrangement micro-services through the information interaction mechanism of the message middleware, so that the cooperation efficiency between the power outage arrangement micro-services is effectively improved.
In one embodiment, the outage orchestration micro-service may include a micro-service front-end and a micro-service back-end, and when the micro-service front-end receives a micro-service application invocation request, an interface (API) gateway may be invoked according to an Internet protocol, and the micro-service back-end may be invoked through the interface gateway. Specifically, the interface network manager may be a hierarchical interface gateway, and when the front end of the micro service invokes the hierarchical interface gateway through Http/Https protocol, the hierarchical interface gateway may determine a rear end of the micro service corresponding to the front end of the micro service through the routing server, and invoke the rear end of the micro service.
In this embodiment, through the interface gateway, the corresponding microservice back end is called by the microservice front end under the condition of distinguishing the microservice front end and the microservice back end, so that front-back end separation is realized, and support is provided for independent development of the front-back end of the microservice for arranging the outage.
In practical applications, when the micro-service application management platform is constructed, automatic service implementation can be performed, including automatic construction, automatic installation and deployment, automatic testing, automatic platform release (for example, through a Docker implementation), and management services and collaborative services are deployed in the micro-service application management platform. For the management service, according to the micro-service architecture, corresponding monitoring and management service and log management service can be matched; aiming at the collaboration service, the development, test and operation and maintenance efficient communication and collaboration can be realized by using the DevOps idea, and the development and operation and maintenance integrated effect is achieved.
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, calling, interaction and QOS information among the micro-services in the network can be managed. Through micro-service data management, data sources, databases, and data content information used by micro-services in the platform may be managed. Through the micro-service resource management, network resources, system resources, storage resources and running environment resources related to the micro-service in the network can be managed. Through network supervision, the micro-service release rule, the micro-service discovery rule, the micro-service scheduling rule, the micro-service combination rule and the service networking rule in the network can be managed.
In one embodiment, for a plurality of outage orchestration micro-services, a technology or a development language of a more suitable service can be selected according to characteristics of different service fields to develop the micro-services, and the consistency of the technology or the language in a service system is not needed to be considered, namely, the plurality of outage orchestration micro-services in a micro-service application management platform can be developed based on different development languages. If standardized techniques or languages are forced to be used for all services in a platform or system, it is difficult to support a specific service scenario effectively. In this 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 the special service scene. In addition, different technical stacks and storage modes can be used between 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 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 normally provide services, and the fault tolerance of the platform is effectively improved.
It should be understood that, although the steps in the flowcharts of fig. 1-3 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 1-3 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor do the order in which the steps or stages are performed necessarily performed in sequence, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
In one embodiment, as shown in fig. 4, there is provided a development device for arranging micro services in power outage, including:
the service flow obtaining module 401 is configured to obtain a preset outage scheduling service flow, and split the outage scheduling 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 target platform related meta-models are used for describing the outage arrangement business process;
a service flow chart acquisition module 402, configured to generate a power outage arrangement service flow chart according to the multiple target platform related 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 style sheet conversion language files corresponding to the multiple target platform related meta-models;
the outage arrangement micro-service generation module 404 is configured to map the extensible markup language file into an outage arrangement micro-service code based on the extensible style sheet conversion language file and the code generator, and generate an outage arrangement micro-service according to the outage arrangement micro-service code.
In one embodiment, the apparatus may further include:
The environment specification acquisition module is used for determining an application running environment specification corresponding to the power outage arrangement micro-service;
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 outage arrangement micro-service in the target application running environment.
In one embodiment, the outage orchestration micro-service generation module 404 comprises:
the function module code determining sub-module is used for determining codes corresponding to the plurality of function modules from the power outage arrangement micro-service codes; the functional modules are used for providing different application functions when power failure is scheduled;
and the function module code conversion sub-module is used for generating a plurality of outage arrangement micro-services with different application functions according to the application codes corresponding to the function modules.
In one embodiment, the apparatus may further include:
the system comprises a target outage arrangement micro-service determining module, a target outage arrangement micro-service determining module and a control module, wherein the target outage arrangement micro-service determining module is used for receiving an outage arrangement request and determining a plurality of target outage arrangement micro-services corresponding to the outage arrangement request from a plurality of outage arrangement micro-services;
And the calling sequence determining module is used for determining the calling sequence corresponding to the plurality of target power outage arrangement micro-services and calling the plurality of target power outage arrangement micro-services according to the calling sequence.
In one embodiment, the plurality of outage orchestration micro services in the micro service application management platform are deployed at different service nodes, respectively, and the apparatus further comprises:
the micro service log acquisition module is used for acquiring micro service logs uploaded by service nodes corresponding to the micro service arranged by power failure; the micro service log is acquired from the corresponding power outage arrangement micro service through a log acquisition component on the service node;
the micro service log storage module is used for storing the plurality of micro service logs into the preset log storage module.
In one embodiment, the plurality of outage arrangement micro-services are configured to generate call information by expressing a layer transformation rule when mutually invoking, and send the call information to a message middleware, so as to forward the call information to the invoked outage arrangement micro-service through the message middleware.
In one embodiment, the outage orchestration micro-service includes a micro-service front end and a micro-service back end, and when the micro-service front end receives a micro-service application call request, the micro-service front end calls an interface gateway through an internet protocol, and calls the micro-service back end through the interface gateway.
For a specific limitation of the development device of the outage arrangement micro-service, reference may be made to the limitation of the development method of the outage arrangement micro-service hereinabove, and the description thereof will not be repeated here. The modules in the development device for arranging the micro-service in the power outage can be fully or partially realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above 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 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing data corresponding to the power outage 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, when executed by a processor, implements a method of developing outage orchestration microservices.
It will be appreciated by those skilled in the art that the structure shown in FIG. 5 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the 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 stored therein a computer program, the processor when executing the computer program performing the steps of:
acquiring a preset outage scheduling service flow, and splitting the outage scheduling 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 target platform related meta-models are used for describing the outage arrangement business process;
generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power outage arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the target platform related meta-models;
And mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
In one embodiment, the steps of the other embodiments described above are also implemented when the processor executes a computer program.
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 outage scheduling service flow, and splitting the outage scheduling 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 target platform related meta-models are used for describing the outage arrangement business process;
generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power outage arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the target platform related meta-models;
and mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
In one embodiment, the computer program, when executed by a processor, also implements the steps of the other embodiments described above.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (10)
1. A method for developing a micro-service for outage orchestration, the method being applied to a micro-service application management platform, the method comprising:
acquiring a preset outage scheduling service flow, and splitting the outage scheduling 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 target platform related meta-models are used for describing the outage arrangement business process;
Generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models, and converting the power outage arrangement business flow chart into an extensible markup language file;
generating extensible style sheet conversion language files corresponding to the target platform related meta-models;
and mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and a code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
2. The method as recited in claim 1, further comprising:
determining an application running environment specification corresponding to the power outage arrangement micro-service;
determining a target application running environment meeting the application running environment specification from a plurality of preset application running environments;
and deploying the outage scheduling micro-service in the target application running environment.
3. The method of claim 1, wherein generating a blackout orchestration micro-service from the blackout orchestration micro-service code comprises:
determining codes corresponding to a plurality of functional modules from the power outage arrangement micro-service codes; the functional modules are used for providing different application functions when power failure is scheduled;
And generating a plurality of outage arrangement micro-services with different application functions according to the application codes corresponding to the functional modules.
4. A method according to claim 3, further comprising:
receiving a power outage arrangement request, and determining a plurality of target power outage arrangement micro-services corresponding to the power outage arrangement request from a plurality of power outage arrangement micro-services;
and determining the calling sequence corresponding to the plurality of target outage scheduling micro-services, and calling the plurality of target outage scheduling micro-services according to the calling sequence.
5. The method of claim 3, wherein a plurality of outage orchestration micro services in the micro service application management platform are deployed at different service nodes, respectively, the method further comprising:
obtaining micro-service logs uploaded by service nodes corresponding to the micro-service arranged in power outage; the micro service log is acquired from the corresponding power outage arrangement micro service through a log acquisition component on the service node;
and storing the plurality of micro service logs into a preset log storage module.
6. The method of claim 1, wherein the plurality of outage orchestration micro-services are configured to generate call information via a presentation state transformation rule when invoked on each other, and to send the call information to a messaging middleware, to forward the call information via the messaging middleware to the invoked outage orchestration micro-service.
7. The method of claim 1, wherein the outage orchestration micro-service comprises a micro-service front-end and a micro-service back-end, the micro-service front-end invoking an interface gateway via an internet protocol upon receiving a micro-service application invocation request, and invoking the micro-service back-end via the interface gateway.
8. A power outage orchestration micro-service development device, for use with a micro-service application management platform, the device comprising:
the business process acquisition module is used for acquiring a preset power outage arrangement business process, and splitting the power outage arrangement business process according to a plurality of platform related meta-models in the model library to obtain a plurality of target platform related meta-models; the target platform related meta-models are used for describing the outage arrangement business process;
the business flow chart acquisition module is used for generating a power outage arrangement business flow chart according to the plurality of target platform related meta-models and converting the power outage arrangement business 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 target platform related meta-models;
The power outage arrangement micro-service generation module is used for mapping the extensible markup language file into a power outage arrangement micro-service code based on the extensible style sheet conversion language file and the code generator, and generating the power outage arrangement micro-service according to the power outage arrangement micro-service code.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements 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 CN112667205A (en) | 2021-04-16 |
| CN112667205B true 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 (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110276592A (en) * | 2019-06-14 | 2019-09-24 | 北京科技大学 | A kind of micro services system business process variability modelling method and system |
| US10425350B1 (en) * | 2015-04-06 | 2019-09-24 | EMC IP Holding Company LLC | Distributed catalog service for data processing platform |
| 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 |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10387631B2 (en) * | 2016-05-06 | 2019-08-20 | Enterpriseweb Llc | Systems and methods for domain-driven design and execution of modular and dynamic services, applications and processes |
| US10985997B2 (en) * | 2016-05-06 | 2021-04-20 | 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 |
| US10762452B2 (en) * | 2017-03-09 | 2020-09-01 | At&T Intellectual Property I, L.P. | System and method for designing and executing control loops in a cloud environment |
| US10983843B2 (en) * | 2018-01-16 | 2021-04-20 | Enterpriseweb Llc | Event-driven programming model based on asynchronous, massively parallel dataflow processes for highly-scalable distributed applications |
-
2020
- 2020-12-19 CN CN202011508925.9A patent/CN112667205B/en active Active
Patent Citations (5)
| 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 |
| 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 |
|---|
| Microservice Ambients: An Architectural Meta-Modelling Approach for Microservice Granularity;Sara Hassan等;《2017 IEEE International Conference on Software Architecture》;第1-10页 * |
| NFV网络编排器发展现状与关键技术研究;金镝等;《信息通信技术与政策》(第03期);第86-91页 * |
| 基于交互流建模语言的微服务架构建模研究;邓禹等;《软件导刊》;第17卷(第1期);第165-168页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112667205A (en) | 2021-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112035228B (en) | Resource scheduling method and device | |
| CN112394947B (en) | Information system based on micro-service architecture | |
| EP1577765A2 (en) | Flexible deployment of software applications | |
| CN101847100B (en) | Method for expanding software application and device | |
| US20080183479A1 (en) | Business process reconstruction method, and its program and computer | |
| CN110262902B (en) | Information processing method and system, medium, and computing device | |
| US20050021697A1 (en) | System and method providing automatic policy enforcement in a multi-computer service application | |
| US20020087734A1 (en) | System and method for managing dependencies in a component-based system | |
| CN111290753A (en) | Method, device, equipment and storage medium for building front-end development environment | |
| CN111381983A (en) | Lightweight message middleware system and method of virtual test target range verification system | |
| CN112698921A (en) | Logic code operation method and device, computer equipment and storage medium | |
| CN101860564A (en) | Protocol-based service combination system and method | |
| CN103390018A (en) | Web service data modeling and searching method based on SDD (service data description) | |
| CN115480753A (en) | Application integration system and corresponding computer device and storage medium | |
| CN117742882A (en) | Scheduling method and system for integrated arrangement of application system | |
| US10223143B2 (en) | System and method for supporting javascript as an expression language in a process defined by a process execution language for execution in a SOA middleware environment | |
| CN113360386A (en) | Switching chip drive test method, device, electronic equipment and storage medium | |
| CN113190341A (en) | Server resource scheduling method and system | |
| CN112667205B (en) | Development method and device for power outage arrangement micro-service and computer equipment | |
| US10268496B2 (en) | System and method for supporting object notation variables in a process defined by a process execution language for execution in a SOA middleware environment | |
| US7885292B2 (en) | Method, system, and computer program product for data exchange | |
| JP2003067356A (en) | Application linkage system and application linkage method | |
| Ma et al. | Model-based management of service composition | |
| CN115809149B (en) | Data lake construction method utilizing cloud primary resources | |
| CN117472553B (en) | Workflow processing method, device, processing equipment and readable storage medium |
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 |