CN-122019230-A - Nuclear power production service management system

CN122019230ACN 122019230 ACN122019230 ACN 122019230ACN-122019230-A

Abstract

The disclosure belongs to the technical field of nuclear power, and particularly relates to a nuclear power production service management system. The system of the present disclosure deploys a governance framework and provides a nuclear power production service governance function based on Kubernetes and Docker container virtualization technologies, and compared with the traditional mode, the system is more stable, robust, simple and convenient for forming software services, and continuous and comprehensive service governance, thereby ensuring high availability of application services and service expandability, reducing non-research and development operations of developers, and being beneficial for the developers to concentrate more on the development of self-service.

Inventors

LI JIE
WU YAOYAO
LI ZHIANG
LUO YOU

Assignees

核动力运行研究所

Dates

Publication Date: 20260512
Application Date: 20260115

Claims (7)

1. The nuclear power production service management system is characterized by comprising a Kubernetes cluster, a service management framework and a plurality of application services; The Kubernetes cluster is used for providing container management functions including service capacity expansion, self-repairing, service discovery and load balancing; the service management framework is deployed on the Kubernetes cluster and comprises a registration center, a configuration center, a fusing protection module and a service call monitoring module; A plurality of application services deployed in a container form under respective namespaces of the Kubernetes cluster, each application Service instance running as a Pod and exposed through Service, wherein the Service binds a set Pods through Label and Selector rules; each application service is configured to access the service governance framework, comprising: When the system is started, registering service information comprising the name, IP address, port and metadata of the application service to the registry, grouping the service according to the name of the application service, registering the instance of the application service with the same name under the same group, and pulling the service registry data from the registry to be cached locally; the configuration center is used for dynamic configuration management, configuration change is monitored through a client-side long polling mechanism, and when the configuration change occurs, the client-side is triggered asynchronously to pull the configuration data and update the local cache; When calling among services, acquiring a called service instance from a local registry, and sending a request to a target instance through a load balancing strategy; the fusing protection module is integrated, and when the overtime or unavailability of the downstream service is detected, a fusing strategy is triggered to perform fusing degradation; integrating the service call monitoring module, recording service call chain data comprising Span and Trace, and reporting to the service call monitoring module for persistence to generate call topology and node detailed information.
2. The system of claim 1, wherein the service governance framework and the application service are deployed in the Kubernetes cluster in a mirrored manner.
3. The system of claim 1, wherein the registry is configured to maintain a service registry and receive heartbeat messages periodically reported by application services to monitor instance status, the application services updating local registry data via a timed pull.
4. The system of claim 1, wherein the configuration center allows a user to create and modify configuration files and trigger configuration change events via a server, and wherein the client is provided with a long polling mechanism for acquiring configuration updates in real time.
5. The system of claim 1, wherein the fuse protection module triggers fuse degradation to prevent system avalanche effects when network anomalies or downstream service faults occur during service invocation.
6. The system of claim 1, wherein the service invocation monitoring module graphically exposes service invocation topology on the control page after persisting the invocation chain data, including the request time, number of invocations, number of failures, and invocation instance information for each invocation node.
7. The system of claim 1, wherein the application service accesses components of the service governance framework by service name and namespace to ensure stability and extensibility of the service governance framework.

Description

Nuclear power production service management system Technical Field The invention belongs to the technical field of nuclear power, and particularly relates to a nuclear power production service management system. Background Nuclear power is accepted and adopted by more and more countries as a safe, clean, low-carbon and reliable energy source, and related industries are expanding continuously. The informatization and digital construction of the nuclear power industry are gradually perfected. The construction of informatization and digitalization depends on software services, the scale of related services is continuously increased along with the expansion of basic services in the nuclear power industry, the complexity of a nuclear power related system is exponentially increased, and the maintenance difficulty and the readability of the system are correspondingly improved, so that the performances of the system, such as stability, usability and the like, are correspondingly reduced, and finally the experience of a user is influenced. For the above-mentioned cases, a general single architecture cannot support stable operation of a large-scale service. Therefore, it is needed to optimize the architecture of the nuclear power industry informatization system and improve the service performance of the system. Disclosure of Invention In order to overcome the problems in the related art, the nuclear power production service management system based on the cloud primordial technology is provided. According to one aspect of the embodiment of the disclosure, a nuclear power production service governance system is provided, which comprises a Kubernetes platform, a service governance framework and a plurality of application services; The Kubernetes platform is used for providing container management functions including service capacity expansion, self-repairing, service discovery and load balancing; the service management framework is deployed on the Kubernetes platform and comprises a registration center, a configuration center, a fusing protection module and a service call monitoring module; A plurality of application services deployed in a container form under a corresponding namespace of the Kubernetes platform, each application Service instance running as a Pod and exposed through Service, wherein the Service binds a set Pods of rules through Label and Selector; each application service is configured to access the service governance framework, comprising: When the system is started, registering service information comprising the name, IP address, port and metadata of the application service to the registry, grouping the service according to the name of the application service, registering the instance of the application service with the same name under the same group, and pulling the service registry data from the registry to be cached locally; the configuration center is used for dynamic configuration management, configuration change is monitored through a client-side long polling mechanism, and when the configuration change occurs, the client-side is triggered asynchronously to pull the configuration data and update the local cache; When calling among services, acquiring a called service instance from a local registry, and sending a request to a target instance through a load balancing strategy; the fusing protection module is integrated, and when the overtime or unavailability of the downstream service is detected, a fusing strategy is triggered to perform fusing degradation; integrating the service call monitoring module, recording service call chain data comprising Span and Trace, and reporting to the service call monitoring module for persistence to generate call topology and node detailed information. In one possible implementation, the service governance framework and the application service are deployed in a mirrored fashion in the Kubernetes platform. In one possible implementation, the registry is configured to maintain a service registry and receive heartbeat messages periodically reported by an application service to monitor an instance state, where the application service updates local registry data via a timed pull mode. In one possible implementation, the configuration center allows a user to create and modify a configuration file, and triggers a configuration change event through a server, and the client is provided with a long polling mechanism for acquiring configuration updates in real time. In one possible implementation, the fuse protection module triggers fuse degradation to prevent system avalanche effects when a network anomaly or downstream service failure occurs during service invocation. In one possible implementation manner, after the service call monitoring module persistence the call chain data, the service call topological relation is displayed in a control page in a graphic manner, wherein the service call topological relation comprises the request time, the call times, the failure num