Disaster recovery method and apparatus for open virtual network control plane, and product and medium

Abstract

The present application relates to the technical field of computers. Disclosed are a disaster recovery method and apparatus for an open virtual network control plane, and a product and a medium. The method comprises: configuring disaster recovery for an open virtual network control plane, so as to obtain at least two service domains, wherein each service domain comprises an open virtual network control plane, a network service component, and a database corresponding to the network service component; determining one service domain to be a primary service domain, and determining the remaining service domains to be backup service domains; by means of a synchronization server, controlling a data plane to be connected to the open virtual network control plane of the primary service domain; by means of the synchronization server, detecting whether the open virtual network control plane in the primary service domain operates normally; and if the open virtual network control plane in the primary service domain operates abnormally, activating the disaster recovery, using the original primary service domain as a backup service domain, selecting a target backup service domain from among all the backup service domains other than the original primary service domain, and using the target backup service domain as a new primary service domain. The service capability and fault-tolerance capability of an open virtual network are thus improved.

Description

An open virtual network control plane disaster recovery method, device, product and medium

[0001] Cross-reference to Related Applications

[0002] The present application claims priority to the Chinese patent application No. 202410693305.9, filed on May 31, 2024, and entitled "An open virtual network control plane disaster recovery method, device, product and medium", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the technical field of computers, and in particular to an open virtual network control plane disaster recovery method, device, product and medium. BACKGROUND

[0004] OVN (Open Virtual Network) is a mainstream open source network control technology solution. OVN itself can provide a primary-backup high-availability cluster function. A single OVN cluster generally has 2N+1 nodes. When the primary node (leader) is down, a certain secondary node (follower) becomes the leader to start service, and the leader node synchronizes data to all follower nodes. After the primary node fails, more than half of the current cluster nodes need to survive to vote for a new primary node, and the other nodes without failure can still provide control plane services. However, when the number of failed nodes exceeds half of the total cluster nodes, the current cluster cannot provide services, and the network control plane function is abnormal. That is, due to the limitation of the leader election mechanism, the related technology can only withstand less than or equal to N node failures. If the number of failed nodes exceeds half of the total cluster nodes, the related technology can only be restored after the failed nodes are repaired, and users / operation and maintenance personnel cannot quickly restore the control plane function, which reduces service capability and user experience. SUMMARY

[0005] Therefore, the present application aims to provide an open virtual network control plane disaster recovery method, device, product and medium, which can improve the service capability and fault tolerance capability of OVN. The alternative solution is as follows:

[0006] The present application discloses an open virtual network control plane disaster recovery method, comprising:

[0007] Configuring an open virtual network control plane disaster recovery to obtain at least two service domains; the service domain includes an open virtual network control plane, a network service component, and a database corresponding to the network service component;

[0008] Determining one service domain as a primary service domain and the remaining service domains as backup service domains;

[0009] controlling, by the synchronization server, the open virtual network control plane connected to the primary service domain by the data plane;

[0010] detecting, by the synchronization server, whether the open virtual network control plane in the primary service domain is running normally;

[0011] if the open virtual network control plane in the primary service domain is running abnormally, starting disaster recovery, taking the original primary service domain as a standby service domain, selecting a target standby service domain from all standby service domains except the original primary service domain, and taking the target standby service domain as a new primary service domain.

[0012] Optionally, before controlling, by the synchronization server, the open virtual network control plane connected to the primary service domain by the data plane, the method further comprises:

[0013] judging whether the network service component of the primary service domain completes data synchronization to the open virtual network control plane;

[0014] if the data synchronization is completed, performing the operation of controlling, by the synchronization server, the open virtual network control plane connected to the primary service domain by the data plane.

[0015] Optionally, the disaster recovery method of the open virtual network control plane further comprises:

[0016] synchronizing, by the network service component, data to the open virtual network control plane, and updating a synchronization state in the open virtual network northbound database according to a synchronization progress; the synchronization state comprises unsynchronized, synchronizing and completed synchronization;

[0017] judging whether the network service component of the primary service domain completes data synchronization to the open virtual network control plane, comprising:

[0018] reading the synchronization state from the open virtual network southbound database;

[0019] if the synchronization state is completed synchronization, judging that the network service component of the primary service domain completes data synchronization to the open virtual network control plane.

[0020] Optionally, detecting, by the synchronization server, whether the open virtual network control plane in the primary service domain is running normally, comprising:

[0021] writing, by the synchronization server, first target data to the open virtual network northbound database of the open virtual network control plane in the primary service domain;

[0022] reading, by the synchronization server, second target data from the open virtual network southbound database of the open virtual network control plane in the primary service domain;

[0023] comparing the first target data with the second target data to judge whether the open virtual network control plane in the primary service domain is running normally.

[0024] Optionally, the method further comprises:

[0025] determining whether the first target data is identical to the second target data;

[0026] determining a time interval between a first time stamp corresponding to the first target data and a second time stamp corresponding to the second target data;

[0027] if the first target data is identical to the second target data and the time interval is less than a preset time threshold, determining that the open virtual network control plane in the primary service domain is running normally;

[0028] if the first target data is not identical to the second target data and the time interval is greater than or equal to the preset time threshold, determining that the open virtual network control plane in the primary service domain is running abnormally.

[0029] Optionally, the method further comprises:

[0030] determining a number of currently existing service domains;

[0031] if the number of service domains is greater than or equal to a preset number threshold, selecting a service domain from all the service domains as the primary service domain;

[0032] if the number of service domains is less than the preset number threshold, adding service domains until the number of service domains is greater than or equal to the preset number threshold.

[0033] Optionally, the method further comprises:

[0034] obtaining a disaster recovery instruction issued by an administrator;

[0035] starting disaster recovery of the open virtual network control plane according to the disaster recovery instruction.

[0036] Optionally, the method further comprises:

[0037] obtaining a standby service domain addition instruction or a deletion instruction issued by the administrator;

[0038] updating the standby service domain according to the addition instruction or the deletion instruction.

[0039] Optionally, the method further comprises:

[0040] starting disaster recovery, stopping the primary service domain from running, and stopping data update of a database corresponding to a network service component.

[0041] Optionally, the method further comprises:

[0042] Determine whether the network service components of the new primary service domain have completed the data synchronization of the virtual network control plane to the new primary service domain;

[0043] If data synchronization is complete, the synchronization server controls the data plane to connect to the open virtual network control plane of the new primary service domain.

[0044] The synchronization server is used to detect whether the open virtual network control plane in the new primary service domain is functioning correctly.

[0045] Optionally, after connecting the control data plane of the synchronization server to the open virtual network control plane of the primary service domain, it also includes:

[0046] The database contents corresponding to the network service components in the primary service domain are synchronized to the database corresponding to the network service components in the backup zone via the synchronization server.

[0047] Optionally, after enabling disaster recovery, the following are also included:

[0048] Stop the synchronization server from synchronizing the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the standby zone.

[0049] Optionally, a target backup service domain may be selected from all backup service domains other than the original primary service domain, including:

[0050] Obtain the priority of each backup service domain;

[0051] Select the highest priority backup service domain as the target backup service domain.

[0052] Optionally, a target backup service domain may be selected from all backup service domains other than the original primary service domain, including:

[0053] The backup service domain that is closest to the original primary service domain among all backup service domains is selected as the target backup service domain.

[0054] Optionally, one service domain may be designated as the primary service domain, and the remaining service domains as backup service domains, including:

[0055] Designate the core service domain from at least two service domains as the primary service domain and the remaining service domains as backup service domains.

[0056] This application discloses an open virtual network control plane disaster recovery device, comprising:

[0057] The disaster recovery configuration module is configured to configure open virtual network control plane disaster recovery, resulting in at least two service domains; each service domain includes the open virtual network control plane, network service components, and the database corresponding to the network service components.

[0058] The primary service domain determination module is configured to determine one service domain as the primary service domain and the remaining service domains as backup service domains.

[0059] The data plane connection module is configured to connect the data plane to the open virtual network control plane of the primary service domain via a synchronization server.

[0060] The detection module is configured to detect whether the open virtual network control plane in the primary service domain is functioning correctly via the synchronization server.

[0061] The disaster recovery module is configured to activate disaster recovery if the open virtual network control plane in the primary service domain malfunctions. It will then use the original primary service domain as a backup service domain, select a target backup service domain from all backup service domains other than the original primary service domain, and use the target backup service domain as the new primary service domain.

[0062] Optionally, the device also includes:

[0063] The judgment unit is configured to determine whether the network service components of the primary service domain have completed data synchronization with the open virtual network control plane before connecting to the open virtual network control plane of the primary service domain through the synchronization server control data plane;

[0064] The execution unit is configured to perform operations on the open virtual network control plane that connects to the primary service domain via the synchronization server control data plane if data synchronization is completed.

[0065] This application discloses a computer program product, including a computer program / instruction, characterized in that the computer program / instruction, when executed by a processor, implements the aforementioned open virtual network control plane disaster recovery method.

[0066] This application discloses an electronic device, including:

[0067] Memory, configured to store computer programs;

[0068] The processor is configured to execute computer programs to implement the aforementioned open virtual network control plane disaster recovery method.

[0069] This application discloses a computer-readable storage medium configured to store a computer program; wherein the computer program, when executed by a processor, implements the aforementioned open virtual network control plane disaster recovery method.

[0070] In this application, OVN control plane disaster recovery is configured to obtain at least two service domains. Each service domain includes the OVN control plane, network service components, and the database corresponding to the network service components. One service domain is designated as the primary service domain, and the remaining service domains are designated as backup service domains. The control data plane of the synchronization server is connected to the OVN control plane of the primary service domain. The synchronization server is used to detect whether the OVN control plane in the primary service domain is operating normally. If the OVN control plane in the primary service domain is abnormal, disaster recovery is initiated, the original primary service domain is designated as the backup service domain, a target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is designated as the new primary service domain. As can be seen, by adding a backup service domain for OVN control plane disaster recovery and by detecting the running status of the OVN control plane through a synchronization server, the backup service domain can be automatically activated as the primary service domain when the OVN control plane in the primary service domain is abnormal, thus achieving control plane disaster recovery. Furthermore, by establishing a connection between the data plane and the OVN control plane through the synchronization server, the continuity of services is guaranteed, and the problem of OVN control plane service interruption due to the failure of more than half of the nodes is avoided. This improves OVN service capabilities and fault tolerance, and enhances the user experience. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0072] Figure 1 is a schematic diagram of the OVN architecture in related technologies;

[0073] Figure 2 is a flowchart of an open virtual network control plane disaster recovery method provided in this application;

[0074] Figure 3 is a schematic diagram of an optional open virtual network architecture provided in this application;

[0075] Figure 4 is a flowchart of an optional open virtual network control plane disaster recovery method provided in this application;

[0076] Figure 5 is a flowchart of an optional open virtual network control plane disaster recovery method provided in this application;

[0077] Figure 6 is a structural diagram of an electronic device provided in this application. Detailed Implementation

[0078] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0079] In related technologies, the OVN cluster architecture is shown in Figure 1. The OVN control plane consists of three independent yet interdependent clusters. The OVN northbound database (ovn-nb-db) cluster primarily stores user-configured network information; the OVN southbound database (ovn-sb-db) cluster primarily stores logical flow information available to the OVN controller; and the OVN communication (ovn-northd) cluster is responsible for translating user-configured network information into machine-readable logical flow information. These three OVN clusters are connected in series to form the OVN control plane. Any cluster failure will lead to OVN control plane failure. If more than half of the nodes in a single OVN cluster fail, recovery can only be achieved after the failed nodes are repaired. Users / maintenance personnel cannot quickly restore control plane functionality, reducing service capacity and user experience.

[0080] This application discloses an open virtual network control plane disaster recovery method, as shown in Figure 2. The method may include the following steps:

[0081] Step S11: Configure OVN control plane disaster recovery to obtain at least two service domains; the service domains include the OVN control plane, network service components, and the databases corresponding to the network service components.

[0082] First, configure OVN control plane disaster recovery, i.e., configure at least two service domains to ensure at least one backup service domain. Each service domain includes the OVN control plane, network service components, and their corresponding databases. The OVN control plane mainly includes processes like ovn-northd for translation work, and processes like ovn-nb-db and ovn-sb-db for providing database server services. Each process can exist in a cluster, providing high availability. The network service component (neutron) provides network support for the entire OpenStack environment, including Layer 2 switching, Layer 3 routing, load balancing, firewalls, and VPNs. The network service component provides a flexible framework; through configuration, both open-source and commercial software can be used to implement these functions. A database (db) is a repository for organizing, storing, and managing data according to data structures; it is a long-term, organized, shareable, and uniformly managed collection of large amounts of data stored on a computer; in the product, it exists as a service provider, offering operations such as data storage, querying, updating, and deleting.

[0083] As shown in Figure 3, the OVN control plane is divided into available domains, namely Service Domain 1 (ZONE1) and Service Domain 2 (ZONE2). Only the primary service domain is active, and the other service domains are backup service domains. Multiple backup service domains can be used according to actual disaster recovery needs. The principle is the same. Figure 3 introduces the case with only one backup service domain.

[0084] Step S12: Determine one service domain as the primary service domain and the remaining service domains as backup service domains.

[0085] Typically, the core data center is initially selected as the primary service domain, while the other service domains are used as backup service domains.

[0086] In some embodiments, before determining a service domain as the primary service domain, the process may further include: determining the number of existing service domains; if the number of service domains is greater than or equal to a preset number threshold, selecting one service domain from all service domains as the primary service domain; if the number of service domains is less than the preset number threshold, adding service domains until the number is greater than or equal to the preset number threshold. That is, based on the user's disaster recovery requirements, a preset number threshold can be configured, and by performing a number determination before determining the primary service domain, subsequent disaster recovery functionality can be ensured.

[0087] Step S13: Connect the control data plane of the synchronization server to the OVN control plane of the primary service domain.

[0088] After determining the primary service domain, the OVN data plane is connected to the OVN control plane of the primary service domain through the synchronization server control. The OVN data plane includes ovn-controller, which is the data plane controller responsible for executing traffic forwarding rules.

[0089] The sync server is configured for probing, control, and data backup. Probing primarily checks the health of the zone's OVN control plane cluster. Control primarily determines whether the current zone's Neutron and OVN control planes are providing services and whether the data plane connects to the providing zones. Data backup primarily determines from which zones data is synchronized to which zones.

[0090] In some embodiments, before connecting the data plane of the synchronization server to the OVN control plane of the primary service domain, the process may further include: determining whether the network service components of the primary service domain have completed data synchronization to the OVN control plane; if data synchronization is completed, then performing the operation of connecting the data plane of the synchronization server to the OVN control plane of the primary service domain. It is understood that starting the data plane only after the network service components have completed data synchronization to the OVN control plane can prevent service interruption.

[0091] Optionally, while synchronizing data with the OVN control plane through the network service component, the synchronization status is updated in the OVN northbound database according to the synchronization progress; the synchronization status includes not synchronized, synchronizing in progress, and synchronization completed; correspondingly, determining whether the network service component of the primary service domain has completed data synchronization with the OVN control plane may include: reading the synchronization status from the OVN southbound database; if the synchronization status is synchronization completed, then determining whether the network service component of the primary service domain has completed data synchronization with the OVN control plane. After Neutron starts, it creates / updates the `ovn_state` of type "neutron_sync_db" with `external_ids:state = no-sync` (not synchronized) in the `ovn_state` of `ovn-nb-db`. When Neutron starts synchronizing data with OVN, it updates the `external_ids:state` of type "neutron_sync_db" with `syncing` (synchronizing in progress). When Neutron finishes synchronizing data with OVN, it updates the `external_ids:state` of type "neutron_sync_db" with `synced` (synchronization complete). A new feature for Northd is added to translate the `ovn_state` in `nb-db` to `sb-db`. This method is used to detect whether the OVN control plane service is ready.

[0092] Step S14: Detect whether the OVN control plane in the primary service domain is running normally through the synchronization server.

[0093] After the primary service domain starts up, the synchronization server detects whether the OVN control plane in the primary service domain is running normally, so that if an abnormality is detected, the backup service domain can be started.

[0094] In some embodiments, detecting whether the OVN control plane in the primary service domain is operating normally via a synchronization server may include: writing first target data to the OVN northbound database of the OVN control plane in the primary service domain via the synchronization server; reading second target data from the OVN southbound database of the OVN control plane in the primary service domain via the synchronization server; and determining whether the OVN control plane in the primary service domain is operating normally by comparing the first target data and the second target data. It is understood that the primary function of the detection is to detect whether the OVN control plane cluster of the zone is normal; an optional detection method may be to write data to the OVN northbound database (ovn-nb-db) and confirm the OVN control plane cluster status based on whether data can be retrieved from the OVN southbound database (ovn-sb-db).

[0095] In some embodiments, determining whether the OVN control plane in the main service domain is operating normally by comparing the first target data and the second target data may include: determining whether the first target data and the second target data are the same; determining the time interval between the first timestamp corresponding to the first target data and the second timestamp corresponding to the second target data; if the first target data and the second target data are the same, and the time interval is less than a preset duration threshold, then the OVN control plane in the main service domain is determined to be operating normally; if the first target data and the second target data are different, and the time interval is greater than or equal to the preset duration threshold, then the OVN control plane in the main service domain is determined to be operating abnormally. That is, the operating status is comprehensively judged from two aspects: whether the corresponding data is read, and the time interval between reading the data. Optionally, data can be written to the northbound database at preset intervals (e.g., every 5 seconds). For example, "1" is written initially, followed by "2" after 5 seconds, then "3" after another 5 seconds, and so on. If the written data reaches 100, but the read data is not 100, it indicates an anomaly in the control plane. To improve accuracy, time is also considered. A current timestamp is added when writing data, and ovn-northd adds a timestamp based on the current time when translating data to the southbound database. By comparing the two timestamps, the operating status of the control panel can be analyzed. If the time interval exceeds a preset redundancy duration, an anomaly in the control plane is also determined. The redundancy duration can be set according to the actual load of ovn.

[0096] Optionally, a new table `ovn_state` needs to be added to both `ovn-nb-db` and `ovn-sb-db`. During probing, a `external_ids:count` of type "ovn_control_plane_test" is created / updated in `ovn_state` of `ovn-nb-db`, where `count` equals the current timestamp. Northd adds a function to translate `ovn_state` from `nb-db` to `sb-db`. After inserting data, the sync-server retrieves the `count` value of type "ovn_control_plane_test" from `ovn-sb-db`. The data plane is identified as faulty by comparing the difference between the timestamp and the last update. The redundancy error range can be set according to the actual load of OVN. Additionally, if the synchronization server cannot connect to `ovn-nb-db` or `ovn-sb-db`, it is also considered a fault. The above scheme enables OVN control plane status probing.

[0097] Step S15: If the OVN control plane in the primary service domain is malfunctioning, disaster recovery is initiated. The original primary service domain is used as the backup service domain. A target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is used as the new primary service domain.

[0098] If the control plane is detected to be malfunctioning, control plane disaster recovery is initiated. Specifically, the current primary service domain is reassigned to a backup service domain. A target backup service domain is selected from all backup service domains other than the original primary service domain and designated as the new primary service domain. This enables automatic deployment control of the OVN cluster, allowing for rapid service recovery after a failure. It resolves the fault without impacting business operations, increasing product intelligence and fault tolerance. Initiating disaster recovery can also involve stopping the primary service domain, which halts data updates to the database corresponding to the network service components. This prevents data inconsistencies during the disaster recovery process.

[0099] In some embodiments, selecting a target backup service domain from all backup service domains other than the original primary service domain may include: obtaining the priority of each backup service domain; selecting the backup service domain with the highest priority as the target backup service domain; and prioritizing backup service domains that are closer to the primary service domain. It is understood that, in order to maintain the service performance of the primary service domain as much as possible, the backup service domain closest to the original primary service domain is preferentially selected as the new primary service domain. For example, if the original primary service domain is in Beijing, and the two backup service domains are in Tianjin and Shanghai respectively, then the backup service domain in Tianjin is preferentially selected as the new primary service domain.

[0100] In some embodiments, the above-described Open Virtual Network (OVN) control plane disaster recovery method may further include: obtaining a disaster recovery instruction issued by an administrator; and initiating OVN control plane disaster recovery according to the disaster recovery instruction. That is, not only can disaster recovery be automated, but manual control of the OVN control plane disaster recovery switch is also possible. For example, operations and maintenance personnel can perform uninterrupted business product upgrades, cluster expansion, and data center migrations through manual disaster recovery switching.

[0101] In some embodiments, the above-described open virtual network control plane disaster recovery method may further include: obtaining an instruction to add or delete a backup service domain issued by an administrator; and updating the backup service domain according to the instruction. That is, backup service domains can be added or deleted at any time as needed throughout the process.

[0102] After designating the target backup service domain as the new primary service domain, the process also includes: determining whether the network service components of the new primary service domain have completed data synchronization with the OVN control plane within the new primary service domain; if data synchronization is complete, connecting the data plane to the OVN control plane of the new primary service domain via a synchronization server; and probing whether the OVN control plane in the new primary service domain is functioning correctly via a synchronization server. In other words, after each new primary service domain is determined, the steps of data synchronization determination, data plane connection, and probing are repeated.

[0103] As can be seen from the above, this embodiment configures OVN control plane disaster recovery to obtain at least two service domains. Each service domain includes the OVN control plane, network service components, and the database corresponding to the network service components. One service domain is determined as the primary service domain, and the remaining service domains are designated as backup service domains. The control data plane of the synchronization server is connected to the OVN control plane of the primary service domain. The synchronization server is used to detect whether the OVN control plane in the primary service domain is operating normally. If the OVN control plane in the primary service domain is abnormal, disaster recovery is initiated, the original primary service domain is designated as the backup service domain, a target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is designated as the new primary service domain. As can be seen, by adding a backup service domain for OVN control plane disaster recovery and by detecting the running status of the OVN control plane through a synchronization server, the backup service domain can be automatically activated as the primary service domain when the OVN control plane in the primary service domain is abnormal. Furthermore, the connection between the data plane and the OVN control plane is realized through the synchronization server, ensuring the continuity of business and avoiding the problem of OVN control plane service interruption due to the failure of more than half of the nodes. This improves OVN service capabilities and fault tolerance, and enhances the user experience.

[0104] This application discloses an optional open virtual network control plane disaster recovery method, as shown in Figure 4. The method may include the following steps:

[0105] Step S21: Configure OVN control plane disaster recovery to obtain at least two service domains; the service domains include the OVN control plane, network service components, and the databases corresponding to the network service components.

[0106] Step S22: Determine one service domain as the primary service domain and the remaining service domains as backup service domains.

[0107] Step S23: Connect the control data plane of the synchronization server to the OVN control plane of the primary service domain.

[0108] Step S24: Synchronize the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the standby zone through the synchronization server.

[0109] In this embodiment, data synchronization between multiple service domains is supported. That is, by adding a backup service domain, the main service domain automatically synchronizes data. Using the backup service domain as a data backup can prevent data loss and improve product security.

[0110] Step S25: Detect whether the OVN control plane in the primary service domain is running normally through the synchronization server.

[0111] Step S26: If the OVN control plane in the primary service domain is malfunctioning, disaster recovery is initiated. The original primary service domain is used as the backup service domain. A target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is used as the new primary service domain.

[0112] In this embodiment, after disaster recovery is initiated, the process may further include: stopping the synchronization server from synchronizing the content of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the backup zone. That is, the data backup operation is stopped after disaster recovery is initiated. If the data backup operation is not stopped after disaster recovery is initiated, the original primary service domain will continue to synchronize data, causing the new primary service domain and the original primary service domain to synchronize data simultaneously, resulting in data anomalies.

[0113] The optional processes for steps S21-S23 and S25 can be referred to the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0114] As can be seen from the above, this embodiment synchronizes the content of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the backup area through a synchronization server. It supports data synchronization between multiple service domains; that is, by adding a backup service domain, the primary service domain automatically performs data synchronization. Using the backup service domain as a data backup can prevent data loss and improve product security.

[0115] For example, Figure 5 shows a flowchart of an optional open virtual network control plane disaster recovery method, which includes the following steps:

[0116] S30: When configuring disaster recovery, at least two or more zones must be available to provide services.

[0117] S31: Select the zone currently providing services as the primary zone and the other zones as backup zones.

[0118] S32: Get the value of external_ids:state of the ovn_state table of the ovn-sb-db of the main zone with type neutron_sync_db. When it is synced, it means that all data of neutron has been written to ovn and ovn can provide services and notify the data plane to connect to the main zone. If it is not synced, query again after one second until state is synced.

[0119] S33: The primary zone begins synchronizing neutron's database data to all backup zones.

[0120] S34: Begin probing the control plane status of the main zone ovn.

[0121] S35: When an anomaly is detected in the OVN control plane of the main zone, automatic disaster recovery is initiated, or manual intervention is also possible.

[0122] S36: Disaster recovery begins by stopping the services of the primary zone, which means stopping data updates in the Neutorn database. This is primarily to avoid potential data inconsistencies during the disaster recovery switchover. If the failure is due to a system crash, network outage, or other reasons, the service has already been stopped.

[0123] S37: Then stop the data synchronization from primary to backup.

[0124] S38: Select one from the backup zones to become the primary zone, and set the previous primary zone as the backup zone. If the failure is due to downtime, network outage, or other reasons, the setting from primary to backup will fail. However, since disaster recovery between zones was enabled before the failure, the zone will actively obtain its role after the failure is recovered. If it finds that it is a backup zone, it will automatically switch to the backup service zone, and there will be no situation where two zones are both primary service zones.

[0125] S39: Once the new primary zone is providing normal service, it will begin the next process from S32.

[0126] Through the above steps, control plane disaster recovery is achieved, ensuring business continuity and preventing OVN control plane service outages due to the failure of more than half of the nodes. This improves OVN service capabilities and fault tolerance, and enhances the user experience. It supports data synchronization between multiple service domains; by adding a backup service domain, the primary service domain automatically synchronizes data. Using the backup service domain as a data backup prevents data loss and improves product security.

[0127] Accordingly, this application also discloses an open virtual network control plane disaster recovery device, which includes:

[0128] Disaster recovery configuration module 11 is configured to configure OVN control plane disaster recovery, resulting in at least two service domains; the service domains include the OVN control plane, network service components, and the databases corresponding to the network service components.

[0129] The primary service domain determination module 12 is configured to determine one service domain as the primary service domain and the remaining service domains as backup service domains.

[0130] Data plane connection module 13 is configured to connect the data plane to the OVN control plane of the primary service domain via a synchronization server.

[0131] The detection module 14 is configured to detect whether the OVN control plane in the primary service domain is operating normally via the synchronization server.

[0132] Disaster recovery module 15 is configured to initiate disaster recovery if the OVN control plane in the primary service domain malfunctions, using the original primary service domain as a backup service domain, selecting a target backup service domain from all backup service domains other than the original primary service domain, and using the target backup service domain as the new primary service domain.

[0133] As can be seen from the above, this embodiment configures OVN control plane disaster recovery to obtain at least two service domains. Each service domain includes the OVN control plane, network service components, and the database corresponding to the network service components. One service domain is determined as the primary service domain, and the remaining service domains are designated as backup service domains. The control data plane of the synchronization server is connected to the OVN control plane of the primary service domain. The synchronization server is used to detect whether the OVN control plane in the primary service domain is operating normally. If the OVN control plane in the primary service domain is abnormal, disaster recovery is initiated, the original primary service domain is designated as the backup service domain, a target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is designated as the new primary service domain. As can be seen, by adding a backup service domain for OVN control plane disaster recovery and by detecting the running status of the OVN control plane through a synchronization server, the backup service domain can be automatically activated as the primary service domain when the OVN control plane in the primary service domain is abnormal. Furthermore, the connection between the data plane and the OVN control plane is realized through the synchronization server, ensuring the continuity of business and avoiding the problem of OVN control plane service interruption due to the failure of more than half of the nodes. This improves OVN service capabilities and fault tolerance, and enhances the user experience.

[0134] In some alternative embodiments, the open virtual network control plane disaster recovery device may include:

[0135] The judgment unit is configured to determine whether the network service components of the primary service domain have completed data synchronization with the OVN control plane before connecting to the OVN control plane of the primary service domain through the synchronization server control data plane;

[0136] The execution unit is configured to perform operations on the OVN control plane that connects to the primary service domain via the synchronization server control data plane if data synchronization is completed.

[0137] In some alternative embodiments, the open virtual network control plane disaster recovery device may further include:

[0138] The first data synchronization unit is configured to synchronize data with the OVN control plane through the network service component and update the synchronization status in the OVN northbound database according to the synchronization progress; the synchronization status includes not synchronized, synchronizing in progress, and synchronization completed.

[0139] Correspondingly, the judgment unit includes:

[0140] The status reading unit is configured to read the synchronization status from the OVN southbound database;

[0141] The execution unit is configured to determine whether the network service component of the main service domain has completed data synchronization with the OVN control plane if the synchronization status is "synchronization complete".

[0142] In some alternative embodiments, running the detection module 14 may include:

[0143] The data writing unit is configured to write the first target data to the OVN northbound database of the OVN control plane in the main service domain via a synchronization server.

[0144] The data reading unit is configured to read the second target data from the OVN southbound database of the OVN control plane in the main service domain via a synchronization server.

[0145] The operation judgment unit is configured to determine whether the OVN control plane in the main service domain is operating normally by comparing the first target data with the second target data.

[0146] In some optional embodiments, the operation determination unit may include:

[0147] The data judgment unit is configured to determine whether the first target data and the second target data are the same;

[0148] The time interval determination unit is configured to determine the time interval between a first timestamp corresponding to the first target data and a second timestamp corresponding to the second target data.

[0149] The normal operation determination unit is configured to determine that the OVN control plane in the main service domain is operating normally if the first target data and the second target data are the same and the time interval is less than a preset duration threshold.

[0150] The operation anomaly determination unit is configured to determine that the OVN control plane in the main service domain is abnormal if the first target data and the second target data are different and the time interval is greater than or equal to a preset duration threshold.

[0151] In some alternative embodiments, the open virtual network control plane disaster recovery device may further include:

[0152] The quantity determination unit is configured to determine the number of existing service domains before determining a service domain as the primary service domain;

[0153] The primary service selection unit is configured to select one service domain as the primary service domain from all service domains if the number of service domains is greater than or equal to a preset number threshold.

[0154] The service domain addition unit is configured to add service domains until the number of service domains is greater than or equal to the preset number threshold if the number of service domains is less than the preset number threshold.

[0155] In some alternative embodiments, the open virtual network control plane disaster recovery device may include:

[0156] The disaster recovery command acquisition unit is configured to acquire disaster recovery commands issued by the administrator;

[0157] The disaster recovery unit is configured to initiate OVN control plane disaster recovery based on disaster recovery instructions.

[0158] In some alternative embodiments, the open virtual network control plane disaster recovery device may include:

[0159] The add / delete command acquisition unit is configured to acquire add or delete commands for the backup service domain issued by the administrator;

[0160] The service domain update unit is configured to update the standby service domain based on add or delete commands.

[0161] In some alternative embodiments, the disaster recovery module 15 may include:

[0162] The service stop unit is configured to enable disaster recovery, stop the operation of the primary service domain, and stop data updates to the database corresponding to the network service components.

[0163] In some optional embodiments, the determining unit is further configured to determine whether the network service component of the new primary service domain has completed data synchronization to the OVN control plane within the new primary service domain;

[0164] The data plane connection module 13 is also configured to connect the data plane to the OVN control plane of the new primary service domain via the synchronization server if data synchronization is completed.

[0165] The detection module 14 is also configured to detect whether the OVN control plane is functioning correctly in the new primary service domain via the synchronization server.

[0166] In some alternative embodiments, the open virtual network control plane disaster recovery device may include:

[0167] The second data synchronization unit is configured to, after connecting to the OVN control plane of the primary service domain via the synchronization server control data plane, synchronize the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the standby zone via the synchronization server.

[0168] In some alternative embodiments, the disaster recovery module 15 may include:

[0169] The data synchronization stop unit is configured to stop the synchronization server from synchronizing the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the standby zone.

[0170] Furthermore, this application also discloses an electronic device, as shown in FIG6. The content in FIG6 should not be considered as any limitation on the scope of use of this application.

[0171] Figure 6 is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. The electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 is configured to store a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the open virtual network control plane disaster recovery method disclosed in any of the foregoing embodiments.

[0172] In this embodiment, the power supply 23 is configured to provide operating voltage to each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is configured to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0173] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored on it include the operating system 221, computer programs 222 and data 223 including the main service domain, etc., and the storage method can be temporary storage or permanent storage.

[0174] The operating system 221 is configured to manage and control the various hardware devices on the electronic device 20 and the computer program 222, so as to enable the processor 21 to perform calculations and processing on the massive data 223 in the memory 22. The operating system 221 can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the open virtual network control plane disaster recovery method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0175] Furthermore, embodiments of this application also disclose a computer program product, including a computer program / instruction, which, when executed by a processor, implements the aforementioned open virtual network control plane disaster recovery method.

[0176] Furthermore, this application also discloses a computer storage medium storing computer-executable instructions. When these instructions are loaded and executed by a processor, they implement the open virtual network control plane disaster recovery method steps disclosed in any of the foregoing embodiments. In this embodiment, the storage medium can be a non-volatile readable storage medium.

[0177] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0178] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0179] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0180] The above provides a detailed description of the open virtual network control plane disaster recovery method, apparatus, product, and medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A disaster recovery method for an open virtual network control plane, characterized in that, include: Configure an open virtual network control plane disaster recovery configuration to obtain at least two service domains; each service domain includes an open virtual network control plane, network service components, and a database corresponding to the network service components. Designate one service domain as the primary service domain and the remaining service domains as backup service domains; The data plane of the synchronization server is connected to the open virtual network control plane of the main service domain. The synchronization server is used to detect whether the open virtual network control plane in the main service domain is operating normally. If the open virtual network control plane in the primary service domain malfunctions, disaster recovery is initiated. The original primary service domain is used as a backup service domain. A target backup service domain is selected from all backup service domains other than the original primary service domain, and the target backup service domain is used as the new primary service domain.

2. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, Before connecting to the Open Virtual Network Control Plane of the primary service domain via the synchronization server control data plane, the process also includes: Determine whether the network service components of the main service domain have completed data synchronization with the open virtual network control plane; If data synchronization is completed, then the operation of connecting the data plane of the synchronization server to the open virtual network control plane of the main service domain is performed.

3. The open virtual network control plane disaster recovery method according to claim 2, characterized in that, Also includes: The network service component synchronizes data with the Open Virtual Network control plane and updates the synchronization status in the Open Virtual Network Northbound Database according to the synchronization progress; the synchronization status includes not synchronized, synchronizing in progress, and synchronization completed. The step of determining whether the network service components of the main service domain have completed data synchronization with the open virtual network control plane includes: Read the synchronization status from the Southbound database of the Open Virtual Network; If the synchronization status is "synchronization complete", then the network service component of the main service domain is determined to have completed data synchronization with the open virtual network control plane.

4. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, The step of detecting whether the open virtual network control plane in the main service domain is running normally through the synchronization server includes: The synchronization server writes the first target data to the Open Virtual Network Northbound Database of the Open Virtual Network Control Plane in the main service domain; The second target data is obtained by reading the Open Virtual Network Southbound Database of the Open Virtual Network Control Plane in the main service domain through the synchronization server; By comparing the first target data with the second target data, it is determined whether the open virtual network control plane in the main service domain is operating normally.

5. The open virtual network control plane disaster recovery method according to claim 4, characterized in that, The step of determining whether the open virtual network control plane in the main service domain is operating normally by comparing the first target data with the second target data includes: Determine whether the first target data and the second target data are the same; Determine the time interval between the first timestamp corresponding to the first target data and the second timestamp corresponding to the second target data; If the first target data is the same as the second target data, and the time interval is less than a preset duration threshold, then it is determined that the open virtual network control plane in the main service domain is operating normally. If the first target data is different from the second target data, and the time interval is greater than or equal to a preset duration threshold, it is determined that the open virtual network control plane in the main service domain is operating abnormally.

6. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, Before determining a service domain as the primary service domain, the process also includes: Determine the number of existing service domains; If the number of service domains is greater than or equal to a preset threshold, then select one service domain from all service domains as the primary service domain. If the number of service domains is less than a preset threshold, then add service domains until the number is greater than or equal to the preset threshold.

7. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, Also includes: Obtain disaster recovery instructions issued by the administrator; Initiate open virtual network control plane disaster recovery according to the disaster recovery instructions.

8. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, Also includes: Obtain commands from the administrator to add or delete backup service domains; Update the standby service domain according to the add instruction or the delete instruction.

9. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, The activation of disaster recovery includes: Initiate disaster recovery by stopping the operation of the primary service domain, thereby halting data updates to the database corresponding to the network service component.

10. The open virtual network control plane disaster recovery method according to claim 1, characterized in that, After designating the target backup service domain as the new primary service domain, the method further includes: Determine whether the network service components of the new primary service domain have completed data synchronization to open the virtual network control plane within the new primary service domain; If data synchronization is completed, the data plane is controlled by the synchronization server to connect to the open virtual network control plane of the new primary service domain. The synchronization server is used to detect whether the open virtual network control plane in the new primary service domain is functioning correctly.

11. The open virtual network control plane disaster recovery method according to any one of claims 1 to 10, characterized in that, After connecting to the Open Virtual Network Control Plane of the primary service domain via the synchronization server control data plane, the process further includes: The synchronization server synchronizes the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the backup zone.

12. The open virtual network control plane disaster recovery method according to claim 11, characterized in that, After the disaster recovery is initiated, it also includes: Stop the operation of the synchronization server to synchronize the contents of the database corresponding to the network service component in the primary service domain to the database corresponding to the network service component in the backup zone.

13. The open virtual network control plane disaster recovery method according to claim 11, characterized in that, Selecting a target backup service domain from all backup service domains other than the original primary service domain includes: Obtain the priority of each backup service domain; Select the highest priority backup service domain as the target backup service domain.

14. The open virtual network control plane disaster recovery method according to claim 11, characterized in that, Selecting a target backup service domain from all backup service domains other than the original primary service domain includes: The backup service domain that is closest to the original primary service domain among all backup service domains is selected as the target backup service domain.

15. The open virtual network control plane disaster recovery method according to claim 11, characterized in that, The step of determining one service domain as the primary service domain and the remaining service domains as backup service domains includes: The core service domain among the at least two service domains is designated as the primary service domain, and the remaining service domains are designated as the backup service domains.

16. An open virtual network control plane disaster recovery device, comprising: The disaster recovery configuration module is configured to configure open virtual network control plane disaster recovery, resulting in at least two service domains; The service domain includes an open virtual network control plane, network service components, and the database corresponding to the network service components; The primary service domain determination module is configured to determine one service domain as the primary service domain and the remaining service domains as backup service domains. The data plane connection module is configured to connect the data plane to the open virtual network control plane of the primary service domain via a synchronization server. The detection module is configured to detect whether the Open Virtual Network Control Plane in the main service domain is operating normally through the synchronization server. The disaster recovery module is configured to activate disaster recovery if the open virtual network control plane in the primary service domain malfunctions, using the original primary service domain as a backup service domain, selecting a target backup service domain from all backup service domains other than the original primary service domain, and using the target backup service domain as the new primary service domain.

17. The open virtual network control plane disaster recovery device according to claim 16, characterized in that, The device further includes: The judgment unit is configured to determine whether the network service components of the main service domain have completed data synchronization with the open virtual network control plane before connecting to the open virtual network control plane of the main service domain through the synchronization server control data plane; The execution unit is configured to perform the operation of connecting the open virtual network control plane of the main service domain through the synchronization server control data plane if data synchronization is completed.

18. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the open virtual network control plane disaster recovery method according to any one of claims 1 to 15.

19. An electronic device, characterized in that, include: Memory, configured to store computer programs; A processor is configured to execute the computer program to implement the open virtual network control plane disaster recovery method as described in any one of claims 1 to 15.

20. A computer-readable storage medium, characterized in that, It is configured to store a computer program; wherein the computer program, when executed by a processor, implements the open virtual network control plane disaster recovery method as described in any one of claims 1 to 15.

Images