Hackathon Goals: Shared Library of VNFs for Onboarding
At Mobile World Congress 2017 in Barcelona, VMWare, Intel, and Cloudify hosted the first ever open VNF onboarding hackathon. The main goal of this event was to demonstrate the ease with which virtual network functions (VNF) onboarding can be done. We were very pleased by the turnout, with around 30 of the most innovative VNF solution providers as well as integrators taking part.
The current VNF onboarding process is quite labor intensive and requires deep understanding of the orchestrator language as well as the underlying infrastructure (VIMs such as Openstack, vCloud Director, VIO, etc.) it is being deployed on.
Read the vCPE/SD-WAN Orchestration White Paper. Go
With this hackathon, we wanted to propose a simpler way to onboard network functions with TOSCA as a common standard language for VNF definition, including advanced life-cycle events and the ability to compose multiple VNF definitions into a service chain. This cuts down the time required for a VNF vendor to take virtualized software and make it cloud native VNF ready.
The ultimate goal is to create a shared common library of VNF definitions where vendors can add their VNF and operators can make use of any vendors’ VNFs. Utilizing the TOSCA standard, users create an agnostic definition that runs on any VIM and offers a standard way to take any existing virtualized function (VF) and onboard it.
Cloudify is used as a TOSCA compliant parser as well as workflow execution engine to deploy VNFs.
The hackathon demo came with a wizard the team created, together with VMware and Intel, to define the VNF type and specify its image and requirements, like memory and disk storage, as depicted in Figure 1.
Figure 1 – TOSCA Wizard
Essentially, the wizard creates a VM to run the chosen VNF with the specified requirements. It can run on any underlying VIM. The VM is then populated with the VNF software.
The next step is to connect the network interfaces (management, inbound and outbound interfaces) correctly. The wizard then prompts you to customize the NIC ordering by specifying which NIC is connected to what network as depicted in Figure 2.
Figure 2 – NIC ordering
Users can also specify scripts for different lifecycle stages (configure, post-conf, start, stop, delete). In the future, we plan to add monitoring, logging and scaling capabilities as well.
This process then generates a downloadable TOSCA compliant file which is ready for onboarding as depicted in Figure 3. You can view the generated sample TOSCA code here.
Figure 3 – download a TOSCA compliant VNF definition
We then demonstrated how to take several VNF definitions and create a service chain with an example of vCPE service chaining a vFW and vUTM (URL filtering) VNFs.
Many vendors with various VNF types participated in this great event, including vFW, vLB vendors as well as new VNF vendors that we encountered the first time.
Vendors were definitely satisfied and, at the same time, surprised how we easily transformed their virtualized software and made it VNF ready, saving them lots of time as well as the need to understand different VIM APIs and specific language definitions.
We achieved our goal of creating one common standard language to define and onboard various VNF types, simple as well as complex.
Many of the VNFs were single VM VNFs, but there were some vendors that asked for a more complex VNF, including multiple VDUs, and we showed them how simple it was with the wizard-generated TOSCA output, even though the wizard was built for a simple, single VM VNF (Cloudify supports complex VNFs with multiple VDUs, and much more).
We got requests to enhance the wizard to support EPA features from Intel. Additional requests were for adding self-healing and scalability for the generated VNF.
Overall, we feel the hackathon was very successful and our partners, VMware and Intel, were really great to work with. Expect to see more from the VNF Onboarding Wizard in the near future.
See the TelecomTV Interview with partners VMware and Intel below as well highlighting the work of the Hackathon with some guest appearances from our team.