CN110413484B - Cluster monitoring method supporting heterogeneous platform - Google Patents
Cluster monitoring method supporting heterogeneous platform Download PDFInfo
- Publication number
- CN110413484B CN110413484B CN201910712545.8A CN201910712545A CN110413484B CN 110413484 B CN110413484 B CN 110413484B CN 201910712545 A CN201910712545 A CN 201910712545A CN 110413484 B CN110413484 B CN 110413484B
- Authority
- CN
- China
- Prior art keywords
- blade
- monitoring
- xml
- project
- interface
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
Abstract
The invention discloses a cluster monitoring method supporting a heterogeneous platform, which adopts a JAVA WEB development framework SSM to respectively establish computing blade monitoring, switching blade monitoring, user management monitoring and interface blade monitoring; writing http api or http addresses which are expected to be introduced into other monitoring frames into corresponding configuration files, and realizing integration of other open-source monitoring items and http api into the frames; shielding the bottom level detail difference of different embedded platforms aiming at the specific embedded platforms, and realizing seamless fusion and butt joint with the system; port state monitoring, port remote control, route display, addition, deletion, port state statistics and chip running state monitoring of a switch board are realized aiming at a switch blade; and port control, self-test control, port state display, state monitoring and hardware state monitoring are realized aiming at the interface blade. The invention provides a safe and reliable user access and management mechanism.
Description
Technical Field
The invention belongs to the technical field of internet, and particularly relates to a cluster monitoring method supporting a heterogeneous platform.
Background
The open source monitoring project, ganglia, nagios, zabbix, which is common on the market today.
Ganglia is an open source monitoring project designed to measure nodes in thousands of records, each computer running a daemon that collects and sends data that will be collected from the operating system and the designated host, the host that receives all the measurement data can display the data and pass a reduced form of the data into the hierarchy just because of the hierarchy, making it well extensible.
nagios is a free network monitoring tool for opening sources, has strong functions and flexibility, can effectively monitor the host states of windows, linux and unix, sends out mails or short messages to alarm to notify website operation and maintenance personnel at the first time when the system or service state is abnormal, and sends out normal mails or short messages to notify the website operation and maintenance personnel after the state is recovered.
Zabbix is a very powerful monitoring system, and the official description thereof is that Zabbix is enterprise-level software designed to monitor the availability and performance of IT facilities, and the Zabbix is an open source monitoring system capable of being built up quickly, for small companies wanting to be available quickly, the item of Zabbix can meet the requirement, through simple configuration, a set of alarm system with complete functions can be built up in a very short time, and for large companies, zabbix can also be supported well, self-defined item can be set, and a report can be generated automatically, and the Zabbix is formed by integrating an API and other systems.
From the introduction of the open source monitoring software, it can be seen that the three open source monitoring software have respective characteristics, ganglia has the advantages of collecting indexes of a super large cluster and performing index expansion, nagios has the advantages of being a platform for collecting and expanding performance indexes, and is strong in expansibility, and zabbix has the advantages of perfecting a strong early warning development mechanism and the like. However, the open-source framework architecture is directed at a large-scale cluster system, has more obvious advantages when the number of clusters is large, has general applicability to a small-scale flexibly configured cluster system, is suitable for a non-embedded operating system platform for performance monitoring indexes collected by the framework, and has no relation to the performance index collection of an embedded operating system.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a cluster monitoring method supporting a heterogeneous platform, aiming at the defects in the prior art, and solve the problems in the prior art that the applicability is poor and the method is not suitable for an embedded system for a miniaturized cluster system.
The invention adopts the following technical scheme:
a cluster monitoring method supporting a heterogeneous platform adopts JAVAWEB development framework SSM to respectively establish computing blade monitoring, switching blade monitoring, user management monitoring and interface blade monitoring, which is beneficial to rapid expansion and cutting to realize layered programming; writing http api or http addresses which are expected to be introduced into other monitoring frames into corresponding configuration files, carrying out java background processing, and transmitting to a foreground page through a springmv frame, so as to realize integration of other open source monitoring items and http api into the frames; defining a development interface of the embedded platform through a java interface technology, shielding bottom layer detail differences of different embedded platforms aiming at specific embedded platforms, and realizing seamless fusion and butt joint with a system; port state monitoring, port remote control, route display, addition, deletion, port state statistics and chip running state monitoring of a switch board are realized aiming at a switch blade; and port control, self-test control, port state display, state monitoring and hardware state monitoring are realized aiming at the interface blade.
Specifically, the blade monitoring calculation specifically includes: the method comprises the following steps of using an SSM framework to build a WEB server development framework, obtaining calculation blade information through a LINUX local command, an open source jar packet and a Linux tool, and finally displaying through a Web page, wherein the displaying comprises the following steps: obtaining and displaying memory information in the computing blade; calculating static information display of the blade, wherein the static information display comprises CPU (central processing unit), memory, magnetic disks, an operating system, network MAC (media access control) and IP (Internet protocol) information; controlling processes and threads; and monitoring the real-time states of the hardware of the gigabit network, the RapidIO, the hard disk, the CPU and the memory.
Further, the concrete implementation steps are as follows:
s101, downloading and installing JDK tools according to the used Linux system, and then respectively downloading and installing Eclipse development tools and Maven development tools
S102, creating a Maven project in an Eclipse development tool;
s103, setting a directory structure and a name of the project according to the project requirement;
s104, integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project;
s105, compiling a corresponding pom.xml file, adding a jar package required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and automatically downloading the jar package configured in the pom.xml file on the network by project loading;
s106, compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis;
s107, compiling a configuration file SpringMVC-configuration.xml integrating springMVC and Spring, and completing the starting function configuration of an automatic scanning controller, a view mode and an annotation;
s108, writing a configuration file application context of Spring, and introducing and integrating objects of a control layer, a service layer and a persistence layer;
s109, compiling a web.xml configuration file, introducing the whole Maven project into the configuration file for integration, and building an SSM framework;
and S110, acquiring the information of the calculation blade through the SSM framework by using the LINUX local command, the open source jar packet and the Linux tool, and displaying the information through a front-end Web page to realize the monitoring of the calculation blade.
Furthermore, in step S106, the Mybatis-config.xml configuration file is used to set mapping rules of object attributes and database storage data, the data mapping interface defined in the class acquisition class defined by the specified directory is scanned, the applicationContext-mybatis.xml configuration file is used to manage the management of Mybatis data source configuration transaction, the creation of sqlSessionFactory and the creation of data mapping interface Mapper by Spring, and sqlSession and the corresponding data mapping interface Mapper need to be acquired in the Mybatis configuration file Mybatis-config.xml, and the mapping is injected by Spring.
Specifically, the monitoring of the exchange blade specifically includes: the method comprises the following steps that a computing blade is connected with an exchange blade through an SSH protocol, after the connection is established, command information of the exchange blade is sent to the exchange blade through the computing blade, after the exchange blade receives a command, the command is executed, an execution result is returned to the computing blade, and finally the command is displayed on the computing blade through a Web page, wherein the displaying comprises the following steps: acquiring and displaying port information in the exchange blade; monitoring the health state of a switching blade gigabit network, a RapidIO chip and a switching blade master control processor; enabling and closing ports of a switching blade gigabit network, a gigabit network and RapidIO; and monitoring the real-time state of each port of the switching blade gigabit network, the gigabit network and the RapidIO.
Further, the concrete implementation steps are as follows:
s201, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding a jar package required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and loading the jar package configured in the pom.xml file automatically on the network by the project; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml is written and integrated with a configuration file SpringMVC-configuration, and the starting function configuration of an automatic scanning controller, a view mode and an annotation is completed; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s202, after the SSM framework is successfully built, the SSH service computing blade and the exchange blade are used for building connection, and sending command information of the exchange blade to the exchange blade, the exchange blade analyzes the command and then transmits the command back to the computing blade, and the computing blade analyzes the returned information and finally displays the information through a Web page.
Further, the user management and monitoring specifically includes: defining users who have legal access and use authority to the system and cluster resources in user management monitoring, viewing a user list, adding and deleting the users and changing the user authority, writing all attributes of the users into a database, and finally displaying results in the database on a Web page of a client, wherein the display comprises the addition of the users, the deletion, the display or the authority management of user groups.
Further, the concrete implementation steps are as follows:
s301, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding a jar package required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and loading the jar package configured in the pom.xml file automatically on the network by the project; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml is written and integrated with a configuration file SpringMVC-configuration, and the starting function configuration of an automatic scanning controller, a view mode and an annotation is completed; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s302, installing a MySQL database, and creating a corresponding table for each attribute of the user in the database;
s303, adding an Apache Shuro installation authentication jar package into the pom.xml file to realize that different users have different access and use authorities;
s304, writing application context-shred.xml, integrating the shred and Spring, and configuring a security manager and an encryption manager of the shred;
s305, sending a request through a front-end Web page, realizing access to a database through an SSM framework, and finally realizing addition and deletion of user management and monitoring of user authority management functions.
Specifically, the monitoring of the interface blade specifically includes: the method comprises the following steps that a computing blade realizes connection with an interface blade by using a TELNET protocol, the interface blade sends interface blade command information to the interface blade, the interface blade executes a command and returns an execution result to the computing blade after receiving the command information, and finally the execution result is displayed on the computing blade through a Web page, wherein the method comprises the following steps: acquiring the maximum optical fiber number in the interface blade; monitoring static information of the interface blade; monitoring the state of the interface blade; interface blade health status; and monitoring the state of the gigabit network and the gigabit network.
Further, the concrete implementation steps are as follows:
s401, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding jar packages required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and automatically downloading jar packages configured in the pom.xml file on a network by the project loading; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml is written and integrated with a configuration file SpringMVC-configuration, and the starting function configuration of an automatic scanning controller, a view mode and an annotation is completed; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s402, after the SSM framework is successfully built, the computing blade uses TELNET service to establish connection with the interface blade, and sends interface blade command information to the interface blade, the interface blade analyzes and executes the command, an execution result is transmitted back to the computing blade, and the computing blade analyzes the returned information and displays the information through a Web page.
Compared with the prior art, the invention has at least the following beneficial effects:
the cluster monitoring method supporting the heterogeneous platform adopts the SSM framework of layered processing, greatly improves the robustness and the expandability of a program, and integrates a corresponding communication protocol for the heterogeneous platform to realize the shielding and the seamless butt joint of the heterogeneous platform.
Further, a system with a desktop is used in the computing blade, so that the visualization operation can be conveniently carried out, and therefore, the invention is deployed on the computing blade. And local and other computing blade information is obtained through a LINUX local command, an open source jar packet and a Linux tool, and is displayed through WEB.
Furthermore, the association of the object, the storage process and the SQL statement is realized by using each XML file, and the Spring is enabled to conveniently integrate the Spring MVC and the Mybases, so that related codes are simplified, and the expandability of the program is improved.
Furthermore, for the architecture and the system of the exchange blade, the SSH service is used for shielding platform difference, and information obtained from the exchange blade is displayed on the computing blade through WEB, so that visual operation is facilitated.
Furthermore, the safe access to the cluster system is realized through the user management module, and the user access can be managed quickly and conveniently according to actual requirements.
Further, aiming at the architecture and the system of the interface blade, the TELNET service is used for shielding platform difference, information obtained from the interface blade is displayed on the computing blade through WEB, and visual operation is convenient to carry out.
In summary, the invention can achieve rapid deployment, convenient visual operation and good expandability by using the SSM framework; aiming at the embedded platform, the adaptability to a heterogeneous platform is improved by integrating SSH and TELNET services; through the user management module, a safe and reliable user access and management mechanism is provided.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
FIG. 1 is a structural framework diagram of a cluster system according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an implementation of the monitoring method supporting heterogeneous clusters according to the embodiment of the present invention.
Detailed Description
Referring to fig. 1 and fig. 2, the cluster monitoring method supporting heterogeneous platforms according to the present invention employs a JAVA WEB development framework SSM, which includes compute blade monitoring, switch blade monitoring, user management monitoring, and interface blade monitoring, and is beneficial to performing fast expansion and clipping, implementing layered programming (including controller layer, service layer, persistence layer, object class layer, foreground display layer), and facilitating flexible configuration;
the http api or http address which is expected to be introduced into other monitoring frames is written into a corresponding configuration file, and is transmitted to a foreground page through a springMVC frame after being processed by a java background, so that other open source monitoring items and the http api are integrated into the frame;
the development (connection, login, sending and receiving) interfaces of the embedded platforms are defined through the interface technology in java, and the interfaces are realized aiming at the specific embedded platforms, so that the shielding of the bottom level detail difference of different embedded platforms can be realized, and the seamless fusion and butt joint with the system can be realized;
port state monitoring, port remote control, route display, addition, deletion, port state statistics and chip running state of the switch board are realized aiming at the switch blade; the method realizes port control, self-test control, port state display, state monitoring and hardware state monitoring aiming at the interface blade. The method comprises the following specific steps:
s1, implementation of monitoring of computing blade
The method comprises the following steps that a computation blade is monitored, a WEB server development framework is built by using an SSM framework, computation blade information is obtained through a LINUX local command, an open source jar packet and a Linux tool, and finally displayed through a Web page, and the method is concretely implemented as follows:
s101, downloading and installing a proper JDK tool according to a used Linux system, and respectively downloading and installing a proper Eclipse development tool and a proper Maven development tool
S102, creating a Maven project in an Eclipse development tool;
s103, reasonably setting a directory structure and a name of the project according to the project requirement;
s104, integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project;
s105, compiling a corresponding pom.xml file according to the functional requirements of the project, adding jar packages required by the project into the pom.xml file, and introducing the pom.xml file into the Maven project, so that the jar packages configured in the pom.xml file can be automatically downloaded on the network when the project is loaded;
s106, because the database is accessed in the project, the integration of Spring and Mybatis is carried out;
integrating Spring and mybasic to write two configuration files, mybasic-configuration.xml and applicationContext-mybasic.xml, wherein the main function of the mybasic-configuration.xml configuration file is to set object attributes and mapping rules of database storage data, and a data mapping interface defined in a class is obtained by scanning the class defined by a specified directory, and the main function of the applicationContext-mybasic.xml configuration file is to submit management of mybasic data source configuration transaction, creation of sqlSessionsFactory and creation of a data mapping interface Mapper to Spring management, so that sqlSessision and a corresponding data mapping interface Mapper are required to be obtained from the mybasic-configuration.xml configuration file of mybasic, and the sqlSessionsion and the corresponding data mapping interface Mapper are injected through Spring;
s107, compiling a configuration file SpringMVC-config.xml for integrating springMVC and Spring;
from the foregoing, it can be seen that the Spring MVC framework is a realization of Spring based on an MVC design pattern, and therefore, a configuration file, spring MVC-configuration.xml, of Spring MVC needs to be configured separately, and the configuration file mainly completes configuration of functions such as an auto-scan controller, a view pattern, and annotation starting;
s108, writing a configuration file application context of Spring, wherein the configuration file is used for introducing and integrating objects of a control layer, a service layer and a persistence layer, and the objects are conveniently used in each layer in a reference mode;
s109, compiling a web.xml configuration file, where the configuration file has a function of introducing all the aforementioned configuration files for the whole Maven project, and integrating all the configuration files mentioned in the foregoing step in the configuration file to build an SSM framework;
s110, after the SSM framework is successfully built, obtaining the information of the computing blade through the SSM framework by using a LINUX local command, an open source jar packet and a Linux tool, and finally displaying the information through a front-end Web page.
Taking the acquisition of the memory information of the computing blade as an example to realize how to utilize the SSM framework to complete the process of acquiring the memory information of the computing blade and displaying the memory information through the Web page, the specific steps are as follows:
1. compiling a Web page memInfo.jsp, defining a URL (uniform resource locator)/jsp/memorylist/", namely a request path, in the memInfo.jsp, and capturing the request by a Spring front-end controller in an SSM (service support manager) framework and automatically forwarding the request to a control layer;
2. class, a control layer class for calculating blade information is written, and the implementation functions of the class are as follows:
firstly, receiving a request from a front-end Web page, and determining a control layer processing function in a control layer for specifically processing the request by analyzing a URL in the request;
secondly, after finding a control layer processing function corresponding to the request, calling a corresponding service layer program to process the request;
thirdly, receiving a processing result returned by the service layer and returning the processing result to the front-end Web page for displaying;
according to the implementation process, the method is specifically implemented as follows:
firstly, defining a member function in the class, and adding @ RequestMapping "/jsp/memorylist/" to the upper line defined by the member function, so that the member function is specially responsible for receiving an acquisition request of memory information from a memInfo.
Secondly, acquiring memory information in the member function by calling the corresponding service layer member function;
and thirdly, obtaining a return result of the corresponding member function of the service layer, and returning the result to a front-end Web page, wherein the Web displaying the memory information is also a URL, and the URL is/jsp/memorylist/' as the requested URL.
3. Compiling a service layer class CalcnodeService class for calculating blade information, wherein the class is responsible for receiving calls from a control layer, realizing specific service logic and returning results to the control layer; for the specific implementation of the acquisition of the memory information, a member function is defined in the class, and the member function is implemented through a LINUX local command, an open source jar packet and a Linux tool.
The above steps are the acquisition and display of memory information in the computing blade, and other computing blade information to be acquired mainly has the following contents:
(1) Calculating static information display of the blade, including information such as a CPU, a memory, a disk, an operating system, a network MAC, an IP and the like;
(2) Controlling processes and threads;
(3) Monitoring the real-time state of hardware such as a gigabit network, rapidIO, a hard disk, a CPU, an internal memory and the like;
the steps of acquiring and displaying the information of the computing blade and the memory information of the computing blade are the same.
S2, implementation of monitoring of exchange blade
The method comprises the following steps that a computing blade is connected with an exchange blade through an SSH protocol, after the connection is established, command information of the exchange blade is sent to the exchange blade through the computing blade, after the exchange blade receives a command, the command is executed, an execution result is returned to the computing blade, and finally the command is displayed on the computing blade through a Web page, and the specific implementation steps are as follows:
s201, repeating the step S101 to the step S109 in the blade calculation;
by utilizing the SSM frame built in the monitoring of the computing blade, the system does not need to be built again;
s202, after an SSM frame is successfully built, connection is built between a computing blade and an exchange blade through SSH service, and command information of the exchange blade is sent to the exchange blade, the exchange blade analyzes the command and then returns the command to the computing blade, and the computing blade analyzes the returned information and finally displays the information through a Web page;
taking the acquisition of the port information of the exchange blade as an example, how to acquire the acquisition of the port information in the exchange blade by using the SSM framework and display the port information through a Web page is shown, and the specific implementation steps are as follows:
1. compiling Web page swportInfo.jsp, defining a URL "/swnode/getPortList/", and a Spring front-end controller in an SSM framework can capture the request and forward the request to a control layer;
2. class, which implements three functions:
firstly, receiving a request from a front-end Web page, and determining a control layer processing function in a control layer for specifically receiving the request by analyzing a URL in the request;
secondly, after receiving the request, calling a corresponding service layer program to process the request according to the URL in the request;
thirdly, receiving a result returned by the service layer and returning the result to the Web page for displaying;
according to the implementation process, the method is specifically implemented as follows:
firstly, defining a member function in the class, and adding @ RequestMapping ("/swnode/getPortList/") in front of the position of the member function, so that the member function is specially responsible for receiving a switching blade port information acquisition request from a swortInfo.jsp page;
secondly, acquiring the information of the exchange blade in the member function by calling the corresponding member function in the service layer class;
and thirdly, acquiring a return result of a corresponding member function of the service layer, returning the result to a corresponding Web page, identifying the Web page responsible for displaying the result by using a URL, and in the example of acquiring the switching blade port information, judging whether the URL of the page responsible for receiving the return result is "/swnode/getPortList/".
S203, compiling a class SwnodeService class of the exchange blade information service layer, wherein the class is responsible for receiving calls from the control layer, realizing specific service logic and returning results to the control layer; for the acquisition of the port information of the exchange blade, firstly defining a member function in the class, realizing the establishment of the connection between the calculation blade and the exchange blade by using SSH connection, establishing a corresponding SSH session, sending a command to the exchange blade through the session, waiting for receiving the information returned by the SSH session after the exchange blade executes the command, analyzing the state of the port from the returned information, and returning the result to the control layer;
the above steps are the acquisition and display of port information in the exchange blade, and other exchange blade information to be acquired mainly has the following contents:
(1) Monitoring the health state of a switching blade gigabit network, a RapidIO chip and a switching blade master control processor;
(2) Enabling and closing ports of a switching blade gigabit network, a gigabit network and RapidIO;
(3) Monitoring the real-time state of each port of a ten-gigabit network, a gigabit network and RapidIO of the switching blade;
the steps of acquiring and displaying other information of the switch blade and acquiring port information of the switch blade are the same.
S3, implementing user management monitoring;
the user management and monitoring defines users who have legal access and use authority to the system and cluster resources, realizes viewing of user lists, addition and deletion of users, modification of user authority and the like, writes various attributes of the users into a database, and finally displays results in the database on a Web page of a client, and the specific implementation steps are as follows:
s301, repeating the operation steps from the step S101 to the step S109 in the blade calculation;
by utilizing the SSM frame built in the monitoring of the computing blade, the system does not need to be built again;
s302, in order to store each attribute value of a user in a database, a corresponding table needs to be created in the database for each attribute of the user, such as a user name table, a user group name table, a user name corresponding authority table and the like, so that the database needs to be installed, and the selected database is a MySQL database;
s303, because different users have different access and use rights, the Apache horio security authentication jar package is used in the project to realize the function, so the Apache horio installation authentication jar package needs to be added into the pom.xml file;
and S304, writing application context-shred.
S305, after the SSM framework is successfully built, a request is sent through a front-end Web page, the database is accessed through the SSM framework, and functions of adding and deleting user management, user authority management and the like are finally achieved.
The whole process is shown below by taking the addition of the user as an example, and the specific implementation steps are as follows:
1. compiling Web page createeser. Jsp, defining a URL "/jsp/user/create/", namely a request path, in the userinfo. Jsp, and capturing the request by a Spring front-end controller in an SSM framework and forwarding the request to a control layer;
2. class, defining the owned attributes of a user, such as a user name, a user group to which the user belongs, a user login password, a user unique ID and the like, automatically generating methods for setting the attributes and methods for obtaining the attributes through an SSM frame, such as setting a user name void setUsername (StringUsername) and obtaining a user name StringgetUsername (), and operating the attribute value of the object of the user through the methods to realize user authority management;
3. class is written as a control layer class for user management, which implements three functions:
firstly, receiving a request from a front-end Web page, and determining a control layer processing function specifically receiving the request in a control layer by analyzing a URL in the request;
secondly, calling a corresponding service layer program to process the request;
thirdly, receiving a processing result returned by the service layer and returning the processing result to the Web page for displaying;
according to the implementation process, the method is specifically implemented as follows:
first, defining a member function in the class, and adding @ RequestMapping ("/jsp/user/transaction/") to the line above the definition of the member function, so that the member function is specifically responsible for receiving a request for user name addition from createmoser. Jsp;
secondly, jumping to a Web page with URL of "/jsp/user/jusercreate/" userinfo. Jsp in the member function, creating a user name, an access authority corresponding to the user name and other user attributes in the Web page, and defining a URL "/jsp/user/insert/", namely a request path, after all the attributes of a new user are filled, wherein a Spring front-end controller in the SSM framework captures the request and forwards the request to a control layer;
4. class defines a member function in the control layer class, and adds @ RequestMapping ("/jsp/user/insert/") in front of the position of the member function to call the member function defined in the service layer;
5. compiling a user management service class, namely user service class, which is responsible for receiving calls from a control layer, realizing specific service logic and returning execution results to the control layer; for the specific implementation of the addition of the user, firstly, defining a member function in the class, calling the member function corresponding to the Mapper layer of the persistent layer in the member function, and returning the member function to the control layer;
6. class, which is responsible for providing an interface for accessing the database, of a user management persistent layer class; declaring function interfaces needing to access a database in a Userservice class, wherein the functions are realized in a UserMapper xml file through a database special language sql language;
7. defining a UserMapper. Xml file, and realizing a function declared in the UserMapper. Class by using a special sql language for accessing a database in the file, so that interaction with the database is successfully realized, the interactive result is returned to a control layer by layer, and the control layer is returned to a front-end page for displaying;
the steps are the addition of users in user management monitoring, and other operations needing user management mainly comprise the following contents:
(1) Deletion, display, authority management and the like of users and user groups;
the above-mentioned operation steps regarding the user right management are the same as the steps of adding the user.
S4, implementation of interface blade monitoring
The method comprises the following steps that a computing blade is connected with an interface blade by using a TELNET protocol, after the connection is established, the computing blade sends interface blade command information to the interface blade, the interface blade receives the command information, executes a command and returns an execution result to the computing blade, and finally, the execution result is displayed on the computing blade through a Web page, and the specific implementation steps are as follows:
s401, repeating the operation steps from the blade calculating step S101 to the step S109;
by utilizing the SSM frame built in the monitoring of the computing blade, the system does not need to be built again;
s402, after the SSM framework is successfully built, the computing blade uses TELNET service to establish connection with the interface blade, and sends interface blade command information to the interface blade, the interface blade analyzes and executes the command, and then returns an execution result to the computing blade, and the computing blade analyzes the returned information and finally displays the information through a Web page;
taking the maximum access optical fiber number of the interface blade as an example, how to obtain the maximum optical fiber access number information in the interface blade by using the SSM framework and displaying the information through a Web page is shown, specifically, the following steps are implemented:
1. compiling Web page interfaceportInfo.jsp, defining a URL/interfacenode/getfibre/", and enabling a Spring front-end controller in an SSM frame to capture the request and forward the request to a control layer;
2. class, which implements three functions:
firstly, receiving a request from a front-end Web page, and determining a control layer processing function specifically receiving the request in a control layer by analyzing a URL in the request;
secondly, calling a corresponding service layer program to process the request;
thirdly, receiving a result returned by the service layer and returning the result to the Web page for displaying;
according to the process, the acquisition of the maximum optical fiber number of the interface blade is specifically realized as follows;
firstly, defining a member function in the class, and adding @ RequestMapping "/interfacenode/getfibre/" to the upper line defined by the member function;
secondly, acquiring the maximum optical fiber number of the interface blade in the member function by calling the corresponding member function in the service layer class;
and thirdly, obtaining a return result of the corresponding member function of the service layer, and returning the result to the corresponding Web page, wherein the page URL responsible for receiving the return result is "/interface/getfibre/".
3. Compiling an interface blade service layer class, which is responsible for receiving calls from a control layer, realizing specific service logic and returning results to the control layer;
for the specific implementation of obtaining the maximum optical fiber number of the interface blade, firstly, defining a member function in the class, realizing the connection establishment of the calculation blade and the interface blade in the member function through TELNET, establishing a corresponding TELNET session, sending an interface blade command to the interface blade through the session, receiving information returned by the TELNET session after the interface blade executes the command, analyzing the result, and returning the result to the control layer;
the above steps are the process of obtaining the maximum number of optical fibers in the interface blade, and the information of other interface blades needing to be obtained mainly includes the following contents:
(1) Monitoring static information of the interface blade, such as version models of FPGA, optical fiber and the like;
(2) Monitoring the state of the interface blade, such as the maximum number of accessed optical fibers, the rear of an optical fiber access port and the like;
(3) The health state of the interface blade, such as whether RapidIO data is normally received and transmitted or not;
(4) Monitoring the state of the gigabit network and the gigabit network;
the steps of acquiring and displaying the interface blade information and acquiring the maximum optical fiber number of the interface blade are the same.
Through actual measurement, the invention is deployed on a processor host with a memory of 2G, a main frequency of 3.2GHz and an i5-6500, the required time is not more than 7s, the average response time of each operation is not more than 50ms, compared with other cluster monitoring software, the invention can realize rapid deployment and response and provide better support for a heterogeneous platform.
The above-mentioned contents are only for illustrating the technical idea of the present invention, and the protection scope of the present invention is not limited thereby, and any modification made on the basis of the technical idea of the present invention falls within the protection scope of the claims of the present invention.
Claims (6)
1. A cluster monitoring method supporting a heterogeneous platform is characterized in that a JAVA WEB development framework SSM is adopted to respectively establish computing blade monitoring, exchange blade monitoring, user management monitoring and interface blade monitoring, which is beneficial to rapid expansion and cutting, and layered programming is realized; writing http api or http addresses of other introduced monitoring frames into corresponding configuration files, after java background processing, transmitting the http api or http addresses to a foreground page through a spring MVC frame, and realizing integration of other open source monitoring items and the http api into the frames; defining a development interface of the embedded platform through a java interface technology, shielding bottom layer detail differences of different embedded platforms aiming at specific embedded platforms, and realizing seamless fusion and butt joint with a system; port state monitoring, port remote control, route display, addition, deletion, port state statistics and chip running state monitoring of a switch board are realized aiming at a switch blade; port control, self-test control, port state display, state monitoring and hardware state monitoring are realized aiming at the interface blade;
the blade monitoring is specifically calculated as follows: the method comprises the following steps of using an SSM framework to build a WEB server development framework, obtaining calculation blade information through a LINUX local command, an open source jar packet and a Linux tool, and finally displaying through a Web page, wherein the displaying comprises the following steps: obtaining and displaying memory information in the computing blade; calculating static information display of the blade, wherein the static information display comprises CPU (central processing unit), memory, magnetic disks, an operating system, network MAC (media access control) and IP (Internet protocol) information; controlling processes and threads; the method comprises the following steps of monitoring the real-time states of a gigabit network, rapidIO, a hard disk, a CPU and memory hardware, and specifically comprises the following steps:
s101, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool;
s102, creating a Maven project in an Eclipse development tool;
s103, setting a directory structure and a name of the project according to the project requirement;
s104, integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project;
s105, compiling a corresponding pom.xml file, adding jar packages required by the project into the pom.xml file, introducing the pom.xml file into a Maven project, and automatically downloading jar packages configured in the pom.xml file on the network by project loading;
s106, compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis;
s107, compiling a configuration file SpringMVC-configuration.xml integrating springMVC and Spring, and completing the starting function configuration of an automatic scanning controller, a view mode and an annotation;
s108, writing a configuration file application context of Spring, and introducing and integrating objects of a control layer, a service layer and a persistence layer;
s109, compiling a web.xml configuration file, introducing the whole Maven project into the configuration file for integration, and building an SSM framework;
s110, obtaining information of the calculation blade through an SSM framework by using a LINUX local command, an open source jar packet and a Linux tool, and displaying the information through a front-end Web page to realize monitoring of the calculation blade;
the interface blade monitoring specifically comprises: the method comprises the following steps that a computing blade realizes connection with an interface blade by using a TELNET protocol, the interface blade sends interface blade command information to the interface blade, the interface blade executes a command and returns an execution result to the computing blade after receiving the command information, and finally the execution result is displayed on the computing blade through a Web page, wherein the method comprises the following steps: acquiring the maximum optical fiber number in the interface blade; monitoring static information of the interface blade; monitoring the state of the interface blade; interface blade health status; the method comprises the following specific steps of monitoring the state of the gigabit network and the gigabit network:
s401, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding a jar package required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and loading the jar package configured in the pom.xml file automatically on the network by the project; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml is written and integrated with a configuration file SpringMVC-configuration, and the starting function configuration of an automatic scanning controller, a view mode and an annotation is completed; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s402, after the SSM framework is successfully built, the computing blade uses TELNET service to establish connection with the interface blade, and sends interface blade command information to the interface blade, the interface blade analyzes and executes the command, an execution result is transmitted back to the computing blade, and the computing blade analyzes the returned information and displays the information through a Web page.
2. The cluster monitoring method supporting the heterogeneous platform according to claim 1, wherein in step S106, a Mybatis-config.xml configuration file is used to set mapping rules for object attributes and database storage data, a data mapping interface defined in a class acquisition class defined by scanning a specified directory definition is used, an applicationContext-mybatis.xml configuration file is used to manage Mybatis data source configuration transactions, creation of sqlSessionFactory and creation of a data mapping interface Mapper by Spring, and sqlSession and a corresponding data mapping interface Mapper are required to be acquired in Mybatis configuration file Mybatis-config.xml and are injected by Spring.
3. The cluster monitoring method supporting heterogeneous platforms according to claim 1, wherein the switching blade monitoring specifically includes: the method comprises the following steps that a computing blade is connected with an exchange blade through an SSH protocol, after the connection is established, command information of the exchange blade is sent to the exchange blade through the computing blade, after the exchange blade receives a command, the command is executed, an execution result is returned to the computing blade, and finally the command is displayed on the computing blade through a Web page, wherein the displaying comprises the following steps: acquiring and displaying port information in the exchange blade; monitoring the health states of a ten-gigabit network, a RapidIO chip and a main control processor of the exchange blade; enabling and closing ports of a switching blade gigabit network, a gigabit network and RapidIO; and monitoring the real-time state of each port of the switching blade gigabit network, the gigabit network and the RapidIO.
4. The cluster monitoring method supporting the heterogeneous platform according to claim 3, comprising the following steps:
s201, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding jar packages required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and automatically downloading jar packages configured in the pom.xml file on a network by the project loading; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml integrating the Spring MVC and the Spring configuration file, namely, spring mvc-configuration.xml, and completing the starting function configuration of an automatic scanning controller, a view mode and an annotation; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s202, after the SSM framework is successfully built, the SSH service computing blade and the exchange blade are used for building connection, and sending command information of the exchange blade to the exchange blade, the exchange blade analyzes the command and then transmits the command back to the computing blade, and the computing blade analyzes the returned information and finally displays the information through a Web page.
5. The cluster monitoring method supporting the heterogeneous platform according to claim 1, wherein the user management monitoring specifically comprises: defining users who have legal access and use authority to the system and cluster resources in user management monitoring, viewing a user list, adding and deleting the users and changing the user authority, writing all attributes of the users into a database, and finally displaying results in the database on a Web page of a client, wherein the display comprises the addition of the users, the deletion of user groups, display or authority management.
6. The cluster monitoring method supporting the heterogeneous platform according to claim 5, comprising the following steps:
s301, downloading and installing a JDK tool according to a used Linux system, and then respectively downloading and installing an Eclipse development tool and a Maven development tool; creating a Maven project in an Eclipse development tool; setting a directory structure and a name of a project according to the project requirement; integrating a Maven tool and an Eclipse tool through configuration options in Eclipse in the created Maven project; compiling a corresponding pom.xml file, adding a jar package required by a project into the pom.xml file, introducing the pom.xml file into a Maven project, and loading the jar package configured in the pom.xml file automatically on the network by the project; compiling two configuration files, namely Mybatis-config.xml and applicationContext-mybatis.xml, and integrating Spring and Mybatis; xml is written and integrated with a configuration file SpringMVC-configuration, and the starting function configuration of an automatic scanning controller, a view mode and an annotation is completed; writing a configuration file application context of Spring, introducing objects of a control layer, a service layer and a persistence layer, and integrating; compiling a web.xml configuration file for introducing the whole Maven project into the configuration file for integration and building an SSM framework;
s302, installing a MySQL database, and creating a corresponding table for each attribute of the user in the database;
s303, adding an Apache horio installation authentication jar package into the pom.xml file to realize that different users have different access and use rights;
s304, writing application context-shred.xml, integrating the shred and Spring, and configuring a security manager and an encryption manager of the shred;
s305, sending a request through a front-end Web page, realizing access to a database through an SSM framework, and finally realizing addition and deletion of user management and monitoring of user authority management functions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910712545.8A CN110413484B (en) | 2019-08-02 | 2019-08-02 | Cluster monitoring method supporting heterogeneous platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910712545.8A CN110413484B (en) | 2019-08-02 | 2019-08-02 | Cluster monitoring method supporting heterogeneous platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110413484A CN110413484A (en) | 2019-11-05 |
| CN110413484B true CN110413484B (en) | 2023-01-31 |
Family
ID=68365625
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910712545.8A Active CN110413484B (en) | 2019-08-02 | 2019-08-02 | Cluster monitoring method supporting heterogeneous platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110413484B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174256A (en) * | 2022-07-27 | 2022-10-11 | 上海宏时数据系统有限公司 | Processing method, device, equipment and medium for Zabbix application |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006277210A (en) * | 2005-03-29 | 2006-10-12 | Nec Corp | Cluster system, power supply control method for blade server and program therefor |
| CN102541714A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Implementation method and device for chip monitoring |
| CN104102291A (en) * | 2014-07-22 | 2014-10-15 | 浪潮(北京)电子信息产业有限公司 | Blade server and blade server monitoring management method and system |
| CN106095408A (en) * | 2016-05-31 | 2016-11-09 | 浙江网新恒天软件有限公司 | A kind of system and method for data monitoring and Code automatic build and deployment |
| CN109783556A (en) * | 2018-12-24 | 2019-05-21 | 浙江工业大学 | Power quality controlling equipment on-line monitoring system and construction method based on Hadoop and SSM framework |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8602896B2 (en) * | 2009-03-05 | 2013-12-10 | Igt | Methods and regulated gaming machines including game gadgets configured for player interaction using service oriented subscribers and providers |
-
2019
- 2019-08-02 CN CN201910712545.8A patent/CN110413484B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006277210A (en) * | 2005-03-29 | 2006-10-12 | Nec Corp | Cluster system, power supply control method for blade server and program therefor |
| CN102541714A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Implementation method and device for chip monitoring |
| CN104102291A (en) * | 2014-07-22 | 2014-10-15 | 浪潮(北京)电子信息产业有限公司 | Blade server and blade server monitoring management method and system |
| CN106095408A (en) * | 2016-05-31 | 2016-11-09 | 浙江网新恒天软件有限公司 | A kind of system and method for data monitoring and Code automatic build and deployment |
| CN109783556A (en) * | 2018-12-24 | 2019-05-21 | 浙江工业大学 | Power quality controlling equipment on-line monitoring system and construction method based on Hadoop and SSM framework |
Non-Patent Citations (3)
| Title |
|---|
| "面向自主刀片服务器的智能监控管理系统设计";叶操;《中国优秀硕士学位论文全文数据库》;20180415;全文 * |
| Zhixin Fu ; Yang Luo ; Chenghong Gu ; Furong Li ; Yuan Yue."Reliability Analysis of Condition Monitoring Network of Wind Turbine Blade Based on Wireless Sensor Networks".《IEEE Transactions on Sustainable Energy》.2018, * |
| 嵌入式工控终端机的云计算架构及服务平台;温泉等;《计算机技术与发展》;20141023(第12期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110413484A (en) | 2019-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11909604B2 (en) | Automatic provisioning of monitoring for containerized microservices | |
| KR101891506B1 (en) | Methods and systems for portably deploying applications on one or more cloud systems | |
| EP3149591B1 (en) | Tracking application deployment errors via cloud logs | |
| CN109889381B (en) | Automatic configuration management method and device based on fort machine | |
| US8510720B2 (en) | System landscape trace | |
| US9231963B2 (en) | Detecting anomalous behavior patterns in an electronic environment | |
| US7152104B2 (en) | Method and apparatus for notifying administrators of selected events in a distributed computer system | |
| US7668924B1 (en) | Methods and system for integrating SAN servers | |
| US20040078787A1 (en) | System and method for troubleshooting, maintaining and repairing network devices | |
| US7376898B1 (en) | Methods and apparatus for managing resources | |
| EP3616061B1 (en) | Hyper dynamic java management extension | |
| US11917033B2 (en) | Techniques for managing distributed computing components | |
| CN106547790B (en) | Relational database service system | |
| CN110413484B (en) | Cluster monitoring method supporting heterogeneous platform | |
| US9307015B1 (en) | Cloud black box for cloud infrastructure | |
| US11635972B2 (en) | Multi-tenant java agent instrumentation system | |
| Seifermann | Application performance monitoring in microservice-based systems | |
| CN112350870A (en) | Operation and maintenance safety auditing method and device for container cluster system | |
| CN103457771B (en) | The management method of the cluster virtual machine of a kind of HA and equipment | |
| US20110214116A1 (en) | Systems and methods for managing software package updates using communication pipes | |
| CN112068953B (en) | Cloud resource fine management traceability system and method | |
| Schmieders et al. | Architectural runtime models for privacy checks of cloud applications | |
| CN112422349B (en) | Network management system, method, equipment and medium for NFV | |
| CN114816914A (en) | Data processing method, equipment and medium based on Kubernetes | |
| CN114625594A (en) | Configuration file generation method, log collection method, device, equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |