Providing Infrastructure Functions for Virtual Networks by Applying - - PowerPoint PPT Presentation

▶
providing infrastructure functions for virtual networks
SMART_READER_LITE
LIVE PREVIEW

Providing Infrastructure Functions for Virtual Networks by Applying - - PowerPoint PPT Presentation

Nov 01, 2022 475 likes •609 views

Providing Infrastructure Functions for Virtual Networks by Applying Node Plug-in Architecture Yasusi Kanada Hitachi, Ltd., Japan Background VNode and VNode Infrastructure was developed in a collaborative project. VNode is a physical

slide-1
SLIDE 1

Providing Infrastructure Functions for Virtual Networks by Applying Node Plug-in Architecture

Yasusi Kanada Hitachi, Ltd., Japan

slide-2
SLIDE 2

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Background

►VNode and VNode Infrastructure was developed in a collaborative project. ►VNode is a physical node with network-virtualization functions. ►VNode Infrastructure is a network architecture and testbed with network-virtualization function.

■ On this infrastructure, multiple developers can create and use slices (i.e., virtual networks) concurrently and independently.

2

VNode

slide-3
SLIDE 3

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Background (cont’d)

►VMs (virtual nodes) in VNodes can implement routing and switching, but the performance is limited. ►VNode contains a layer-3 (L3) switch, which has high- performance routing and switching functions. ►Slices can not use its functions, such as switching or routing.

3

VNode manager Redirector

(networking component)

Programmer

(computational component)

VNode (virtualization node)

L3 switch

slide-4
SLIDE 4

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Proposal

►A method for supporting L3 switch functions to slices is proposed. ►This method is based on the node plug-in architecture, which was proposed in previous papers.

4

slide-5
SLIDE 5

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

VNode Infrastructure and Slice Definition (Previous Work)

▶ A developer can create a slice by sending a slice definition (RSpecs) to the management server (i.e., DC). ▶ A slice definition contains definitions of virtual nodes and links of predefined types.

5

3

Gate- way Gate- way User’s PC/VM User’s PC/VM DC

VNode VNode VNode

IP Router

VNode

DC: Domain Controller

Virtualization platform (IP network)

Slice definition

<nodeSliver name="..." ...> <instance type="SlowPath_VM">... </instance> ... </nodeSliver> ... <linkSliver name="..." type="link" ...> ... </linkSliver> ...

Predefined virtual-node type Predefined virtual-link type

slide-6
SLIDE 6

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Plug-in Architecture for VNode (Previous Work)

►Plug-ins enable new types of virtual nodes/links to be added to VNode. ►New types can be specified in a slice definition.

■ All the implementation parameters can be specified by the developer,

  • r

■ The implementation parameters can be hidden from the developer (can be supplied by control/management components).

6

<nodeSliver name="vrf1" …> <instance type="virtual_router"> <params> ... </params> </instance> <vports><vport name="p1"/> … <vport name="pm"/></vports> </nodeSliver> <nodeSliver name="vrf1" …> <instance type="extension"> <params> <param key="PlugInName" value="intSw" /> <param key="DataPort" value="vlan" /> <param key="ControlPort" value="192.168.110.61" /> <param key="Command-runNodeSliver" value="run_vrf" /> <param key="Command-stopNodeSliver" value="stop_vrf" /> ... </params> </instance> <vports><vport name="p1"/> … <vport name="pm"/> </vports> </nodeSliver>

New virtual node-type name Plug-in name, control and data I/F Plug-in parameters

slide-7
SLIDE 7

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Plug-in Architecture for VNode (Previous Work) (cont’d)

►New types are implemented by a combination of two types of plug-ins:

■ Data plug-ins extend data-plane functions such as packet forwarding. ■ Control plug-ins extend control-plane functions: manages data plug-ins.

VNode Control plug-in interface Data plug-in interface Plug-ins Extended VNode Control-plane component Data plug-in (Packet handling plug-in) Data-plane component (L3 switch) C-plane D-plane Control plug-in

7

slide-8
SLIDE 8

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Proposal: Plug-ins and Interfaces for L3 Switch Functions

►Data plug-in: the L3 switch

■ The same switch as the data-plane component of the VNode, ■ The data plug-in must be isolated from the VNode.

►Data plug-in interface (DPII) is extended:

■ Original DPII is MAC-address-based ■ New DPII is VLAN-based ― L3-switch requirements

8

SDMACSSMAC SEType VLAN tag Payload PDMACPSMAC PEType SDMACSSMAC SEType Payload

Virtual node

VLAN V1 VLAN V2 VLAN V3

p1 p2 p3

Virtual node

MAC address M1 p1

p2 p3

MAC address M2 MAC address M3

DPII Data plug-in

(L3 switch)

Data-plane component

(L3 switch)

Same switch VNode

slide-9
SLIDE 9

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Proposal: Plug-ins and Interfaces for L3 Switch Functions (cont’d)

►Control plug-in must be developed.

■ It assigns VLAN IDs for the DPII.

►Control plug-in interface (CPII)

■ CLI is used for CPII. ■ Command names for this CLI must be specified.

  • E.g., when they are specified in slice definitions:

■ Parameters for the commands must be specified.

9

CPII Control-plane component Control plug-in VNode

<param key="Command-runNodeSliver" value="run_vrf" /> <param key="Command-stopNodeSliver" value="stop_vrf" />

slide-10
SLIDE 10

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

L3 Switch Functions to be Provided to Slices

►Switching function (of Ethernet)

■ Number of ports is arbitrary. ■ No plug-in parameters are required.

►Routing function (VRF function)

■ Number of ports is arbitrary.

■ Routing parameters are specified as parameters in the slice definition.

<param key="routing_protocol" value="ospf" /> <param key="ospf_subnet" value="192.168.0.0" /> <param key="ospf_mask" value="0.0.15.255" /> <param key="ospf_area" value="110" /> <param key="ospf_domain" value="1" /> <param key="router_ip" value="192.168.101.1" />

10

VLAN V1 VLAN V2 VLAN V3 VLAN V4 switch VRF (router) VLAN V1 VLAN V2 VLAN V3

slide-11
SLIDE 11

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Prototyping and Evaluation

►The plug-in interfaces were partially implemented to a type of VNode called NACE (NC). ►The control plug-in was implemented in Perl.

■ It communicates with the L3 switch through CLI,

►OSPF-based IP routing and Ethernet switching plug-ins were implemented.

■ Routing and switching among three terminals were tested. ■ Rerouting between two virtual routers were tested.

11

slide-12
SLIDE 12

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Prototyping and Evaluation (cont’d)

►Virtual-node development cost (when plug-in parameters are embedded to control components)

■ Ethernet switching: only 8 lines are required for specifying a virtual switch.

  • 16 lines with plug-in parameters.

■ OSPF routing: only 19 lines (including OSPF parameters) are required for specifying a virtual router

  • 25 lines with plug-in parameters.

12

<nodeSliver name="vrf1" …> <instance type="virtual_router"> <params> <param key="P1" value="V1" /> … <param key="Pn" value="Vn" /> </params> </instance> <vports> <vport name="p1"/> … <vport name="pm"/> </vports> </nodeSliver> <nodeSliver name="sw1" …> <instance type="virtual_switch" /> <vports> <vport name="p1"/> … <vport name="pm"/> </vports> </nodeSliver>

slide-13
SLIDE 13

SDN NGAS 2014 2014-8-20 Yasusi Kanada, Hitachi, CRL

Summary and Conclusion

►Summary

■ A method for supporting L3 switch functions, which is based on the node plug-in architecture, is proposed. ■ OSPF routing and Ethernet switching functions were prototyped for VNode by this method and evaluated.

►Conclusions

■ Plug-ins for routing and switching can easily be developed. ■ Slice developers can easily use the plug-in functions in slices.

►Future work

■ Extending switch/router plug-ins and implementing new plug-ins (e.g., switching non-Ethernet addresses).

13