Routing information broadcasting method and device, equipment and medium

Abstract

The invention relates to the technical field of cloud transmission, particularly can be applied to a financial network scene, and discloses a routing information broadcasting method and device, equipment and a medium. Switching the routing mode of the cloud native network from the first routing control mode to a second routing control mode through routing parameter configuration; configuring neighbor information of a border gateway protocol in the routing daemon process according to the second routing control mode; and synchronizing the routing information distributed by the cluster node to a routing daemon process, so that the routing daemon process broadcasts the routing information distributed by the cluster node to external network equipment according to the neighbor information of the border gateway protocol. The application range of a cloud native network in a complex network environment can be expanded, and the requirements of complex deployment scenes and network environments can be met.

Description

Technical Field

[0001] The present invention relates to the field of cloud transmission technology, and can be specifically applied to financial network scenarios, and particularly relates to a method, device, equipment and medium for broadcasting routing information. Background Art

[0002] The rapid development of cloud-native applications has brought new requirements for network connection and access. Cloud-native networks based on the Extended Berkeley Packet Filter (eBPF) technology provide a highly flexible, scalable and secure solution to meet the network and security requirements of cloud-native applications. Especially for financial scenarios, the eBPF technology can accurately collect the metadata of the financial network, filter sensitive information according to regulatory requirements, generate compliance reports, and help financial institutions meet compliance requirements such as data isolation and audit traceability. The eBPF technology can also dynamically analyze the network latency and bandwidth occupancy between microservices in the financial network, optimize the load balancing strategy, and improve the response efficiency in high-frequency trading scenarios.

[0003] In related technologies, cloud-native networks based on the eBPF technology support the Border Gateway Protocol. Through the Border Gateway Protocol, the routing information within the cluster can be broadcast to external network devices, such as physical routers or switches, to achieve cross-network communication. However, during the broadcast process of routing information, due to the strong dependence of the Border Gateway Protocol, for financial enterprises with complex network requirements, the application scope of cloud-native networks in the financial network environment will be restricted, and it is difficult to meet the network environment requirements of financial scenarios. Summary of the Invention

[0004] The present invention provides a method, device, computer equipment and medium for broadcasting routing information, so as to solve the technical problem that in the related technology, during the broadcast process of routing information, due to the strong dependence of the Border Gateway Protocol, for financial enterprises with complex network requirements, the application scope of cloud-native networks in the financial network environment will be restricted, and it is difficult to meet the network environment requirements of financial scenarios.

[0005] In a first aspect, a method for broadcasting routing information is provided, including:

[0006] During the process of deploying cloud-native network components, switch the routing mode of the cloud-native network from a first routing control mode to a second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the routing daemon deployed on the host using the Border Gateway Protocol;

[0007] Configure the neighbor information of the Border Gateway Protocol (BGP) in the routing daemon according to the second routing control mode, where the neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices;

[0008] Synchronize the routing information allocated to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information allocated to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0009] In a second aspect, a routing information broadcasting device is provided, including:

[0010] A switching unit, configured to switch the routing mode of the cloud native network from a first routing control mode to a second routing control mode through routing parameter configuration during the deployment of cloud native network components. The first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the Border Gateway Protocol through a routing daemon deployed on the host;

[0011] A configuration unit, configured to configure the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode, where the neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices;

[0012] A broadcasting unit, configured to synchronize the routing information allocated to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information allocated to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0013] In a third aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above routing information broadcasting method are implemented.

[0014] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above routing information broadcasting method are implemented.

[0015] In the solution implemented by the above-mentioned method, device, computer device, and storage medium for broadcasting routing information, during the process of deploying cloud-native network components by the client, the routing mode of the cloud-native network can be switched from the first routing control mode to the second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol (BGP), and the second routing control mode is used to exchange routing information using the routing daemon deployed on the host using the Border Gateway Protocol. Configure the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode. The neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and the external network device. Synchronize the routing information allocated to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information allocated to the cluster node to the server side of the external network device according to the neighbor information of the Border Gateway Protocol. In the present invention, by switching the routing control mode, the cloud-native network is integrated with the routing daemon to enhance the routing function of the Border Gateway Protocol. Here, the routing daemon supports the extension of multiple border network protocols and has more advanced functional characteristics compared to the border network protocol, which can enhance the application scope of the cloud-native network in the financial network environment, thereby meeting the requirements of the financial scenario for the network environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0017] Figure 1 is an application environment schematic diagram of the method for broadcasting routing information in an embodiment of the present invention;

[0018] Figure 2 is a flowchart of the method for broadcasting routing information in an embodiment of the present invention;

[0019] Figure 3 is Figure 1 a schematic flowchart of a specific implementation manner of step S10 in

[0020] Figure 4 is a flowchart of the method for broadcasting routing information in another embodiment of the present invention;

[0021] Figure 5 is a flowchart of the method for broadcasting routing information in another embodiment of the present invention;

[0022] Figure 6 is a schematic structural diagram of the device for broadcasting routing information in an embodiment of the present invention;

[0023] Figure 7 It is a schematic structural diagram of a computer device in an embodiment of the present invention;

[0024] Figure 8 It is another schematic structural diagram of a computer device in an embodiment of the present invention. Detailed implementation manners

[0025] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0026] The method for broadcasting routing information provided by the embodiments of the present invention can be applied to an application environment such as Figure 1 In the process of deploying cloud-native network components, the routing mode of the cloud-native network is switched from the first routing control mode to the second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol (BGP), and the second routing control mode is used to exchange routing information using the routing daemon deployed on the host using the Border Gateway Protocol (BGP); configure the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode, and the neighbor information is used to ensure the connectivity between the cluster nodes where the routing daemon is located and external network devices; synchronize the routing information assigned to the cluster nodes to the routing daemon, so that the routing daemon broadcasts the routing information assigned to the cluster nodes to the server side of the external network device according to the neighbor information of the Border Gateway Protocol. In the present invention, by switching the routing control mode, the cloud-native network is integrated with the routing daemon to enhance the routing function of the Border Gateway Protocol. Here, the routing daemon supports the extension of multiple border network protocols and has more advanced functional characteristics than the border network protocol, which can enhance the application scope of the cloud-native network in the financial network environment, thereby meeting the requirements of the financial scenario for the network environment. Among them, the client can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, and portable wearable devices. The server side can be implemented by an independent server or a server cluster composed of multiple servers. The present invention will be described in detail through specific embodiments below.

[0027] Please refer to Figure 2 as shown in Figure 2 which is a flowchart of a method for broadcasting routing information provided by an embodiment of the present invention, including the following steps:

[0028] S10: During the process of deploying cloud-native network components, switch the routing mode of the cloud-native network from the first routing control mode to the second routing control mode through routing parameter configuration.

[0029] The routing information broadcasting method provided by the present invention can be applied to scenarios where the network in the cluster performs efficient routing with the external network. For example, when the services in the cluster need to be accessed externally, or when the cluster is distributed in multiple data centers and dynamic routing is required. Specifically, it can be applied to hybrid cloud or multi-cloud environments. In such an environment, there may be multiple clusters distributed in different cloud service providers or local data centers. The Border Gateway Protocol is used to dynamically exchange routing information to ensure that traffic can be correctly routed between different clusters. In the scenario of a hybrid cloud or multi-cloud environment, the cloud-native network is responsible for network communication and policies within the cluster, and the routing daemon is responsible for handling external routing using the Border Gateway Protocol. In this way, the entire network architecture can provide a flexible, efficient, and reliable network solution in various complex network environments, especially in scenarios that require dynamic routing and integration with the external network.

[0030] In this embodiment, the first routing control mode is used to exchange routing information using the Border Gateway Protocol. In the case of using the first routing control mode, the cloud-native network can achieve various routing functions by using the Border Gateway Protocol. For example, it can establish neighbor sessions with external network devices, and can also perform route advertisement and withdrawal, and can also support simple routing policies. The second routing control mode is used to exchange routing information using the Border Gateway Protocol through the routing daemon deployed on the host. In the second routing control mode, the cloud-native network does not use the Border Gateway Protocol, but is responsible for managing the container network, allocating routing information for cluster nodes, writing the routing information into the local routing table, which is obtained by the routing daemon deployed on the host through the kernel routing table, and using the Border Gateway Protocol to broadcast the routing information.

[0031] It should be noted that due to the limitations of the cloud-native network, it is necessary to combine with other tools to support complex routing policies. At the same time, it is also necessary to configure the external router to receive connections from the cloud-native network cluster nodes using the Border Network Protocol and set appropriate routing policies. The embodiment of the present invention combines the cloud-native network with the routing daemon strategy for routing configuration. The routing daemon interacts with other peers using the Border Gateway Protocol to exchange routing information. At this time, the function of using the Border Gateway Protocol in the cloud-native network is turned off, and the routing daemon is pulled up by the host to provide the routing function of using the Border Gateway Protocol.

[0032] In a specific implementation scenario, the switching of the routing control mode requires explicitly shutting down the original routing function used by the cloud-native network, that is, the function of exchanging routing information using the Border Gateway Protocol (BGP). At the same time, the host starts a routing daemon process to implement the function of exchanging routing information using the Border Gateway Protocol through the routing daemon process. Among them, as Figure 3 shown, in step S10, that is, during the deployment of cloud-native network components, the routing mode of the cloud-native network is switched from the first routing control mode to the second routing control mode through routing parameter configuration, including the following steps:

[0033] S11: During the deployment of cloud-native network components, the function of exchanging routing information using the Border Gateway Protocol in the cloud-native network components is shut down through routing configuration parameters.

[0034] S12: Configure a routing daemon process on the host according to the cloud-native network so that the configured routing daemon process points to the routing information of the cluster nodes in the cloud-native network and exchanges the routing information using the Border Gateway Protocol.

[0035] For steps S11 - S12, through routing parameter configuration, the first routing control mode of the cloud-native network is shut down. After shutdown, the cloud-native network does not participate in any BGP-based routing advertisement or learning, but obtains routing information through the routing daemon process deployed on the host. Specifically, the routing information of the containers to be advertised can be defined in the configuration file of the routing daemon process through static configuration, and the obtained routing information can also be configured in the routing daemon process by obtaining the routing information of the cluster nodes in real time. Here, the routing daemon process serves as an independent routing control mode plane, can establish a Border Gateway Protocol session with physical network devices, can announce the routing network segments of the container network to the physical network, and can also learn external reachable routes from the physical network.

[0036] Generally speaking, the cloud-native network uses the Border Gateway Protocol to exchange routing information with external network devices. After shutting down the function of exchanging routing information using the Border Gateway Protocol in the cloud-native network components, the cloud-native network itself does not use the Border Gateway Protocol, and it is necessary to configure the routing daemon process to use the Border Gateway Protocol to exchange routing information.

[0037] Specifically, by setting the routing configuration parameter enable-bgp-control-plane = False, the cloud-native network component can be made to turn off the function of exchanging routing information using the Border Gateway Protocol (BGP), thus avoiding unnecessary network traffic and potential security risks. However, since BGP is a routing protocol running on an open network protocol, it may expose the topology structure and packet content to unauthorized third parties, which may in turn affect the network connectivity and routing capabilities. In this case, other routing protocols or technologies need to be used to ensure the normal operation of the network.

[0038] S20: Configure the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode.

[0039] In this embodiment, the neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices. Here, the external network devices can be switches or routers that need to establish a neighbor relationship using BGP with the cluster nodes in the cloud-native network. That is to say, the cloud-native network and the routing daemon run on different nodes or containers respectively, rather than being integrated. Although the cloud-native network itself supports the function of exchanging routing information using BGP, the configuration of the cloud-native network here needs to turn off the function of exchanging routes using BGP and instead use the routing daemon to replace this routing function in order to provide more complex routing functions through the routing daemon. At this time, if you want to broadcast the routing information generated by the cloud-native network through the routing daemon, you need to make the routing daemon establish neighbor information with external network devices using an external border protocol.

[0040] It should be noted that to ensure the correct dissemination of routing information, it is necessary to ensure that the correct routing information is written into the kernel routing table. That is to say, the neighbor information in the routing daemon is correctly set, including specifying the local AS number, the IP and AS number of the neighbor, and correctly exporting routes.

[0041] Specifically, to ensure that the cloud-native network is correctly configured to accurately generate the required routing information, it may be necessary to enable the function of the cloud-native network to use the Border Gateway Protocol (BGP) and specify the routing daemon as a peer. Further, when the cloud-native network transfers the routing information to the routing daemon, some transfer mechanisms are required, such as route reflection or sharing through the routing table. Then, the neighbor information of the Border Gateway Route is set in the routing daemon, and this neighbor information points to the IP address of the external network device, specifically including but not limited to information such as the correct AS number, neighbor address, authentication, etc. In addition, if the routing daemon wants to obtain the routes generated by the cloud-native network, it needs to receive the routes from the cloud-native network through the kernel routing table or a certain protocol. Finally, to enable the routing information generated by the cloud-native network to be obtained by the routing daemon, the routing information can be injected into the kernel routing table in the cloud-native network configuration. Correspondingly, the routing daemon reads the routes from the kernel and broadcasts them, or the cloud-native network can directly send the routing information to the routing daemon through a certain API or protocol.

[0042] S30: Synchronize the routing information allocated by the cluster nodes to the routing daemon, so that the routing daemon broadcasts the routing information allocated by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol.

[0043] In this embodiment, the cloud-native network is responsible for allocating routing information on the cluster nodes and writing the routing information into the kernel routing table. The routing daemon, as an independent process using the Border Gateway Protocol, reads the routing information allocated by the cluster nodes from the kernel routing table and broadcasts it to the external network devices with neighbor relationships using the Border Gateway Protocol.

[0044] In an actual application scenario, the above process of broadcasting routing information can be applied to the network environment of the financial scenario. Specifically, it can be applied to the integration process of network protocols in the financial scenario. The network environment of the financial scenario can be integrated with the routing daemon, and the routing control mode can be switched according to the financial business requirements to achieve dynamic selection of the optimal path. For example, high-frequency trading uses low-latency dedicated line routing, and batch clearing uses cost-priority links. Specifically, it can also be applied to border protection and traffic scheduling in the financial network scenario. The routing function of the enhanced Border Gateway Protocol can be used to filter abnormal route announcements at the financial network border, such as for locations like the data center exit and hybrid cloud gateway, to prevent route hijacking attacks.

[0045] It can be understood that the combination of the above steps S20 and S30 respectively realizes the function of establishing neighbor information using the Border Gateway Protocol and broadcasting routing information through the neighbor information. Specifically, in one implementation scenario, the neighbor information of the Border Gateway Protocol can be loaded by modifying the configuration file of the routing daemon. Among them, as Figure 4As shown, in step S20, that is, configuring the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode, includes the following steps:

[0046] S21: Obtain the routing configuration parameters of the cloud-native network according to the second routing control mode.

[0047] S22: Extract the neighbor information specified during the routing process from the routing configuration parameters.

[0048] S23: Apply the neighbor information specified during the routing process to the configuration file of the routing daemon.

[0049] In this embodiment, the routing configuration parameters are the routing parameters configured by the cloud-native network using the Border Gateway Protocol. Generally speaking, when the cloud-native network enables the function of exchanging routing information using the Border Gateway Protocol, it will be integrated with the routing daemon to automatically generate a configuration file. However, in this embodiment, after the function of exchanging routing information using the Border Gateway Protocol is turned off, when customizing the function of exchanging routing information using the Border Gateway Protocol, the configuration file for integration with the routing daemon is generated. For example, adding neighbor information or policies using the Border Gateway Protocol. This requires adjusting the configuration file of the routing daemon accordingly, and then triggering the reloading of the configuration file, without the need to restart the service.

[0050] Specifically, the user needs to configure the routing parameters of the cloud-native network using the Border Gateway Protocol to obtain the routing configuration parameters. For example, configuring the function parameters for enabling the Border Gateway Protocol in the cloud-native network, specifying the local AS number, specifying the neighbor IP address using the Border Gateway Protocol, allowing the routes that can be notified to the cluster nodes through the Border Gateway Protocol, etc. Correspondingly, restart the proxy end of the cloud-native network using the routing configuration parameters to ensure that the function of exchanging routing information using the Border Gateway Protocol is initialized and takes effect. It can be understood that after the cloud-native network enables the function of exchanging routing information using the Border Gateway Protocol, a configuration file of the routing daemon will be automatically generated. In order to accurately broadcast routing information to external network devices, when the cloud-native network switches the routing mode, it is necessary to check whether the configuration file of the daemon process contains the expected neighbor information. If the configuration file of the routing daemon does not contain the expected neighbor information, it is necessary to extract the neighbor information specified during the routing process from the routing configuration parameters, and correspondingly add or adjust it in the configuration file of the routing daemon, so as to apply the neighbor information specified during the routing process to the configuration file of the routing daemon. After modifying the configuration file, there is no need to restart the routing daemon service, but to reload the configuration file through the control command of the routing daemon.

[0051] It should be noted that in order to ensure the accuracy of the neighbor information of the border network protocol, the session state of the border network protocol can be verified, the session state of the border network protocol can be checked, and whether the routing of the cluster nodes uses the border network protocol for correct advertisement can be viewed.

[0052] Considering that when nodes of external network devices need to be added to the cloud-native network, the ability to automatically establish connections also needs to be synchronized without improvement. Further, after step S23, the above routing information broadcasting method further includes the following steps:

[0053] When nodes of external network devices are added to the cloud-native network, the newly added external network device nodes are dynamically discovered.

[0054] Using the routing parameters pre-defined for configuring the Border Gateway Protocol, establish a connection using the Border Gateway Protocol for the newly added external network device nodes to ensure the consistency of the corresponding configuration files in the routing daemon; or allocate fixed routing parameters for the newly added external network device nodes to establish a connection using the Border Gateway Protocol for the newly added external network device nodes by dynamically identifying the corresponding fixed routing parameters.

[0055] It can be understood that specifically after dynamically discovering the newly added external network device nodes, the connection using the Border Gateway Protocol for the newly added external network device nodes can be established in two different ways. One way is to perform standardized configuration on the design points of the newly added external network devices. In this process, the routing parameters pre-defined for configuring the Border Gateway Protocol are used to establish a connection using the Border Gateway Protocol for the newly added external network device nodes to ensure the consistency of the corresponding configuration files in the routing daemon. In this way, unified configuration parameters of the Border Gateway Protocol, such as AS numbers and authentication passwords, will be pre-defined for all external network device nodes to ensure the consistency of the configuration templates. Another way is to allocate fixed routing parameters for the newly added external network device nodes to establish a connection using the Border Gateway Protocol for the newly added external network device nodes by dynamically identifying the corresponding fixed routing parameters. In this way, a fixed IP segment can be allocated for the external network device nodes or DHCP reserved addresses can be used for easy dynamic identification.

[0056] Further, in order to ensure that the newly added external network service nodes can automatically update the corresponding routing parameters, the routing parameters configured using the Border Gateway Protocol can also be obtained based on the dynamic discovery mechanism, and the configuration file of the routing daemon is correspondingly generated, and the neighbor information of the border network protocol is included in this configuration file.

[0057] Correspondingly, in step S30, that is, synchronizing the routing information allocated by the cluster nodes to the routing daemon, so that the routing daemon broadcasts the routing information allocated by the cluster nodes to the external network devices according to the neighbor information of the Border Gateway Protocol, includes the following steps:

[0058] S31: When it is monitored that the routing information allocated by the cluster nodes changes, write the changed routing information into the configuration file of the routing daemon.

[0059] S32: Update the configuration file of the routing daemon by using a predefined template file.

[0060] S33: Reload the updated configuration file of the routing daemon, so that the routing daemon broadcasts the changed routing information to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0061] In this embodiment, the file template includes a static part and a dynamic part of the routing daemon configuration. The dynamic part is the changed routing information, and the changed routing information replaces the placeholder in the template file by adding a new route. The routing information allocated by the cluster nodes refers to the network segments allocated by the cluster nodes. When the routing information allocated by the cluster nodes changes, it may be necessary to add a new route to the configuration file of the routing daemon. For example, by defining a routing protocol, using the routing protocol to announce the route, or using an external gateway protocol to broadcast the route to the external network devices. Specifically, when it is monitored that the routing information allocated by the nodes changes, write the changed routing information into the configuration file of the routing daemon; update the configuration file of the routing daemon by using a predefined template file. The file template includes a static part and a dynamic part of the routing daemon configuration. The dynamic part is the changed routing information, and the changed routing information replaces the placeholder in the template file by adding a new route; reload the updated configuration file of the routing daemon, so that the routing daemon broadcasts the changed routing information to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0062] It should be noted that considering the configuration file path of the routing daemon in the host, the installation paths may be different for different distributions, and it is necessary to configure the path parameters or perform automatic detection to verify whether the configuration file in the routing daemon is correct after adding a new route.

[0063] Specifically, in another implementation scenario, the neighbor information of the Border Gateway Protocol can be loaded by combining an operation and maintenance tool with a script to render the configuration file of the routing daemon. Among them, as Figure 5 shown, in step S20, that is, configuring the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode, includes the following steps:

[0064] S24: Create a configuration template file for the routing daemon according to the second routing control mode.

[0065] S25: Inject the pre-maintained neighbor information of the Border Gateway Protocol (BGP) as variable data into the configuration template file for script rendering, and then distribute the script-rendered configuration file to the specified path of the cluster nodes.

[0066] S26: Configure the neighbor information of the Border Gateway Protocol to the routing daemon according to the specified path of the cluster nodes.

[0067] In this embodiment, the configuration template file includes dynamic variables and routing policies. The variable parameters are replaced with placeholders through the dynamic variables. Here, the dynamic variables include, but are not limited to, the local AD number, the IP of the external network device, the neighbor AS number, etc. The fixed routing policies can be solidified in the configuration template file through the routing policies to ensure that the dynamic variables only involve neighbor information. Here, the fixed routing policies can include, but are not limited to, routing filtering rules, protocol priorities, etc.

[0068] In this embodiment, the pre-maintained Border Network Protocol can be maintained through a static inventory file, which stores information such as the AS number, IP address, authentication password, etc. of the Border Network Protocol. It can also be supplemented through dynamic discovery. If the node information of the external network device changes dynamically, the cluster interface can be called through a script or the configuration management database can be queried to generate variable data in real time.

[0069] Specifically, in the script rendering configuration, an operation and maintenance tool can be used to parse the configuration file template, inject the pre-maintained neighbor information of the Border Gateway Protocol into the configuration file template to generate a script-rendered configuration file, and then distribute the script-rendered configuration file to the specified path of the cluster nodes.

[0070] Correspondingly, in step S30, that is, synchronizing the routing information allocated by the cluster nodes to the routing daemon so that the routing daemon broadcasts the routing information allocated by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol, includes the following steps:

[0071] S34: Listen for the routing information allocated by the cluster nodes through a timed script task to write the changed routing information into the configuration file of the routing daemon.

[0072] S35: Enable the routing daemon in the script to broadcast the routing information allocated by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol.

[0073] It can be understood that during the process of listening to the routing information of cluster node allocation through a timed script task, it is necessary to query the interface regularly to obtain the changed routing information, which may generate a large number of unnecessary requests and affect the performance of the cluster. Here, event-driven can be adopted to replace the polling of the timed script task, so that the script only needs to focus on the change of the interpreted version, and can also control the request frequency of the interface. A lightweight check method can also be used to directly read the local script file or check the kernel routing table, etc.

[0074] Furthermore, in order to optimize the execution function efficiency of the timed script task, here, multiple events can be merged and processed by setting a time window to avoid frequently reloading the configuration file of the routing daemon process.

[0075] It should be noted that if the timed script task is not used, and the script only responsible for receiving parameters, modifying the configuration file of the routing daemon process and reloading, then an operation and maintenance tool is required to configure and run the script. Of course, in the case of a small-scale cluster, the configuration file of the routing daemon process can also be configured manually.

[0076] It should be understood that the magnitudes of the sequence numbers of the steps in the above embodiments do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0077] In one embodiment, a routing information broadcasting device is provided, and the routing information broadcasting device corresponds one-to-one to the routing information broadcasting method in the above embodiment. As Figure 6 shown, the routing information broadcasting device includes a switching module 101, a configuration module 102, and a broadcasting module 103. The detailed description of each functional module is as follows:

[0078] The switching module 101 is used to switch the routing mode of the cloud-native network from the first routing control mode to the second routing control mode through routing parameter configuration during the process of deploying cloud-native network components. The first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the Border Gateway Protocol through a routing daemon process deployed on the host.

[0079] The configuration module 102 is used to configure the neighbor information of the Border Gateway Protocol in the routing daemon process according to the second routing control mode. The neighbor information is used to ensure the connectivity between the cluster node where the routing daemon process is located and external network devices.

[0080] The broadcasting module 103 is used to synchronize the routing information allocated by the cluster node to the routing daemon process, so that the routing daemon process broadcasts the routing information allocated by the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0081] In one embodiment, the switching module 101 is specifically configured to:

[0082] During the process of deploying cloud-native network components, disable the function of exchanging routing information using the Border Gateway Protocol in the cloud-native network components through routing configuration parameters;

[0083] Correspondingly, configure a routing daemon on the host according to the cloud-native network, so that the configured routing daemon points to the routing information of the cluster nodes in the cloud-native network, and uses the Border Gateway Protocol to exchange the routing information.

[0084] In one embodiment, the configuration module 102 is specifically configured to:

[0085] Obtain the routing configuration parameters of the cloud-native network according to the second routing control mode, where the routing configuration parameters are the routing parameters configured by the cloud-native network using the Border Gateway Protocol;

[0086] Extract the neighbor information specified during the routing process from the routing configuration parameters;

[0087] Apply the neighbor information specified during the routing process to the configuration file of the routing daemon.

[0088] In one embodiment, the configuration module 102 is further configured to:

[0089] After applying the neighbor information specified during the routing process to the configuration file of the routing daemon, when a node of an external network device is added to the cloud-native network, dynamically discover the newly added external network device node;

[0090] Use the routing parameters pre-defined to be configured using the Border Gateway Protocol to establish a connection using the Border Gateway Protocol for the newly added external network device node to ensure the consistency of the corresponding configuration file in the routing daemon; or allocate fixed routing parameters for the newly added external network device node to establish a connection using the Border Gateway Protocol for the newly added external network device node by dynamically identifying the corresponding fixed routing parameters.

[0091] In one embodiment, the broadcasting module 103 is specifically configured to:

[0092] When it is monitored that the routing information allocated to the cluster node changes, write the changed routing information into the configuration file of the routing daemon;

[0093] Update the configuration file of the routing daemon using a predefined template file, where the file template includes a static part and a dynamic part of the routing daemon configuration, the dynamic part being the changing routing information, and the changing routing information replacing placeholders in the template file through newly added routes;

[0094] Reload the updated configuration file of the routing daemon so that the routing daemon broadcasts the changing routing information to the external network device according to the neighbor information of the Border Gateway Protocol.

[0095] In one embodiment, the configuration module 102 is specifically configured to:

[0096] Create a configuration template file for the routing daemon according to the second routing control mode, where the configuration template file includes dynamic variables and routing policies;

[0097] Inject the pre-maintained neighbor information of the Border Gateway Protocol into the configuration template file as variable data for script rendering, so as to distribute the script-rendered configuration file to the specified path of the cluster nodes;

[0098] Configure the neighbor information of the Border Gateway Protocol into the routing daemon according to the specified path of the cluster nodes.

[0099] In one embodiment, the broadcast module 103 is specifically configured to:

[0100] Listen for the routing information allocated by the cluster nodes through a timed script task to write the changing routing information into the configuration file of the routing daemon;

[0101] Enable the routing daemon in the script to broadcast the routing information allocated by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol.

[0102] The present invention provides a routing information broadcast device, which integrates the cloud native network with the routing daemon by switching the routing control mode to implement enhanced routing functions of the Border Gateway Protocol. Here, the routing daemon supports the extension of multiple border network protocols and has more advanced functional features compared with the border network protocol, which can enhance the application scope of the cloud native network in the financial network environment, so as to meet the requirements of the financial scenario for the network environment.

[0103] For the specific limitations of the routing information broadcasting device, reference can be made to the limitations of the intelligent question answering method described above, which will not be elaborated here. Each module in the above routing information broadcasting device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above modules can be embedded in the processor of the computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each of the above modules.

[0104] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 7 shown. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage media. The network interface of the computer device is used to communicate with an external client through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the server side of a routing information broadcasting method.

[0105] In one embodiment, a computer device is provided. The computer device can be a client, and its internal structure diagram can be as Figure 8 shown. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The non-volatile storage media stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage media. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the client side of a routing information broadcasting method

[0106] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are realized:

[0107] During the process of deploying cloud-native network components, the routing mode of the cloud-native network is switched from a first routing control mode to a second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the routing daemon deployed on the host using the Border Gateway Protocol;

[0108] Configure the neighbor information of the Border Gateway Protocol (BGP) in the routing daemon according to the second routing control mode, where the neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices;

[0109] Synchronize the routing information assigned to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information assigned to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0110] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0111] During the process of deploying cloud-native network components, switch the routing mode of the cloud-native network from the first routing control mode to the second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the Border Gateway Protocol through the routing daemon deployed on the host;

[0112] Configure the neighbor information of the Border Gateway Protocol (BGP) in the routing daemon according to the second routing control mode, where the neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices;

[0113] Synchronize the routing information assigned to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information assigned to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

[0114] It should be noted that for the functions or steps that can be achieved by the above computer-readable storage medium or computer device, reference can be made to the relevant descriptions on the server side and the client side in the foregoing method embodiments. To avoid repetition, they will not be described in detail here.

[0115] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0116] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0117] The above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features. These modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention and should all be included in the protection scope of the present invention.

Claims

1. A method for broadcasting routing information, characterized in that, Including: During the process of deploying cloud-native network components, the routing mode of the cloud-native network is switched from a first routing control mode to a second routing control mode through routing parameter configuration. The first routing control mode is used to exchange routing information using the Border Gateway Protocol (BGP), and the second routing control mode is used to exchange routing information using the Border Gateway Protocol through a routing daemon deployed on the host; Configure the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode. The neighbor information is used to ensure the connectivity between the cluster node where the routing daemon is located and external network devices; Synchronize the routing information assigned to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information assigned to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol.

2. The broadcast method of routing information according to claim 1, characterized in that The step of switching the routing mode of the cloud-native network from the first routing control mode to the second routing control mode through routing parameter configuration during the process of deploying cloud-native network components includes: During the process of deploying cloud-native network components, disable the function of exchanging routing information using the Border Gateway Protocol in the cloud-native network components; Correspondingly, configure a routing daemon on the host according to the cloud-native network, so that the configured routing daemon points to the routing information of the cluster nodes in the cloud-native network and exchanges the routing information using the Border Gateway Protocol.

3. The broadcast method of routing information according to claim 1, characterized in that The step of configuring the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode includes: Obtain the routing configuration parameters of the cloud-native network according to the second routing control mode. The routing configuration parameters are the routing parameters configured by the cloud-native network using the Border Gateway Protocol; Extract the neighbor information specified during the routing process from the routing configuration parameters; Apply the neighbor information specified during the routing process to the configuration file of the routing daemon.

4. The method for broadcasting routing information according to claim 3, characterized in that, After applying the neighbor information specified during the routing process to the configuration file of the routing daemon, the method further includes: When a node of an external network device is added to the cloud-native network, dynamically discover the newly added external network device node; Use the pre-defined routing parameters configured using the Border Gateway Protocol to establish a connection using the Border Gateway Protocol for the newly added external network device node to ensure the consistency of the corresponding configuration file in the routing daemon; or assign fixed routing parameters to the newly added external network device node to establish a connection using the Border Gateway Protocol for the newly added external network device node by dynamically identifying the corresponding fixed routing parameters.

5. The method for broadcasting routing information according to claim 3, characterized in that, The step of synchronizing the routing information assigned to the cluster node to the routing daemon, so that the routing daemon broadcasts the routing information assigned to the cluster node to the external network devices according to the neighbor information of the Border Gateway Protocol, includes: When it is monitored that the routing information assigned to the cluster node changes, write the changed routing information to the configuration file of the routing daemon; Update the configuration file of the routing daemon using a predefined template file, where the file template includes a static part and a dynamic part of the routing daemon configuration, the dynamic part being the changing routing information, and the changing routing information replaces the placeholder in the template file by adding a new route; Reload the updated configuration file of the routing daemon so that the routing daemon broadcasts the changing routing information to the external network device according to the neighbor information of the Border Gateway Protocol.

6. The broadcast method of routing information according to claim 1, wherein The configuration of the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode includes: Create a configuration template file for the routing daemon according to the second routing control mode, where the configuration template file includes dynamic variables and routing policies; Inject the pre-maintained neighbor information of the Border Gateway Protocol into the configuration template file as variable data for script rendering, so as to distribute the script-rendered configuration file to the specified path of the cluster nodes; Configure the neighbor information of the Border Gateway Protocol into the routing daemon according to the specified path of the cluster nodes.

7. The method for broadcasting routing information according to claim 6, characterized in that, The synchronization of the routing information assigned by the cluster nodes to the routing daemon so that the routing daemon broadcasts the routing information assigned by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol includes: Listen for the routing information assigned by the cluster nodes through a timed script task to write the changing routing information into the configuration file of the routing daemon; Enable the routing daemon in the script to broadcast the routing information assigned by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol.

8. A broadcast device for routing information, characterized in that, Includes: A switching module for switching the routing mode of the cloud-native network from the first routing control mode to the second routing control mode during the deployment of the cloud-native network components through routing parameter configuration, where the first routing control mode is used to exchange routing information using the Border Gateway Protocol, and the second routing control mode is used to exchange routing information using the Border Gateway Protocol through the routing daemon deployed on the host; A configuration module for configuring the neighbor information of the Border Gateway Protocol in the routing daemon according to the second routing control mode, where the neighbor information is used to ensure the connectivity between the cluster nodes where the routing daemon is located and the external network device; A broadcast module for synchronizing the routing information assigned by the cluster nodes to the routing daemon so that the routing daemon broadcasts the routing information assigned by the cluster nodes to the external network device according to the neighbor information of the Border Gateway Protocol.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the routing information broadcasting method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the routing information broadcasting method according to any one of claims 1 to 7.

Images