CN113992574A

CN113992574A - Method, system and equipment for setting router binding node priority

Info

Publication number: CN113992574A
Application number: CN202111157603.9A
Authority: CN
Inventors: 周恒�; 秦海中
Original assignee: Jinan Inspur Data Technology Co Ltd
Current assignee: Jinan Inspur Data Technology Co Ltd
Priority date: 2021-09-30
Filing date: 2021-09-30
Publication date: 2022-01-28
Anticipated expiration: 2041-09-30
Also published as: CN113992574B

Abstract

The invention provides a method for setting the priority of a binding node of a router under openstack, which comprises the following steps: creating a router, expanding the attribute of the router, acquiring binding information agents from the information for creating the router through an interface for creating the router, and assembling each agent into a database object to be written into a database; the updating router is used for judging whether the updated router is provided with a gateway or not through an interface of the updating router; when a user calls an interface to acquire routing information, inquiring binding information from a database according to the router ID, updating a router object and returning; and updating the router binding information, which is used for inquiring the existing binding nodes in the database when the user calls the update router binding node interface, comparing the existing binding nodes with the binding nodes transmitted by the user, and updating the routing binding information according to the comparison result.

Description

Method, system and equipment for setting router binding node priority

Technical Field

The invention relates to the technical field of cloud computing, in particular to a method, a system, a storage medium and equipment for setting router binding node priority under openstack.

Background

Openstack is an open-source cloud platform management project and can provide extensible and flexible cloud platform management. Since Openstack has many tenants, in order to ensure the security of each tenant, in the cloud data center of Openstack, isolation is required between different tenants.

Currently, in a private cloud, Openstack uses a Virtual Router (vRouter) to forward east-west traffic and north-south traffic. Because adjusting the binding network node will cause the flow passing through the router to be interrupted, it will affect the production environment service. Therefore, the algorithm of automatic adjustment cannot well guarantee the service continuity. With manual operation, the network maintenance time can be specified, the service user is informed in advance, and some preparations are made in advance.

Disclosure of Invention

In view of this, the present invention provides a method, a system, a storage medium, and a device for setting a router binding node priority under an openstack, so as to supplement an automatic scheduling network node.

Based on the above purpose, the invention provides a method for setting the priority of a router binding node under openstack, which comprises the following steps:

creating a router, expanding the attribute of the router, acquiring binding information agents from the information for creating the router through an interface for creating the router, and assembling each agent into a database object to be written into a database;

the updating router is used for judging whether the updated router is provided with a gateway or not through an interface of the updating router;

when a user calls an interface to acquire routing information, inquiring the binding information from the database according to the router ID, updating a router object and returning; and

and updating the router binding information, which is used for inquiring the existing binding nodes in the database when the user calls the interface of the updated router binding nodes, comparing the binding nodes with the binding nodes transmitted by the user, and updating the routing binding information according to the comparison result.

In some embodiments, an "agent" is a list, where each agent object in the list contains an agent ID, an agent hostname, disabled, and render.

In some embodiments, the smaller the index of the agent object in the list, the higher the priority.

In some embodiments, when creating a router, the disabled attribute of the agent object is false, the replay is set to null, and the priority value of the priority attribute is sequentially increased by 1 starting from a specific value.

In some embodiments, if a gateway is bound when a router is created, after writing to the database, a plug-in triggers scheduling according to the currently docked l3 processing; if the gateway is not bound when the router is created, the disabled of the bound node is set to true and the replay is updated.

In some embodiments, when a router is updated, if it is determined that the updated router does not have a gateway, gateway node information bound to the router is updated, disabled is set to true, and replay is updated to nocateway; and if the updated router is judged to be provided with the gateway, acquiring all gateway node information bound by the router, setting disabled of the binding information with disabled being true and replay being Nogateway to false, setting replay to be null, and triggering scheduling according to the currently-butted l3 processing plug-in.

In some embodiments, when a user calls an interface for updating a router binding node, if the current router has a gateway node, inquiring an existing binding node in a database and comparing the existing binding node with the binding node transmitted by the user, and if the comparison does not exist, setting a disabled attribute of the node to true and setting a relay to Deleted; if the existing nodes are compared, the priority is adjusted as required, the binding nodes transmitted by the user are written into the database, then the plug-in processing triggering scheduling is carried out according to the currently-butted l3, if the gateway node does not exist in the current router, the existing binding nodes in the database are inquired and compared with the nodes transmitted by the user, and if the existing binding nodes do not exist in the current router, the existing binding nodes are directly deleted; and comparing the existing nodes, adjusting the priority level as required, writing the binding nodes transmitted by the user into the database, setting all the disabled binding nodes to true, and updating the replay.

In some embodiments, the method further includes adding a new scheduler, calling the legacy scheduler for scheduling before the new scheduler is scheduled, querying current binding node information according to the router ID after scheduling is completed,

calling a corresponding real implementation binding interface to delete the searched disabled nodes in the database; for the reason Deleted, delete the record in the database,

finding out nodes without disabled for the database, comparing the nodes with the scheduled list, and using the nodes if the nodes are in the scheduled list; if the current node is not in the scheduled list, updating the binding information of the binding node, setting the disabled attribute to true and updating the replay attribute;

and after the final binding node is determined, calling a corresponding real implementation binding interface for binding.

In another aspect of the present invention, a system for setting a router binding node priority under openstack is further provided, including:

the router creating module is used for creating a router, expanding the attribute of the router, acquiring binding information agents from the information for creating the router through an interface for creating the router, and assembling each agent into a database object to be written into a database;

the router updating module is used for judging whether the updated router is provided with a gateway or not through the interface of the updated router;

the router obtaining module is used for inquiring the binding information from the database according to the router ID when a user calls an interface to obtain the routing information, updating a router object and returning; and

and the binding information updating module is used for inquiring the existing binding nodes in the database when the user calls the binding node interface of the updating router, comparing the existing binding nodes with the binding nodes transmitted by the user, and updating the binding information of the router according to the comparison result.

In yet another aspect of the present invention, there is also provided a computer readable storage medium storing computer program instructions which, when executed, implement any one of the methods described above.

In yet another aspect of the present invention, a computer device is provided, which includes a memory and a processor, the memory storing a computer program, the computer program executing any one of the above methods when executed by the processor.

The invention has at least the following beneficial technical effects:

1. the invention provides a technical scheme which allows a user to set network nodes bound by a virtual machine router and can define the priority of each node by user, and the technical scheme is a supplement to an automatic scheduling network node. The user can freely control the physical path forwarded by the router under a more complex scene, and the forwarding path is optimized. The method is very suitable for high-order network users, and the usability of cloud products is enhanced;

2. the invention designs the processing of expanding and creating the route, updating the route and acquiring the route, and increases the interface for updating the route binding. A new plug-in is designed to process the expansion and the new interface. The new plug-in can self-define whether to load the plug-in according to whether the bottom layer supports the setting of the priority, provide this function, and is more flexible, easy-to-use.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.

Fig. 1 is a schematic diagram of a method for setting a router binding node priority under openstack according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a system for setting a router binding node priority under openstack according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a computer-readable storage medium for implementing a method for setting a router binding node priority under openstack according to an embodiment of the present invention;

fig. 4 is a schematic hardware structural diagram of a computer device for executing the method for setting the priority of the router binding node under openstack according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.

It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two non-identical entities with the same name or different parameters, and it is understood that "first" and "second" are only used for convenience of expression and should not be construed as limiting the embodiments of the present invention. Furthermore, the terms "comprises" and "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements does not include all of the other steps or elements inherent in the list.

Based on the above purpose, a first aspect of the embodiments of the present invention provides an embodiment of a method for setting a priority of a router binding node under openstack. Fig. 1 is a schematic diagram illustrating an embodiment of a method for setting a router binding node priority under openstack according to the present invention. As shown in fig. 1, the embodiment of the present invention includes the following steps:

step S10, creating a router, expanding the attribute of the router, acquiring binding information agents from the information of the router by the interface of the router, assembling each agent into a database object and writing the database object into the database;

step S20, updating the router, which is used to judge whether the updated router has gateway through the interface of the updating router;

step S30, when the user calls the interface to obtain the routing information, according to the router ID, inquiring the binding information from the database, updating the router object and returning;

and step S40, updating the router binding information, which is used for inquiring the existing binding nodes in the database when the user calls the router binding node updating interface, comparing the existing binding nodes with the binding nodes transmitted by the user, and updating the routing binding information according to the comparison result.

openstack is an open source cloud computing platform management platform project. The router is a router in openstack, a virtual router. The functions of the router are implemented by software. Each virtual router needs to run on a physical node to provide functionality. Typically, to ensure high availability of a virtual router, one virtual router is bound to multiple nodes at the same time. Some algorithms ensure that one node bound is the master node serving and the other nodes are the standby nodes. The network node and the gateway node have the same meaning in the scheme, and both represent physical servers for actually realizing the forwarding function of the router.

Openstack currently does not support manual setting of which nodes a router binds, and the priority of the nodes. At present, openstack has some algorithms for automatically setting the nodes bound by the router. And (3) random algorithm: and randomly selecting certain nodes from the candidate nodes. Minimum load algorithm: and all the nodes are sorted according to the number of the bound routers, and the nodes with the small number of the bound routers are selected. Available domain algorithm: and screening out nodes meeting the conditions of the available domain according to the allowed available domain set by the router, and then randomly selecting certain nodes. Once the algorithm determines the bound node, the algorithm will not change if the bound node is working properly. There is no way for binding nodes to change.

The flow passing through the router is interrupted due to the adjustment of the bound network nodes, and the production environment service is influenced. Therefore, the algorithm of automatic adjustment cannot well guarantee the service continuity. With manual operation, the network maintenance time can be specified, the service user is informed in advance, and some preparations are made in advance.

In the following scenes, a first scene is urgently required to be designated, a high-performance gateway node is newly added into a cluster, and a router needs high-performance forwarding; in a second scenario, a physical link of a certain network node in the cluster is temporarily not conformed to the forwarding of a router, but the cloud platform cannot automatically sense the failure, and the router needs to be modified to replace the bound network node; a third scenario, two related routers need to be bound on different nodes; and in a fourth scenario, manual designation is a good temporary scheme when the automatic algorithm cannot match all the features to be matched temporarily.

The invention realizes that the user can set the node bound by the virtual router and set the priority of the node by calling the interface. The method comprises the steps of creating an interface of a router, designing an extension to create and update the interface of the router, and processing binding information transmitted by a user. And a new updating interface is designed, so that the binding information of the router can be independently called and updated, and the efficiency is improved. There is also no suitable data table for storing priority information. New interfaces and database tables need to be designed.

In some embodiments, an "agent" is a list, where each agent object in the list contains an agent ID, an agent hostname, disabled, and render. The smaller the index of the agent object in the list, the higher the priority.

Table 1 an example of a database table

Column name	Type (B)	Allowed to be empty	Whether or not to make a key	Default value
					router_id	varchar(36)	Whether or not	Is that	null
agent_id	varchar(36)	Whether or not	Is that	null
					priority	int(11)	Whether or not	Whether or not	null
disabled	tinyint(1)	Is that	Whether or not	0
					reason	varchar(255)	Is that	Whether or not	null

According to the invention, the setting of the priority of the virtual router binding node is optional, and the user can automatically call and allocate the priority of the node and the node without setting the priority. For distinguishing the user-specified priority from the system automatic assignment, it may be, for example, agreed that the priority of the node of the user-specified binding is greater than 20, and the priority of the system automatic invocation is less than or equal to 20.

When a user specifies a node bound by a router, some circumstances may occur, causing the bound node not to actually take effect. For example, the original gateway node is removed, the original network node is not qualified for screening of the available domain and the like, and the original network node is disabled. The external gateway is removed or changed, etc. If the bound node cannot take effect, the condition of directly deleting the binding is adopted, the user can be confused, and the bound node disappears, so that the platform is considered to be in a problem. Therefore, the fields of the binding information of the present invention are increased:

disabled attribute: the binding condition judging module is used for identifying whether the current binding condition is effective or not;

the replay attribute: the method is used for indicating the reason of the current state, and is convenient for a user to know the failure reason of the node bound by the user.

The system for setting the router binding node priority under openstack provides a technical scheme for allowing a user to set a network node bound by a virtual machine router and customizing the priority of each node. Is a supplement to the automated scheduling network node. The user can freely control the physical path forwarded by the router under a more complex scene, and the forwarding path is optimized. Is very suitable for high-order network users. The method designs the process of expanding and creating the route, updating the route and acquiring the route, and increases the interface for updating the route binding. A new plug-in is designed to process the expansion and the new interface. The new plug-in can self-define whether to load the plug-in according to whether the bottom layer supports the setting of the priority, provide this function, and is more flexible, easy-to-use.

In some embodiments, when creating a router, the disabled attribute of the agent object is false, the replay is set to null, and the priority value of the priority attribute is sequentially increased by 1 starting from a specific value. For example, the specific value may be 20, or may be any other suitable value.

In this embodiment, if a gateway is bound when a router is created, after writing the gateway into the database, a plug-in is processed according to l3 currently docked to trigger scheduling; if the gateway is not bound when the router is created, the disabled of the bound node is set to true and the replay is updated.

Specifically, in this embodiment, when the user calls the update router binding node interface, if the current router has a gateway node, the existing binding node in the database is queried and compared with the binding node transmitted by the user, and if the comparison does not exist, the disabled attribute of the node is set to true and the release is set to released (the subsequent is actually Deleted by the scheduler). If the existing nodes are compared, the priority is adjusted as required, the binding nodes transmitted by the user are written into the database, then the plug-in processing triggering scheduling is carried out according to the currently-butted l3, if the gateway node does not exist in the current router, the existing binding nodes in the database are inquired and compared with the nodes transmitted by the user, and if the existing binding nodes do not exist in the current router, the existing binding nodes are directly deleted; and comparing the existing nodes, adjusting the priority level as required, writing the binding nodes transmitted by the user into the database, setting all the disabled binding nodes to true, and updating the replay.

In some embodiments, to ensure that the original schedule is available, it may be considered to inherit the original one of the schedulers. E.g., inherits the available domain scheduler, to ensure that scheduling can still be performed according to the available domain. The method also comprises the steps of adding a new scheduler, calling the inherited scheduler for scheduling before the new scheduler is scheduled, and inquiring the current binding node information according to the router ID after the new scheduler is scheduled. And calling the corresponding real implementation binding interface to delete the searched disabled node of the database (for example, if the node is ovn, the northbound interface needs to be called, and the bound node is actually deleted). For the replay as Deleted, the records in the database are Deleted. Finding out nodes without disabled for the database, comparing the nodes with the scheduled list, and using the nodes if the nodes are in the scheduled list; if the current node is not in the scheduled list, updating the binding information of the binding node, setting the disabled attribute to true and updating the replay attribute; after the final binding node is determined, the corresponding real implementation binding interface is called for binding (for example, if the interface is the interface ovn, the northbound interface needs to be called for binding update of the router gateway node).

According to the method for setting the priority of the router binding node under the openstack provided by the first aspect of the embodiment of the invention, a bottom CPU architecture is not depended on, and various architectures are supported: x86 arm, also can use ovn to implement l 3-router.

The invention distinguishes the nodes appointed by the user and the nodes automatically called by the system. For the nodes automatically called by the system, if the nodes are not actually effective, the direct deletion of the binding relationship is designed, because for the user, the nodes automatically called by the system do not care which nodes are.

The second aspect of the embodiment of the invention also provides a system for setting the priority of the router binding node under the openstack. Fig. 2 is a schematic diagram illustrating an embodiment of a system for setting a router binding node priority under openstack according to the present invention. As shown in fig. 2, a system for setting a router binding node priority under openstack includes: the router creating module 10 is configured to create a router, expand the attributes of the router, obtain binding information agents from information for creating the router through an interface of the router, and assemble each agent into a database object to be written into the database; the router updating module 20 is configured to determine whether the updated router further includes a gateway through an interface of the updated router; the router obtaining module 30 is configured to, when a user calls an interface to obtain routing information, query the binding information from the database according to a router ID, update a router object, and return the router object; and a binding information updating module 40, configured to, when the user invokes the update router binding node interface, query the existing binding nodes in the database, compare the existing binding nodes with the binding nodes transmitted by the user, and update the routing binding information according to the comparison result.

The system for setting the router binding node priority under the openstack provides a technical scheme for allowing a user to set a network node bound by a virtual machine router and customizing the priority of each node. Is a supplement to the automated scheduling network node. The user can freely control the physical path forwarded by the router under a more complex scene, and the forwarding path is optimized. Is very suitable for high-order network users. The method designs the process of expanding and creating the route, updating the route and acquiring the route, and increases the interface for updating the route binding. A new plug-in is designed to process the expansion and the new interface. The new plug-in can self-define whether to load the plug-in according to whether the bottom layer supports the setting of the priority, provide this function, and is more flexible, easy-to-use.

In a third aspect of the embodiment of the present invention, a computer-readable storage medium is further provided, and fig. 3 is a schematic diagram of a computer-readable storage medium for implementing the method for setting the priority of a router binding node under openstack according to the embodiment of the present invention. As shown in fig. 3, the computer-readable storage medium 3 stores computer program instructions 31, the computer program instructions 31 being executable by a processor. The computer program instructions 31 when executed implement the method of any of the embodiments described above.

It should be understood that all of the embodiments, features and advantages set forth above with respect to the method of setting router binding node priority under an openstack according to the present invention are equally applicable to the system and storage medium of setting router binding node priority under an openstack according to the present invention, without conflicting with each other.

In a fourth aspect of the embodiments of the present invention, there is further provided a computer device, including a memory 402 and a processor 401, where the memory stores a computer program, and the computer program, when executed by the processor, implements the method of any one of the above embodiments.

Fig. 4 is a schematic hardware structural diagram of an embodiment of a computer device for executing the method for setting a router binding node priority under openstack according to the present invention. Taking the computer device shown in fig. 4 as an example, the computer device includes a processor 401 and a memory 402, and may further include: an input device 403 and an output device 404. The processor 401, the memory 402, the input device 403 and the output device 404 may be connected by a bus or other means, and fig. 4 illustrates an example of a connection by a bus. The input device 403 can receive input numeric or character information and generate key signal inputs related to user settings and function controls under openstack for setting the router binding node priority system. The output device 404 may include a display device such as a display screen.

The memory 402, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the method for setting the priority of a router binding node under openstack in this embodiment of the present application. The memory 402 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the data storage area can store data created by using the method for setting the priority of the router binding node under openstack and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, memory 402 may optionally include memory located remotely from processor 401, which may be connected to local modules via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The processor 401 executes various functional applications and data processing of the server by running the nonvolatile software program, instructions and modules stored in the memory 402, that is, the method for setting the priority of the router binding node under openstack of the above method embodiment is implemented.

Finally, it should be noted that the computer-readable storage medium (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in a variety of forms such as synchronous RAM (DRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with the following components designed to perform the functions herein: a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP, and/or any other such configuration.

The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.

Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.

Claims

1. A method for setting router binding node priority under openstack is characterized by comprising the following steps:

2. The method of claim 1,

wherein, an agent is a list, and each agent object in the list comprises an agent ID, an agent hostname, disabled and a render.

3. The method of claim 2,

the smaller the subscript of the agent object in the list, the higher the priority.

4. The method of claim 3,

when a router is created, the disabled attribute of the agent object is false, the replay is null, and the priority values of the priority attributes are sequentially increased by 1 from a specific value.

5. The method of claim 4,

if a gateway is bound when a router is created, writing the gateway into the database, and triggering and scheduling according to a currently docked l3 processing plug-in;

and if the gateway is not bound when the router is created, setting the disabled of the binding node as true and updating the replay.

6. The method of claim 5,

when updating the router, if the updated router is judged not to have the gateway, updating the gateway node information bound by the router, setting disabled to true, and updating relay to be Nogateway;

and if the updated router is judged to be provided with the gateway, acquiring all gateway node information bound by the router, setting disabled of the binding information with disabled being true and replay being Nogateway to false, setting replay to be null, and triggering scheduling according to the currently-butted l3 processing plug-in.

7. The method of claim 6,

when a user invokes an update router binding node interface,

if the current router has a gateway node, inquiring the existing binding node in the database and comparing the binding node with the binding node transmitted by the user, and if the comparison does not exist, setting the disabled attribute of the node to true and setting the relay to Deleted; if the nodes exist in comparison, the priority is adjusted as required, the binding nodes transmitted by the user are written into the database, then the plug-in trigger scheduling is processed according to the currently docked l3, and

if the current router does not have the gateway node, inquiring the existing binding node in the database, comparing the binding node with the binding node transmitted by the user, and directly deleting the binding node if the binding node does not exist; and comparing the existing nodes, adjusting the priority level as required, writing the binding nodes transmitted by the user into the database, setting all the disabled binding nodes to true, and updating the replay.

8. The method of claim 1, further comprising

Adding a new scheduler, calling the inheritance scheduler for scheduling before the new scheduler is scheduled, inquiring the current binding node information according to the router ID after the scheduling is finished,

9. A system for setting router binding node priority under openstack is characterized by comprising:

10. A computer device comprising a memory and a processor, characterized in that the memory has stored therein a computer program which, when executed by the processor, performs the method according to any one of claims 1-8.