WO2018006704A1

WO2018006704A1 - Public network ip allocation method and apparatus, and virtual data center system

Info

Publication number: WO2018006704A1
Application number: PCT/CN2017/089166
Authority: WO
Inventors: 李秀芳; 沈世元; 叶松青
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-07-04
Filing date: 2017-06-20
Publication date: 2018-01-11
Also published as: CN107580077A

Abstract

The present disclosure provides a public network IP allocation method and apparatus, and a virtual data center system. The method comprises: obtaining an access virtual local area network VLAN ID list of a traditional network; establishing a mapping relationship between multiple subinterfaces of a virtual extensible local area network (VXLAN) gateway and all VLAN IDs in the VLAN ID list by means of a first specified interface of a software defined network (SDN) controller; and mapping the mapping relationship to a virtual network ID of a virtual data center (VDC) tenant by means of a second specified interface of the SDN controller. By means of the present disclosure, the problem in the related art of resource waste caused by a network access mode in which a public network IP is allocated to each user in a traditional network is resolved, thereby achieving the effect of saving public network IP resources.

Description

Public network IP allocation method, device and virtualized data center system

Technical field

The present disclosure relates to the field of communications, and in particular, to a public network IP allocation method and apparatus, and a virtualized data center system.

Background technique

Virtual Data Center (VDC) is a new type of data center that applies the concept of cloud computing to the Internet Data Center (IDC). Through the combination of traditional Internet data center IDC business and cloud computing technology, a unified and innovative VDC operation management system will be built, and technologies such as virtualization and automated deployment will be applied to build a scalable virtualized infrastructure, using centralized management and distributed service models. The user provides a basic IT facility solution and service for acceptance and network-wide services. The main difference between VDC and traditional IDC is that the infrastructure is provided as a service through technical means; the physical resources are abstractly integrated through virtualization technology to enhance service capabilities; and resource utilization and service reliability are improved through dynamic resource allocation and scheduling; Automate service provisioning capabilities, reduce O&M costs, and provide a convenient user experience; provide more security mechanisms and reliability mechanisms to meet enterprise-level application security standards.

Software Defined Network (SDN), whose core technology OpenFlow separates the control plane of the network device from the data plane, thus achieving flexible control of network traffic and providing a good core network and application innovation. The platform, currently in the carrier network, is relatively pure SDN. Firstly, it can start from the relatively closed data center and other scenarios to build a new SDN enhanced VDC. By introducing an SDN controller on the network control side, the vSwitch and OF protocol enhanced Top of Rack (ToR) hardware switches built on the computing resources are centrally controlled, and the traditional data center is changed. The complex network topology is a large Layer 2 network architecture.

However, in the related art, the traditional network model is mainly for assigning a public network IP to each user, which inevitably causes a shortage of limited resources of the public network IP.

For the related art, the problem of waste of public network IP resources caused by the allocation of a public network IP access mode for each user of the traditional network has not yet proposed an effective solution.

Summary of the invention

The embodiment of the present disclosure provides a method, an apparatus, and a virtualized data center system for public network IP, to at least solve the public network IP caused by the Internet access mode in which a public network IP is allocated to each user of the traditional network in the related art. The problem of wasting resources.

According to an embodiment of the present disclosure, a public network IP allocation method is provided, including: obtaining a virtual network local area VLAN ID list of a traditional network; establishing a virtual scalable local area network VXLAN through a first designated interface of a software defined network SDN controller Multiple subinterfaces of the gateway and each VLAN ID in the list of VLAN IDs The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.

Optionally, before the mapping between the multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list is established by using the first designated interface of the software-defined network SDN controller, the method further includes: The first designated interface of the SDN controller creates a plurality of sub-interfaces of the VXLAN gateway.

Optionally, after the multiple sub-interfaces of the VXLAN gateway are created by using the first designated interface of the SDN controller, the method further includes: saving an object attribute of the sub-interface; wherein the object attribute includes at least: The attributes of the SDN that are reported by the VXLAN gateway and the sub-interface labels corresponding to the VLAN ID of the virtual network.

Optionally, mapping the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant by using the second designated interface of the SDN controller includes: acquiring an interface attribute of the second specified interface of the SDN controller The interface attribute includes at least one of: a virtual network ID, a label, an interface ID, a port type, and a device ID; and mapping the mapping relationship to a virtualized data center VDC tenant by the interface attribute Machine network ID.

Optionally, the first designated interface is a VLAN sub-interface object operation interface addVlanInf; and the second designated interface is a port-virtual network mapping object operation interface addPortVnetMap.

According to another embodiment of the present disclosure, a public network IP distribution apparatus is provided, including: an obtaining module, configured to obtain a virtual network local area VLAN ID list of a traditional network; and a first establishing module, configured to define a network SDN by software. The first designated interface of the controller establishes a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list, and a mapping module is configured to control the mapping relationship by using the SDN The second specified interface of the device is mapped to the virtual machine network ID of the virtualized data center VDC tenant.

Optionally, the apparatus further includes: a second establishing module, configured to establish, in the plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each of the VLAN ID lists, by using a first designated interface of the software-defined network SDN controller Before the mapping between the VLAN IDs, multiple sub-interfaces of the VXLAN gateway are created by the first designated interface of the SDN controller.

Optionally, the device further includes: a saving module, configured to save an object attribute of the sub-interface after creating a plurality of sub-interfaces of the VXLAN gateway by using the first designated interface of the SDN controller; The object attribute includes at least: an attribute of the VXLAN gateway reported to the SDN, and a sub-interface label corresponding to the access virtual VLAN ID of the traditional network.

Optionally, the mapping module includes: an acquiring unit, configured to acquire an interface attribute of the second specified interface of the SDN controller, where the interface attribute includes at least one of the following: a virtual network ID, a label, and an interface ID. The mapping unit is configured to map the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant by using the interface attribute.

According to another embodiment of the present disclosure, a virtualized data center system is provided, including: a resource operation system IROS, configured to obtain a virtual network local area VLAN ID list of a traditional network; and is established by using a first designated interface of the SDN controller a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list; mapping the mapping relationship to the virtualized data center VDC through the second designated interface of the SDN controller a virtual machine network ID of the tenant; a software-defined network SDN controller for setting a first designated interface and a second designated interface; and a virtual scalable local area network VXLAN gateway for creating a plurality of sub-interfaces, wherein the plurality of sub-interfaces The tag corresponds to the virtual network VLAN ID of the traditional network.

According to still another embodiment of the present disclosure, a storage medium is also provided. The storage medium is configured to store program code for performing the following steps: obtaining a list of access virtual local area network VLAN IDs of the legacy network; establishing a plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway by using a first designated interface of the software-defined network SDN controller The mapping relationship between each VLAN ID in the VLAN ID list is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.

Through the disclosure, obtaining a virtual network local area network VLAN ID list of the traditional network; establishing a plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list by using a first designated interface of the software-defined network SDN controller The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller. That is to say, by mapping the VLAN ID of the traditional network to the VNI of different tenants in the center of the VDC cloud platform, the public network IP caused by the public network IP mode assigned to each user of the traditional network in the related art is solved. The problem of wasting resources has achieved the effect of saving public network IP resources.

DRAWINGS

The drawings described herein are provided to provide a further understanding of the present disclosure, which is a part of the present disclosure, and the description of the present disclosure and the description thereof are not intended to limit the disclosure. In the drawing:

1 is a flowchart of a public network IP allocation method according to an embodiment of the present disclosure;

2 is an optional flowchart of a public network IP allocation method according to an embodiment of the present disclosure;

3 is a structural block diagram of a public network IP distribution device according to an embodiment of the present disclosure;

4 is a structural block diagram (1) of a public network IP distribution apparatus according to an embodiment of the present disclosure;

FIG. 5 is a structural block diagram (2) of a public network IP distribution apparatus according to an embodiment of the present disclosure; FIG.

6 is a structural block diagram (3) of a public network IP distribution apparatus according to an embodiment of the present disclosure;

7 is a block diagram showing the structure of a virtualized data center system in accordance with an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a public network IP distribution device architecture according to an embodiment of the present disclosure.

detailed description

The present disclosure will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second", and the like in the specification and claims of the present disclosure are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

In this embodiment, a public network IP allocation method is provided. FIG. 1 is a flowchart of a public network IP allocation method according to an embodiment of the present disclosure. As shown in FIG. 1, the process includes the following steps:

Step S102: Obtain a VLAN ID list of the access virtual local area network of the traditional network.

Step S104, establishing, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list;

Step S106: The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.

Optionally, in this embodiment, the application scenario of the public network IP allocation method includes, but is not limited to, a network in which a traditional network and a virtualized data center VDC are fused, and in the application scenario, accessing a traditional network is obtained. a virtual local area network VLAN ID list; establishing, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list; The second designated interface of the SDN controller is mapped to the virtual machine network ID of the virtualized data center VDC tenant. That is to say, in this embodiment, by mapping the VLAN ID of the traditional network to the VNI of different tenants in the center of the VDC cloud platform, the method for allocating a public network IP for each user of the traditional network in the related art is solved. The problem of waste of public network IP resources is caused, and the effect of saving public network IP resources is achieved.

The present embodiment will be exemplified below with reference to specific examples.

The technical problem to be solved in this embodiment is that in the virtual data center (Virtual Data Center, VDC for short), the access vlan in the traditional network model is provided through a specific interface provided by the SDN controller of the VDC cloud platform center (zenic). -logical-conf: addPortVnetMap), which implements the vlan ID for access switching and the different tenant VNI mapping for the VDC cloud platform center. Specifically, the I Resource Operation System (IROS) platform calls the SDN interface (zenic-physical-conf: addVlanInf) to create a vlan sub-interface (vlan sub-interface) for the port of the VDC's underlying virtual scalable LAN VXLAN gateway device. The number ranges from 0 to 4096, and the sub-interface is mapped to the access switch vlan tag, and the mapping relationship is mapped to the zen controller by the zenic-logical-conf:addPortVnetMap interface. To the VNI network of the VDC tenant, this method not only implements the traditional network access to the VDC center, but also supports the overlap of the vlan id in the tenant through different implementations of the VXLAN gateway device port. This technology connects the traditional network to the virtual private cloud (VPC) of the VDC platform. After the mapping is completed, the client (whether the physical terminal of the traditional network or the virtual machine terminal of the VDC platform) is completed. The network traffic of the originating network can be mapped to the public network through the carrier-level network address translation (Carrier-Grade NAT, cgn) module of the VXLAN gateway of the cloud platform center, so that multiple users share the function of one public network IP. Waste of public network IP resources. The above technical problem of the embodiment is solved in this way, the management interface IROS of the VDC creates, deletes and queries the vnet network by calling the RESTConf interface (zenic-logical-conf: addVnet) provided by the SDN controller, and the IROS saves the vnet under the tenant. The key attributes of the network (zenic-types: vrf-id, zenic-types: vnet-id, zenic-types: vnet-name), the IROS management interface determines the vnet of the vnet network, and records the tenant ID, vnet-id key attributes, It cannot be repeated between all VDC networks. IROS then interacts with the SDN controller interface (zenic-physical-conf: addVlanInf) to create, delete, and query vlan subinterfaces, and also saves vlan subinterface object attributes, including vxlan gateway devices in the VDC data center. The capability negotiation is reported to several key attributes of the SDN, and the vlan interface label attribute of the traditional network access exchange that is ready to be connected to the VDC cloud platform center, through which the interface-id of the vxlan gateway device port in the VDC data center is established. Mapping relationship with vport-id. Then, IROS implements the relationship mapping between the interface-id, vport-id of the vxlan gateway device port and the vnet created by the VDC tenant by calling the port-virtual network mapping object operation interface (zenic-logical-conf: addPortVnetMap) provided by the SDN module. Finally, the vxlan gateway device port obtains the flow table from the SDN module through its own cgn module. Implement the function of vlan mapping to the public network.

The method for allocating the public network IP in the embodiment mainly includes the following steps:

Step S11, the VDC management interface IROS creates, deletes, and queries the vnet network by calling the RESTConf interface (zenic-logical-conf: addVnet) provided by the SDN controller, and the IROS saves the key attributes of the vnet network under the tenant (zenic-types: Vrf-id, zenic-types: vnet-id, zenic-types: vnet-name), the IROS management interface determines the vnet of the vnet network, and records the tenant ID, vnet-id key attributes, which cannot be repeated among all VDC networks.

In step S12, the IROS interacts with the interface of the SDN controller (zenic-physical-conf: addVlanInf) to create, delete, and query the vlan sub-interface to create, delete, and query the vlan sub-interface, and save the vlan sub-interface object attribute (zenic). -types: device-id, zenic-types: port-id, zenic-types: interface-id, zenic-types: encap-id, zenic-types: vport-id). The first three attributes are vxlan in the VDC data center. The gateway device reports the key attributes of the SDN through the capability negotiation. The last attribute vport-id is the vlan interface label that the traditional network prepares to access and exchange with the VDC cloud platform center. Through this interface, the VDC data center is established. Correspondence between the interface-id and vport-id of the device in the vxlan gateway.

In step S13, the IROS issues a create, delete, and query request by calling a port-virtual network mapping object operation interface (zenic-logical-conf: addPortVnetMap) provided by the SDN module, and the addPortVnetMap interface provides a zenic-types: vnet-id, Zenic-types: tag, zenic-types: interface-id, zenic-types: port-type, zenic-types: port-id, zenic-types: device-id, etc., through vnet-id and the following parameters The mapping between the interface attributes, the interface-id, the vport-id, and the vnet relationship created by the VDC tenant, implements the virtual network that connects the traditional access switching vlan to the VDC cloud platform, and supports different ports through the vxlan gateway device. The function of vlan overlap.

In the step S14, the SDN sends the flow table to the vxlan gateway device through the openflow protocol, and the vxlan gateway device port performs the flow table forwarding processing through the cgn module of the vlan, thereby implementing the three-layer forwarding interworking of the vlan to the public network.

In an optional implementation manner, a plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list are established between the first designated interface of the software-defined network SDN controller Before mapping the relationship, the following steps are also included:

Step S21: Create multiple sub-interfaces of the VXLAN gateway through the first designated interface of the SDN controller.

By creating multiple sub-interfaces of the VXLAN gateway, the VLAN ID of the traditional network can be corresponding to the VNI of different tenants accessing the center of the VDC cloud platform.

Optionally, after the multiple sub-interfaces of the VXLAN gateway are created by using the first designated interface of the SDN controller, the following steps are further included:

Step S31, saving the object attribute of the sub-interface.

It should be noted that the foregoing object attributes include at least: an attribute of the VXLAN gateway reported to the SDN, and a sub-interface label corresponding to the VLAN ID of the access network of the traditional network.

By storing the object attributes of the multiple sub-interfaces, the access VLAN ID list of the traditional network and the multiple sub-interfaces can be mapped one by one, so that the access VLAN of the traditional network is connected to the VNIs of different tenants of the VDC cloud platform center.

In an optional implementation manner, mapping the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller includes the following steps:

Step S41: Obtain an interface attribute of the second designated interface of the SDN controller, where the interface attribute includes at least one of the following: a virtual network ID, a label, an interface ID, a port type, and a device ID;

In step S42, the mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the interface attribute.

The mapping between the multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the above steps S41 to S42. The problem of wasting public network IP resources caused by the public network IP mode allocated to each user of the traditional network in the related art is solved, thereby achieving the effect of saving public network IP resources.

In this example, a public network IP allocation method is mainly provided, as shown in FIG. 2, which mainly includes the following steps:

Step 1: The VXLAN gateway reports the related port of the bind to the domain to the SDN controller through the capability negotiation. The SDN controller records the detailed information of the related device (device-id, DPID, port-id, openflow table, openflow address, Protocal). , status, capacity) and other information;

Step 2: The IROS platform obtains a list of vlanIDs accessed in the traditional network model through the agent plug-in;

Step 3: The IROS platform synchronizes the vlan id list of the legacy network to the SDN controller;

Step 4: The VDC management platform IROS module sends a request for creation, deletion, and query to the SDN controller by calling the RESTConf interface (zenic-logical-conf: addVnet) provided by the SDN module, and creates it in the VDC platform center. The tenant is under the vnet network. After IROS successfully created multiple vnet networks, IROS Save the key attributes (vrf-id, vnet-id, name) of each vnet network under the tenant. The tenant ID and vnet-id key attributes cannot be duplicated among all VDC networks.

Step 5: The SDN controller calls the cloud platform interface, and generates a corresponding openflow data flow table, which is sent to the DVS device and the vxlan gateway device.

Step 6: The IROS platform creates, deletes, and queries the first vlan subinterface of the first port hosted by the VXLAN gateway device to the domain by using the zenic-physical-conf:addVlanInf interface of the SDN controller, and saves the vlan sub-interface. Interface object attributes (device-id, port-id, interface-id, encap-id, vport-id). The first three attributes are several key attributes related to the vxlan gateway device hosting port in the VDC data center. The last attribute is vport. -id is the access switch vlan interface label (repeatable) that is ready to be connected to the traditional network of the VDC cloud platform center. The specific value is obtained from the vlanID list obtained in step 2. Through this interface, the vxlan gateway in the VDC data center is established. The mapping between the port-id, interface-id, and vport-id of the device.

Step 7: IROS continues to create, delete, and query the nth vlan subinterface of the mth port hosted by the VXLAN gateway device through the zenic-physical-conf:addVlanInf interface of the SDN controller (where m>=1,1) <=n<=4096), the attributes of each vlan sub-interface object are saved, and the mapping relationship between the port-id, interface-id, and vport-id of the vxlan gateway device is established.

Step 8: SDN calls the interface provided by the MySQL platform of the IROS database, and sends the relevant data and flow table to the DVS device and the vxlan gateway device according to the vlan sub-interface information generated in the database according to the above steps;

Step 9: IROS sends a request for creation, query, and deletion by calling the port-virtual network mapping object operation interface (zenic-logical-conf: addPortVnetMap) provided by the SDN module, and the port-virtual network mapping interface provides a vnet-id. Interface attributes such as tag, interface-id, port-type, port-id, and device-id are mapped by vnet-id and several other parameters. The following description is as follows: You can configure the vlan sub-interface to be mapped to a different vnet-id by creating a request (the vnet-id created in step 4), so that the attributes port-id, interface-id, and the attributes of the zenic-physical-conf:addVlanInf interface are implemented. Zenic-logical-conf: The mapping of the vnet-id attribute of the addVnet interface not only further realizes the function of identifying different tenants, but also supports the overlapping function of the access exchange vlanid in the traditional network;

Step 10: The SDN calls the IROS database platform interface, and according to the above steps, the port-virtual network mapping object operation sub-interface information generated in the database is sent, and the relevant data is delivered to the vxlan gateway. The vxlan gateway device generates the vlan sub-interface data of each port synchronously, and the SDN synchronizes the openflow flow table to the vxlan gateway device.

Step 11: The user client device in the traditional network sends a request for obtaining an IP to the DHCP agent module of OPENSTACK in the IROS platform;

Step 12: DHCP AGENT in the openstack of the IROS platform initiates a request for obtaining an IP to the zenic-logical-conf:DhcpPool interface of the SDN controller;

Step 13: The SDN controller returns the assigned IP result to the DHCP AGENT module in the openstack, and the DHCP AGENT is sent to the client of the traditional network through the agent plug-in of the IROS platform;

Step 14: The SDN controller updates the host information table, the arp information table, and the like, and delivers the corresponding openflow. Flow table to vxlan gateway and DVS. When the traditional network initiates the network traffic to the vxlan interface of the vxlan gateway, the flow table is forwarded through the cgn module of the VXLAN gateway, so that the vlan to the public network has three layers of forwarding and interworking.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, portions of the technical solutions of the present disclosure that contribute substantially or to the prior art may be embodied in the form of a software product stored in a storage medium (eg, ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

Example 2

In this embodiment, a public network IP distribution device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 3 is a structural block diagram of a public network IP distribution apparatus according to an embodiment of the present disclosure. As shown in FIG. 3, the apparatus includes:

1) The obtaining module 32 is configured to obtain a VLAN ID list of the access virtual network of the traditional network;

2) a first establishing module 34, configured to establish, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list;

The mapping module 36 is configured to map the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.

Optionally, in this embodiment, the application scenario of the public network IP distribution device includes, but is not limited to, a network in which a traditional network and a virtualized data center VDC are fused, and in the application scenario, accessing the traditional network is obtained. a virtual local area network VLAN ID list; establishing, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list; The second designated interface of the SDN controller is mapped to the virtual machine network ID of the virtualized data center VDC tenant. That is to say, in this embodiment, by mapping the VLAN ID of the traditional network to the VNI of different tenants in the center of the VDC cloud platform, the method for allocating a public network IP for each user of the traditional network in the related art is solved. The problem of waste of public network IP resources is caused, and the effect of saving public network IP resources is achieved.

In an alternative embodiment, FIG. 4 is a structural block diagram (1) of a public network IP distribution apparatus according to an embodiment of the present disclosure. As shown in FIG. 4, the apparatus includes, in addition to all the modules shown in FIG. :

1) The second establishing module 42 is configured to establish a mapping relationship between the plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list by using the first designated interface of the software-defined network SDN controller Creating a plurality of sub-interfaces of the VXLAN gateway through the first designated interface of the SDN controller.

The multiple sub-interfaces of the VXLAN gateway can be created by using the device shown in FIG. 4, so that the VLAN ID of the traditional network can correspond to the VNI of different tenants accessing the center of the VDC cloud platform.

In an alternative embodiment, FIG. 5 is a structural block diagram (2) of a public network IP distribution apparatus according to an embodiment of the present disclosure. As shown in FIG. 5, the apparatus includes, in addition to all the modules shown in FIG. :

The save module 52 is configured to save the object attributes of the sub-interface after the multiple sub-interfaces of the VXLAN gateway are created by the first designated interface of the SDN controller, where the object attributes include: the VXLAN gateway reports The sub-interface label corresponding to the attribute of the SDN and the VLAN ID of the virtual network access of the traditional network.

The device attributes of the plurality of sub-interfaces are saved by using the device shown in FIG. 5, and the access VLAN ID list of the traditional network and the plurality of sub-interfaces are further mapped one by one to enable the access VLAN of the traditional network to access the VDC cloud platform center. The different tenants of the VNI.

In an alternative embodiment, FIG. 6 is a structural block diagram (3) of a public network IP distribution apparatus according to an embodiment of the present disclosure. As shown in FIG. 6, the mapping module 36 includes:

1) an obtaining unit 62, configured to acquire an interface attribute of a second designated interface of the SDN controller, where the interface attribute includes at least one of the following: a virtual network ID, a label, an interface ID, a port type, and a device ID;

2) The mapping unit 64 is configured to map the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the interface attribute.

The mapping relationship between the multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list is mapped to the virtual machine network ID of the virtualized data center VDC tenant by using the apparatus shown in FIG. Further, the problem of waste of public network IP resources caused by the public network IP mode allocated to each user of the traditional network in the related art is further solved, thereby achieving the effect of saving public network IP resources.

Optionally, the first designated interface is a VLAN sub-interface object operation interface addVlanInf; the second designated interface is a port-virtual network mapping object operation interface addPortVnetMap.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination. The forms are located in different processors.

Example 3

In this embodiment, a virtualized data center system is also provided, as shown in FIG. 7, including:

1) The resource operation system IROS72 is configured to obtain a virtual network VLAN ID list of the traditional network; establish a plurality of sub-interfaces of the virtual scalable LAN VXLAN gateway and each VLAN in the VLAN ID list through the first designated interface of the SDN controller The mapping relationship between the IDs is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller;

2) a software-defined network SDN controller 74, configured to set a first designated interface and a second designated interface;

3) The virtual scalable local area network VXLAN gateway 76 is configured to create multiple sub-interfaces, wherein the labels of the multiple sub-interfaces correspond to the access virtual VLAN VLAN IDs of the traditional network.

The embodiment will be exemplified below with reference to the structural diagram of FIG. 8. As shown in FIG. 8, it includes: Openstack virtual platform, SDN controller, management system sub-module of VDC, core switch (traditional network part), VXLAN gateway device module, and the like.

Openstack Virtual Platform: OpenStack is an open source cloud computing management platform project that combines several major components to accomplish specific tasks. OpenStack supports almost all types of cloud environments. The goal of the project is to provide a cloud computing management platform that is simple to implement, scalable, rich, and standardized.

SDN controller: What SDN does is to separate the control rights on the network device and manage it by the centralized controller. It does not need to rely on the underlying network devices (routers, switches, firewalls), and shields the differences from the underlying network devices.

VDC management system management sub-module: resource management system, which provides centralized, flexible, and highly reliable computing, storage, network and other resources for VDC, unified management, on-demand distribution, and rental services.

Access and core switches: The aggregation layer access switch must be able to handle all traffic from the access layer devices and provide uplinks to the core layer. The core switches are mainly Layer 3 switches, working at the network layer. The Layer 2 switch is more upscale and more powerful. Because it works in the network layer of the OSI/RM model, it has a routing function. It provides IP address information to the network path selection. The northbound interface of the core switch is open to the SDN controller. It is convenient for it to deliver routing flow tables.

VXLAN gateway device module for extending services and management in physical and virtual networks, capable of bridging network services between software-based network overlays and underlying physical infrastructure, and enabling network coverage over tunneling protocols such as VXLAN Layer, deploy a software-based virtual cloud computing network. The core module of the VXLAN gateway is mainly a network device supporting openflow in the VDC platform. It is a carrier-class router. Its service processing board provides complex services and protocol processing, such as VXLAN gateway function, supporting NAT, IPSec, Protocols and services such as DPI, NetFlow, and CGN.

Example 4

Embodiments of the present disclosure also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. Obtain a VLAN ID list of the access virtual network of the traditional network.

S2, establishing, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list;

S3: The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in the embodiment, the processor performs the above steps S1, S2, and S3 according to the stored program code in the storage medium.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Obviously, those skilled in the art should understand that the above modules or steps of the present disclosure can be used in a universal manner. Implemented by computing devices, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented in program code executable by the computing device, such that they may be The storage is performed by the computing device in a storage device, and in some cases, the steps shown or described may be performed in an order different than that herein, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present disclosure, and is not intended to limit the disclosure, and various changes and modifications may be made to the present disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the present disclosure are intended to be included within the scope of the present disclosure.

Industrial applicability

The public network IP allocation method provided by the embodiment of the present disclosure can be applied, for example, to a network where a traditional network and a virtualized data center VDC are fused, and the VLAN ID of the traditional network is mapped to the VNI of different tenants of the VDC cloud platform center. In the related art, the problem of waste of public network IP resources caused by a public network IP access mode is allocated to each user of the traditional network, thereby achieving the effect of saving public network IP resources.

Claims

A public network IP allocation method includes:

Obtain a list of access virtual LAN VLAN IDs of the traditional network;

Establishing, by the first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list;

Mapping the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.
The method of claim 1, wherein the mapping between the plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each of the VLAN IDs in the list of VLAN IDs is established by a first designated interface of the software-defined network SDN controller Before the relationship, it also includes:

A plurality of sub-interfaces of the VXLAN gateway are created by the first designated interface of the SDN controller.
The method of claim 2, further comprising: after creating the plurality of sub-interfaces of the VXLAN gateway by using the first designated interface of the SDN controller:

Saving the object attributes of the sub-interface;

The object attribute includes at least: an attribute of the VXLAN gateway reported to the SDN, and a sub-interface label corresponding to the access virtual VLAN ID of the traditional network.
The method of claim 1, wherein mapping the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller comprises:

Acquiring an interface attribute of the second designated interface of the SDN controller, where the interface attribute includes at least one of the following: a virtual network ID, a label, an interface ID, a port type, and a device ID;

The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the interface attribute.
The method according to any one of claims 1 to 4, wherein

The first designated interface is a VLAN sub-interface object operation interface addVlanInf; and the second designated interface is a port-virtual network mapping object operation interface addPortVnetMap.
A public network IP distribution device includes:

Obtaining a module, configured to obtain a list of access virtual LAN VLAN IDs of the traditional network;

a first establishing module, configured to establish, by using a first designated interface of the software-defined network SDN controller, a mapping relationship between multiple sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list;

The mapping module is configured to map the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller.
The apparatus of claim 6 wherein said apparatus further comprises:

a second establishing module, configured to establish a virtual one at a first designated interface of the network defined SDN controller through a software Before extending the mapping relationship between the plurality of sub-interfaces of the local area network VXLAN gateway and each of the VLAN IDs, the plurality of sub-interfaces of the VXLAN gateway are created by the first designated interface of the SDN controller.
The apparatus of claim 7 wherein said apparatus further comprises:

a saving module, configured to save an object attribute of the sub-interface after creating a plurality of sub-interfaces of the VXLAN gateway by using the first designated interface of the SDN controller; wherein the object attribute at least includes: The VXLAN gateway reports the attributes of the SDN and the sub-interface labels corresponding to the VLAN ID of the traditional network.
The apparatus of claim 6, wherein the mapping module comprises:

An acquiring unit, configured to acquire an interface attribute of the second specified interface of the SDN controller, where the interface attribute includes at least one of the following: a virtual network ID, a label, an interface ID, a port type, and a device ID;

The mapping unit is configured to map the mapping relationship to the virtual machine network ID of the virtualized data center VDC tenant by using the interface attribute.
The apparatus according to any one of claims 6 to 9, wherein

The first designated interface is a VLAN sub-interface object operation interface addVlanInf; and the second designated interface is a port-virtual network mapping object operation interface addPortVnetMap.
A virtualized data center system, including:

The resource operation system IROS is configured to obtain a list of access virtual LAN VLAN IDs of the traditional network; establish a plurality of sub-interfaces of the virtual scalable local area network VXLAN gateway and each VLAN ID in the VLAN ID list through the first designated interface of the SDN controller The mapping relationship is mapped to the virtual machine network ID of the virtualized data center VDC tenant through the second designated interface of the SDN controller;

a software-defined network SDN controller configured to set a first designated interface and a second designated interface;

The virtual scalable LAN VXLAN gateway is configured to create a plurality of sub-interfaces, wherein the labels of the plurality of sub-interfaces correspond to the access virtual VLAN VLAN ID of the traditional network.
A storage medium for storing program code for performing the public network IP allocation method according to any one of claims 1 to 5.