CN116915834A - A method, equipment and medium for reporting business status of an ODL controller - Google Patents

Abstract

This application discloses a business status reporting method, equipment and medium for an ODL controller. The method includes: based on its own first IP address, the first ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in. ; Among them, the first ODL node is the master node; through the network-odl plug-in, create the associated first database listener; disconnect the websocket connection with the Neutron Server server; the master node switches from the first ODL node to the second ODL Node, the second ODL node establishes a websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; creates an associated second database listener through the network-odl plug-in; listens according to the second database The server monitors the business status change data of the virtual networking environment from the MDSAL database, and reports the business status change data to the Neutron Server server through the websocket connection. It can automatically report virtual business status data after switching the master node.

Description

A method, equipment and medium for reporting business status of an ODL controller

Technical field

This application relates to the technical field of SDN controllers, and in particular to a method, equipment and medium for reporting service status of an ODL controller.

Background technique

OpenDayLight (ODL) is an SDN controller based on microservice architecture and supports a wide range of network protocols, such as OpenFlow, SNMP, NETCONF, OVSDB, BGP, LISP, etc. ODL has good programmability, uses OSGi Karaf as the bottom layer to implement service modularization, and exposes module interfaces through MDSAL and yang models. This model embeds LevelDB and includes a cluster communication solution based on Akka Cluster. It is feature-rich and can be used out of the box.

ODL's OpenStack ML2 plug-in-networking-odl provides a mechanism for routing port status updates. Simply put, this plug-in will create a websocket server. After the ODL controller is started, it will connect to this websocket and change the MDSAL operational database data of the neutron port. The event is sent to this websocket server. After receiving the message, the plug-in parses the port status: status and updates it to the Neutron Server to implement Underlay routing port status reporting.

However, based on the hardware Overlay networking environment, in the ODL cluster environment, since the network-odl plug-in only knows the unique virtual IP of the controller cluster, when the virtual IP is implemented through keepAlive and other solutions, initializing the websocket connection will create a database on a specific ODL node. Listener, however, after switching the master node, the database listener will not be found after the websocket re-establishes the connection with the new master node, and the business status change data cannot be automatically reported to the Neutron Server.

Contents of the invention

The embodiment of this application provides a method, equipment and medium for reporting the business status of an ODL controller, which is used to solve the problem that after switching the master node, the database listener cannot be found after the websocket re-establishes a connection with the new master node, and the business cannot be automatically reported. Issues with reporting status change data to Neutron Server.

The embodiments of this application adopt the following technical solutions:

On the one hand, embodiments of the present application provide a method for reporting service status of an ODL controller. The method includes: based on its first IP address, the first ODL node establishes initialization with the Neutron Server through the network-odl plug-in. websocket connection; wherein, the first ODL node is the master node; through the network-odl plug-in, create an associated first database listener; disconnect the websocket connection with the Neutron Server server; if the master node is slave The first ODL node is switched to a second ODL node, and the second ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; through the network -odl plug-in, creates an associated second database listener; according to the second database listener, monitors the business status change data of the virtual networking environment from the MDSAL database, and connects the business status change data through the websocket Report to the Neutron Server.

In one example, monitoring the service status change data of the virtual networking environment from the MDSAL database according to the second database listener specifically includes: within a preset period, the second ODL node passes the MDSAL database The monitoring mechanism extracts the configuration information of the preset monitoring type of the physical network device; determines the corresponding virtual service status data in the virtual networking environment based on the configuration information, and stores the virtual service status data in the MDSAL database; in the In the MDSAL database, the virtual service status data is compared with the historical virtual service status data; if they are inconsistent, service status change data of the virtual networking environment is generated, and according to the second database listener, the Business status change data of the virtual networking environment.

In one example, before determining the corresponding virtual service status data in the virtual networking environment according to the configuration information and storing the virtual service status data in the MDSAL database, the method further includes: the second ODL The node creates a compatibility layer for the MDSAL database; through the compatibility layer, sets a monitoring field type for the physical network device to register monitoring for the field in the MDSAL database.

In one example, the configuration information is text information, and the second ODL node extracts the configuration information of the preset listening type of the physical network device through the listening mechanism of the MDSAL database, which specifically includes: the second ODL node The configuration information is parsed to obtain tree configuration information in the form of a tree structure; through regular expressions, the configuration information of the preset monitoring type of the physical network device is extracted from the tree configuration information.

In one example, the second ODL node parses the configuration information to obtain tree configuration information in the form of a tree structure, which specifically includes: when the second ODL node traverses the configuration information, If a parent node is detected, generate a tree structure group for the parent node; determine whether the parent node includes child nodes; if so, divide the child nodes into the tree structure group; after the traversal is completed, Generate multiple tree structure groups and obtain tree configuration information in the form of a tree structure.

In one example, the disconnection of the websocket connection with the Neutron Server server specifically includes: if the first ODL node is offline in a non-faulty state, or is in a faulty state and cannot run, disconnecting the connection with the Neutron Server server. The websocket connection between the Neutron Server servers; after the associated second database listener is created through the network-odl plug-in, the method further includes: converting the first ODL node from the offline state to When in the online state, if an error message is detected in the first database listener, the first database listener is deleted.

In one example, after the business status change data is reported to the Neutron Server through the websocket connection, the method further includes: retrieving the change of the business status data in a pre-built mapping relationship table. A management interface display model corresponding to the field type; based on the management interface model, the business status data changes are displayed on the management interface.

In one example, the method further includes: if the virtual service status data is consistent with the historical virtual service status data, the second ODL node calculates the acquisition time of the virtual service status data and the historical virtual service status data. The time difference between the acquisition times; calculate the difference between the time difference and the time of the preset period; if the difference is greater than the preset difference threshold, it is determined that the first ODL node and the second ODL node exist A suspension of work occurred at the same time.

On the other hand, embodiments of the present application provide a service status reporting device for an ODL controller, applied to a second ODL node, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein , the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can: if the master node switches from the first ODL node to The second ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; wherein the first ODL node establishes an initial websocket connection with the Neutron Server based on its own second IP address. An IP address, establish an initial websocket connection with the Neutron Server server through the network-odl plug-in; create an associated first database listener through the network-odl plug-in; disconnect the websocket with the Neutron Server server Connect; create an associated second database listener through the network-odl plug-in; listen to the business status change data of the virtual networking environment from the MDSAL database according to the second database listener, and report the business status change The data is reported to the Neutron Server through the websocket connection.

On the other hand, embodiments of the present application provide a non-volatile computer storage medium for ODL controller business status reporting, which stores computer-executable instructions and is applied to the second ODL node. The computer-executable instructions are set to: If the master node switches from the first ODL node to the second ODL node, the second ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; wherein, The first ODL node establishes an initial websocket connection with the NeutronServer server through the network-odl plug-in based on its own first IP address; creates an associated first database listener through the network-odl plug-in; disconnects from The websocket connection between the Neutron Server servers; create an associated second database listener through the network-odl plug-in; monitor the business status of the virtual networking environment from the MDSAL database according to the second database listener Change data: report the business status change data to the Neutron Server through the websocket connection.

At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

Through the network-odl plug-in, the Neutron Server server is connected to the real IP address of the ODL node, so that in a cluster environment, each time the master node is switched, after the WebSocket is disconnected, the ODL node of the new master node can be restarted. Establish an initial websocket connection with the Neutron Server server, so as to automatically create a database listener, establish a listener with a specific MDSAL database associated with the ODL node, and continue to obtain the listener's event dispatch for MDSAL database changes.

Description of the drawings

In order to explain the technical solution of the present application more clearly, some embodiments of the present application will be described in detail below with reference to the accompanying drawings, in which:

Figure 1 is a schematic flow chart of a method for reporting business status of an ODL controller provided by an embodiment of the present application;

Figure 2 is a schematic framework diagram of the ODL controller's business status reporting system in an application scenario provided by the embodiment of the present application;

Figure 3 is a schematic structural diagram of a service status reporting device of an ODL controller provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

Some embodiments of the present application are described in detail below with reference to the accompanying drawings.

Figure 1 is a schematic flowchart of a method for reporting service status of an ODL controller provided by an embodiment of the present application. Certain input parameters or intermediate results in the process allow for manual intervention to help improve accuracy.

The process in Figure 1 may include the following steps:

S101: Based on its first IP address, the first ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in.

Among them, the first ODL node is the master node.

It should be noted that the network-odl plug-in is the key for the cloud platform OpenStack to call the SDN controller. Neutron-server is a server that provides neutron network services. Any request from an individual with network needs will be sent to such a server for network requests.

S102: Create an associated first database listener through the network-odl plug-in.

S103: Disconnect the websocket connection with the Neutron Server.

Among them, if the first ODL node goes offline in a non-faulty state, or is in a faulty state and cannot run, the websocket connection with the Neutron Server server is disconnected. For example, when the first ODL node is shut down, it is in a faulty state and cannot run. The first ODL node is in a non-fault offline state due to network interruption.

S104: If the master node switches from the first ODL node to the second ODL node, the second ODL node establishes an initialization websocket with the Neutron Server server through the network-odl plug-in based on its own second IP address. connect.

S105: Create an associated second database listener through the network-odl plug-in.

Wherein, when the first ODL node transitions from the offline state to the online state, if an error message is detected in the first database listener, the first database listener is deleted.

S106: According to the second database listener, monitor the business status change data of the virtual networking environment from the MDSAL database, and report the business status change data to the NeutronServer server through the websocket connection.

In some embodiments of the present application, in the pre-built mapping relationship table, the management interface display model corresponding to the field type of the business status data change is retrieved. Based on the management interface model, changes in business status data are displayed on the management interface.

In some embodiments of the present application, within a preset period, the second ODL node extracts the configuration information of the preset listening type of the physical network device through the listening mechanism of the MDSAL database.

Then, according to the configuration information, the corresponding virtual service status data in the virtual networking environment is determined, and the virtual service status data is stored in the MDSAL database.

In the MDSAL database, compare virtual service status data with historical virtual service status data.

If they are inconsistent, the service status change data of the virtual networking environment is generated, and the service status change data of the virtual networking environment is monitored according to the second database listener.

If they are consistent, the service status change data of the virtual networking environment will no longer be generated.

In addition, due to some special needs, the developer caused the ODL node cluster to suspend its work. At this time, the ODL node cluster was unable to obtain business status data within the preset period.

Based on this, when the virtual service status data of the second ODL node is consistent with the historical virtual service status data, the second ODL node calculates the time difference between the acquisition time of the virtual service status data and the acquisition time of the historical virtual service status data.

Calculate the difference between the time difference and the time of the preset period;

If the difference is greater than the preset difference threshold, it is determined that the first ODL node and the second ODL node are suspended at the same time. On the contrary, there is no simultaneous suspension of work.

In some embodiments of this application, for the MDSAL database, the monitoring mechanism of the ODL built-in database is used, but a compatibility layer is provided based on the MDSAL database. There is no need to define yang for each database and then manually create cluster monitoring for it. And process WebSocket messages, that is, there is no need to create multiple different MDSAL databases for the second ODL node, but with the help of a shard on different nodes, that is, multiple ODL nodes are in the same shard, each ODL The contents of the node-related databases are the same, and with the help of a separate state database synchronized at the bottom of the raft algorithm, you only need to simply register a listener for a certain field of this database, and you can use a global listener to generate change events for its field data.

Based on this, the second ODL node creates a compatibility layer for the MDSAL database; through the compatibility layer, a monitoring field type for the physical network device is set to register field monitoring in the MDSAL database.

In some embodiments of the present application, the configuration information extracted by the second ODL node from the physical network device is text information. Instead of directly using regular expressions to restore it to a tree structure, the text information is modeled with tree commands. , which can more flexibly and accurately restore the preset configuration information of physical network devices into a tree structure, with higher fault tolerance.

Specifically, the second ODL node parses the configuration information to obtain tree configuration information in the form of a tree structure.

Among them, when the second ODL node traverses the configuration information, if the parent node is detected, a tree structure group is generated for the parent node;

Determine whether the parent node includes child nodes; if so, divide the child nodes into tree structure groups. If not, re-detect the parent node.

After the traversal is completed, multiple tree structure groups are generated, and tree configuration information in the form of a tree structure is obtained.

Then, through regular expressions, the configuration information of the preset listening type of the physical network device is extracted from the tree configuration information.

This application performs fast, efficient, and compatible analysis of tree structure configurations, so that the virtual service status can be obtained based on the configuration information. For example, the status of the routing port must depend on the correct routing configuration of the underlying network device: appropriate vrf, vrf configuration, vni and vlan mapping, etc. For non-network devices, such as firewall hardware devices, the configuration commands are generally based on the tree structure returned. Therefore, this part needs to implement a general tree structure configuration parser, and cannot be hard-coded into regular expressions or string searches. The latter is difficult to get right. For example, in a tree structure based on indentation such as part1 part1.1part1.2 part1.3, if it is determined that part1.1 exists under part1, just search using regular expressions, but it is possible that the configuration will be changed to part1 part1.0 part1.1 later. part1.2 part1.3, which will break the regular rules. The function implemented by the present invention can model tree commands: typically, show running-config, and then quickly find whether a certain parent node contains child nodes, or whether a certain child node exists on a certain parent node. Based on this The state detection method is more robust, and there is no need to separately adapt each hardware network device or even different versions of network devices, and the reliability is higher.

It provides tree-like command status checking, database monitoring and message push process abstraction in a one-layer hardware Overlay networking environment. On the data collection end, tree-like command parsing is more robust than regular and string search. , and there is no need to perform command line videos on switches of different versions, and the adaptation status check logic for multiple models of switches or firewalls is also very simple. Compared with the single-node and single-database solution provided by ODL, the database monitoring and message pushing process is easier to use. There is no template code and only two or three lines of configuration are needed to integrate the business. And it adapts well to the cluster master node switching of ODL cluster.

It should be noted that although the embodiment of the present application describes step S101 to step S106 sequentially with reference to FIG. 1 , this does not mean that steps S101 to step S106 must be executed in a strict sequence. The reason why this embodiment of the present application sequentially introduces steps S101 to step S106 in the order shown in Figure 1 is to facilitate those skilled in the art in understanding the technical solutions of the embodiment of the present application. In other words, in this embodiment of the present application, the order between step S101 to step S106 can be appropriately adjusted according to actual needs.

Through the method in Figure 1, the Neutron Server server is connected to the real IP address of the ODL node through the network-odl plug-in, so that in a cluster environment, each time the master node is switched, after the WebSocket is disconnected, the new master node All ODL nodes can re-establish the initial websocket connection with the Neutron Server server, so as to automatically create a database listener, establish a listener with a specific MDSAL database associated with the ODL node, and continue to obtain the Listener listener for MDSAL database changes. event dispatch.

Figure 2 is a schematic framework diagram of the ODL controller's service status reporting system in an application scenario provided by the embodiment of the present application.

In Figure 2, by providing an SDN environment based on Spine-Leaf hardware Overlay networking on the OpenDayLight+OpenStack platform, the business status data of the virtual networking environment is extracted from the tree configuration of the underlying network equipment, and then with the help of Based on OpenDayLight's MDSAL database listening mechanism, by updating the status to the MDSAL database, it triggers the Listener to exchange data with the Neutron Server that has established a WebSocket connection, and obtains the changed status in the network-odl plug-in, and updates it to the OpenStack platform. Abstract mechanism. This mechanism can be used to quickly update the business status data of virtual Overlay routing ports, VPN sites, and VPN IPSec site connection status to OpenStack or OpenStack-compatible cloud platforms to improve the network. State observability.

Through the system in Figure 2, the reporting function of virtual routing port status, VPN service, VPN IPSEC site connection and other status in the hardware Overlay networking environment of the OpenDayLight controller cluster is realized. In other words, an abstraction is implemented based on the basic ODL status communication mechanism. This abstraction can perform targeted various business detection on the switch configuration and status in the hardware overlay environment, and report it to the neutron server reliably and stably, including It is not limited to the abstraction of routing port status, VPN service status, and VPN IPSEC tree command parsing;

Based on the abstraction of the data update monitoring and push process of a single database on each ODL node, WebSocket is more suitable for status event change notifications than REST requests and has less overhead. This abstraction can adapt to different brands and versions of switches, load balancing, firewalls and other equipment. It has good versatility, low difficulty in adapting services, and is more robust and stable. Site connection status, etc.

For example, in the existing technology, separate codes are used for each model and each system version of switches and firewalls to obtain their configurations, and then regular and string parsing is performed, exposed as a REST interface, and network-odl in the neutron server is polled. Find data, diff the data and get status change information. Compared with this solution, this solution lacks the level of abstraction, and the coupling of various parts is serious (switch configuration and code, switch version and code, code for parsing status changes and code for sending status changes rely on database transfer), and poor performance (neutron Server cluster and ODL cluster have poor performance in polling data changes).

Based on the same idea, some embodiments of the present application also provide equipment and non-volatile computer storage media corresponding to the above method.

Figure 3 is a schematic structural diagram of a service status reporting device of an ODL controller provided by an embodiment of the present application. It is applied to the second ODL node and includes:

at least one processor; and,

a memory communicatively connected to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

If the master node switches from the first ODL node to the second ODL node, the second ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; wherein, The first ODL node establishes an initial websocket connection with the Neutron Server server based on its first IP address through the network-odl plug-in; creates an associated first database listener through the network-odl plug-in; disconnects websocket connection with the Neutron Server server;

Create an associated second database listener through the network-odl plug-in;

According to the second database listener, the business status change data of the virtual networking environment is monitored from the MDSAL database, and the business status change data is reported to the Neutron Server server through the websocket connection.

Some embodiments of the present application provide a non-volatile computer storage medium for ODL controller business status reporting, which stores computer-executable instructions. The computer-executable instructions are set to:

If the master node switches from the first ODL node to the second ODL node, the second ODL node establishes an initial websocket connection with the Neutron Server server through the network-odl plug-in based on its own second IP address; wherein, The first ODL node establishes an initial websocket connection with the Neutron Server server based on its first IP address through the network-odl plug-in; creates an associated first database listener through the network-odl plug-in; disconnects websocket connection with the Neutron Server server;

Create an associated second database listener through the network-odl plug-in;

According to the second database listener, the business status change data of the virtual networking environment is monitored from the MDSAL database, and the business status change data is reported to the Neutron Server server through the websocket connection.

Each embodiment in this application is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the descriptions are relatively simple. For relevant details, please refer to the partial description of the method embodiments.

The equipment, medium and method provided by the embodiments of the present application are in one-to-one correspondence. Therefore, the equipment and medium also have beneficial technical effects similar to their corresponding methods. Since the beneficial technical effects of the method have been described in detail above, therefore, The beneficial technical effects of the equipment and media will not be repeated here.

Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer-readable media, random access memory (RAM), and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information. Information may be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory. (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device. As defined in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

The above descriptions are only examples of the present application and are not intended to limit the present application. To those skilled in the art, various modifications and variations may be made to this application. Any modifications, equivalent substitutions, improvements, etc. made within the technical principles of this application shall fall within the protection scope of this application.

Claims (10)

1. The service state reporting method of the ODL controller is characterized by comprising the following steps:

the first ODL node establishes an initialization websocket connection with a Neutron Server through a networking-ODL plug-in based on a first IP address of the first ODL node; wherein the first ODL node is a master node;

creating an associated first database listener through the networking-odl plugin;

disconnecting websocket connection with the neutral Server;

if the master node is switched from the first ODL node to a second ODL node, the second ODL node establishes an initialization websocket connection with a neutral Server through the networking-ODL plug-in based on a second IP address of the second ODL node;

creating an associated second database listener through the networking-odl plugin;

and according to the second database monitor, monitoring service state change data of the virtual networking environment from an MDSAL database, and reporting the service state change data to the neutral Server through the websocket connection.

2. The method of claim 1, wherein the monitoring, according to the second database monitor, service state change data of the virtual networking environment from the MDSAL database specifically includes:

in a preset period, the second ODL node extracts configuration information of a preset monitoring type of the physical network equipment through a monitoring mechanism of the MDSAL database;

determining corresponding virtual service state data in a virtual networking environment according to the configuration information, and storing the virtual service state data into an MDSAL database;

comparing the virtual service state data with historical virtual service state data in the MDSAL database;

and if the service state change data of the virtual networking environment are inconsistent, generating service state change data of the virtual networking environment, and monitoring the service state change data of the virtual networking environment according to the second database monitor.

3. The method of claim 2, wherein the determining, based on the configuration information, corresponding virtual traffic state data in a virtual networking environment, before storing the virtual traffic state data in an MDSAL database, the method further comprises:

the second ODL node creates a compatible layer for the MDSAL database;

and setting a monitoring field type aiming at the physical network equipment through the compatibility layer so as to register field monitoring aiming at the MDSAL database.

4. The method of claim 2, wherein the configuration information is text information, and the second ODL node extracts, through a monitoring mechanism of the MDSAL database, configuration information of a preset monitoring type of the physical network device, specifically including:

the second ODL node analyzes the configuration information to obtain tree configuration information taking a tree structure as a display form;

extracting configuration information of a preset monitoring type of the physical network equipment from the tree configuration information through a regular expression.

5. The method according to claim 4, wherein the second ODL node parses the configuration information to obtain tree configuration information in a tree structure as a display form, and the method specifically includes:

the second ODL node traverses the configuration information, and if a father node is detected, a tree structure group is generated for the father node;

judging whether the father node comprises a child node or not;

if yes, dividing the child nodes into the tree structure group;

after traversing, generating a plurality of tree structure groups to obtain tree configuration information taking a tree structure as a display form.

6. The method according to claim 1, wherein said disconnecting the websocket connection with the Neutron Server comprises:

if the first ODL node is in a non-fault state and is in a fault state or is in a non-operation state, disconnecting websocket connection with the neutral Server;

after the creating, by the networking-odl plug-in, the associated second database listener, the method further includes:

when the first ODL node is converted from the offline state to the online state, if the first database monitor is detected to have error reporting information, the first database monitor is deleted.

7. The method of claim 1, wherein after the reporting the service state change data to the Neutron Server via the websocket connection, the method further comprises:

searching a management interface display model corresponding to the field type of the service state data change in a pre-constructed mapping relation table;

and based on the management interface model, carrying out state display on the business state data change on a management interface.

8. The method according to claim 2, wherein the method further comprises:

if the virtual service state data is consistent with the historical virtual service state data, the second ODL node calculates a time difference between the acquisition time of the virtual service state data and the acquisition time of the historical virtual service state data;

calculating a difference value between the time difference and the time of a preset period;

if the difference is greater than a preset difference threshold, determining that the first ODL node and the second ODL node have the condition of simultaneously suspending operation.

9. The service state reporting device of the ODL controller is characterized by being applied to a second ODL node, and comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

if the master node is switched from the first ODL node to a second ODL node, the second ODL node establishes an initialization websocket connection with a Neutron Server through the networking-ODL plug-in based on a second IP address of the second ODL node; the first ODL node establishes an initialization websocket connection with a neutral Server through a networking-ODL plug-in based on a first IP address of the first ODL node; creating an associated first database listener through the networking-odl plugin; disconnecting websocket connection with the neutral Server;

creating an associated second database listener through the networking-odl plugin;

and according to the second database monitor, monitoring service state change data of the virtual networking environment from an MDSAL database, and reporting the service state change data to the neutral Server through the websocket connection.

10. A non-volatile computer storage medium for reporting a service status of an ODL controller, storing computer executable instructions, wherein the computer executable instructions are applied to a second ODL node and configured to:

if the master node is switched from the first ODL node to a second ODL node, the second ODL node establishes an initialization websocket connection with a Neutron Server through the networking-ODL plug-in based on a second IP address of the second ODL node; the first ODL node establishes an initialization websocket connection with a neutral Server through a networking-ODL plug-in based on a first IP address of the first ODL node; creating an associated first database listener through the networking-odl plugin; disconnecting websocket connection with the neutral Server;

creating an associated second database listener through the networking-odl plugin;

and according to the second database monitor, monitoring service state change data of the virtual networking environment from an MDSAL database, and reporting the service state change data to the neutral Server through the websocket connection.