Method and system for customizing deployment of a simulated SDN switch network

Abstract

The application provides a method and system for customizing deployment of a simulated SDN switch network, comprising: step 1, creating a virtual node for each network node; step 2, configuring the connection of virtual network cards between the virtual nodes on a virtualization platform; step 3, placing a switch system program in a shared directory of a physical host, using remote control to traverse each virtual node, and commanding the virtual node to copy the switch system program from the shared directory to the system directory of the virtual node; step 4, using remote control to traverse each virtual node, and commanding the virtual node to execute the system program immediately or after a delay; and step 5, adding each virtual network card in the virtual node to the port of a virtual SDN switch, and completing the construction of the virtualized SDN network. The application sets a delay waiting mechanism for the switch system program, and realizes fine control over the start time of each virtualized SDN switch.

Description

Technical Field

[0001] This invention relates to the field of SDN switch network technology, and more specifically, to a method and system for custom-deploying simulated SDN switch networks. Background Technology

[0002] Software-defined networking (SDN) is a novel network architecture that separates the data forwarding and logical control of traditional network devices. It uses a centralized controller with standardized interfaces to manage and configure various network devices. Mininet, a widely used lightweight SDN network simulation platform, offers highly flexible capabilities for customizing SDN networks. Mininet supports the creation of virtual switches based on the open-source software Open vSwitch (OVS), which uses process virtualization technology to run up to 4096 node instances on a single OS kernel, facilitating the verification of SDN network functionality and performance.

[0003] Patent document CN110191065A (application number: CN201910493937.X) discloses a high-performance load balancing system based on software-defined networking, mainly addressing the problems of uneven load and link congestion in the core layer of existing data center networks. It includes a Fat-Tree underlying network and an SDN controller. The Fat-Tree underlying network deploys a traffic sampling and detection module, a DCTCP traffic control module, and a FEC-based encoded transmission module, which respectively perform real-time traffic sensing and differentiation between mouse-flow and image-flow functions, adjust port traffic rates based on link latency, and add redundant packets to reduce mouse-flow latency.

[0004] When performing SDN network simulation, the current simulation platform Mininet lacks the ability to customize and control the system behavior of virtualized SDN switch nodes (referred to as virtual nodes). Specifically:

[0005] (1) After the topology of a simulated network is completed, the startup process of all virtual nodes is automatically performed by the SDN simulation platform. Users cannot decide the startup time of a network node or the startup order of certain nodes.

[0006] (2) The system program path loaded when the virtual node starts is also configured by the system default and cannot be changed for each virtual node.

[0007] Therefore, current SDN simulation platforms cannot meet the needs of fine-grained deployment of simulated SDN networks. Summary of the Invention

[0008] To address the shortcomings of existing technologies, the purpose of this invention is to provide a method and system for customizing the deployment of simulated SDN switch networks.

[0009] The method for customizing and deploying a simulated SDN switch network according to the present invention includes:

[0010] Step 1: Based on the user's SDN network topology, use the virtualization platform on the physical host to create an independent virtual node for each network node. When creating the virtual node, configure the virtual network card of the virtual node and the file sharing directory between the virtual node and the physical host. Treat each virtual node as a virtual SDN switch without loading system programs.

[0011] Step 2: Configure the virtual network interface card (NIC) connections between each virtual node on the virtualization platform according to the connection relationships in the network topology;

[0012] Step 3: Place the switch system program in the shared directory of the physical host, and use remote control to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to the system directory of the virtual node;

[0013] Step 4: Based on the user's configuration of the SDN switch startup timing, traverse each virtual node remotely and command the virtual node to execute the system program immediately or after a delay.

[0014] Step 5: After the system program starts, add each virtual network card in the virtual node to the port of the virtual SDN switch to complete the construction of the virtualized SDN network.

[0015] Preferably, the Docker command is used to create and run a container for each network node, with each container running a Linux operating system and a shared destination location set up within the container with the physical host.

[0016] Preferably, use Docker commands to create bridge-type networks, and use the add network command to add the created network to the container. Each network added to a container is equivalent to adding another network card.

[0017] Preferably, the OVS program files on the physical host are placed in a shared directory between the physical host and the container, and the OVS program files on the physical host are copied to the file system of each container by logging into the container.

[0018] Preferably, based on the user's requirements for the startup timing of the SDN switch, remote login is made to each container, and the execution of the OVS program is controlled using a delay command. After the OVS program starts, each network card in the container is added to the OVS port system to complete the construction of the virtualized SDN network.

[0019] The system for custom deployment of a simulated SDN switch network according to the present invention includes:

[0020] Module M1: Based on the user's SDN network topology, it uses the virtualization platform in the physical host to create an independent virtual node for each network node. When creating the virtual node, it configures the virtual network card of the virtual node and the file sharing directory between the virtual node and the physical host, and treats each virtual node as a virtual SDN switch without loading system programs.

[0021] Module M2: Configures the connection of virtual network cards between virtual nodes on the virtualization platform according to the connection relationship in the network topology;

[0022] Module M3: Places the switch system program in the shared directory of the physical host, and uses remote control to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to the virtual node's system directory;

[0023] Module M4: Based on the user's configuration of the SDN switch startup timing, it remotely controls each virtual node to execute or delay the execution of system programs.

[0024] Module M5: After the system program starts, it adds each virtual network card in the virtual node to the port of the virtual SDN switch, thus completing the construction of the virtualized SDN network.

[0025] Preferably, the Docker command is used to create and run a container for each network node, with each container running a Linux operating system and a shared destination location set up within the container with the physical host.

[0026] Preferably, use Docker commands to create bridge-type networks, and use the add network command to add the created network to the container. Each network added to a container is equivalent to adding another network card.

[0027] Preferably, the OVS program files on the physical host are placed in a shared directory between the physical host and the container, and the OVS program files on the physical host are copied to the file system of each container by logging into the container.

[0028] Preferably, based on the user's requirements for the startup timing of the SDN switch, remote login is made to each container, and the execution of the OVS program is controlled using a delay command. After the OVS program starts, each network card in the container is added to the OVS port system to complete the construction of the virtualized SDN network.

[0029] Compared with the prior art, the present invention has the following beneficial effects:

[0030] (1) When the virtualized SDN switch is created, the present invention designs a mechanism for the switch system program to be loaded independently from the external file system, which ensures differentiated control of the system program loading path;

[0031] (2) When the virtualized SDN switch starts up, the present invention sets a delay waiting mechanism for the switch system program to realize fine control of the startup time of each virtualized SDN switch. Fine control of the startup time of each virtualized SDN switch can simulate the random process of SDN network construction; fine control of the running status of each virtualized SDN switch can simulate the random changes of the state such as node failure and node restart in the SDN network; fine control of the system program loading path of each virtualized SDN switch can load different system programs for different nodes, making the simulation of heterogeneous system networking more flexible. Attached Figure Description

[0032] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0033] Figure 1 A schematic diagram illustrating the method for deploying a virtualized SDN switch network;

[0034] Figure 2 This is a schematic diagram illustrating the implementation process. Detailed Implementation

[0035] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the scope of protection of the present invention.

[0036] Example 1:

[0037] This invention provides a method for customizing the deployment of virtual SDN switch networks. It uses a virtualization platform to create virtual nodes for each switch node, selects the system program loading path for the virtual nodes through a shared file system, and performs a delayed startup operation by reading the user's startup time configuration requirements for the virtual nodes before the system program executes. This method enables customized control of the startup timing of simulated SDN networks and differentiated control of loading paths.

[0038] like Figure 1 This method specifically includes the following steps:

[0039] Step 1: Based on the user's SDN network topology, create an independent virtual node for each network node using the virtualization platform on the physical host. When creating the virtual node, configure the virtual network interface card (NIC) of the virtual node and the file-sharing directory between the virtual node and the physical host. Each virtual node acts as a virtual SDN switch, with no system programs loaded yet.

[0040] Step 2: Configure the virtual network interface card (NIC) connections between each virtual node on the virtualization platform according to the connection relationships in the network topology.

[0041] Step 3: Place the switch system program in the shared directory of the physical host, and use remote control to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to the virtual node's system directory.

[0042] Step 4: Based on the user's configuration of the SDN switch startup timing, traverse each virtual node remotely and command the virtual node to execute the system program immediately or after a delay.

[0043] Step 5: After the system program starts, add each network card in the virtual node to the port of the virtual SDN switch to complete the construction of the virtualized SDN network.

[0044] Examples of implementation of the method of the present invention Figure 2 As shown, the physical host uses the Linux operating system, the virtual SDN switch software is Open vSwitch (OVS), and the implementation process of deploying a virtualized SDN switch network in this invention is illustrated using the Docker virtualization platform as an example:

[0045] Step 1: Use Docker commands to create and run a container for each network node, with each container running a Linux operating system. Set up a shared destination location with the physical host within the container.

[0046] Step 2: Use Docker commands to create a bridged network, and then use the add network command to add the created network to the container. Adding a network to a container is equivalent to adding another network interface card (NIC).

[0047] Step 3: Place the OVS program file from the physical host in a shared directory between the physical host and the container. Then, copy this file to the file system of each container by logging into the container.

[0048] Step 4: Based on the user's requirements for the startup timing of the SDN switch, remotely log in to each container and use delay commands such as Sleep to control the execution of the OVS program.

[0049] Step 5: After the OVS program starts, add each network card in the container to the OVS port system to complete the construction of the virtualized SDN network.

[0050] Example 2:

[0051] This invention also provides a system for customizing the deployment of a virtual SDN switch network. This system can be implemented by executing the steps of the method for customizing the deployment of a virtual SDN switch network. That is, those skilled in the art can understand the method for customizing the deployment of a virtual SDN switch network as a preferred embodiment of the system. The system specifically includes the following modules:

[0052] Module M1: Based on the user's SDN network topology, the virtualization platform on the physical host creates an independent virtual node for each network node. During virtual node creation, the virtual network interface card (NIC) of the virtual node and the file-sharing directory between the virtual node and the physical host are configured. Each virtual node acts as a virtual SDN switch without its system program loaded. Module M2: According to the connection relationships in the network topology, the virtualization platform configures the connections between the virtual NICs of each virtual node. Module M3: The switch system program is placed in the shared directory of the physical host. Remote control is used to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to its system directory. Module M4: Based on the user's configuration for the SDN switch startup timing, remote control is used to traverse each virtual node, commanding the virtual node to execute the system program immediately or with a delay. Module M5: After the system program starts, each virtual NIC in the virtual node is added to the port of the virtual SDN switch, completing the construction of the virtualized SDN network.

[0053] Using Docker commands, a container is created and run for each network node, with each container running a Linux operating system. Shared destinations with the physical host are configured within the container. Bridged networks are created using Docker commands, and the created networks are added to the containers using the add network command. Adding a network to a container is equivalent to adding another network interface card (NIC). The OVS program files from the physical host are placed in a shared directory between the physical host and the containers. The OVS program files are copied from the physical host to the file system of each container by logging into the container. Based on the user's requirements for the SDN switch startup timing, remote login is made to each container, and the execution of the OVS program is controlled using delay commands. After the OVS program starts, each NIC in the container is added to the OVS port system, completing the construction of the virtualized SDN network.

[0054] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0055] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A method for customizing and deploying a simulated SDN switch network, characterized in that, include: Step 1: Based on the user's SDN network topology, use the virtualization platform on the physical host to create an independent virtual node for each network node. When creating the virtual node, configure the virtual network card of the virtual node and the file sharing directory between the virtual node and the physical host. Treat each virtual node as a virtual SDN switch without loading system programs. Step 2: Configure the virtual network interface card (NIC) connections between each virtual node on the virtualization platform according to the connection relationships in the network topology; Step 3: Place the switch system program in the shared directory of the physical host, and use remote control to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to the system directory of the virtual node; Step 4: Based on the user's configuration of the SDN switch startup timing, traverse each virtual node remotely and command the virtual node to execute the system program immediately or after a delay. Step 5: After the system program starts, add each virtual network card in the virtual node to the port of the virtual SDN switch to complete the construction of the virtualized SDN network.

2. The method of claim 1, wherein, Using Docker commands, a container is created and run for each network node, with each container running a Linux operating system. Shared destinations with the physical host are set up within the container.

3. The method of claim 1, wherein, Use Docker commands to create bridge-type networks, and use the add network command to add the created network to the container. Adding a network to a container is equivalent to adding another network card.

4. The method of claim 1, wherein, Place the OVS program files on the physical host in a shared directory between the physical host and the container, and then copy the OVS program files from the physical host to the file system of each container by logging into the container.

5. The method of claim 1, wherein, Based on the user's requirements for the startup timing of the SDN switch, remote login is made to each container, and the execution of the OVS program is controlled using delay commands. After the OVS program starts, each network card in the container is added to the OVS port system to complete the construction of the virtualized SDN network.

6. A system for customizing deployment of a simulated SDN switch network, the system comprising: include: Module M1: Based on the user's SDN network topology, it uses the virtualization platform in the physical host to create an independent virtual node for each network node. When creating the virtual node, it configures the virtual network card of the virtual node and the file sharing directory between the virtual node and the physical host, and treats each virtual node as a virtual SDN switch without loading system programs. Module M2: Configures the connection of virtual network cards between virtual nodes on the virtualization platform according to the connection relationship in the network topology; Module M3: Places the switch system program in the shared directory of the physical host, and uses remote control to traverse each virtual node, commanding the virtual node to copy the switch system program from the shared directory to the virtual node's system directory; Module M4: Based on the user's configuration of the SDN switch startup timing, it remotely controls each virtual node to execute or delay the execution of system programs. Module M5: After the system program starts, it adds each virtual network card in the virtual node to the port of the virtual SDN switch, thus completing the construction of the virtualized SDN network.

7. The system for customizing deployment of a simulated SDN switch network of claim 6, wherein, Using Docker commands, a container is created and run for each network node, with each container running a Linux operating system. Shared destinations with the physical host are set up within the container.

8. The system for customizing deployment of a simulated SDN switch network of claim 6, wherein, Use Docker commands to create bridge-type networks, and use the add network command to add the created network to the container. Adding a network to a container is equivalent to adding another network card.

9. The system for customizing deployment of a simulated SDN switch network of claim 6, wherein, Place the OVS program files on the physical host in a shared directory between the physical host and the container, and then copy the OVS program files from the physical host to the file system of each container by logging into the container.

10. The system for customizing deployment of a simulated SDN switch network of claim 6, wherein, Based on the user's requirements for the startup timing of the SDN switch, remote login is made to each container, and the execution of the OVS program is controlled using delay commands. After the OVS program starts, each network card in the container is added to the OVS port system to complete the construction of the virtualized SDN network.

Images