Roadside node cluster management system

Abstract

The embodiment of the invention relates to a roadside node cluster management system. The system comprises a first management cluster and a plurality of first roadside node clusters, the user and cluster management main node is used for performing user registration management, user node permission allocation, user node login verification, node resource management, roadside cluster management and roadside cluster monitoring; the application warehouse management main node is used for loading and unloading an application and updating an application version; the application deployment main node is used for performing application deployment scheme management and roadside node application configuration; and the application operation and maintenance main node is used for performing roadside node application monitoring processing. According to the invention, the personalized configuration / management capability of the system on the roadside nodes can be improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a roadside node cluster management system. Background Art

[0002] Edge computing nodes refer to physical hosts or virtual machines that perform data computing and analysis tasks at the edge of the network. Roadside nodes are a type of edge computing node in intelligent transportation systems. Roadside nodes are used to perform real-time computing and analysis on traffic data collected in real time, thereby assisting the intelligent transportation system in optimizing traffic flow and reducing traffic congestion. Under normal circumstances, a node management system is configured for routine management of roadside node networks deployed on a large scale. However, this routine management is often based on status monitoring and has poor capabilities for personalized management of nodes (such as the personalized ability to deploy different applications on different nodes, the personalized ability to actively restart / reinstall nodes where applications are suspended / failed to load, etc.). Summary of the invention

[0003] The purpose of the present invention is to provide a roadside node cluster management system in response to the defects of the prior art, the system comprising: a first management cluster and multiple first roadside node clusters; each first roadside node cluster is composed of a first master node and multiple first working nodes connected to the master node; the first management cluster comprises cluster storage, user and cluster management master node, application warehouse management master node, application deployment master node and application operation and maintenance master node; wherein the cluster storage comprises a user database (for storing a user registration information table and a user authority information table), a cluster database (for storing a node resource information table, a cluster deployment information table and a cluster monitoring information table) and an application database (for storing an application image information table and an application deployment plan information table); the user and cluster management master node is used for user registration management, user node authority allocation, user node login verification, node resource management, roadside cluster management and roadside cluster monitoring; the application warehouse management master node is used for application delisting and application version update processing; the application deployment master node is used for application deployment plan management and roadside node application configuration; the application operation and maintenance master node is used for roadside node application monitoring processing. The present invention can not only strengthen the system's monitoring capability for roadside nodes, but also improve the system's personalized configuration / management capability for roadside nodes, thereby solving the problem of poor personalized management capability of nodes in conventional management methods.

[0004] To achieve the above object, an embodiment of the present invention provides a roadside node cluster management system, the system comprising: a first management cluster and a plurality of first roadside node clusters;

[0005] The first management cluster is connected to each of the first roadside node clusters respectively;

[0006] The first management cluster includes cluster storage, a user and cluster management master node, an application warehouse management master node, an application deployment master node and an application operation and maintenance master node; the user and cluster management master node, the application warehouse management master node, the application deployment master node and the application operation and maintenance master node are respectively connected to the cluster storage; the cluster storage includes a user database, a cluster database and an application database;

[0007] The user database is used to store a user registration information table and a user authority information table; the cluster database is used to store a node resource information table, a cluster deployment information table and a cluster monitoring information table; the application database is used to store an application image information table and an application deployment solution information table;

[0008] The user and cluster management master node is used for user registration management; the user and cluster management master node is also used for user node authority allocation; the user and cluster management master node is also used for user node login verification; the user and cluster management master node is also used for node resource management; the user and cluster management master node is also used for roadside cluster management; the user and cluster management master node is also used for roadside cluster monitoring; the application warehouse management master node is used for application on-shelf and off-shelf and application version update processing; the application deployment master node is used for application deployment plan management; the application deployment master node is also used for roadside node application configuration; the application operation and maintenance master node is used for roadside node application monitoring processing;

[0009] The first roadside node cluster consists of a first master node and multiple first working nodes; the first master node is connected to each of the first working nodes respectively; the first master node is also connected to the user and cluster management master node, the application deployment master node and the application operation and maintenance master node respectively.

[0010] Preferably, the user registration information table includes a plurality of first user registration records; the first user registration records correspond to registered users one by one; the first user registration record includes at least a first user identifier, a first user name, a first user password, a first user identity identifier, a first user type and a first affiliated organization; the first user identity identifier is the unique identity identifier information of the current registered user; the first user type includes individual users and institutional users; when the first user type is an individual user, the first affiliated organization is empty; when the first user type is an institutional user, the first affiliated organization is the name of the organization to which the current user belongs;

[0011] The user authority information table includes a plurality of first user authority records; the first user authority record corresponds one-to-one with the first user registration record; the first user authority record includes a second user identifier and a first authorized resource set; the first and second user identifiers correspond one-to-one; the first authorized resource set, when not empty, is composed of one or more authorized cluster information; the authorized cluster information is composed of an authorized cluster identifier and an authorized node set; the authorized node set is composed of one or more authorized node identifiers;

[0012] The node resource information table includes multiple first node resource records; the first node resource record includes a first node identifier, a first node purchase time, a first node basic information, a first node working condition, a first node allocation type, a first belonging cluster identifier and a first node label set; each of the first node resource records corresponds to a node resource, and each node resource is a physical host or a virtual machine; the first node basic information includes at least all software and hardware configuration information and network configuration information of the current node resource; the first node working condition includes idle, occupied and faulty; when the first node working condition is idle, the first node allocation type, the first belonging cluster identifier and the first node label set are all empty; when the first node working condition is occupied or faulty, the first node allocation type includes the master node type and the working Node type, the first cluster identifier is the cluster identifier of the cluster to which the current node resource belongs, the first node label set is composed of one or more first label information; the first label information is composed of a first label type and a first label value; the first label type includes a regional label, a security domain label, an organization label and an application label; when the first label type is a regional label, the first label value is the corresponding regional name; when the first label type is a security domain label, the first label value is the corresponding security domain name; when the first label type is an organization label, the first label value is the corresponding organization name; when the first label type is an application label, the first label value is the corresponding application image and version name, and the application image and version name is composed of the corresponding application image name and application version;

[0013] The cluster deployment information table includes a plurality of first cluster deployment records; the first cluster deployment record corresponds to the first roadside node cluster one by one; the first cluster deployment record includes a first cluster identifier, a first cluster name, a first cluster creation time, a first cluster basic information, a first cluster working condition, a first master node configuration, a first working node configuration set, a first regional deployment configuration and a first security domain deployment configuration; the first cluster basic information includes at least cluster storage configuration information and cluster network configuration information of the current roadside node cluster; the first cluster working condition includes normal and fault; the first master node configuration corresponds to the first master node of the current roadside node cluster; the first master node configuration is the first node identifier corresponding to the corresponding first master node; the first working node configuration set is composed of a plurality of first working node configurations; the first working node configuration corresponds to the first working node of the current roadside node cluster one by one; the first working node configuration is the first node identifier corresponding to the corresponding first working node; the first regional deployment configuration is the regional configuration information of the current roadside node cluster, consisting of one or more regional names; the first security domain deployment configuration is the security domain configuration information of the current roadside node cluster, consisting of one or more security domain names;

[0014] The cluster monitoring information table is composed of a plurality of first cluster monitoring logs; the first cluster monitoring log includes a first monitoring time, a first monitoring cluster identifier and a first cluster monitoring report; the first monitoring cluster identifier is the first cluster identifier corresponding to the first roadside node cluster; the first cluster monitoring report is composed of a plurality of first node monitoring logs; the first node monitoring log includes a first monitoring node identifier and a first monitoring node report; the first monitoring node identifier corresponds one-to-one to the first working node under the first roadside node cluster corresponding to the current first monitoring cluster identifier, and the first monitoring node identifier is the first node identifier corresponding to the corresponding first working node; the first monitoring node report includes at least first CPU information, first GPU information, first memory information, first hard disk information and a first application information set; the first CPU information includes CPU manufacturer information and CPU usage; the first GPU information includes GPU manufacturer information and GPU usage; the first memory information includes memory manufacturer information, total memory capacity and memory usage; the first hard disk information includes hard disk manufacturer information, total hard disk storage capacity and hard disk storage usage; the first application information set includes a plurality of first application information; the first application information includes application image and version name and application usage status; the application usage status includes normal use, normal idle, abnormal suspension and loading failure;

[0015] The application image information table includes multiple first application image records; each of the first application image records corresponds to an application image; the first application image record includes a first application image identifier, a first application image name, first application image basic information, a first application version and a first version software package; the first application image name is the application image name of the current application image; the first application image basic information includes at least the algorithm / software developer information and the summary introduction information of the algorithm / software function of the current application image;

[0016] The application deployment scheme information table includes multiple first application deployment schemes; the first application deployment scheme includes a first scheme identifier, a first scheme startup time, a first deployment configuration, a first node screening condition, a first deployment state and a first failed node set; the first deployment configuration is composed of one or more first application deployment information, and the first application deployment information is composed of a corresponding application image name and an application version; the first node screening condition is a node screening condition set adapted to the current deployment, and the node screening condition set is composed of one or more groups of screening means based on regional names, and / or one or more groups of screening means with security domain names, and / or one or more groups of screening means based on organization names, and / or one or more groups of screening means based on the node's own computing power conditions, and / or one or more groups of screening means based on node labels, each screening means is a type of screening method set according to a satisfying or not satisfying relationship, or a type of screening method set according to an affinity or anti-affinity relationship; the first scheme deployment status includes not started, full node deployment success, full node deployment failure and partial node deployment failure; when the first scheme deployment status is not started or full node deployment success, the first failed node set is empty; when the first scheme deployment status is full node deployment failure or partial node deployment failure, the first failed node set is composed of the first node identifiers of all the first working nodes that failed in this deployment.

[0017] Preferably, the user and cluster management master node are specifically used for performing the user node login verification:

[0018] Step 31, receiving a first node login verification request sent by the first master node of any first roadside node cluster; and using the current first master node as the corresponding current cluster master node;

[0019] The first node login verification request includes a first login cluster identifier, a first login node identifier, a first login user name, and a first login user password;

[0020] Step 32, taking the first user registration record in the user registration information table of the user database in which the first user name matches the first login user name and the first user password matches the first login user password as the corresponding current user registration record; and identifying whether the current user registration record is empty; if the current user registration record is empty, setting the corresponding first user verification status to unauthorized user, and going to step 34; if the current user registration record is not empty, going to step 33;

[0021] Step 33, taking the first user authority record in which the second user identifier in the user authority information table of the user database matches the first user identifier of the current user registration record as the corresponding current user authority record; and taking the authorization cluster information in which the authorization cluster identifier in the first authorization resource set of the current user authority record matches the first login cluster identifier as the corresponding current authorization cluster information; and identifying whether the current authorization cluster information is empty; if the current authorization cluster information is empty, setting the corresponding first user verification status to an unauthorized user; if the current authorization cluster information is not empty, identifying whether the authorization node set of the current authorization cluster information contains the first login node identifier, if not, setting the corresponding first user verification status to an unauthorized user, and if so, setting the corresponding first user verification status to an authorized user;

[0022] Wherein, the first user verification status includes authorized users and unauthorized users;

[0023] Step 34: Use the first login cluster identifier and the first login node identifier as the corresponding first verification cluster identifier and first verification node identifier; and send a corresponding first verification request feedback composed of the first verification cluster identifier, the first verification node identifier and the first user verification status back to the current cluster master node.

[0024] Preferably, the first working node is used to receive the login username and login password input by the current user as the corresponding first login username and the first login password when the user logs in to the node; and use the belonging cluster identification information and the node identification information stored locally on the node as the corresponding first login cluster identification and the first login node identification; and the first login cluster identification, the first login node identification, the first login username and the first login user password form a corresponding first node login verification request; and send the first node login verification request to the user and the cluster management master node through the corresponding first master node; and receive the first verification request feedback sent back by the user and the cluster management master node through the corresponding first master node; and The first verification cluster identifier, the first verification node identifier and the first user verification status in the first verification request feedback are identified; if the first verification cluster identifier matches the belonging cluster identifier information stored locally at the node and the first verification node identifier matches the node identifier information stored locally at the node and the first user verification status is an authorized user, a login success message is fed back to the current login and the current logged-in user is allowed to use local node resources; if the first verification cluster identifier does not match the belonging cluster identifier information stored locally at the node, or the first verification node identifier does not match the node identifier information stored locally at the node, or the first user verification status is an unauthorized user, a login failure message is fed back to the current login and the current logged-in user is prohibited from using local node resources.

[0025] Preferably, the management types of the node resource management include node purchase, node query, cluster allocation, fault marking, repair marking, label marking, and label revocation; the management types of the roadside cluster management include cluster creation, cluster query, cluster regional deployment, cluster security domain deployment, and cluster deletion.

[0026] Preferably, the user and cluster management master node are specifically used for: when performing roadside cluster monitoring: regularly sending patrol signals to the first master node groups of all the first roadside node clusters according to a preset first patrol frequency; and after the patrol signal group sending is completed, waiting for patrol report reception according to a preset first waiting time; and when the waiting time does not exceed the first waiting time, each time a first cluster monitoring report sent by the first master node is received, the first cluster identifier corresponding to the first roadside node cluster corresponding to the current first master node is used as the corresponding first monitoring cluster identifier, and the current time is used as the corresponding first monitoring time, and a corresponding first cluster monitoring log consisting of the current first cluster monitoring report, the corresponding first monitoring time and the first monitoring cluster identifier is added to the cluster monitoring information table; and when the waiting time exceeds the first waiting time, the patrol report reception wait is terminated, and a round of cluster and node status update processing is performed based on all the first cluster monitoring logs added this time.

[0027] Preferably, the first master node is used to send the inspection signal to all the corresponding first working nodes in a group upon receiving the inspection signal; and after the inspection signal is sent in a group, initialize the corresponding first cluster monitoring report to be empty, and wait for the inspection report reception according to the preset second waiting time; and when the waiting time does not exceed the second waiting time, each time a first node monitoring log sent by the first working node is received, the current first node monitoring log is added to the first cluster monitoring report; and when the waiting time exceeds the second waiting time, end the inspection report reception wait, and send the latest first cluster monitoring report to the user and the cluster management master node; 0<second waiting time<first waiting time;

[0028] The first working node is also used to, when receiving the inspection signal, summarize all local resource information to obtain the corresponding first monitoring node report; and use the node identification information stored locally as the corresponding first monitoring node identification; and the first monitoring node identification and the first monitoring node report form the corresponding first node monitoring log and send it to the corresponding first master node.

[0029] Preferably, the application deployment master node is specifically used for:

[0030] Step 81, receiving a first solution management application submitted by a sixth management interface;

[0031] The sixth management interface includes an administrator, any management user who obtains application deployment authority, and any system processing interface who obtains application deployment authority; the first solution management application includes a fourth management type and a fourth management parameter; the fourth management type includes solution submission / update and solution query;

[0032] When the fourth management type is solution submission / update, the fourth management parameter includes a submitted solution identifier, a planned startup time, an application deployment information set, and a node screening condition; the application deployment information set includes one or more application deployment information; the application deployment information consists of a corresponding application image name and an application version;

[0033] When the fourth management type is a scheme query, the fourth management parameter includes a third query mode and a third query parameter; the third query mode includes an eighth mode and a ninth mode; when the third query mode is the eighth mode, the third query parameter is empty; when the third query mode is the ninth mode, the third query parameter consists of one or more query scheme identifiers;

[0034] Step 82, if the fourth management type is solution submission / update, the submitted solution identifier, the planned startup time, the application deployment information set and the node screening condition of the fourth management parameter are used as the corresponding current solution identifier, the current solution startup time, the current application deployment information set and the current node screening condition; and the first application deployment solution whose first solution identifier in the application deployment solution information table of the application database matches the current solution identifier and whose first deployment status is not started is used as the corresponding matching deployment solution; and whether the matching deployment solution is empty is identified; if the matching deployment solution is empty, a new first application deployment solution is added to the application deployment solution information table as the corresponding current deployment solution, and the first The solution identifier, the first solution startup time, the first deployment configuration and the first node screening condition are set to the corresponding current solution identifier, the current solution startup time, the current application deployment information set and the current node screening condition, and the first deployment state of the current deployment solution is set to not started, and the first failed node set of the current deployment solution is set to empty; if the current matching record is not empty, the first solution startup time, the first deployment configuration and the first node screening condition of the current matching record are updated to the corresponding current solution startup time, the current application deployment information set and the current node screening condition; and when the application deployment solution corresponding to the current fourth management parameter is added or updated, the corresponding fourth management application feedback is set to success;

[0035] Step 83, if the fourth management type is solution query, the third query mode and the third query parameter of the fourth management parameter are used as the corresponding current query mode and current query parameter; and the current query mode is identified; if the current query mode is the eighth mode, the application deployment solution information table is used as the corresponding fourth management application feedback; if the current query mode is the ninth mode, the first application deployment solution whose first solution identifier in the application deployment solution information table matches each query solution identifier of the third query parameter is extracted to form the corresponding fourth management application feedback;

[0036] Step 84: Feedback the fourth management application obtained this time to the sixth management interface.

[0037] Preferably, the application deployment master node is specifically used for:

[0038] Step 91, regularly taking the first application deployment schemes in the application deployment scheme information table of the application database whose start time is not later than the current time and whose first deployment status is not started as corresponding first inspection schemes according to the preset first time frequency; and taking the first inspection scheme with the earliest start time as the corresponding current configuration scheme; and initializing the first counter to 0;

[0039] Step 92, extract the first version software package of the first application image record whose first application image name and the first application version satisfy the first deployment configuration of the current configuration scheme in the application image information table of the application database to form a corresponding first software set;

[0040] Step 93, extracting the first node identifiers of the first node resource records that meet the first node screening condition of the current configuration solution from the node resource information table of the cluster database to form a corresponding first node identifier set;

[0041] Step 94, the first node identifiers in the first node identifier set that belong to the same first roadside node cluster are grouped into one category to form a corresponding first node identifier group; and the working node groups corresponding to each of the first node identifier groups are recorded as corresponding first node groups; and the first master node of the first roadside node cluster where each of the first node groups is located is taken as the corresponding second master node;

[0042] Step 95, and establish a corresponding remote control channel with each of the first working nodes of the corresponding first node group through each of the second master nodes, recorded as a first remote control channel; and transmit the first software set to the corresponding first working node through each of the first remote control channels, and after the software set transmission is completed, perform corresponding image instance creation and operation processing on all application images included in the first software set on the corresponding first working node through each of the first remote control channels to obtain a corresponding first processing result; and identify whether each of the first processing results is successful, if the current first processing result is successful, delete the software package set on the corresponding first working node through the corresponding first remote control channel, if the current first processing result is a failure, delete the software package set, clear the application image instance and release the corresponding node resources on the corresponding first working node through the corresponding first remote control channel; and close all the first remote control channels;

[0043] Wherein, the first processing result includes success and failure;

[0044] Step 96, and identify all the first processing results obtained; if all the first processing results are successful or failed, set the corresponding current deployment state to all success or all failure, and go to step 97; if all the first processing results are partially successful and partially failed, set the corresponding current deployment state to partially failed, and form a new first node identifier set by the first node identifiers corresponding to all the first processing results that are specifically failed, and add 1 to the first counter, and identify whether the first counter after adding 1 exceeds the preset first counter threshold, if so, go to step 97, if not, return to step 94 after waiting for the preset first time length;

[0045] Step 97, identify the latest current deployment status; if the current deployment status is full success, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full-node deployment success; if the current deployment status is full failure or partial failure, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full-node deployment failure or partial node deployment failure, and set the first failed node set of the current configuration scheme to the latest first node identification set.

[0046] Preferably, the application operation and maintenance master node is specifically used for:

[0047] Step 101, regularly extracting the first cluster identifiers of the first cluster deployment records whose first cluster working condition is normal from the cluster deployment information table of the cluster database at a preset second time frequency to form a corresponding first cluster identifier set;

[0048] Step 102, extracting the first cluster monitoring report of the first cluster monitoring log whose first monitoring cluster identifier in the cluster monitoring information table of the cluster database matches each first cluster identifier of the first cluster identifier set and whose first monitoring time is closest to the current time to form a corresponding first cluster monitoring report set;

[0049] Step 103, extracting from the first cluster monitoring report set at least one of the first monitoring node reports in which the application usage status of the first application information is abnormal suspension or loading failure to form a corresponding first monitoring node report set;

[0050] Step 104, when the first monitoring node report set is not empty, the first monitoring node identifier, application image and version name, and the application usage status corresponding to the first application information of each application usage status of abnormal suspension or loading failure in the current first monitoring node report set are used as the corresponding first abnormal node identifier, first abnormal application information, and first abnormal status to form a corresponding abnormal node application record; and all the obtained abnormal node application records form a corresponding abnormal node application report;

[0051] Step 105, when the abnormal node application report is not empty, the abnormal node application report is sent to the preset abnormal node application warning interface; and each of the abnormal node application records is used as the corresponding current record; and the first abnormal node identifier, the first abnormal application information and the first abnormal state of the current record are used as the corresponding current node identifier, the current abnormal application information and the current abnormal state; and the first working node corresponding to the current node identifier is used as the corresponding current working node; and the first belonging cluster identifier of the first node resource record whose first node identifier in the node resource information table of the cluster database matches the current node identifier is used as the corresponding current cluster identifier; and the first master node corresponding to the first master node configuration of the first cluster deployment record whose first cluster identifier in the cluster deployment information table of the cluster database matches the current cluster identifier is used as the corresponding current master node; and a corresponding remote control channel is established between the current master node and the current working node, recorded as The corresponding current remote control channel is used; and the current abnormal state is identified; if the current abnormal state is loading failure, the first application image name and the first application version in the application image information table of the application database are extracted from the first version software package of the first application image record corresponding to the current abnormal application information as the corresponding current software package, and the application image instance corresponding to the current abnormal application information is cleared and the corresponding node resources are released on the current working node through the current remote control channel, and the current software package is transmitted to the current working node through the current remote control channel, and after the software package transmission is completed, the image instance of the application image corresponding to the current software package is rebuilt and run on the current working node through the current remote control channel; if the current abnormal state is abnormal suspension, the application image instance corresponding to the current abnormal application information is restarted on the current working node through the current remote control channel; and the current remote control channel is closed.

[0052] The embodiment of the present invention provides a roadside node cluster management system. As can be seen from the above content, the system includes: a first management cluster and multiple first roadside node clusters; each first roadside node cluster is composed of a first master node and multiple first working nodes connected to the master node; the first management cluster includes cluster storage, user and cluster management master node, application warehouse management master node, application deployment master node and application operation and maintenance master node; wherein, the cluster storage includes a user database (used to store user registration information table and user authority information table), a cluster database (used to store node resource information table, cluster deployment information table and cluster monitoring information table) and an application database (used to store application image information table and application deployment scheme information table); the user and cluster management master node is used for user registration management, user node authority allocation, user node login verification, node resource management, roadside cluster management and roadside cluster monitoring; the application warehouse management master node is used for application on and off shelves and application version update processing; the application deployment master node is used for application deployment scheme management and roadside node application configuration; the application operation and maintenance master node is used for roadside node application monitoring processing. The embodiments of the present invention not only enhance the monitoring capability of the system on the roadside nodes, but also improve the personalized configuration / management capability of the system on the roadside nodes. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 A module structure diagram of a roadside node cluster management system provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0055] The embodiment of the present invention provides a roadside node cluster management system such as Figure 1 As shown in the module structure diagram of a roadside node cluster management system provided by an embodiment of the present invention, the system mainly includes: a first management cluster 1 and multiple first roadside node clusters 2. The first management cluster 1 is connected to each first roadside node cluster 2 respectively.

[0056] (I) First management cluster 1:

[0057] The first management cluster 1 of the embodiment of the present invention includes a cluster storage 11, a user and cluster management master node 12, an application warehouse management master node 13, an application deployment master node 14, and an application operation and maintenance master node 15. Among them, the user and cluster management master node 12, the application warehouse management master node 13, the application deployment master node 14, and the application operation and maintenance master node 15 are respectively connected to the cluster storage 11. The cluster storage 11 includes a user database 111, a cluster database 112, and an application database 113.

[0058] Here, the first management cluster 1 of the embodiment of the present invention is actually the management cluster of all first roadside node clusters 2, also known as a host cluster; multiple master nodes can be defined in the first management cluster 1 to handle management tasks, among which the user and cluster management master node 12, the application warehouse management master node 13, the application deployment master node 14 and the application operation and maintenance master node 15 are four types of master nodes used to handle user and cluster management tasks, application warehouse management tasks, application deployment management tasks and application operation and maintenance management tasks, respectively.

[0059] The user database 111 is used to store a user registration information table and a user authority information table. The cluster database 112 is used to store a node resource information table, a cluster deployment information table and a cluster monitoring information table. The application database 113 is used to store an application image information table and an application deployment solution information table.

[0060] Here, the user registration information table of the embodiment of the present invention includes multiple first user registration records. The first user registration record corresponds to the registered user one by one. The first user registration record includes at least a first user identifier, a first user name, a first user password, a first user identity identifier, a first user type and a first affiliated organization; the first user identity identifier is the unique identity identifier information of the current registered user; the first user type includes individual users and institutional users; when the first user type is an individual user, the first affiliated organization is empty; when the first user type is an institutional user, the first affiliated organization is the name of the organization to which the current user belongs.

[0061] The user authority information table of the embodiment of the present invention includes multiple first user authority records. The first user authority record corresponds one-to-one with the first user registration record. The first user authority record includes a second user identifier and a first authorized resource set. The first and second user identifiers correspond one-to-one. When the first authorized resource set is not empty, it is composed of one or more authorized cluster information; each authorized cluster information is composed of an authorized cluster identifier and an authorized node set; the authorized node set is composed of one or more authorized node identifiers.

[0062] The node resource information table of the embodiment of the present invention includes multiple first node resource records. The first node resource record includes a first node identifier, a first node purchase time, a first node basic information, a first node operating condition, a first node allocation type, a first belonging cluster identifier and a first node label set. Each first node resource record corresponds to a node resource, and each node resource is a physical host or a virtual machine. The first node identifier is a unique node identifier of the current node resource. The first node purchase time is the purchase time of the current node resource. The first node basic information includes at least all software and hardware configuration information and network configuration information of the current node resource. The first node operating condition includes idle, occupied and faulty. When the first node operating condition is idle, the first node allocation type, the first belonging cluster identifier and the first node label set are all empty. When the first node operating condition is occupied or faulty, the first node allocation type includes a master node type and a working node type, the first belonging cluster identifier is the cluster identifier of the cluster to which the current node resource belongs, and the first node label set consists of one or more first label information. The first tag information consists of a first tag type and a first tag value; the first tag type includes a regional tag, a security domain tag, an organizational tag and an application tag; when the first tag type is a regional tag, the first tag value is the corresponding regional name; when the first tag type is a security domain tag, the first tag value is the corresponding security domain name; when the first tag type is an organizational tag, the first tag value is the corresponding organizational name; when the first tag type is an application tag, the first tag value is the corresponding application image and version name, and the application image and version name is composed of the corresponding application image name and application version.

[0063] The cluster deployment information table of the embodiment of the present invention includes multiple first cluster deployment records. The first cluster deployment record corresponds one-to-one to the first roadside node cluster 2. The first cluster deployment record includes a first cluster identifier, a first cluster name, a first cluster creation time, a first cluster basic information, a first cluster operating condition, a first master node configuration, a first working node configuration set, a first regional deployment configuration, and a first security domain deployment configuration. The first cluster basic information includes at least cluster storage configuration information and cluster network configuration information of the current roadside node cluster. The first cluster operating condition includes normal and fault. The first master node configuration corresponds to the first master node 21 of the current roadside node cluster; the first master node configuration is the first node identifier corresponding to the corresponding first master node 21. The first working node configuration set is composed of multiple first working node configurations; the first working node configuration corresponds one-to-one to the first working node 22 of the current roadside node cluster; the first working node configuration is the first node identifier corresponding to the corresponding first working node 22. The first regional deployment configuration is the regional configuration information of the current roadside node cluster, consisting of one or more regional names. The first security domain deployment configuration is the security domain configuration information of the current roadside node cluster, consisting of one or more security domain names.

[0064] The cluster monitoring information table of the embodiment of the present invention is composed of multiple first cluster monitoring logs. The first cluster monitoring log includes a first monitoring time, a first monitoring cluster identifier and a first cluster monitoring report. The first monitoring cluster identifier is a first cluster identifier corresponding to a first roadside node cluster 2. The first cluster monitoring report is composed of multiple first node monitoring logs. The first node monitoring log includes a first monitoring node identifier and a first monitoring node report. The first monitoring node identifier corresponds one-to-one to the first working node 22 under the first roadside node cluster 2 corresponding to the current first monitoring cluster identifier, and the first monitoring node identifier is the first node identifier corresponding to the corresponding first working node 22. The first monitoring node report includes at least first CPU information, first GPU information, first memory information, first hard disk information and a first application information set. The first CPU information includes CPU manufacturer information and CPU usage. The first GPU information includes GPU manufacturer information and GPU usage. The first memory information includes memory manufacturer information, total memory capacity and memory usage. The first hard disk information includes hard disk manufacturer information, total hard disk storage capacity and hard disk storage usage. The first application information set includes a plurality of first application information; the first application information includes the application image and version name and the application use status; the application use status includes normal use, normal idle, abnormal suspension and loading failure.

[0065] The application image information table of the embodiment of the present invention includes multiple first application image records. Each first application image record corresponds to an application image of an algorithm / software. The first application image record includes a first application image identifier, a first application image name, first application image basic information, a first application version, and a first version software package. The first application image identifier is a unique identifier of the current application image. The first application image name is the application image name of the current application image. The first application image basic information includes at least the algorithm / software developer information and the summary introduction information of the algorithm / software function of the current application image. The first application version is the version information of the current application image. The first version software package is an integrated software package of the current application image.

[0066] The application deployment scheme information table of the embodiment of the present invention includes multiple first application deployment schemes. The first application deployment scheme includes a first scheme identifier, a first scheme startup time, a first deployment configuration, a first node screening condition, a first deployment state, and a first failed node set. The first deployment configuration is composed of one or more first application deployment information; the first application deployment information is composed of the corresponding application image name and application version. The first node screening condition is a node screening condition set adapted to the current deployment, and the node screening condition set is composed of one or more groups of screening means based on the regional name, and / or one or more groups of screening means based on the security domain name, and / or one or more groups of screening means based on the organization name, and / or one or more groups of screening means based on the node's own computing power conditions, and / or one or more groups of screening means based on the node label; each screening means is a type of screening method set according to the satisfying or not satisfying relationship, or a type of screening method set according to the affinity or anti-affinity relationship. The first scheme deployment state includes not started, full node deployment success, full node deployment failure, and partial node deployment failure. When the first scheme deployment status is not started or all nodes are deployed successfully, the first failed node set is empty; when the first scheme deployment status is all nodes failed to deploy or some nodes failed to deploy, the first failed node set is composed of the first node identifiers of all first working nodes 22 that failed in this deployment.

[0067] The user and cluster management master node 12 of the embodiment of the present invention is used for user registration management. The user and cluster management master node 12 is also used for user node authority allocation. The user and cluster management master node 12 is also used for user node login verification. The user and cluster management master node 12 is also used for node resource management. The user and cluster management master node 12 is also used for roadside cluster management. The user and cluster management master node 12 is also used for roadside cluster monitoring.

[0068] The application repository master node 13 of the embodiment of the present invention is used to perform application on-shelf and off-shelf and application version update processing.

[0069] The application deployment master node 14 of the embodiment of the present invention is used to manage application deployment solutions. The application deployment master node 14 is also used to configure roadside node applications.

[0070] The application operation and maintenance master node 15 of the embodiment of the present invention is used to perform roadside node application monitoring processing.

[0071] In a specific implementation of the embodiment of the present invention, the user and cluster management master node 12 is specifically used to:

[0072] Step A1, receiving a first user registration request submitted by a first management interface;

[0073] Here, the first management interface of the embodiment of the present invention includes an administrator, any management user who obtains user registration management authority, and any system processing interface that obtains user registration management authority; the first user registration request includes a first request user name, a first request user password, a first request user identity, a first request user type, and a name of an organization to which the first request user belongs; the first request user type includes an individual user and an organization user; when the first request user type is an individual user, the name of the organization to which the first request user belongs is empty, and when the first request user type is an organization user, the organization to which the first request user belongs is not empty;

[0074] Step A2, taking the first user registration record in the user registration information table of the user database 111 where the first user name matches the first request user name and the first user identity matches the first request user identity as the corresponding current query record;

[0075] Step A3, identifying whether the current query record is empty;

[0076] Step A4: if the current query record is not empty, set the corresponding first registration request feedback as the user has registered;

[0077] Step A5, if the current query record is empty, a unique user identifier is generated for the current registered user as the corresponding first user identifier; and the first request user name, the first request user password, the first request user identity identifier, the first request user type and the name of the first request user's organization are used as the corresponding first user name, the first user password, the first user identity identifier, the first user type and the first organization; and the first user identifier, the first user name, the first user password, the first user identity identifier, the first user type and the first organization obtained this time form a corresponding first user registration record and add it to the user registration information table; and add a first user authority record to the user authority information table of the user database 111 as the corresponding current newly added record; and set the second user identifier of the current newly added record to the corresponding first user identifier; and set the first authorized resource set of the current newly added record to the empty set; and set the corresponding first registration request feedback to registration success;

[0078] Step A6: Feedback the obtained first registration request to the first management interface.

[0079] In another specific implementation of the embodiment of the present invention, the user and cluster management master node 12 is specifically used to:

[0080] Step B1, receiving a first user rights configuration request submitted by a second management interface;

[0081] Here, the second management interface of the embodiment of the present invention includes an administrator, any management user who obtains the user authority configuration management authority, and any system processing interface that obtains the user authority configuration management authority; the first user authority configuration request includes a second request user name, a second request user password, and a first configuration resource set; the first configuration resource set is composed of one or more first cluster configurations; the first cluster configuration is composed of a first configuration cluster identifier and a first configuration node set; the first configuration node set is composed of one or more first configuration node identifiers;

[0082] Step B2, taking the first user registration record in the user registration information table of the user database 111, in which the first user name matches the second request user name and the first user password matches the second request user password, as the corresponding current user registration record; and identifying whether the current user registration record is empty; if the current user registration record is empty, setting the corresponding first configuration request feedback as a user name or user password error, and going to step B6; if the current user registration record is not empty, going to step B3;

[0083] Step B3, perform a round of traversal of all first cluster configurations of the first configuration resource set; and in this round of traversal, use the currently traversed first cluster configuration as the corresponding current cluster configuration; and use the first configuration cluster identifier and the first configuration node set of the current cluster configuration as the corresponding current cluster identifier and the current node set; and use the first cluster deployment record in the cluster deployment information table of the cluster database 112 that matches the first cluster identifier with the current cluster identifier as the corresponding current cluster deployment record; and identify whether the current cluster deployment record is empty; if the current cluster deployment record is empty, set the corresponding first configuration request feedback as a cluster identifier error, end this round of traversal and go to step B6; if the current cluster deployment record is not empty, then the first master node configuration and the first working node configuration set of the current cluster deployment record constitute the corresponding current cluster node identifier full set, and identify whether the current cluster node identifier full set contains all the first configuration node identifiers of the current node set, if not, set the corresponding first configuration request feedback as a node identifier error, end this round of traversal and go to step B6, if so, continue to traverse the next first cluster configuration until the last first cluster configuration traversal is completed;

[0084] Step B4, taking the first user authority record in the user authority information table of the user database 111 that matches the second user identifier with the first user identifier of the current user registration record as the corresponding current user authority record; and taking the first authorized resource set of the current user authority record as the corresponding current authorized resource set;

[0085] Step B5, perform a second round of traversal on all first cluster configurations of the first configuration resource set; and in this round of traversal, use the currently traversed first cluster configuration as the corresponding current cluster configuration; and use the first configuration cluster identifier and the first configuration node set of the current cluster configuration as the corresponding current configuration cluster identifier and the current configuration node set; and use the authorized cluster information whose authorized cluster identifier in the current authorized resource set matches the current configuration cluster identifier as the corresponding current authorized cluster information; and identify whether the current authorized cluster information is empty; if the current authorized cluster information is empty, use the current configuration cluster identifier and the current configuration node set as the corresponding authorized cluster identifier and the authorized node set to form a corresponding authorized cluster The information is added to the current authorized resource set; if the current authorized cluster information is not empty, the authorized node set of the current authorized cluster information is used as the corresponding current authorized node set, and the node identifier intersection of the current authorized node set and the current configuration node set is identified to obtain the corresponding current node identifier intersection, and whether the current node identifier intersection is empty is identified. If the current node identifier intersection is empty, the current configuration node set is added to the current authorized node set. If the current node identifier intersection is not empty, all other first configuration node identifiers in the current configuration node set except the current node identifier intersection are added to the current authorized node set; and at the end of this round of traversal, the corresponding first configuration request feedback is set to configuration success;

[0086] Step B6: Feedback the first configuration request obtained this time to the second management interface.

[0087] In another specific implementation of the embodiment of the present invention, the user and the cluster management master node 12 are specifically used to perform the user node login verification:

[0088] Step C1, receiving a first node login verification request sent by the first master node 21 of any first roadside node cluster 2; and using the current first master node 21 as the corresponding current cluster master node;

[0089] The first node login verification request includes a first login cluster identifier, a first login node identifier, a first login user name, and a first login user password;

[0090] Step C2, taking the first user registration record in the user registration information table of the user database 111, in which the first user name matches the first login user name and the first user password matches the first login user password, as the corresponding current user registration record; and identifying whether the current user registration record is empty; if the current user registration record is empty, setting the corresponding first user verification status to an unauthorized user, and going to step C4; if the current user registration record is not empty, going to step C3;

[0091] Step C3, taking the first user permission record in which the second user identifier in the user permission information table of the user database 111 matches the first user identifier of the current user registration record as the corresponding current user permission record; and taking the authorization cluster information in which the authorization cluster identifier in the first authorization resource set of the current user permission record matches the first login cluster identifier as the corresponding current authorization cluster information; and identifying whether the current authorization cluster information is empty; if the current authorization cluster information is empty, setting the corresponding first user verification status to an unauthorized user; if the current authorization cluster information is not empty, identifying whether the authorization node set of the current authorization cluster information contains the first login node identifier, if not, setting the corresponding first user verification status to an unauthorized user, and if so, setting the corresponding first user verification status to an authorized user; wherein the first user verification status includes an authorized user and an unauthorized user;

[0092] Step C4, using the first login cluster identifier and the first login node identifier as the corresponding first verification cluster identifier and the first verification node identifier; and sending back a corresponding first verification request feedback composed of the first verification cluster identifier, the first verification node identifier and the first user verification status to the current cluster master node.

[0093] It should be noted that the node resource management types of the user and cluster management master node 12 in the embodiment of the present invention include node purchase, node query, cluster allocation, fault marking, repair marking, label marking, and label revocation. Specifically, in another specific implementation of the embodiment of the present invention, the user and cluster management master node 12 are specifically used to:

[0094] Step D1, receiving a first node management application submitted by a third management interface;

[0095] Here, the third management interface of the embodiment of the present invention includes an administrator, any management user who obtains node management authority, and any system processing interface that obtains node management authority; the first node management application includes a first management type and a first management parameter; the first management type includes node purchase, node query, cluster allocation, fault marking, repair marking, label marking, and label revocation;

[0096] When the first management type is node purchase, the first management parameter includes one or more first physical host / virtual machine purchase information; the first physical host / virtual machine purchase information includes the first physical host / virtual machine purchase time and the first physical host / virtual machine basic information;

[0097] When the first management type is node query, the first management parameter includes a first query mode and a first query parameter; the first query mode includes a first mode, a second mode and a third mode; when the first query mode is the first mode, the first query parameter is empty; when the first query mode is the second mode, the first query parameter consists of one or more first query cluster identifiers; when the first query mode is the third mode, the first query parameter consists of one or more first query node identifiers;

[0098] When the first management type is cluster allocation, the first management parameter includes one or more first allocation parameters; the first allocation parameter consists of the first allocation type, the first allocation cluster identifier, and one or more first allocation node identifiers; the first allocation type includes a master node type and a working node type; when the first allocation type is a master node type, the number of corresponding first allocation node identifiers is unique;

[0099] When the first management type is a fault mark, the first management parameter includes one or more first fault node identifiers;

[0100] When the first management type is a repair mark, the first management parameter includes one or more first repair node identifiers;

[0101] When the first management type is label annotation, the first management parameter includes one or more first annotation parameters; the first annotation parameter consists of a first annotation node identifier and a first annotation label set; the first annotation label set consists of one or more second label information; the second label information consists of a second label type and a second label value; the second label type includes a regional label, a security domain label, an organization label and an application label; when the second label type is a regional label, the corresponding second label value is a regional name; when the second label type is a security domain label, the corresponding second label value is a security domain name; when the second label type is an organization label, the corresponding second label value is an organization name; when the second label type is an application label, the corresponding second label value is an application image and version name;

[0102] When the first management type is label revocation, the first management parameter includes one or more first revocation parameters; the first revocation parameter consists of a first revocation node identifier and a first revocation label set; the first revocation label set consists of one or more third label information; the third label information consists of a third label type and a third label value; the third label type includes a regional label, a security domain label, an organization label and an application label; when the third label type is a regional label, the corresponding third label value is a regional name; when the third label type is a security domain label, the corresponding third label value is a security domain name; when the third label type is an organization label, the corresponding third label value is an organization name; when the third label type is an application label, the corresponding third label value is an application image and version name;

[0103] Step D2, if the first management type is node purchase, then each first physical host / virtual machine purchase information in the first management parameter is used as the corresponding current purchase information; and a unique node identifier is assigned to the current purchase information as the corresponding current node identifier; and a first node resource record is added to the node resource information table of the cluster database 112 as the corresponding current node resource record; and the first node identifier of the current node resource record is set to the corresponding current node identifier, the first node purchase time is set to the first physical host / virtual machine purchase time of the current purchase information, the first node basic information is set to the first physical host / virtual machine basic information of the current purchase information, the first node working condition is set to idle, the first node allocation type is set to empty, the first belonging cluster identifier is set to empty, and the first node label set is set to empty; and after the first node resource records corresponding to all the first physical host / virtual machine purchase information of the current first management parameter are completed with record addition and setting, the corresponding first management application feedback is set to success;

[0104] Step D3, if the first management type is node query, the first query mode and the first query parameter of the first management parameter are used as the corresponding current query mode and current query parameter; and the previous query mode is identified; if the previous query mode is the first mode, the node resource information table is used as the corresponding first management application feedback; if the previous query mode is the second mode, each first query cluster identifier in the current query parameter is used as the corresponding current cluster identifier, and all first node resource records in the node resource information table that match the first belonging cluster identifier and the current cluster identifier are extracted to form a corresponding first node query list, and each first query cluster identifier and its corresponding first node query list form a corresponding first cluster query result, and all the first cluster query results obtained this time form the corresponding first management application feedback; if the previous query mode is the third mode, the first node resource record in the node resource information table that matches the first node identifier and each first query node identifier of the current query parameter is recorded as the corresponding query matching record, and all the query matching records obtained this time form the corresponding first management application feedback;

[0105] Step D4, if the first management type is cluster allocation, then each first allocation parameter of the first management parameter is used as the corresponding current allocation parameter; and the first node resource record whose first node identifier in the node resource information table matches each first allocation node identifier of the current allocation parameter is recorded as the corresponding allocation node record, and the first node working conditions of all allocation node records corresponding to the current allocation parameter are reset to occupied, and the first node allocation type of all allocation node records corresponding to the current allocation parameter is reset to the first allocation type of the current allocation parameter, and the first belonging cluster identifier of all allocation node records corresponding to the current allocation parameter is reset to the first allocation cluster identifier of the current allocation parameter; and when the record information reset of all node resource records corresponding to the current allocation parameter is completed, the first cluster identifier in the cluster deployment information table of the cluster database 112 is matched with the current The first cluster deployment record that matches the first allocation cluster identifier of the allocation parameter is the corresponding current cluster deployment record; and when the first allocation type of the current allocation parameter is the master node type, the first master node configuration of the current cluster deployment record is set to the first allocation node identifier that is unique in the current allocation parameter; and when the first allocation type of the current allocation parameter is the working node type, the first working node configuration set of the current cluster deployment record and all the first allocation node identifiers in the current allocation parameters are subjected to node identifier deduplication and merging processing to obtain a corresponding node identifier collection, and the first working node configuration set of the current cluster deployment record is reset to the corresponding node identifier collection; and when the reset of the record information of all node resource records corresponding to all the first allocation parameters of the current first management parameter and all cluster deployment records is completed, the corresponding first management application feedback is set to success;

[0106] Step D5, if the first management type is a fault mark, each first fault node identifier of the first management parameter is used as the corresponding current fault node identifier; and the first node working condition of the first node resource record whose first node identifier matches the current fault node identifier in the node resource information table is reset to fault; and when the reset of the record information of all node resource records corresponding to all first fault node identifiers of the current first management parameter is completed, the corresponding first management application feedback is set to success;

[0107] Step D6, if the first management type is a repair mark, each first repair node identifier of the first management parameter is used as the corresponding current repair node identifier; and the first node working condition of the first node resource record whose first node identifier matches the current repair node identifier in the node resource information table is reset to occupied; and when the reset of the record information of all node resource records corresponding to all first repair node identifiers of the current first management parameter is completed, the corresponding first management application feedback is set to success;

[0108] Step D7, if the first management type is label labeling, then each first labeling parameter of the first management parameter is used as the corresponding current labeling parameter; and the first node resource record whose first node identifier in the node resource information table matches the first labeling node identifier of the current labeling parameter is recorded as the corresponding current labeling node record; and the first node label set of the current labeling node record and the first labeling label set of the current labeling parameter are subjected to label deduplication and merging processing to obtain a corresponding label collection; and the first node label set of the current labeling node record is reset to the corresponding label collection; and when the record information reset of all node resource records corresponding to all first labeling parameters of the current first management parameter is completed, the corresponding first management application feedback is set to success;

[0109] Step D8, if the first management type is label revocation, each first revocation parameter of the first management parameter is used as the corresponding current revocation parameter; and the first node resource record whose first node identifier in the node resource information table matches the first labeled node identifier of the current revocation parameter is recorded as the corresponding current revocation node record; and all first label information corresponding to the first revocation label set of the current revocation parameter in the first node label set of the current revocation node record is deleted; and when the record information reset of all node resource records corresponding to all first revocation parameters of the current first management parameter is completed, the corresponding first management application feedback is set to success;

[0110] Step D9: Feedback the first management application obtained this time to the third management interface.

[0111] It should be noted that the management types of the roadside cluster management of the user and the cluster management master node 12 in the embodiment of the present invention include cluster creation, cluster query, cluster regional deployment, cluster security domain deployment, and cluster deletion. Specifically, in another specific implementation of the embodiment of the present invention, the user and the cluster management master node 12 are specifically used to perform roadside cluster management:

[0112] Step E1, receiving a first cluster management application submitted by a fourth management interface;

[0113] Here, the fourth management interface of the embodiment of the present invention includes an administrator, any management user who obtains cluster management authority, and any system processing interface that obtains cluster management authority; the first cluster management application includes a second management type and a second management parameter; the second management type includes cluster creation, cluster query, cluster regional deployment, cluster security domain deployment, and cluster deletion;

[0114] When the second management type is cluster creation, the second management parameter includes one or more first newly created cluster information; the first newly created cluster information includes the first newly created cluster name and the first newly created cluster basic information;

[0115] When the second management type is cluster query, the second management parameter includes a second query mode and a second query parameter; the second query mode includes a fourth mode and a fifth mode; when the second query mode is the fourth mode, the second query parameter is empty; when the second query mode is the fifth mode, the second query parameter consists of one or more second query cluster identifiers;

[0116] When the second management type is cluster regional deployment, the second management parameter includes one or more first regional deployment parameters; the first regional deployment parameter consists of a first deployment cluster identifier and one or more first regional names;

[0117] When the second management type is cluster security domain deployment, the second management parameter includes one or more first security domain deployment parameters; the first security domain deployment parameters are composed of the second deployment cluster identifier and one or more first security domain names;

[0118] When the second management type is cluster deletion, the second management parameter includes one or more first deletion cluster identifiers;

[0119] Step E2, if the second management type is cluster creation, then each first newly created cluster information of the second management parameter is used as the corresponding current newly created cluster information; and a unique cluster identifier is assigned to the current newly created cluster information as the corresponding current cluster identifier; and the current time is used as the corresponding current cluster creation time; and a first cluster deployment record is added to the cluster deployment information table of the cluster database 112 as the corresponding current cluster deployment record; and the first cluster identifier of the current cluster deployment record is set to the corresponding current cluster identifier, the first cluster name is set to the first newly created cluster name of the current newly created cluster information, the first cluster creation time is set to the corresponding current cluster creation time, the first cluster basic information is set to the first newly created cluster basic information of the current newly created cluster information, the first cluster working condition is set to normal, the first master node configuration is set to empty, the first working node configuration set is set to empty, the first regional deployment configuration is set to empty, and the first security domain deployment configuration is set to empty; and when the record addition and record information setting of all cluster deployment records corresponding to all the first newly created cluster information of the current second management parameter are completed, the corresponding second management application feedback is set to success;

[0120] Step E3, if the second management type is cluster query, the second query mode and the second query parameter of the second management parameter are used as the corresponding current query mode and current query parameter; and the previous query mode is identified; if the previous query mode is the fourth mode, the cluster deployment information table is used as the corresponding second management application feedback; if the previous query mode is the fifth mode, the first cluster deployment record that matches the first cluster identifier in the cluster deployment information table with each second query cluster identifier in the current query parameter is extracted to form the corresponding second management application feedback;

[0121] Step E4, if the second management type is cluster regional deployment, then each first regional deployment parameter of the second management parameter is used as the corresponding current regional deployment parameter; and the first cluster deployment record that matches the first cluster identifier of the cluster deployment information table with the first deployment cluster identifier of the current regional deployment parameter is used as the corresponding current cluster deployment record; and the first regional deployment configuration of the current cluster deployment record and all the first regional names of the current regional deployment parameter are deduplicated and merged to obtain a corresponding regional name collection; and the first regional deployment configuration of the current cluster deployment record is reset to the corresponding regional name collection; and when the record information settings of all cluster deployment records corresponding to all the first regional deployment parameters of the current second management parameter are completed, the corresponding second management application feedback is set to success;

[0122] Step E5, if the second management type is cluster security domain deployment, then each first security domain deployment parameter of the second management parameter is used as the corresponding current security domain deployment parameter; and the first cluster deployment record that matches the first cluster identifier of the cluster deployment information table with the second deployment cluster identifier of the current security domain deployment parameter is used as the corresponding current cluster deployment record; and the first security domain deployment configuration of the current cluster deployment record and all the first security domain names of the current security domain deployment parameter are deduplicated and merged to obtain a corresponding security domain name collection; and the first security domain deployment configuration of the current cluster deployment record is reset to the corresponding security domain name collection; and when the record information settings of all cluster deployment records corresponding to all the first security domain deployment parameters of the current second management parameter are completed, the corresponding second management application feedback is set to success;

[0123] Step E6, if the second management type is cluster deletion, each first deletion cluster identifier of the second management parameter is used as the corresponding current deletion cluster identifier; and the first cluster deployment record matching the first cluster identifier of the cluster deployment information table with the current deletion cluster identifier is deleted; and after all cluster deployment records corresponding to all first deletion cluster identifiers of the current second management parameter are successfully deleted, the corresponding second management application feedback is set to success;

[0124] Step E7: Feedback the second management application obtained this time to the fourth management interface.

[0125] In another specific implementation of the embodiment of the present invention, the user and cluster management master node 12 are specifically used for: when performing roadside cluster monitoring: regularly group-send inspection signals to the first master nodes 21 of all first roadside node clusters 2 according to the preset first inspection frequency; and after the group sending of the inspection signal is completed, wait for the inspection report reception according to the preset first waiting time; and when the waiting time does not exceed the first waiting time, each time a first cluster monitoring report sent by the first master node 21 is received, the first cluster identifier corresponding to the first roadside node cluster 2 corresponding to the current first master node 21 is used as the corresponding first monitoring cluster identifier, and the current time is used as the corresponding first monitoring time, and a corresponding first cluster monitoring log composed of the current first cluster monitoring report, the corresponding first monitoring time and the first monitoring cluster identifier is added to the cluster monitoring information table; and when the waiting time exceeds the first waiting time, the inspection report reception wait is terminated, and a round of cluster and node status update processing is performed based on all the first cluster monitoring logs added this time. Here, the first inspection frequency is a preset time frequency parameter, and the first waiting time is a preset time length parameter.

[0126] In another specific implementation method of an embodiment of the present invention, the user and the cluster management master node 12 are specifically used to perform a round of cluster and node status update processing based on all the first cluster monitoring logs added this time: deduplicate and merge the first monitoring cluster identifiers of the first cluster monitoring reports of all the first cluster monitoring logs added this time to obtain a corresponding cluster identifier collection; and set the first cluster operating condition of the first cluster deployment record in the cluster deployment information table of the cluster database 112 where the first cluster identifier does not appear in the cluster identifier collection to abnormal; and set the first cluster operating condition of the first cluster deployment record in the cluster deployment information table of the cluster database 112 where the first cluster identifier appears in the cluster identifier collection to normal; and deduplicate and merge the first monitoring node identifiers of the first cluster monitoring reports of all the first cluster monitoring logs added this time to obtain a corresponding node identifier collection; and set the first node operating condition of the first node resource record in the node resource information table of the cluster database 112 where the first node identifier does not appear in the node identifier collection to fault; and set the first node operating condition of the first node resource record in the node resource information table of the cluster database 112 where the first node identifier appears in the node identifier collection to occupied.

[0127] In another specific implementation of the embodiment of the present invention, the application warehouse management master node 13 is specifically used to:

[0128] Step F1, receiving a first application management application submitted by a fifth management interface;

[0129] The fifth management interface includes an administrator, any management user who obtains the application image management authority, and any system processing interface that obtains the application image management authority; the first application management application includes a third management type and a third management parameter; the third management type includes application listing, application query, application delisting, and application version update;

[0130] When the third management type is application launch, the third management parameters include the first launch application image name, the first launch application image basic information, the first launch application version and the first launch version software package;

[0131] When the third management type is application query, the third management parameter is empty;

[0132] When the third management type is application removal, the third management parameter includes the first removed application image identifier, the first removal mode and the first removed application version; the first removal mode includes the sixth mode and the seventh mode; when the first removal mode is the sixth mode, the first removed application version is empty; when the first removal mode is the seventh mode, the first removed application version is a specified application version of the current application image;

[0133] When the third management type is application version update, the third management parameter includes the first updated application image identifier, the first updated application version and the first updated version software package;

[0134] Step F2, if the third management type is application listing, the first listing application image name, the first listing application image basic information, the first listing application version and the first listing version software package of the third management parameter are used as the corresponding current application image name, the current application image basic information, the current application version and the current software package; and a corresponding unique identifier is assigned to the current application image as the corresponding current application image identifier; and a first application image record is added to the application image information table of the application database 113 as the corresponding current newly added record; and the first application image identifier of the current newly added record is set to the corresponding current application image identifier, the first application image name is set to the corresponding current application image name, the first application image basic information is set to the corresponding current application image basic information, the first application version is set to the corresponding current application version, and the first version software package is set to the corresponding current software package; and when the record addition and record setting of the application image record corresponding to the current third management parameter are completed, the corresponding third management application feedback is set to success;

[0135] Step F3: if the third management type is application query, the application image information table is used as the corresponding third management application feedback;

[0136] Step F4, if the third management type is application delisting, the first delisted application image identifier, the first delisting mode and the first delisted application version of the third management parameter are used as the corresponding current application image identifier, the current delisting mode and the current application version; and the current delisting mode is identified; if the current delisting mode is the sixth mode, all first application image records in the application image information table whose first application image identifier matches the current application image identifier are deleted; if the current delisting mode is the seventh mode, the first application image record in the application image information table whose first application image identifier matches the current application image identifier and whose first application version matches the current application version is deleted; and when the record deletion of all application image records corresponding to the current third management parameter is completed, the corresponding third management application feedback is set to success;

[0137] Step F5, if the third management type is application version update, the first updated application image identifier, the first updated application version and the first updated version software package in the third management parameter are used as the corresponding current application image identifier, the current application version and the current software package; the first application image record in the application image information table whose first application image identifier matches the current application image identifier and whose addition time is the earliest is used as the corresponding current root record; and the first application image name and the first application image basic information of the current root record are used as the corresponding current application image name and the current application image basic information; and the first application image record in the application image information table whose first application image identifier matches the current application image identifier and whose first application version matches the current application version is used as the corresponding current matching record; and the current matching record is empty for identification; if the current matching record is empty, a first application image record is added to the application image information table of the application database 113 as the corresponding current newly added record, and the first application image identifier, the first application image name, the first application image basic information, the first application version and the first version software package of the current newly added record are set to the corresponding current application image identifier, the current application image name, the current application image basic information, the current application version and the current software package; if the current matching record is not empty, the first application version and the first version software package of the current matching record are reset to the corresponding current application version and the current software package; and when the record addition or record update operation of the application image record corresponding to the current third management parameter is completed, the corresponding third management application feedback is set to success;

[0138] Step F6: Feedback the third management application obtained this time to the fifth management interface.

[0139] In another specific implementation of the embodiment of the present invention, the application deployment master node 14 is specifically used to manage the application deployment solution:

[0140] Step G1, receiving a first solution management application submitted by a sixth management interface;

[0141] Here, the sixth management interface includes an administrator, any management user who obtains application deployment authority, and any system processing interface who obtains application deployment authority; the first solution management application includes a fourth management type and a fourth management parameter; the fourth management type includes solution submission / update and solution query;

[0142] When the fourth management type is plan submission / update, the fourth management parameter includes a submitted plan identifier, a planned start time, an application deployment information set, and a node screening condition; the application deployment information set includes one or more application deployment information; the application deployment information consists of a corresponding application image name and an application version;

[0143] When the fourth management type is solution query, the fourth management parameter includes the third query mode and the third query parameter; the third query mode includes the eighth mode and the ninth mode; when the third query mode is the eighth mode, the third query parameter is empty; when the third query mode is the ninth mode, the third query parameter consists of one or more query solution identifiers;

[0144] Step G2, if the fourth management type is solution submission / update, then the submission solution identifier, planned startup time, application deployment information set and node screening condition of the fourth management parameter are used as the corresponding current solution identifier, current solution startup time, current application deployment information set and current node screening condition; and the first application deployment solution in the application deployment solution information table of the application database 113 whose first solution identifier matches the current solution identifier and whose first deployment state is not started is used as the corresponding matching deployment solution; and whether the matching deployment solution is empty is identified; if the matching deployment solution is empty, a new first application deployment solution is added to the application deployment solution information table as the corresponding current deployment solution, and the current deployment solution is The first scheme identifier, the first scheme start time, the first deployment configuration and the first node screening condition of the scheme are set to the corresponding current scheme identifier, the current scheme start time, the current application deployment information set and the current node screening condition, and the first deployment state of the current deployment scheme is set to not started, and the first failed node set of the current deployment scheme is set to empty; if the current matching record is not empty, the first scheme start time, the first deployment configuration and the first node screening condition of the current matching record are updated to the corresponding current scheme start time, the current application deployment information set and the current node screening condition; and when the application deployment scheme corresponding to the current fourth management parameter is added or updated, the corresponding fourth management application feedback is set to success;

[0145] Step G3, if the fourth management type is solution query, the third query mode and the third query parameter of the fourth management parameter are used as the corresponding current query mode and current query parameter; and the current query mode is identified; if the current query mode is the eighth mode, the application deployment solution information table is used as the corresponding fourth management application feedback; if the current query mode is the ninth mode, the first application deployment solution whose first solution identifier in the application deployment solution information table matches each query solution identifier of the third query parameter is extracted to form the corresponding fourth management application feedback;

[0146] Step G4: Feedback the fourth management application obtained this time to the sixth management interface.

[0147] In another specific implementation of the embodiment of the present invention, the application deployment master node 14 is specifically used to:

[0148] Step H1, regularly taking the first application deployment schemes in the application deployment scheme information table of the application database 113 whose first scheme startup time is not later than the current time and whose first deployment status is not started as the corresponding first inspection schemes according to the preset first time frequency; and taking the first inspection scheme with the earliest first scheme startup time as the corresponding current configuration scheme; and initializing the first counter to 0;

[0149] Here, the first time frequency is a preset time frequency parameter;

[0150] Step H2, extracting the first version software package of the first application image record whose first application image name and first application version satisfy the first deployment configuration of the current configuration scheme in the application image information table of the application database 113 to form a corresponding first software set;

[0151] Step H3, extracting the first node identifiers of the first node resource records that meet the first node screening condition of the current configuration scheme in the node resource information table of the cluster database 112 to form a corresponding first node identifier set;

[0152] Step H4, the first node identifiers in the first node identifier set belonging to the same first roadside node cluster 2 are grouped into one category to form a corresponding first node identifier group; and the working node groups corresponding to each first node identifier group are recorded as corresponding first node groups; and the first master nodes 21 of the first roadside node cluster 2 where each first node group is located are taken as corresponding second master nodes;

[0153] Step H5, and establish a corresponding remote control channel recorded as a first remote control channel through each second master node and each first working node 22 of the corresponding first node group; and transmit the first software set to the corresponding first working node 22 through each first remote control channel, and after the software set transmission is completed, all application images included in the first software set are created and run on the corresponding first working node 22 through each first remote control channel to obtain a corresponding first processing result; and identify whether each first processing result is successful, if the current first processing result is successful, the software package set is deleted on the corresponding first working node 22 through the corresponding first remote control channel, if the current first processing result is a failure, the software package set is deleted, the application image instance is cleared, and the corresponding node resource release processing is performed on the corresponding first working node 22 through the corresponding first remote control channel; and all first remote control channels are closed;

[0154] The first processing result includes success and failure;

[0155] Step H6, and identify all the first processing results obtained; if all the first processing results are successful or failed, set the corresponding current deployment state to all success or all failure, and go to step H7; if all the first processing results are partially successful and partially failed, set the corresponding current deployment state to partially failed, and form a new first node identifier set from the first node identifiers corresponding to all the first processing results that are specifically failed, and add 1 to the first counter, and identify whether the first counter after adding 1 exceeds the preset first counter threshold, if so, go to step H7, if not, return to step H4 after waiting for the preset first time length;

[0156] Here, the first counter threshold is a preset threshold parameter; the first duration is a preset time length parameter;

[0157] Step H7, identify the latest current deployment status; if the current deployment status is full success, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full node deployment success; if the current deployment status is full failure or partial failure, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full node deployment failure or partial node deployment failure, and set the first failed node set of the current configuration scheme to the latest first node identification set.

[0158] In another specific implementation of the embodiment of the present invention, the application operation and maintenance master node 15 is specifically used to:

[0159] Step J1, regularly extracting first cluster identifiers of first cluster deployment records with a first cluster operating condition being normal from the cluster deployment information table of the cluster database 112 at a preset second time frequency to form a corresponding first cluster identifier set;

[0160] Here, the second time frequency is a preset time frequency parameter;

[0161] Step J2, extracting the first cluster monitoring report of the first cluster monitoring log whose first monitoring time is closest to the current time and whose first monitoring cluster identifier in the cluster monitoring information table of the cluster database 112 matches each first cluster identifier of the first cluster identifier set to form a corresponding first cluster monitoring report set;

[0162] Step J3, extracting the first monitoring node report in which at least one first application information application usage status is abnormal suspension or loading failure from the first cluster monitoring report set to form a corresponding first monitoring node report set;

[0163] Step J4, when the first monitoring node report set is not empty, the first monitoring node identifier, application image and version name, and application usage status corresponding to the first application information of each application usage status of abnormal suspension or loading failure in the current first monitoring node report set are used as the corresponding first abnormal node identifier, first abnormal application information, and first abnormal status to form a corresponding abnormal node application record; and all the obtained abnormal node application records form a corresponding abnormal node application report;

[0164] Step J5, when the abnormal node application report is not empty, the abnormal node application report is sent to the preset abnormal node application warning interface; and each abnormal node application record is used as the corresponding current record; and the first abnormal node identifier, the first abnormal application information and the first abnormal state of the current record are used as the corresponding current node identifier, the current abnormal application information and the current abnormal state; and the first working node 22 corresponding to the current node identifier is used as the corresponding current working node; and the first belonging cluster identifier of the first node resource record whose first node identifier in the node resource information table of the cluster database 112 matches the current node identifier is used as the corresponding current cluster identifier; and the first master node 21 corresponding to the first master node configuration of the first cluster deployment record whose first cluster identifier in the cluster deployment information table of the cluster database 112 matches the current cluster identifier is used as the corresponding current master node; and a corresponding remote control channel is established between the current master node and the current working node Recorded as the corresponding current remote control channel; and identify the current abnormal state; if the current abnormal state is loading failure, the first application image name and the first application version in the application image information table of the application database 113 are extracted from the first version software package of the first application image record corresponding to the current abnormal application information as the corresponding current software package, and the application image instance corresponding to the current abnormal application information is cleared and the corresponding node resources are released on the current working node through the current remote control channel, and the current software package is transmitted to the current working node through the current remote control channel, and after the software package transmission is completed, the image instance of the application image corresponding to the current software package is rebuilt and run on the current working node through the current remote control channel; if the current abnormal state is abnormal suspension, the application image instance corresponding to the current abnormal application information is restarted on the current working node through the current remote control channel; and the current remote control channel is closed.

[0165] Here, the abnormal node application warning interface is a pre-set warning interface set, which consists of one or more user warning interfaces. Each user warning interface corresponds to a staff member responsible for system management / operation / maintenance. The interface type of each user warning interface can be an email interface type, a SMS interface type, a voice interface type, an office platform / system interface type, an instant messaging software interface type, etc.

[0166] (II) First roadside node cluster 2:

[0167] The first roadside node cluster 2 of the embodiment of the present invention is composed of a first master node 21 and multiple first working nodes 22; the first master node 21 is connected to each first working node 22 respectively; the first master node 21 is also connected to the user and cluster management master node 12, the application deployment master node 14 and the application operation and maintenance master node 15 respectively.

[0168] The first master node 21 of the embodiment of the present invention is used to send a patrol signal to all corresponding first working nodes 22 when receiving the patrol signal; and after the patrol signal is sent in batches, the corresponding first cluster monitoring report is initialized to be empty, and the patrol report reception wait is performed according to the preset second waiting time; and when the waiting time does not exceed the second waiting time, each time a first node monitoring log sent by the first working node 22 is received, the current first node monitoring log is added to the first cluster monitoring report; and when the waiting time exceeds the second waiting time, the patrol report reception wait is terminated, and the latest first cluster monitoring report is sent to the user and the cluster management master node 12. Here, the second waiting time is a preset time length parameter, and 0<second waiting time<first waiting time.

[0169] The first working node 22 of the embodiment of the present invention is used to receive the login user name and login user password input by the current user as the corresponding first login user name and first login user password when the user logs in to the node; and use the belonging cluster identification information and node identification information stored locally in the node as the corresponding first login cluster identification and first login node identification; and the first login cluster identification, the first login node identification, the first login user name and the first login user password form a corresponding first node login verification request; and send the first node login verification request to the user and cluster management master node 12 through the corresponding first master node 21; and receive the first verification request feedback sent back by the user and the cluster management master node 12 through the corresponding first master node 21; and The first verification cluster identifier, the first verification node identifier and the first user verification status in the verification request feedback are identified; if the first verification cluster identifier matches the belonging cluster identifier information stored locally at the node and the first verification node identifier matches the node identifier information stored locally at the node and the first user verification status is an authorized user, a login success message is fed back to the current login and the current logged-in user is allowed to use the local node resources; if the first verification cluster identifier does not match the belonging cluster identifier information stored locally at the node, or the first verification node identifier does not match the node identifier information stored locally at the node, or the first user verification status is an unauthorized user, a login failure message is fed back to the current login and the current logged-in user is prohibited from using the local node resources.

[0170] The first working node 22 of the embodiment of the present invention is also used to, when receiving a patrol signal, summarize all local resource information to obtain a corresponding first monitoring node report; and use the node identification information stored locally as the corresponding first monitoring node identification; and the first monitoring node identification and the first monitoring node report form a corresponding first node monitoring log and send it to the corresponding first master node 21.

[0171] It should also be noted that the division of the various system components / modules of the above system can be regarded as a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these system components / modules can all be implemented in the form of software calling through processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the user and cluster management master node can be separately established processing elements, or they can be integrated in a chip of the above system for implementation. In addition, they can also be stored in the memory of the above system in the form of program code, and called and executed by a processing element of the above system. The implementation of other system components / modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, the processing steps of each module of the aforementioned system can be completed by the hardware integrated logic circuit in the processor element or the instructions in the form of software.

[0172] For example, the system components / modules of the above system may be one or more integrated circuits configured to implement the functions of the corresponding components / modules, such as: one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a system component / module of the above system is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0173] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the above system are generated. The above computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The above-mentioned computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the above-mentioned computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, Bluetooth, microwave, etc.) methods. The above-mentioned computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The above-mentioned available medium can be a magnetic medium (such as a floppy disk, a hard disk, a tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0174] In summary, an embodiment of the present invention provides a roadside node cluster management system; as can be seen from the above content, the system includes: a first management cluster and multiple first roadside node clusters; each first roadside node cluster is composed of a first master node and multiple first working nodes connected to the master node; the first management cluster includes cluster storage, user and cluster management master node, application warehouse management master node, application deployment master node and application operation and maintenance master node; wherein, the cluster storage includes a user database (for storing user registration information table and user authority information table), a cluster database (for storing node resource information table, cluster deployment information table and cluster monitoring information table) and an application database (for storing application image information table and application deployment plan information table); the user and cluster management master node is used for user registration management, user node authority allocation, user node login verification, node resource management, roadside cluster management and roadside cluster monitoring; the application warehouse management master node is used for application delisting and application version update processing; the application deployment master node is used for application deployment plan management and roadside node application configuration; the application operation and maintenance master node is used for roadside node application monitoring processing. The embodiments of the present invention not only enhance the monitoring capability of the system on the roadside nodes, but also improve the personalized configuration / management capability of the system on the roadside nodes.

[0175] The professionals should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0176] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0177] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A roadside node cluster management system, characterized in that: The system comprises: a first management cluster and a plurality of first roadside node clusters; The first management cluster is connected to each of the first roadside node clusters respectively; The first management cluster includes cluster storage, a user and cluster management master node, an application warehouse management master node, an application deployment master node and an application operation and maintenance master node; the user and cluster management master node, the application warehouse management master node, the application deployment master node and the application operation and maintenance master node are respectively connected to the cluster storage; the cluster storage includes a user database, a cluster database and an application database; The user database is used to store a user registration information table and a user authority information table; the cluster database is used to store a node resource information table, a cluster deployment information table and a cluster monitoring information table; the application database is used to store an application image information table and an application deployment solution information table; The user and cluster management master node is used for user registration management; the user and cluster management master node is also used for user node authority allocation; the user and cluster management master node is also used for user node login verification; the user and cluster management master node is also used for node resource management; the user and cluster management master node is also used for roadside cluster management; the user and cluster management master node is also used for roadside cluster monitoring; the application warehouse management master node is used for application on-shelf and off-shelf and application version update processing; the application deployment master node is used for application deployment plan management; the application deployment master node is also used for roadside node application configuration; the application operation and maintenance master node is used for roadside node application monitoring processing; The first roadside node cluster consists of a first master node and multiple first working nodes; the first master node is connected to each of the first working nodes respectively; the first master node is also connected to the user and cluster management master node, the application deployment master node and the application operation and maintenance master node respectively.

2. The roadside node cluster management system according to claim 1, characterized in that: The user registration information table includes a plurality of first user registration records; the first user registration records correspond to registered users one by one; the first user registration record includes at least a first user identifier, a first user name, a first user password, a first user identity identifier, a first user type and a first affiliated organization; the first user identity identifier is the unique identity identifier information of the current registered user; the first user type includes individual users and institutional users; when the first user type is an individual user, the first affiliated organization is empty; when the first user type is an institutional user, the first affiliated organization is the name of the organization to which the current user belongs; The user authority information table includes a plurality of first user authority records; the first user authority record corresponds one-to-one with the first user registration record; the first user authority record includes a second user identifier and a first authorized resource set; the first and second user identifiers correspond one-to-one; the first authorized resource set, when not empty, is composed of one or more authorized cluster information; the authorized cluster information is composed of an authorized cluster identifier and an authorized node set; the authorized node set is composed of one or more authorized node identifiers; The node resource information table includes a plurality of first node resource records; The first node resource record includes a first node identifier, a first node purchase time, first node basic information, a first node operating condition, a first node allocation type, a first cluster identifier and a first node label set; each of the first node resource records corresponds to a node resource, and each node resource is a physical host or a virtual machine; the first node basic information includes at least all software and hardware configuration information and network configuration information of the current node resource; the first node operating condition includes idle, occupied and faulty; when the first node operating condition is idle, the first node allocation type, the first cluster identifier and the first node label set are all empty; when the first node operating condition is occupied or faulty, the first node allocation type includes a master node type and a working node type, and the first cluster identifier and the first node label set are all empty. The cluster identifier is the cluster identifier of the cluster to which the current node resource belongs, and the first node label set is composed of one or more first label information; the first label information is composed of a first label type and a first label value; the first label type includes a regional label, a security domain label, an organization label and an application label; when the first label type is a regional label, the first label value is the corresponding regional name; when the first label type is a security domain label, the first label value is the corresponding security domain name; when the first label type is an organization label, the first label value is the corresponding organization name; when the first label type is an application label, the first label value is the corresponding application image and version name, and the application image and version name is composed of the corresponding application image name and application version; The cluster deployment information table includes a plurality of first cluster deployment records; The first cluster deployment record corresponds to the first roadside node cluster one by one; the first cluster deployment record includes a first cluster identifier, a first cluster name, a first cluster creation time, first cluster basic information, a first cluster working condition, a first master node configuration, a first working node configuration set, a first regional deployment configuration, and a first security domain deployment configuration; The first cluster basic information includes at least cluster storage configuration information and cluster network configuration information of the current roadside node cluster; The first cluster operating condition includes normal and fault; the first master node configuration corresponds to the first master node of the current roadside node cluster; The first master node is configured as the first node identifier corresponding to the corresponding first master node; The first working node configuration set is composed of a plurality of first working node configurations; the first working node configuration corresponds one-to-one to the first working node of the current roadside node cluster; the first working node configuration is the first node identifier corresponding to the corresponding first working node; The first regional deployment configuration is the regional configuration information of the current roadside node cluster, which is composed of one or more regional names; the first security domain deployment configuration is the security domain configuration information of the current roadside node cluster, which is composed of one or more security domain names; The cluster monitoring information table is composed of a plurality of first cluster monitoring logs; the first cluster monitoring log includes a first monitoring time, a first monitoring cluster identifier and a first cluster monitoring report; The first monitoring cluster identifier is the first cluster identifier corresponding to the first roadside node cluster; The first cluster monitoring report is composed of multiple first node monitoring logs; the first node monitoring log includes a first monitoring node identifier and a first monitoring node report; the first monitoring node identifier corresponds one-to-one to the first working node under the first roadside node cluster corresponding to the current first monitoring cluster identifier, and the first monitoring node identifier is the first node identifier corresponding to the corresponding first working node; the first monitoring node report includes at least first CPU information, first GPU information, first memory information, first hard disk information and first application information set; the first CPU information includes CPU manufacturer information and CPU usage; the first GPU information includes GPU manufacturer information and GPU usage; the first memory information includes memory manufacturer information, total memory capacity and memory usage; the first hard disk information includes hard disk manufacturer information, total hard disk storage capacity and hard disk storage usage; the first application information set includes multiple first application information; the first application information includes application image and version name and application usage status; the application usage status includes normal use, normal idle, abnormal suspension and loading failure; The application image information table includes multiple first application image records; each of the first application image records corresponds to an application image; the first application image record includes a first application image identifier, a first application image name, first application image basic information, a first application version and a first version software package; the first application image name is the application image name of the current application image; The first application image basic information includes at least algorithm / software developer information and algorithm / software function summary information of the current application image; The application deployment scheme information table includes multiple first application deployment schemes; the first application deployment scheme includes a first scheme identifier, a first scheme startup time, a first deployment configuration, a first node screening condition, a first deployment state and a first failed node set; the first deployment configuration is composed of one or more first application deployment information, and the first application deployment information is composed of a corresponding application image name and an application version; the first node screening condition is a node screening condition set adapted to the current deployment, and the node screening condition set is composed of one or more groups of screening means based on regional names, and / or one or more groups of screening means based on region ... The method comprises a screening method based on the security domain name, and / or one or more screening methods based on the organization name, and / or one or more screening methods based on the node's own computing power conditions, and / or one or more screening methods based on node labels, each of which is a screening method set according to a satisfying or not satisfying relationship, or a screening method set according to an affinity or anti-affinity relationship; the first scheme deployment status includes not started, full node deployment success, full node deployment failure, and partial node deployment failure; when the first scheme deployment status is not started or full node deployment success, the first failed node set is empty; When the deployment status of the first solution is all-node deployment failure or part-node deployment failure, the first failed node set is composed of the first node identifiers of all the first working nodes that failed in this deployment.

3. The roadside node cluster management system according to claim 2, characterized in that: The user and cluster management master node is specifically used for performing user node login verification: Step 31, receiving a first node login verification request sent by the first master node of any first roadside node cluster; And use the current first master node as the corresponding current cluster master node; The first node login verification request includes a first login cluster identifier, a first login node identifier, a first login user name, and a first login user password; Step 32, taking the first user registration record in the user registration information table of the user database in which the first user name matches the first login user name and the first user password matches the first login user password as the corresponding current user registration record; and identifying whether the current user registration record is empty; if the current user registration record is empty, setting the corresponding first user verification status to unauthorized user, and going to step 34; if the current user registration record is not empty, going to step 33; Step 33, taking the first user authority record in which the second user identifier in the user authority information table of the user database matches the first user identifier of the current user registration record as the corresponding current user authority record; and taking the authorization cluster information in which the authorization cluster identifier in the first authorization resource set of the current user authority record matches the first login cluster identifier as the corresponding current authorization cluster information; and identifying whether the current authorization cluster information is empty; if the current authorization cluster information is empty, setting the corresponding first user verification status to an unauthorized user; if the current authorization cluster information is not empty, identifying whether the authorization node set of the current authorization cluster information contains the first login node identifier, if not, setting the corresponding first user verification status to an unauthorized user, and if so, setting the corresponding first user verification status to an authorized user; Wherein, the first user verification status includes authorized users and unauthorized users; Step 34: Use the first login cluster identifier and the first login node identifier as the corresponding first verification cluster identifier and first verification node identifier; and send a corresponding first verification request feedback composed of the first verification cluster identifier, the first verification node identifier and the first user verification status back to the current cluster master node.

4. The roadside node cluster management system according to claim 3, characterized in that: The first working node is used to receive the login user name and login user password input by the current user when the user logs in to the node as the corresponding first login user name and first login user password; and using the belonging cluster identification information and the node identification information stored locally at the node as the corresponding first login cluster identification and the first login node identification; and forming the corresponding first node login verification request with the first login cluster identification, the first login node identification, the first login user name and the first login user password; And send the first node login verification request to the user and cluster management main node through the corresponding first master node; and receive the first verification request feedback sent back by the user and cluster management main node through the corresponding first master node; and identify the first verification cluster identifier, the first verification node identifier and the first user verification status in the first verification request feedback; if the first verification cluster identifier matches the belonging cluster identifier information stored locally at the node and the first verification node identifier matches the node identifier information stored locally at the node and the first user verification status is an authorized user, then feedback login success information to the current login and open the current logged-in user's right to use local node resources; if the first verification cluster identifier does not match the belonging cluster identifier information stored locally at the node, or the first verification node identifier does not match the node identifier information stored locally at the node, or the first user verification status is an unauthorized user, then feedback login failure information to the current login and prohibit the current logged-in user from having the right to use local node resources.

5. The roadside node cluster management system according to claim 1, characterized in that: The management types of the node resource management include node purchase, node query, cluster allocation, fault marking, repair marking, label marking, and label revocation; The management types of the roadside cluster management include cluster creation, cluster query, cluster regional deployment, cluster security domain deployment, and cluster deletion.

6. The roadside node cluster management system according to claim 2, characterized in that: The user and cluster management master node is specifically used to: periodically send a patrol signal to the first master node group of all the first roadside node clusters according to a preset first patrol frequency when performing roadside cluster monitoring; After the inspection signal group is sent, the inspection report reception wait is performed according to the preset first waiting time; and when the waiting time does not exceed the first waiting time, each time a first cluster monitoring report sent by the first master node is received, the first cluster identifier corresponding to the first roadside node cluster corresponding to the current first master node is used as the corresponding first monitoring cluster identifier, and the current time is used as the corresponding first monitoring time, and a corresponding first cluster monitoring log composed of the current first cluster monitoring report, the corresponding first monitoring time and the first monitoring cluster identifier is added to the cluster monitoring information table; When the waiting time exceeds the first waiting time, the waiting for receiving the inspection report is terminated, and a round of cluster and node status update processing is performed based on all the first cluster monitoring logs added this time.

7. The roadside node cluster management system according to claim 6, characterized in that: The first master node is used to send the inspection signal to all corresponding first working nodes in a group upon receiving the inspection signal; After the inspection signal group transmission is completed, the corresponding first cluster monitoring report is initialized to be empty, and the inspection report reception wait is performed according to the preset second waiting time; and when the waiting time does not exceed the second waiting time, each time a first node monitoring log sent by the first working node is received, adding the current first node monitoring log to the first cluster monitoring report; When the waiting time exceeds the second waiting time, the waiting for receiving the inspection report is terminated, and the latest first cluster monitoring report is sent to the user and the cluster management master node; 0<second waiting time<first waiting time; The first working node is further configured to collect statistics of all local resource information to obtain the corresponding first monitoring node report when receiving the inspection signal; The node identification information stored locally in the node is used as the corresponding first monitoring node identification; and the first monitoring node identification and the first monitoring node report constitute the corresponding first node monitoring log and send it to the corresponding first master node.

8. The roadside node cluster management system according to claim 2, characterized in that: The application deployment master node is specifically used for: Step 81, receiving a first solution management application submitted by a sixth management interface; The sixth management interface includes an administrator, any management user who obtains application deployment authority, and any system processing interface who obtains application deployment authority; the first solution management application includes a fourth management type and a fourth management parameter; the fourth management type includes solution submission / update and solution query; When the fourth management type is solution submission / update, the fourth management parameter includes a submitted solution identifier, a planned startup time, an application deployment information set, and a node screening condition; the application deployment information set includes one or more application deployment information; the application deployment information consists of a corresponding application image name and an application version; When the fourth management type is a scheme query, the fourth management parameter includes a third query mode and a third query parameter; the third query mode includes an eighth mode and a ninth mode; when the third query mode is the eighth mode, the third query parameter is empty; when the third query mode is the ninth mode, the third query parameter consists of one or more query scheme identifiers; Step 82, if the fourth management type is solution submission / update, the submitted solution identifier, the planned startup time, the application deployment information set and the node screening condition of the fourth management parameter are used as the corresponding current solution identifier, the current solution startup time, the current application deployment information set and the current node screening condition; and the first application deployment solution whose first solution identifier in the application deployment solution information table of the application database matches the current solution identifier and whose first deployment status is not started is used as the corresponding matching deployment solution; and whether the matching deployment solution is empty is identified; if the matching deployment solution is empty, a new first application deployment solution is added to the application deployment solution information table as the corresponding current deployment solution, and the first The solution identifier, the first solution startup time, the first deployment configuration and the first node screening condition are set to the corresponding current solution identifier, the current solution startup time, the current application deployment information set and the current node screening condition, and the first deployment state of the current deployment solution is set to not started, and the first failed node set of the current deployment solution is set to empty; if the current matching record is not empty, the first solution startup time, the first deployment configuration and the first node screening condition of the current matching record are updated to the corresponding current solution startup time, the current application deployment information set and the current node screening condition; and when the application deployment solution corresponding to the current fourth management parameter is added or updated, the corresponding fourth management application feedback is set to success; Step 83, if the fourth management type is solution query, the third query mode and the third query parameter of the fourth management parameter are used as the corresponding current query mode and current query parameter; and the current query mode is identified; if the current query mode is the eighth mode, the application deployment solution information table is used as the corresponding fourth management application feedback; if the current query mode is the ninth mode, the first application deployment solution whose first solution identifier in the application deployment solution information table matches each query solution identifier of the third query parameter is extracted to form the corresponding fourth management application feedback; Step 84: Feedback the fourth management application obtained this time to the sixth management interface.

9. The roadside node cluster management system according to claim 2, characterized in that: The application deployment master node is specifically used when performing the roadside node application configuration: Step 91, regularly taking the first application deployment schemes in the application deployment scheme information table of the application database whose start time is not later than the current time and whose first deployment status is not started as corresponding first inspection schemes according to a preset first time frequency; And taking the first inspection scheme with the earliest start time among the first schemes as the corresponding current configuration scheme; And initialize the first counter to 0; Step 92, extract the first version software package of the first application image record whose first application image name and the first application version satisfy the first deployment configuration of the current configuration scheme in the application image information table of the application database to form a corresponding first software set; Step 93, extracting the first node identifiers of the first node resource records that meet the first node screening condition of the current configuration solution from the node resource information table of the cluster database to form a corresponding first node identifier set; Step 94, grouping the first node identifiers in the first node identifier set that belong to the same first roadside node cluster into one category to form a corresponding first node identifier group; and recording the working node group corresponding to each of the first node identification groups as the corresponding first node group; and recording the first master node of the first roadside node cluster where each of the first node groups is located as the corresponding second master node; Step 95, and establish a corresponding remote control channel through each of the second master nodes and each of the first working nodes of the corresponding first node group, recorded as a first remote control channel; and transmit the first software set to the corresponding first working node through each of the first remote control channels, and after the software set transmission is completed, create and run corresponding image instances of all application images included in the first software set on the corresponding first working node through each of the first remote control channels to obtain a corresponding first processing result; and identifying whether each of the first processing results is successful; if the current first processing result is successful, deleting the software package set on the corresponding first working node through the corresponding first remote control channel; if the current first processing result is failed, deleting the software package set, clearing the application image instance, and releasing the corresponding node resources on the corresponding first working node through the corresponding first remote control channel; and closing all the first remote control channels; Wherein, the first processing result includes success and failure; Step 96, and identify all the first processing results obtained; if all the first processing results are successful or failed, set the corresponding current deployment state to all success or all failure, and go to step 97; if all the first processing results are partially successful and partially failed, set the corresponding current deployment state to partially failed, and form a new first node identifier set by the first node identifiers corresponding to all the first processing results that are specifically failed, and add 1 to the first counter, and identify whether the first counter after adding 1 exceeds the preset first counter threshold, if so, go to step 97, if not, return to step 94 after waiting for the preset first time length; Step 97, identify the latest current deployment status; if the current deployment status is full success, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full-node deployment success; if the current deployment status is full failure or partial failure, update the first deployment status of the current configuration scheme in the application deployment scheme information table to the corresponding full-node deployment failure or partial node deployment failure, and set the first failed node set of the current configuration scheme to the latest first node identification set.

10. The roadside node cluster management system according to claim 2, characterized in that: The application operation and maintenance master node is specifically used for: Step 101, regularly extracting the first cluster identifiers of the first cluster deployment records whose first cluster working condition is normal from the cluster deployment information table of the cluster database at a preset second time frequency to form a corresponding first cluster identifier set; Step 102, extracting the first cluster monitoring report of the first cluster monitoring log whose first monitoring cluster identifier in the cluster monitoring information table of the cluster database matches each first cluster identifier of the first cluster identifier set and whose first monitoring time is closest to the current time to form a corresponding first cluster monitoring report set; Step 103, extracting from the first cluster monitoring report set at least one of the first monitoring node reports in which the application usage status of the first application information is abnormal suspension or loading failure to form a corresponding first monitoring node report set; Step 104, when the first monitoring node report set is not empty, the first monitoring node identifier, application image and version name, and the application usage status corresponding to the first application information of each application usage status of abnormal suspension or loading failure in the current first monitoring node report set are used as the corresponding first abnormal node identifier, first abnormal application information, and first abnormal status to form a corresponding abnormal node application record; and all the obtained abnormal node application records form a corresponding abnormal node application report; Step 105: When the abnormal node application report is not empty, the abnormal node application report is sent to a preset abnormal node application warning interface; and taking each of the abnormal node application records as the corresponding current record; and taking the first abnormal node identifier, the first abnormal application information and the first abnormal state of the current record as the corresponding current node identifier, the current abnormal application information and the current abnormal state; and taking the first working node corresponding to the current node identifier as the corresponding current working node; and taking the first belonging cluster identifier of the first node resource record whose first node identifier matches the current node identifier in the node resource information table of the cluster database as the corresponding current cluster identifier; And the first master node corresponding to the first master node configuration of the first cluster deployment record whose first cluster identifier in the cluster deployment information table of the cluster database matches the current cluster identifier is taken as the corresponding current master node; and a corresponding remote control channel is established between the current master node and the current working node and recorded as the corresponding current remote control channel; and the current abnormal state is identified; if the current abnormal state is a loading failure, the first version software package of the first application image record corresponding to the first application image name and the first application version in the application image information table of the application database and the current abnormal application information is extracted as the corresponding current software package, and the application image instance corresponding to the current abnormal application information is cleared and the corresponding node resources are released on the current working node through the current remote control channel, and the current software package is transmitted to the current working node through the current remote control channel, and after the software package transmission is completed, the image instance of the application image corresponding to the current software package is rebuilt and run on the current working node through the current remote control channel; If the current abnormal state is abnormal suspension, the application image instance corresponding to the current abnormal application information is restarted on the current working node through the current remote control channel; and the current remote control channel is closed.

Images