WO2023109346A1

WO2023109346A1 - Network virtualization service system and network virtualization server

Info

Publication number: WO2023109346A1
Application number: PCT/CN2022/129240
Authority: WO
Inventors: 林宝洪; 樊勇兵; 吴林泽; 黄志兰; 陈天; 刘艺
Original assignee: 中国电信股份有限公司
Priority date: 2021-12-16
Filing date: 2022-11-02
Publication date: 2023-06-22
Also published as: CN114205176A

Abstract

Provided in the present disclosure are a network virtualization service system and a network virtualization server. The network virtualization server comprises: a first network card, which is deployed with a network virtualization edge device, a standard interface library of the network virtualization edge device, and a first kernel and a first operable software library, which the network virtualization device depends on; a virtual machine and a second network card thereof, wherein the second network card is a virtual network card; and a virtual machine hypervisor, and a second kernel and a second operable software library, which the virtual machine hypervisor depends on, wherein by means of the standard interface library, the virtual machine hypervisor binds the second network card of the virtual machine with a virtual interface of the network virtualization edge device or unbinds the second network card of the virtual machine from the virtual interface of the network virtualization edge device. By means of the present disclosure, a dependence environment conflict between a network virtualization edge device and a virtual machine hypervisor is solved, and private interface adaptation problems for different network virtual edge devices are also solved.

Description

Network virtualization service system and network virtualization server

Cross References to Related Applications

This application is based on the application with CN application number 202111542834.1 and the application date is December 16, 2021, and claims its priority. The disclosure content of this CN application is hereby incorporated into this disclosure as a whole.

technical field

The present disclosure relates to the field of cloud computing, in particular, to a network virtualization service system and a network virtualization server.

Background technique

Referring to Fig. 1, in the network virtualization service, in order to facilitate the virtual machine monitor 120 (Hypervisor) to carry out the virtual interface (Vport) 111 of SDN (Software Defined Network, software defined network) NVE110 (Network Virtualization Edge, network virtual edge device) Binding and unbinding with the interface of the virtual network card 141 (VNIC) of the virtual machine 140 (Virtual Machine, VM), usually the NVE110 is directly deployed in the operating system of the Hypervisor120, and the operating system kernel and the executable software library 130 are shared with the Hypervisor120. Thus, the network virtualization server 100 can be integrated with the network virtual edge device 110 , the virtual machine monitor 120 and the virtual machine 140 .

This integration method has the following problems: NVE relies on the hypervisor kernel and executable software library, and each manufacturer/version hypervisor needs to be developed and adapted one by one to solve the problem of the two dependent environment conflicts; different SDN manufacturers have different NVE private interfaces, Hypervisors of different manufacturers/versions need to be developed and adapted one by one.

In this regard, the publication number CN112068924A, a patent application titled Network Virtualization System and Method, proposes to deploy NVE and its binary/library in a container environment to reduce the difficulty of integrating NVE and Hypervisor, but NVE still needs to adapt to the Hypervisor kernel. And the Hypervisor still needs to adapt the NVE private interface one by one.

It can be seen from this that how to solve the conflict between NVE's dependency on Hypervisor's kernel and executable software library, and the need to develop and adapt each manufacturer/version of Hypervisor one by one; and different NVE private interfaces of different SDN manufacturers, different manufacturers/versions Version hypervisor needs to be developed and adapted one by one, which is a technical problem to be solved urgently by those skilled in the art.

It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to those of ordinary skill in the art.

Contents of the invention

An embodiment of the present disclosure provides a network virtualization server, including:

The first network card is deployed with a network virtualization edge device, a standard interface library of the network virtualization edge device, a first kernel and a first executable software library that the network virtualization device depends on;

A virtual machine and its second network card, where the second network card is a virtual network card;

The virtual machine monitor and its dependent second kernel and second executable software library, the virtual machine monitor binds or unbinds the network virtualization to the second network card of the virtual machine through the standard interface library Virtual interface for edge devices.

In some embodiments of the present disclosure, the standard interface library of the network virtualization edge device includes:

A standardized interface is used to define an operation method and parameters for binding or/and unbinding the virtual interface of the network virtualization edge device to the second network card of the virtual machine in the standard interface library;

The interface plug-in is inherited from the standardized interface, so as to realize the conversion between the virtual interface and the standardized interface of the network virtualization edge device.

In some embodiments of the present disclosure, the interface plug-in is updated with the version update of the virtual interface of the network virtualization edge device.

In some embodiments of the present disclosure, the first network card is a SoC type network card.

In some embodiments of the present disclosure, the network virtualization edge device is an open virtual switching standard network virtualization edge device.

In some embodiments of the present disclosure, the first network card also includes:

The data path offloading engine is used to provide the data path offloading of the open virtual switching standard.

In some embodiments of the present disclosure, the network virtualization edge device, the standard interface library of the network virtualization edge device, the first kernel and the first executable software library that the network virtualization device depends on are deployed on the In the ARM processor of the first network card mentioned above.

In some embodiments of the present disclosure, the second kernel and the second executable software library that the virtual machine monitor depends on are deployed in the virtual machine monitor.

According to yet another aspect of the present disclosure, a network virtualization service system is also provided, including:

A network virtualization server as described above;

a virtual machine monitor manager, configured to manage the network virtualization server;

A software-defined network controller, configured to deliver control information to the network virtualization edge device.

In some embodiments of the present disclosure, the virtual machine monitor manager and the software-defined network controller are managed by a cloud computing platform.

Description of drawings

Other features, objects and advantages of the present disclosure will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings.

FIG. 1 is a block diagram of a network virtual server in the background technology.

FIG. 2 is a block diagram of an embodiment of the network virtual server of the present disclosure.

Fig. 3 is a block diagram of an embodiment of the network virtual service system of the present disclosure.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals denote the same or similar structures in the drawings, and thus their repeated descriptions will be omitted.

One of the purposes of the present disclosure is to provide a method, device, device, and storage medium for dynamically configuring signal resources, so as to solve the problem that network virtual edge devices rely on the kernel and executable software library of the virtual machine monitor, and meet the needs of various manufacturers/versions of virtual machine monitors. There is a conflict between the two dependent environments for one-by-one development and adaptation; and the private interfaces of network virtual edge devices of different software-defined network manufacturers are different, and different manufacturers/versions of virtual machine monitors need to be developed and adapted one by one.

Referring to FIG. 2 , FIG. 2 is a block diagram of an embodiment of the network virtual server of the present disclosure. The network virtualization server 200 includes a first network card 210 , a virtual machine 230 and its second network card 231 , a virtual machine monitor 220 and its dependent second kernel, and a second executable software library 221 .

The first network card 210 is deployed with a network virtualization edge device 212 , a standard interface library 211 of the network virtualization edge device, a first kernel and a first executable software library 214 on which the network virtualization device 212 depends. The second network card 231 is a virtual network card. The virtual machine monitor 220 binds or unbinds the second network card 231 of the virtual machine 230 to or unbinds the virtual interface 213 of the network virtualization edge device 212 through the standard interface library 221 .

This disclosure aims at the current network virtual edge devices that need to be developed one by one to adapt to each manufacturer/version virtual machine monitor, and the interface coupling between the virtual machine monitor and the network virtual edge device is high. By combining the network virtual edge device and the required kernel, The binary/library is deployed to the server network card through network card offloading, and the private interface of different manufacturers/versions of network virtual edge devices is shielded through the standardized interface library. The advantages of the present disclosure are: 1. Deploy network virtual edge devices and their dependencies by using network card offloading, which improves the deployment efficiency of software-defined networks; 2. Network virtual edge devices and virtual machine monitors depend on different kernels, binary/ 3. The virtual machine monitor calls the virtual network card of the standardized virtual machine to bind the virtual interface of the network virtual edge device, and the network virtual edge devices of different manufacturers are uniformly adapted to realize virtual Unification of service interfaces between machine monitors and network virtual edge devices.

Referring to FIG. 3 below, FIG. 3 is a block diagram of an embodiment of the network virtual service system of the present disclosure.

The network virtualization service system includes a cloud computing platform 301 , a virtual machine monitor manager 302 , a software-defined network controller 303 and a network virtualization server 300 .

The network virtualization server 300 includes a first network card 310 , a virtual machine 330 and its second network card 331 , a virtual machine monitor 320 and its dependent second kernel, and a second executable software library 321 .

The first network card 310 is deployed with a network virtualization edge device 312, a standard interface library 311 of the network virtualization edge device, a first kernel and a first executable software library 314 on which the network virtualization device 312 depends, and data path offloading engine 315. The second network card 331 is a virtual network card. The virtual machine monitor 320 binds the second network card 331 of the virtual machine 330 to the virtual interface 313 of the network virtualization edge device 312 through the standard interface library 321 .

In some embodiments, the first network card 310 may be, for example, a SOC (System on Chip, system-on-chip) type smart network card. The network virtualization edge device 312, the standard interface library 311 of the network virtualization edge device 312, the first kernel and the first executable software library 314 that the network virtualization device 312 depends on are deployed on the first network card 310 ARM (Advanced RISC Machine) processor, where RISC stands for Reduced Instruction Set Computer (Reduced Instruction Set Computer).

In some embodiments, the network virtualization edge device 312 is an Open Virtual Switching Standard (Open vSwitch, OVS) network virtualization edge device.

In some embodiments, the standard interface library 311 of the network virtualization edge device 312 includes a standardized interface 321A and an interface plug-in 321B. The standardized interface 321A is used to define an operation method and parameters for the standard interface library to bind or/and unbind the virtual interface of the network virtualization edge device to the second network card of the virtual machine. The interface plug-in 321B is inherited from the standardized interface, so as to realize the conversion between the virtual interface and the standardized interface of the network virtualization edge device. Therefore, the interface plug-in can be updated along with the version update of the virtual interface of the network virtualization edge device, without changing the virtual machine monitor 320 .

In some embodiments, the standard interface library 311 is, for example, the os-vif standard interface library of OpenStack. OpenStack is an open source cloud computing management platform project, which is a combination of a series of software open source projects. The os-vif standard interface in the os-vif standard interface library defines the operation method and parameters of VM VNIC binding/unbinding NVE VPORT. OVS provides the OVS plug-in (321B ), and implement the conversion from the standard interface to the OVS private interface in the plug-in.

In some embodiments, the data path offload engine 315 is configured to provide the data path offload of the Open Virtual Switching standard. Therefore, it is convenient to implement binding and unbinding between interfaces.

In some embodiments, the second kernel and the second executable software library 321 that the virtual machine monitor 320 depends on are deployed in the virtual machine monitor 320 . Therefore, it is not necessary to change the existing virtual machine monitor 320 .

In some embodiments, the first kernel and the second kernel may be, for example, Linux operating system kernels, the present disclosure is not limited thereto, and kernels of other operating systems are also within the protection scope of the present disclosure. The executable software library may be, for example, a binary library for users to call software, packages or functions therein.

In some embodiments, the software-defined network controller 303 is configured to deliver control information to the network virtualization edge device 312 . The control information may be, for example, at least one of flow table and configuration information. The configuration information may be, for example, enabling or disabling a certain port number, so as to cooperate with the process of creating or deleting a virtual machine. Thus, the network virtualization edge device 312 can process the network virtualization edge device according to the first kernel and the first executable software library 314 of the dependent network virtualization edge device 312 and the control information issued by the software-defined network controller 303 312 corresponds to the network traffic of the virtual machine 330.

In some embodiments, the virtual machine monitor manager 302 is used to manage the network virtualization server.

In some embodiments, the software-defined network controller 303 and the hypervisor manager 302 can be managed by a cloud computing platform 301 (such as Openstack).

Therefore, in the network virtualization service system provided by the present disclosure:

Deploy NVE and its dependencies (kernel, binary/library) independently by using network card offloading, which improves the deployment efficiency of SDN, and NVE and Hypervisor depend on different kernels, binaries/libraries, which solves the problem of conflict between the two dependent environments; The Hypervisor calls the standardized VM VNIC to bind the NVE port interface. NVEs from different manufacturers provide Plugins for unified adaptation to realize the unification of business interfaces between the Hypervisor and NVE, and the version change of the NVE private interface only needs to update the corresponding Plugin without affecting Hypervisor.

This disclosure aims at the current network virtual edge devices that need to be developed one by one to adapt to each manufacturer/version virtual machine monitor, and the interface coupling between the virtual machine monitor and the network virtual edge device is high. By combining the network virtual edge device and the required kernel, The binary/library is deployed to the server network card through network card offloading, and the private interface of different manufacturers/versions of network virtual edge devices is shielded through the standardized interface library. The advantages of the present disclosure are:

1. Use network card offloading to deploy network virtual edge devices and their dependencies, which improves the deployment efficiency of software-defined networks;

2. Network virtual edge devices and virtual machine monitors depend on different kernels, binaries/libraries, which solves the problem of conflicts between the two dependent environments;

3. The virtual machine monitor calls the virtual network card of the standardized virtual machine to bind the virtual interface of the network virtual edge device, and the network virtual edge devices of different manufacturers are uniformly adapted to realize the service interface between the virtual machine monitor and the network virtual edge device. Unite.

The above content is a further detailed description of the present disclosure in conjunction with specific preferred embodiments, and it cannot be considered that the specific implementation of the present disclosure is limited to these descriptions. For those of ordinary skill in the technical field to which the present disclosure belongs, without departing from the concept of the present disclosure, some simple deductions or substitutions can be made, which should be deemed to belong to the protection scope of the present disclosure.

Claims

A network virtualization server comprising:

The first network card is deployed with a network virtualization edge device, a standard interface library of the network virtualization edge device, a first kernel and a first executable software library that the network virtualization device depends on;

A virtual machine and its second network card, where the second network card is a virtual network card;

The virtual machine monitor and its dependent second kernel and second executable software library, the virtual machine monitor binds or unbinds the network virtualization to the second network card of the virtual machine through the standard interface library Virtual interface for edge devices.
The network virtualization server according to claim 1, wherein the standard interface library of the network virtualization edge device comprises:

A standardized interface is used to define an operation method and parameters for binding or/and unbinding the virtual interface of the network virtualization edge device to the second network card of the virtual machine in the standard interface library;

The interface plug-in is inherited from the standardized interface, so as to realize the conversion between the virtual interface and the standardized interface of the network virtualization edge device.
The network virtualization server according to claim 2, wherein the interface plug-in is updated with the version update of the virtual interface of the network virtualization edge device.
The network virtualization server according to claim 1, wherein the first network card is a system-on-a-chip network card.
The network virtualization server according to claim 1, wherein the network virtualization edge device is an open virtual switching standard network virtualization edge device.
The network virtualization server according to claim 5, wherein the first network card further comprises:

The data path offloading engine is used to provide the data path offloading of the open virtual switching standard.
The network virtualization server according to claim 1, wherein the network virtualization edge device, the standard interface library of the network virtualization edge device, the first kernel on which the network virtualization device depends, and the first executable The software library is deployed in the ARM processor of the first network card.
The network virtualization server according to claim 1, wherein the second kernel and the second executable software library on which the virtual machine monitor depends are deployed in the virtual machine monitor.
A network virtualization service system, comprising:

The network virtualization server according to any one of claims 1 to 7;

a virtual machine monitor manager, configured to manage the network virtualization server;

A software-defined network controller, configured to deliver control information to the network virtualization edge device.
The network virtualization service system according to claim 9, wherein the virtual machine monitor manager and the software-defined network controller are managed by a cloud computing platform.