CN111277431A - Server Architecture Method for Online Monitoring of Ultra-UHV Transmission Lines - Google Patents
Server Architecture Method for Online Monitoring of Ultra-UHV Transmission LinesDownload PDFInfo
- Publication number
- CN111277431A CN111277431ACN202010019004.XACN202010019004ACN111277431ACN 111277431 ACN111277431 ACN 111277431ACN 202010019004 ACN202010019004 ACN 202010019004ACN 111277431 ACN111277431 ACN 111277431A
- Authority
- CN
- China
- Prior art keywords
- docker
- layer
- server
- ultra
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
- H04L41/0286—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP] for search or classification or discovery of web services providing management functionalities
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Remote Monitoring And Control Of Power-Distribution Networks (AREA)
Abstract
Description
Translated fromChinese技术领域technical field
本发明属于服务器架构领域，涉及超特高压输电线路在线监测服务器架构方法。The invention belongs to the field of server architecture, and relates to a server architecture method for on-line monitoring of ultra-high voltage transmission lines.
背景技术Background technique
在微服务出现之前，网站服务(web)、接口服务(移动端)的服务架构通常是“一站式”的。一个服务应用中通常包含多个模块和接口，传统的开发模式和设计风格是将所有功能、接口统一设计，分层设计，逐层开发实现。以一个典型的web网站为例。它至少包含表示层(UI)、业务层(逻辑控制)、服务层(services)、数据访问层(D A O)、持久层(数据库) 5层。在这5层的几十上百个模块中，若有任何一处没有完成开发或编译成功，都可能影响整个站点的部署。针对上述问题，20世纪90年代末，SOA(Service Oriented Architecture)面向服务架构被提出[21SO A首次提出了在软件架构设计时，使用低耦合并面向服务流程的思想。将流程分解为步骤，而每个步骤的实现都可以定义为一个服务。但 SOA的架构中，复杂的E SB企业服务总线依然处于非常重要的位置，整个系统的架构并没有实现完全的组件化以及面向服务，它的学习和使用门槛依然偏高。微服务架构的思想本质上来源于项目设计中对业务功能和模块的水平、垂直切割、拆分。2012年，微服务的架构被提出，并陆续出现了诸多设计案例。在随后的几年里Amazon、Uber等企业进行了各自的实践并取得了成功。微服务强调完全的组件化和面向服务。所有微服务均是独立的，微服务对外以RESTAPI形式暴露给调用者。Before the emergence of microservices, the service architecture of website service (web) and interface service (mobile terminal) was usually "one-stop". A service application usually contains multiple modules and interfaces. The traditional development mode and design style is to design all functions and interfaces in a unified manner, design them in layers, and develop and implement them layer by layer. Take a typical web site as an example. It contains at least the presentation layer (UI), business layer (logic control), service layer (services), data access layer (DA O), persistence layer (database) 5 layers. Among the dozens or hundreds of modules in these 5 layers, if any part is not developed or compiled successfully, it may affect the deployment of the entire site. In response to the above problems, in the late 1990s, SOA (Service Oriented Architecture) was proposed [21 SOA first proposed the idea of using low coupling and service-oriented process in software architecture design. The process is broken down into steps, and the implementation of each step can be defined as a service. However, in the SOA architecture, the complex ESB enterprise service bus is still in a very important position. The architecture of the entire system has not been fully componentized and service-oriented, and its learning and use threshold is still high. The idea of microservice architecture essentially comes from the horizontal and vertical cutting and splitting of business functions and modules in project design. In 2012, the architecture of microservices was proposed, and many design cases appeared one after another. In the following years, companies such as Amazon and Uber have carried out their own practices and achieved success. Microservices emphasize complete componentization and service orientation. All microservices are independent, and the microservices are exposed to the caller in the form of REST API.
发明内容SUMMARY OF THE INVENTION
本发明的目的在于：提供了超特高压输电线路在线监测服务器架构方法，解决了目前服务器的服务的应用和发布不管、服务的运维和治理没有透明化、服务化的能力，并且没有一整套高效支撑应用快速开发迭代的服务化架构的问题。The purpose of the present invention is to provide a server architecture method for on-line monitoring of ultra-high voltage transmission lines, which solves the problem that the application and release of services of the current server are not transparent and service-oriented, and there is no complete set of services. The problem of a service-based architecture that efficiently supports the rapid development and iteration of applications.
本发明采用的技术方案如下：超特高压输电线路在线监测服务器架构方法，所述方法包括如下步骤:S1：采用Docker服务器为基础，将Docker服务器分为表现层、业务层和运行层；S2：在表现层内建立web门户网站，用户可以对正在提供服务的应用容器请求访问，在门户网站查看和管理运行层的容器；S3：在业务层内建立自动化持续集成的构建器模块，通过构建器模块进行容器服务的负载均衡，并通过构建器模块生成工程文件；S4：在业务层内选用应用进行上线运行，从业务层得到可部署的工程文件后，将该文件与相应的应用环境进行镜像，生成镜像文件上传到服务器的镜像仓库进行存储，在将镜像文件通过表现层的web门户网站放出，供用户请求和访问；S5：超特高压输电线路监控装置采集的监控数据，通过外网服务器输入至交换系统内，通过交换系统导入Docker服务器内，用户通过表现层登录后，对监控数据进行处理。The technical scheme adopted in the present invention is as follows: an ultra-ultra-high voltage transmission line online monitoring server architecture method, the method includes the following steps: S1: using a Docker server as a basis, and dividing the Docker server into a presentation layer, a business layer and an operation layer; S2: Build a web portal in the presentation layer, users can request access to the application container that is providing services, view and manage the containers in the running layer on the portal website; S3: Build a builder module for automated continuous integration in the business layer, through the builder The module performs load balancing of container services, and generates project files through the builder module; S4: Select applications in the business layer to run online, obtain deployable project files from the business layer, and mirror the files with the corresponding application environment , generate image files and upload them to the mirror warehouse of the server for storage, and then release the image files through the web portal website of the presentation layer for users to request and access; S5: The monitoring data collected by the ultra-high voltage transmission line monitoring device, through the external network server Input into the exchange system, import it into the Docker server through the exchange system, and process the monitoring data after the user logs in through the presentation layer.
在目前的服务器架构中，服务化架构的演进历史经历了MVC架构、RPC架构、SOA 机构、微服务架构。MVC架构它主要用来解决前后端、界面、控制逻辑和业务逻辑分层问题。比较流行的技术堆栈就是Spring+Struts+iBatis5(Hibernate)+Tomcat(JBoss)。RPC 随着业务特别是互联网的发展，业务规模的扩大，模块化逐步成为一种趋势，此时解决模块之间远程调用的RPC框架应运而生。In the current server architecture, the evolution history of service-oriented architecture has gone through MVC architecture, RPC architecture, SOA organization, and microservice architecture. MVC architecture is mainly used to solve the problem of front-end and back-end, interface, control logic and business logic layering. The more popular technology stack is Spring+Struts+iBatis5(Hibernate)+Tomcat(JBoss). RPC With the development of business, especially the Internet, and the expansion of business scale, modularization has gradually become a trend. At this time, the RPC framework for solving remote calls between modules came into being.
RPC需要解决模块之间跨进程通信的问题，不同的团队开发不同的模块，通过一个RPC框架实现远程调用，RPC框架帮业务把通信细节给屏蔽掉，但是RPC框架也有自身的缺点。RPC本身不负责服务化，例如：服务的自动发现不管、服务的应用和发布不管、服务的运维和治理也不管。没有透明化、服务化的能力，对整个应用层的侵入还是比较深的。RPC needs to solve the problem of cross-process communication between modules. Different teams develop different modules and implement remote calls through an RPC framework. The RPC framework helps the business to shield the communication details, but the RPC framework also has its own shortcomings. RPC itself is not responsible for serviceization, such as automatic discovery of services, application and release of services, and operation, maintenance and governance of services. Without the ability of transparency and service, the invasion of the entire application layer is still relatively deep.
SOA服务化架构，企业级资产重用和异构系统间的集成对接，SOA架构的现状：在传统企业IT领域，主要是解决异构系统之间的互通和粗粒度的标准化(WebService)。互联网领域，提供一套高效支撑应用快速开发迭代的服务化架构。例如各个互联网公司自研或者开源的分布式服务框架。SOA service-based architecture, enterprise-level asset reuse and integration between heterogeneous systems, the status quo of SOA architecture: In the traditional enterprise IT field, it is mainly to solve the intercommunication and coarse-grained standardization (WebService) between heterogeneous systems. In the Internet field, it provides a set of service-oriented architecture that efficiently supports the rapid development and iteration of applications. For example, various Internet companies have developed or open source distributed service frameworks.
而本申请文件采用的微服务架构(MSA)是一种架构风格，旨在通过将功能分解到各个离散的服务中以实现对解决方案的解耦。它有如下几个特征：小，且只干一件事情。独立部署和生命周期管理。异构性：轻量级通信，RPC或者Restful。相比于传统的物理机部署，微服务可以由PaaS服务器实现微服务自动化部署和生命周期管理。除了部署和运维自动化，微服务云化之后还可以充分享受到更灵活的资源调度：云的弹性和敏捷。云的动态性和资源隔离。微服务架构符合智能运检管控服务器技术路线，与国网公司技术路线保持一致，可以与智能运检管控服务器实现无缝对接。The Microservice Architecture (MSA) adopted in this application is an architectural style that aims to decouple the solution by decomposing functions into discrete services. It has the following characteristics: small, and only do one thing. Independent deployment and lifecycle management. Heterogeneity: Lightweight communication, RPC or Restful. Compared with traditional physical machine deployment, microservices can be automatically deployed and life cycle managed by PaaS servers. In addition to automation of deployment and operation and maintenance, microservices can also fully enjoy more flexible resource scheduling after cloudification: the elasticity and agility of the cloud. The dynamism and resource isolation of the cloud. The micro-service architecture conforms to the technical route of the intelligent inspection and control server, which is consistent with the technical route of the State Grid Corporation, and can be seamlessly connected with the intelligent inspection and control server.
进一步地，所述步骤S1中的Docker服务器为基于LXC技术之上构建的Container容器引擎服务器。因为LXC轻量级的特点，其启动快，而且docker能够只加载每个container变化的部分，这样资源占用小，能够在单机环境下与KVM之类的虚拟化方案相比能够更加快速和占用更少资源。Further, the Docker server in the step S1 is a Container container engine server constructed based on the LXC technology. Because of the lightweight characteristics of LXC, its startup is fast, and docker can only load the changed part of each container, so that the resource consumption is small, and it can be faster and occupy more in a stand-alone environment than virtualization solutions such as KVM. less resources.
进一步地，所述步骤S1中的Docker服务器使用客户端-服务器架构模式，Docker客户端会与Docker守护进程进行通信，通过Docker守护进程会处理进程任务，并发布Docker容器。Further, the Docker server in the step S1 uses the client-server architecture mode, and the Docker client communicates with the Docker daemon, processes the process tasks through the Docker daemon, and publishes the Docker container.
进一步地，所述Docker客户端和守护进程运行在同一个系统上，通过Docker客户端去连接一个远程的Docker守护进程。实际上是docker的二进制程序，是主要的用户与Docker交互方式。它接收用户指令并且与背后的Docker守护进程通信，如此来回往复。Further, the Docker client and the daemon run on the same system, and a remote Docker daemon is connected through the Docker client. It is actually the docker binary and is the main way users interact with Docker. It receives user commands and communicates with the underlying Docker daemon, back and forth.
进一步地，所述Docker客户端和守护进程之间通过socket或者RESTful API进行通信。Further, the Docker client and the daemon process communicate through socket or RESTful API.
进一步地，所述步骤S2中的web门户网站内包括有应用开发者注册、登录、查看代码仓库的项目代码、指定工程一键部署功能，在注册登录后对正在提供服务的应用容器请求访问。Further, the web portal website in the step S2 includes the function of application developer registration, login, viewing the project code of the code warehouse, and one-key deployment of the designated project, and requests access to the application container that is providing the service after registration and login.
进一步地，所述步骤S3中构建器模块选择Jenkins来作为应用自动化构建的工具，利用Jenkins直接通过Web界面进行配置。Further, in the step S3, the builder module selects Jenkins as a tool for automated construction of the application, and uses Jenkins to configure directly through the web interface.
进一步地，所述所述步骤S4中的工程文件通过Dockerfile写入到Docker镜像中，在持续的自动化构建过程中容器重启、迁移和扩展通过业务层的HECD配置进行处理。Further, the project file in the described step S4 is written into the Docker image through the Dockerfile, and the container restart, migration and expansion are processed through the HECD configuration of the business layer in the continuous automated construction process.
综上所述，由于采用了上述技术方案，本发明的有益效果是：To sum up, due to the adoption of the above-mentioned technical solutions, the beneficial effects of the present invention are:
1.超特高压输电线路在线监测服务器架构方法，放弃了传统大规模的单块集成应用，改为细粒度、松耦合、可灵活组合的自治单元，成为云计算时代应用的主要构建方式微服务架构以其高度的弹性、灵活性和效率的巨大提升。1. The server architecture method for online monitoring of ultra-high voltage transmission lines has abandoned the traditional large-scale single-block integrated application and replaced it with a fine-grained, loosely coupled, and flexibly combined autonomous unit, which has become the main construction method for applications in the cloud computing era. Microservices Architecture with its high degree of elasticity, flexibility and a huge increase in efficiency.
2.本发明中通过将应用和服务分解成更小的、松散耦合的组件，它们可以更加容易升级和扩展，除了部署和运维自动化，微服务云化之后还可以充分享受到更灵活的资源调度：云的弹性和敏捷。云的动态性和资源隔离。微服务架构符合智能运检管控服务器技术路线，可以与智能运检管控服务器实现无缝对接。2. In the present invention, by decomposing applications and services into smaller and loosely coupled components, they can be upgraded and expanded more easily. In addition to automation of deployment and operation and maintenance, microservices can also fully enjoy more flexible resources after cloudification. Scheduling: The elasticity and agility of the cloud. The dynamism and resource isolation of the cloud. The micro-service architecture conforms to the technical route of the intelligent inspection and control server, and can be seamlessly connected with the intelligent inspection and control server.
附图说明Description of drawings
为了更清楚地说明本发明实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，应当理解，以下附图仅示出了本发明的某些实施例，因此不应被看作是对范围的限定，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他相关的附图，其中：In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings used in the embodiments. It should be understood that the following drawings only show some embodiments of the present invention, and therefore do not It should be regarded as a limitation of the scope. For those of ordinary skill in the art, other related drawings can also be obtained from these drawings without creative efforts, wherein:
图1是超特高压输电线路在线监测服务器架构方法Docker服务器架构结构图；Fig. 1 is the structure diagram of the Docker server architecture method of the online monitoring server for ultra-ultra-high voltage transmission lines;
图2是超特高压输电线路在线监测服务器架构方法流程示意图Fig. 2 is a schematic flow chart of the method for the online monitoring server architecture of ultra-ultra-high voltage transmission lines
具体实施方式Detailed ways
为了使本发明的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本发明，并不用于限定本发明，即所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。通常在此处附图中描述和示出的本发明实施例的组件可以以各种不同的配置来布置和设计。In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention, that is, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. The components of the embodiments of the invention generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations.
因此，以下对在附图中提供的本发明的实施例的详细描述并非旨在限制要求保护的本发明的范围，而是仅仅表示本发明的选定实施例。基于本发明的实施例，本领域技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都属于本发明保护的范围。Thus, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the invention as claimed, but is merely representative of selected embodiments of the invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present invention.
需要说明的是，术语“第一”和“第二”等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。It should be noted that relational terms such as the terms "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any relationship between these entities or operations. any such actual relationship or sequence exists. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.
超特高压输电线路在线监测服务器架构方法，所述方法包括如下步骤:S1：采用Docker 服务器为基础，将Docker服务器分为表现层、业务层和运行层；S2：在表现层内建立web 门户网站，用户可以对正在提供服务的应用容器请求访问，在门户网站查看和管理运行层的容器；S3：在业务层内建立自动化持续集成的构建器模块，通过构建器模块进行容器服务的负载均衡，并通过构建器模块生成工程文件；S4：在业务层内选用应用进行上线运行，从业务层得到可部署的工程文件后，将该文件与相应的应用环境进行镜像，生成镜像文件上传到服务器的镜像仓库进行存储，在将镜像文件通过表现层的web门户网站放出，供用户请求和访问；S5：超特高压输电线路监控装置采集的监控数据，通过外网服务器输入至交换系统内，通过交换系统导入Docker服务器内，用户通过表现层登录后，对监控数据进行处理。UHV transmission line online monitoring server architecture method, the method may further comprise the steps: S1: using Docker server as the basis, the Docker server is divided into presentation layer, business layer and operation layer; S2: in presentation layer, establish a web portal website , the user can request access to the application container that is providing the service, and view and manage the container of the running layer on the portal website; S3: establish a builder module for automatic continuous integration in the business layer, and use the builder module to perform load balancing of container services. And generate the project file through the builder module; S4: select the application in the business layer to run online, after obtaining the deployable project file from the business layer, mirror the file with the corresponding application environment, generate the image file and upload it to the server. The mirror warehouse is stored, and the mirror files are released through the web portal website of the presentation layer for users to request and access; S5: The monitoring data collected by the ultra-high voltage transmission line monitoring device is input into the exchange system through the external network server, and the exchange The system is imported into the Docker server, and after the user logs in through the presentation layer, the monitoring data is processed.
本申请文件中的步骤S1～S3采用了在Docker服务器中的现有操作，在步骤S4中设立的业务层中，其将可部署工程文件进行镜像后分成两部分操作，一部分进行存储备查，另一部分直接通过表现层的web门户网站放出，供用户请求和访问，而在步骤S5中，为了匹配目前Docker服务器尚未进入的超特高也输电线路领域，因为该领域现场监控情况复杂，不同地区、不同电网采用的服务器不同、运维不同，不能够统一进行管理，后端的服务器人员对现场监控的情况无法实时监控并作出反应，因此需要使用Docker服务器的全新架构方式进入，用单独的反馈处理流程和全新的服务器架构对监控数据进行处理。Steps S1 to S3 in this application document adopt the existing operations in the Docker server. In the business layer established in step S4, the deployable project file is mirrored and divided into two parts of operation, one part is stored for future reference, and the other part is stored for future reference. Part of it is directly released through the web portal website of the presentation layer for users to request and access. In step S5, in order to match the field of ultra-high power transmission lines that the Docker server has not yet entered, because the on-site monitoring situation in this field is complex, different regions, Different power grids use different servers and different operation and maintenance, which cannot be managed in a unified way. The back-end server personnel cannot monitor and respond to the on-site monitoring situation in real time. Therefore, it is necessary to use the new architecture of the Docker server to enter and use a separate feedback processing process. And a new server architecture to process monitoring data.
微服务架构的发展已过走了3年多的历程，从最初的概念到一些大企业的积极实践。尽管实际应用中各家设计的细节不尽相同，但它引领了一种全新的大规模软件服务器的设计样式。从行业的反应来看，微服务架构将在未来几年中更加深刻地影响软件行业和其它与“互联网+”相关行业。The development of the microservice architecture has gone through more than 3 years, from the initial concept to the active practice of some large enterprises. Although the details of each design in practical applications are different, it leads a new design style of large-scale software servers. Judging from the industry's response, the microservice architecture will have a more profound impact on the software industry and other "Internet +" related industries in the next few years.
下面结合实施例对本发明的特征和性能作进一步的详细描述。The features and performances of the present invention will be further described in detail below in conjunction with the embodiments.
实施例一Example 1
如图1～2所示，本发明较佳实施例提供的超特高压输电线路在线监测服务器架构方法，所述步骤S1中的Docker服务器为基于LXC技术之上构建的Container容器引擎服务器。因为LXC轻量级的特点，其启动快，而且docker能够只加载每个container变化的部分，这样资源占用小，能够在单机环境下与KVM之类的虚拟化方案相比能够更加快速和占用更少资源。As shown in FIGS. 1-2 , in the method for constructing an EHV transmission line online monitoring server provided by a preferred embodiment of the present invention, the Docker server in the step S1 is a Container engine server constructed based on the LXC technology. Because of the lightweight characteristics of LXC, its startup is fast, and docker can only load the changed part of each container, so that the resource consumption is small, and it can be faster and occupy more in a stand-alone environment than virtualization solutions such as KVM. less resources.
所述步骤S1中的Docker服务器使用客户端-服务器架构模式，Docker客户端会与Docker守护进程进行通信，通过Docker守护进程会处理进程任务，并发布Docker容器。Docker服务器整体上采用B/S架构，移动应用内网服务端采用分层技术和面向服务(SOA)的架构，提供RESTful风格的服务，通信协议采用HTTP，数据格式采用JSON。The Docker server in the step S1 uses a client-server architecture mode, and the Docker client communicates with the Docker daemon, processes the process tasks through the Docker daemon, and publishes the Docker container. The Docker server adopts B/S architecture as a whole, and the mobile application intranet server adopts layered technology and service-oriented (SOA) architecture to provide RESTful services. The communication protocol adopts HTTP and the data format adopts JSON.
所述Docker客户端和守护进程运行在同一个系统上，通过Docker客户端去连接一个远程的Docker守护进程。实际上是docker的二进制程序，是主要的用户与Docker交互方式。它接收用户指令并且与背后的Docker守护进程通信，如此来回往复。The Docker client and the daemon run on the same system, and a remote Docker daemon is connected through the Docker client. It is actually the docker binary and is the main way users interact with Docker. It receives user commands and communicates with the underlying Docker daemon, back and forth.
所述Docker客户端和守护进程之间通过socket或者RESTful API进行通信。所述步骤S2中的web门户网站内包括有应用开发者注册、登录、查看代码仓库的项目代码、指定工程一键部署功能，在注册登录后对正在提供服务的应用容器请求访问。The Docker client and the daemon process communicate through socket or RESTful API. The web portal in the step S2 includes the functions of application developer registration, login, viewing the project code of the code warehouse, and one-key deployment of the designated project, and requests access to the application container that is providing the service after registration and login.
所述步骤S3中构建器模块选择Jenkins来作为应用自动化构建的工具，利用Jenkins 直接通过Web界面进行配置。所述所述步骤S4中的工程文件通过Dockerfile写入到 Docker镜像中，在持续的自动化构建过程中容器重启、迁移和扩展通过业务层的HECD配置进行处理。In the step S3, the builder module selects Jenkins as a tool for automatic construction of the application, and uses Jenkins to configure directly through the web interface. The project file in the described step S4 is written into the Docker image through the Dockerfile, and in the continuous automated construction process, the container restart, migration and expansion are processed through the HECD configuration of the business layer.
表现层：用户与服务器的交互过程以及代码托管服务器的授权通过表现层来完成。为提升应用开发者的友好体检，服务器在表现层设计了一套Web门户网站，帮助开发者完成代码管理和选定应用的一键部署工作。用户门户模块主要需求包括应用开发者注册、登录、查看代码仓库的项目代码、指定工程一键部署等功能。用户可以对正在提供服务的应用容器请求访问。除此之外，开发者可以在门户网站查看和管理运行层的容器。考虑到开发者在使用服务器前大多数都已经用代码托管服务器来管理自己的项目，服务器给开发者提供代码托管仓库如GitLab、GitHub的接入功能。服务器使用OAUTH与代码托管服务器进行对接，OAUTH协议为用户资源的授权提供了一个安全的、开放而又简易的标准。OAUTH 的授权不会使第三方触及到用户的账号信息，无需使用用户的用户名与密码就可以申请获得该用户资源11的授权，因此OAUTH是安全的。通过OAUTH授权，服务器获得权限访问代码托管服务器中的用户项目代码等资源，再通过API调用，将用户的项目Pull到服务器中进行接下来的构建发布等操作。Presentation layer: The interaction process between the user and the server and the authorization of the code hosting server are completed through the presentation layer. In order to improve the friendly physical examination of application developers, the server has designed a set of web portals at the presentation layer to help developers complete code management and one-click deployment of selected applications. The main requirements of the user portal module include application developer registration, login, viewing the project code of the code repository, and one-click deployment of specified projects. Users can request access to the application container that is providing the service. In addition, developers can view and manage containers at the runtime layer in the portal. Considering that most developers have used the code hosting server to manage their projects before using the server, the server provides developers with access to code hosting repositories such as GitLab and GitHub. The server uses OAUTH to interface with the code hosting server. The OAUTH protocol provides a secure, open and simple standard for user resource authorization. The authorization of OAUTH will not allow a third party to access the user's account information, and the authorization of the user resource 11 can be applied for without using the user's username and password, so OAUTH is safe. Through OAUTH authorization, the server obtains permission to access the user's project code and other resources in the code hosting server, and then uses the API call to pull the user's project to the server for subsequent construction and release operations.
业务层：业务层是服务器的核心部分，主要负责应用自动化持续构建、容器服务的负载均衡和服务发现模块。在自动化持续集成的构建器模块中，服务器选择Jenkins来作为应用自动化构建的工具。Jenkins是基于Java开发的一种持续集成工具，用于监控持续重复的工作，功能包括持续的软件版本发布或测试项目，监控外部调用执行的工作。Jenkins易于安装，不需要数据库的支持，直接通过Web界面进行配置，集成了RSS/Email的通知机制，支持分布式构建，具有丰富的插件，这些都是Jenkins相比其他持续集成服务器的优势所在。在我们的开发者服务服务器中，新建Jenkins项目并配置后，Jenkins会轮询版本控制的存储库，当发现版本库发生变更后，通过预先定义的Ant脚本或Maven对用户的源码进行编译构建，Jenkins会根据项目需求将构建的任务分配到Slave端。然而对开发者而言，创建和完善Jenkins的项目配置都是不可见的，Jenkins提供了Jenkins-cli命令行操作，服务器直接调用命令行进行创建和配置操作，真正让开发者感觉到一键进行自动化持续集成构建的体验。服务器研究使用Haproxy+Etcd+Confd组合打造基于Docker的负载均衡和服务发现功能，这套方案整合了多种开源的软件，形成一个有机的整体，互相联系、互相作用。Etcd是一个高可用的Key/Value存储系统，主要用于分享配置和服务发现。Confd 是一个轻量级的配置管理工具。通过查询Etcd，结合配置模板引擎，保持本地配置最新，同时具备定期探测机制，配置变更自动Reload。Haproxy提供高可用性、负载均衡等解决方案，是基于TCP和HTTP应用的代理。Business layer: The business layer is the core part of the server and is mainly responsible for the continuous construction of application automation, load balancing of container services, and service discovery modules. In the builder module for automating continuous integration, the server chooses Jenkins as the tool to automate the build of the application. Jenkins is a continuous integration tool developed based on Java. It is used to monitor continuous and repetitive work. Its functions include continuous software version release or test projects, and monitoring of work performed by external calls. Jenkins is easy to install, does not require database support, can be configured directly through the web interface, integrates RSS/Email notification mechanisms, supports distributed builds, and has a wealth of plugins. These are the advantages of Jenkins compared to other continuous integration servers. In our developer service server, after a new Jenkins project is created and configured, Jenkins will poll the version-controlled repository. When the repository is found to have changed, it will compile and build the user's source code through a predefined Ant script or Maven. Jenkins will assign the build tasks to the Slaves according to the project requirements. However, for developers, it is invisible to create and improve the project configuration of Jenkins. Jenkins provides Jenkins-cli command line operations, and the server directly calls the command line to create and configure operations, which really makes developers feel one-click operation. The experience of automating continuous integration builds. Server research uses Haproxy+Etcd+Confd combination to create Docker-based load balancing and service discovery functions. This solution integrates a variety of open source software to form an organic whole, which is interconnected and interacts with each other. Etcd is a highly available Key/Value storage system, mainly used for sharing configuration and service discovery. Confd is a lightweight configuration management tool. By querying Etcd, combined with the configuration template engine, the local configuration is kept up-to-date, and at the same time, it has a regular detection mechanism, and configuration changes are automatically Reloaded. Haproxy provides high availability, load balancing and other solutions, and is a proxy for TCP and HTTP applications.
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明的保护范围，任何熟悉本领域的技术人员在本发明的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本发明的保护范围之内。The above are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made by any person skilled in the art within the spirit and principles of the present invention, etc. , should be included within the protection scope of the present invention.
Claims (8)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019004.XACN111277431A (en) | 2020-01-08 | 2020-01-08 | Server Architecture Method for Online Monitoring of Ultra-UHV Transmission Lines |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010019004.XACN111277431A (en) | 2020-01-08 | 2020-01-08 | Server Architecture Method for Online Monitoring of Ultra-UHV Transmission Lines |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111277431Atrue CN111277431A (en) | 2020-06-12 |
Family
ID=71000109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010019004.XAPendingCN111277431A (en) | 2020-01-08 | 2020-01-08 | Server Architecture Method for Online Monitoring of Ultra-UHV Transmission Lines |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111277431A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112765678A (en)* | 2020-12-30 | 2021-05-07 | 南京南瑞继保工程技术有限公司 | Electric power market security check method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544561A (en)* | 2013-10-10 | 2014-01-29 | 广东电网公司电力科学研究院 | Method for realizing dynamic display of power transmission circuits, method for realizing operational maintenance of power transmission circuits and system for realizing management of power transmission circuits |
| CN105119378A (en)* | 2015-09-09 | 2015-12-02 | 国网浙江省电力公司湖州供电公司 | Low-voltage power distribution line on-line monitoring system |
| EP3282356A1 (en)* | 2016-08-11 | 2018-02-14 | Entit Software LLC | Container monitoring configuration deployment |
| CN108616419A (en)* | 2018-03-30 | 2018-10-02 | 武汉虹旭信息技术有限责任公司 | A kind of packet capture analysis system and its method based on Docker |
- 2020
- 2020-01-08CNCN202010019004.XApatent/CN111277431A/enactivePending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544561A (en)* | 2013-10-10 | 2014-01-29 | 广东电网公司电力科学研究院 | Method for realizing dynamic display of power transmission circuits, method for realizing operational maintenance of power transmission circuits and system for realizing management of power transmission circuits |
| CN105119378A (en)* | 2015-09-09 | 2015-12-02 | 国网浙江省电力公司湖州供电公司 | Low-voltage power distribution line on-line monitoring system |
| EP3282356A1 (en)* | 2016-08-11 | 2018-02-14 | Entit Software LLC | Container monitoring configuration deployment |
| CN108616419A (en)* | 2018-03-30 | 2018-10-02 | 武汉虹旭信息技术有限责任公司 | A kind of packet capture analysis system and its method based on Docker |
Non-Patent Citations (3)
| Title |
|---|
| 刘亮等: "一种光伏电站在线监测解决方案", 《电气应用》* |
| 刘淑平,纪鑫,胡强新,贾旭策,杨俊伟: ""云架构下的电网GIS平台容器化管理技术研究"", 《电力信息与通信技术》* |
| 刘琳羽等: "一种基于Docker的开发者服务平台设计", 《科研信息化技术与应用》* |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112765678A (en)* | 2020-12-30 | 2021-05-07 | 南京南瑞继保工程技术有限公司 | Electric power market security check method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20240220214A1 (en) | System and method for workflow application programming interfaces (apis) | |
| US10761903B2 (en) | Management instrumentation and discovery (MID) server support for executing automated flows within a cloud based system | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| Rattanapoka et al. | An MQTT-based IoT cloud platform with flow design by Node-RED | |
| US12093705B2 (en) | System and method for simple object access protocol (SOAP) interface creation | |
| Xiao et al. | RETRACTED ARTICLE: Cloud platform wireless sensor network detection system based on data sharing | |
| Jaju | Maximizing DevOps Scalability in Complex Software Systems: Maximizing DevOps Scalability in Complex Software Systems | |
| CN111277431A (en) | Server Architecture Method for Online Monitoring of Ultra-UHV Transmission Lines | |
| Prist et al. | Cyber-physical manufacturing systems: An architecture for sensor integration, production line simulation and cloud services | |
| Vault | Microsoft Azure | |
| Rossi Tisbeni et al. | A Big Data Platform for heterogeneous data collection and analysis in large-scale data centres | |
| CN117311804A (en) | Application migration method, device, electronic equipment and computer readable medium | |
| US12353864B2 (en) | Common platform for implementing RPA services on customer premises | |
| US10397072B2 (en) | Systems, devices, and methods for incident management interactions | |
| CN115774573A (en) | Application integration method and device, electronic equipment and storage medium | |
| CN114911590A (en) | Task scheduling method and device, computer equipment and readable storage medium | |
| CN108470047B (en) | Remote platform monitoring system based on Internet of Things | |
| Zhang et al. | Design of M2M Platform Based on J2EE and SOA | |
| Katreddy | Modernizing Middleware for Enhanced Cloud Compatibility and Performance | |
| Mikhailovich et al. | Methods of creating fault-tolerant geographically distributed systems | |
| KR102637540B1 (en) | System for configuring cloud computing environment and automating opertation based on standard stack and intelligent operator | |
| US20250265103A1 (en) | Systems and methods for legacy application migration and deployment automation | |
| US12217063B2 (en) | Preconfigured robots for robotic process automation | |
| CN116032745B (en) | Automatic configuration method and device of hadoop cluster | |
| US20220191167A1 (en) | Organizational modelling for routing rpa related services of an rpa cloud suite |
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 | ||
| RJ01 | Rejection of invention patent application after publication | Application publication date:20200612 | |
| RJ01 | Rejection of invention patent application after publication |