A VNode Plug-in Architecture to Evolve VNode
Yasusi Kanada and Toshiaki Tarui Hitachi, Ltd.
S mmar VNode enabled m t all independent e ol tion of programmers Summary: VNode enabled mutually independent evolution of programmers and redirectors. In this presentation, a method for evolving VNodes and developing new species of virtual links by using both control and data plug- ins and a publicly available testbed is proposed.
1. Introduction
Background: VNode enabled mutually independent evolution of programmers and redirectors [2],
which are components of VNode.
VNode manager (VNM)
VNode (virtualization node)
Problem to solve: A method for evolving VNode, especially for developing
d d di t d t f li k li (i i t l li k ) h ld
Redirector
(networking component)
Programmer
(computational component)
g ( )
advanced redirectors and new types of link slivers (i.e., virtual links), should be developed.
2. Proposed evolution steps
Step 1: To develop new node functions as Redirector/Programmer prototype components in a publicly available testbed (such as JGN-X).y y ( )
- There is no need to extend VNM and the network manager (SNC/TNC).
Step 2: To implement management of new successful functions in VNM, the network manager, and Redirector/Programmer in the testbed.
- The network manager manages the resources of the new node function, and can select the best node function.
Redirector VNM
Redirector component Redirector component Redirector component
Redirector New VNM
Redirector component Redirector component Redirector component
Step 1 Step 2
Redirector VNM
VNodein Osaka Extended VNode
Programmer Programmer Programmer Programmer component
VNodeextensions in Tokyo, Nagoya, etc.
(in a private environment) New VNodein Osaka (in a public testbed)
Programmer Programmer
component Programmer
component Programmer
component VNodein Osaka
(in a public testbed) Programmer
3. A plug-in architecture for step 1
The following architecture and method is used.
- An open VNode plug-in interface (OVPI) is used
Controller OVPI for
Control Plug-ins
Control plug-ins VNM
Redirector
Redirector control plug-in
interface (OVPI) is used for this extension.
- OVPI has both C-plane and D-plane interfaces.
- Plug-ins may be placed at a distant place from
OVPI for Data Plug-ins VNode
Programmer
manager Programmer
control plug-in
Programmer data plug-in manager
Redirector data plug-in Slow paths
& fast paths (Programmer
part) Switch
(Redirector part)
C-plane D-plane
the VNode.
4. Prototyping and evaluation
• A preliminary version of OVPI was implemented in the Redirector.
• An open and high-level language “CSP” and its development environment
“ N t” f C i O t ® t k [1] d f l ti
Data plug-ins VNode
Extended VNode p )
“+Net” for Cavium Octeon® network processor [1] was used for evaluation.
• VLAN-based virtual links (link slivers) were implemented and tested by using this prototype.
Controller OVPIfor Control Pl i
Controller OVPIfor
Control Pl i
VNM VNM
Inter-VNode C-plane ←→Exchanging virtual link parameters
Redirector manager
Switch (Redirector
part)
Plug-ins (CLI)
OVPIfor Data
Redirector manager
Switch (Redirector
part) Plug-in
(CLI)
OVPIfor Data Control
plug-in
Data plug-in Network processor
(Octeon)
b d
Control plug-in
Data plug-in Network processor
(Octeon)
b d
VNM VNM
New type of virtual links (link slivers)
C-plane D-plane
5. Concluding remarks
• A method of evolving VNode is proposed and the step 1 of this method is
i ll d b di h R di
Data Plug-ins
(VLAN)
Data Plug-ins (VLAN)
board Inter- board
VNode D-planes
VNode VNode
Extended VNode Linux PC Linux PC Extended VNode
(link slivers)
Built-in virtual link (GRE link sliver)
partially tested by extending the Redirector.
• A future work is to apply this method to the VNodes in JGN-X.
Acknowledgments
•Part of the research results is an outcome of the Advanced Network Virtualization Platform Project A funded by NICT.
• The authors thank Kazuhisa Yamada from NTT, Akihiro Nakao from the University of Tokyo, and
th b f th b j t f di i th l ti
other members of the above project for discussions on the evolution process.
References
[1] Kanada, Y., “ネットワーク・プロセッサのためのオープンで高級で移植可能なプログラミング環境”,電子
情報通信学会 第 7回 ネットワーク仮想化時限研究会, July 2013 (notyetavailable in English).
[2] Kanada, Y., Shiraishi, K., and Nakao, A., “Network-virtualization Nodes that Support Mutually Independent Development and Evolution of Node Components”, 13th IEEE International Conference on Communication Systems (ICCS 2012), November 2012.
