OpenDaylight is an open source project and open to all. Developers can contribute at the individual level just like any other open source project. This blog series highlights the people who are collaborating to create the future of Software Defined-Networking (SDN) and Network Functions Virtualization (NFV).
Su-Hun Yun is a Senior Manager at NEC Corporation of America and leads business development for NEC's Software-Defined Networking (SDN) products and creating an OpenFlow-based SDN ecosystem. As a member of the original team working on the NEC ProgrammableFlow Networking Suite product line, he was instrumental in launching the world's first production-ready SDN product in 2011. He also has more than 20 years of experience in carrier and enterprise networking.
How did you get involved with OpenDaylight? What is your background?
I have been involved in OpenDaylight from the founding phase, and have been active in OpenFlow since 2009, when I started the OpenFlow controller project in NEC. NEC has been a supporter of SDN research at Stanford from the beginning and has been a leader in the development of OpenFlow and in the SDN industry itself, shipping the first generally available SDN product, ProgrammableFlow® Networking Suite, in May of 2011.
I recognize the need to have an open source community for development of the SDN controller because of customers' concerns regarding vendor lock-in and closed solutions. This support of open source is one of the reasons NEC became a founding member of the OpenDaylight community.
What project are you working on for OpenDaylight? Any new developments to share?
I am working on the Virtual Tenant Network (VTN) project in OpenDaylight. VTN is a core technology of NEC's ProgrammableFlow network fabric, and we have contributed our source code from the production software. As VTN has been deployed to 100+ users, including proof of concept (PoC), it's very stable, functionally rich and highly robust.
Key VTN capabilities include:
- It hides the complexity of the physical network and provides an abstracted view to users and applications; and
- VTN models virtualize the physical network.
- vBridge: a logical representation of L2 network;
- vRouter: a logical representation of L3 network;
- vTunnel: a logical representation of tunnel;
- vLink: a logical representation of physical connectivity;
- Enables multi-tenancy and traffic in each VTN is totally isolated and secure from other VTNs; and
- Provides a northbound API for SDN applications and orchestration, such as OpenStack.
In the VTN project, we are porting VTN source code from the NEC ProgrammableFlow product to the OpenDaylight Controller. The ported code was successfully demonstrated at the recent Hackfest. The initial development of the VTN project will soon be completed and will be part Hydrogen release in December.
People have different definitions for SDN depending on how they're using the network. What's your definition of SDN?
My definition of SDN is driven by my experience working with customers to deploy production-ready SDN networks. VTN in OpenDaylight is an OpenFlow-based network virtualization solution that enables users to create and manage multi-tenant virtual networks. I have worked with many switch vendors on OpenFlow interoperability and am also working closely with application partners. These partners use the NEC controller's northbound API to provide many SDN-based management, security and optimization applications. Based on all of these experiences, I would define SDN as an OpenFlow-based, multi-vendor fabric with SDN applications using the controller's northbound API.
From your perspective, what are the major benefits of making OpenDaylight an open source project?
I believe OpenDaylight will accelerate the maturity of the SDN market. OpenFlow and SDN have gained a lot of attention from the market, but it's still an emerging technology. An open source SDN controller will increase SDN users and developers and provide many opportunities to deploy it to market. I expect to see many SDN applications using the OpenDaylight Controller, including VTN's northbound API. I strongly believe that SDN has the potential to change networking history. And being open is the most important aspect in realizing that vision.
What advice would you give to someone just getting started in an open source project?
Since this is actually my first time to work on an open source project, I'm still learning. However, I will say that the Linux Foundation and OpenDaylight are well organized, and I'm very comfortable working in this community. I believe that with the Hydrogen release, the market at large will have a better understanding of the enormous potential of the OpenDaylight community and will be able to very easily start to work with the project.
No comments:
Post a Comment