1. OPEN-O VNF Supplier APIs & SDK Project Proposal
Zongbiao
Alex

2. Project Overview Project Name: VNF Supplier APIs & SDK
Repository name: vnfsdk
Project Description:
This project will deliver automation tools for VNF product specification, packaging, publication and ingestion
This project will also deliver a whole process of onboarding(parameter validation, function test, uploading to marketplace) for VNF
This project will also support onboarding and instantiation of VNF products with EPA dependencies on VIMs and NVF-I.
The functionality supplied by this project is intended for use by NFV operators, VNF product developers and VNF product DevOps teams.
Project Participants:
CMCC, Intel, GigaSpaces, Huawei, ZTE…

3. Project Scope – Problems Being Solved
Current VNF on-boarding, instantiation and maintenance procedures, used by NFVI operators are highly manual, time consuming and specifically tailored to individual operators, VIMs, NFV infrastructures and VNF types
VNF suppliers want to participate in a large ecosystem for more market opportunities, and to develop their VNF products in a way that is attractive to the largest range of buyers
In order to support multiple service and business scenarios, VNF suppliers want to package and deliver their VNF products in a way that is highly standardized, automated and configurable
VNF suppliers, who rely on specific NFVI and VIM capabilities, as well as telemetry feedback, want to ensure that their VNF infrastructure and VIM dependencies are met, so that their VNF product can function as designed
Current versions of ETSI/MANO VNF package (VNFD) and VNF record(VNFR) definitions prevent VNF suppliers from expressing NFVI and VIM dependencies and requirements*
* - based on ETSI/MANO Specification, v1.1.1, December 2014

4. Project Scope – Features & Functionality
DECLARITION: the features and functions listed in the below MAY referenced to the other projects in OPEN-O, and the detail information will be described in the next pages.
Standardized VNF product packaging based on TOSCA
TOSCA node, requirement and capability types to support specification of the VNF product functional, operational and deployment requirements, inclusive of VIM and NFVI dependencies, service quality characteristics and telemetry KPIs
TOSCA compatible extensions to ETSI/MANO VNFD, VDU and VNFR definitions to support specification of VIM and NFVI dependencies, service quality characteristics and telemetry KPIs
NFV operator tools and SDK for ingestion (download) of VNF products from the VNF marketplace
VNF Supplier DevOps tools and SDK for automated packaging and publication of VNF product releases
A Network Function Marketplace (NF-MP) for publication, upload and download of VNF products and offerings
Tooling necessary to support VNF coherence, environment and dependency checking during packaging, upload and download.
NFV-O lifecycle manager workflow extensions to support on-boarding and instantiation of VNF products with EPA dependencies on VIMs and NFV-IC

5. Project Scope – Value Proposition
VNF Suppliers
Reduce TTM
Maximize developer efficiency
Minimize development costs
VNFI Operators
Reduce TTV
Maximize operational efficiency
Minimize TCO
Service Operators
Reduce TTM
Maximize service delivery efficiency
Minimize service delivery costs

6. User’s View of the Project
Legend:
VNF
Design & Package Tool
This Project Scope
Validate
Lifecycle
Test
Function
Test
Market place
Out of the Scope
use
VNF
Package
VNF Marketplace
(VNF Onboarding)
upload
Vendor
VNF
Package
Operator
download
Operator Production Environment

7. Relations between VNF SDK and the other Projects
Common TOSKA
<Model Designer>
Modelling
NFV-O
other Function Test
None
reference
reference
invoke
invoke
invoke
hook
VNF
Design & Package Tool
Models
Models
VNF Onboarding
Validate
Lifecycle
Test
Function
Test
Market place
Self Development
other Function Test: OPNFV FuncTest Project, Operator Function Test System, …

8. APIs & Interfaces Models Function Test Hook GUI Upload VNF
Design & Package Tool
Models
VNF Onboarding
CLI
Validate
Lifecycle
Test
Function
Test
Market place
Download
SDK

9. Architecture Alignment
Portal
GUI Portal …
Marketplace
(Onboarding)
Common Service
Orchestrator Service
O-Common
GS-O
Micro-Service Bus
External System Register
Abstract NBI
Analytics
Service Lifecycle Mgr.
Service Decomposer
Service
Parser HA
Policy
SDN-O
NFV-O
Template Mgr.
Log
Inventory
Abstract NBI
Abstract NBI
Test
&
Lab
SDN
Monitor
SDN Lifecycle Mgr.
NFV Monitor
NS Lifecycle Mgr.
Auth.
Catalog
VPN
VAS Mgr.
Workflow Engine
Driver Mgr.
Parser
SDN Res.
Mgr.
Traffic Optimize …
NFV Res. Mgr.
Model Designer
Protocol Stack …
Abstract SBI
Abstract SBI
SDN
Driver
NFV
Driver …
ACCESS/WAN SDN Controller Drivers
EMS/NMS Driver
VIM Drivers
NFV SDN
Controller Drivers
VNFM Drivers
VIM Drivers
Legend:
Project Scope
Project Reference
Project Invoked

10. Testing & Integration Plans
Unit testing (functional & API)
End-to-end, round trip testing using “emulator” functions
Integration testing
TBD

11. Architectural Alignment – Standards
This project will extend existing interfaces specified and curated by ETSI/MANO community
This project will extend existing interfaces specified and curated by OASIS/TOSCA community
In parallel, this project will work outside of OPEN-O to promote the adoption of above changes into relevant standards, and to seek feedback from the broader community and EUTAB

12. Resource Contact Person Zongbiao Li Alex Vul Developers
Gigaspace – 2 developers
Intel – 2-4 developers as needed
Huawei – TDB
CMCC – TBD
Initial Committers
Johnson Li
Tal Liron
Uri Elzur
Amir Levy
Danny Zhou
Project Roles (RACI)
TBD

13. 谢谢 https://wiki.open-o.org/view/VNF_Supplier_APIs_and_SDK
For more information about VNF SDK:

14. Relation between MKT Place and Catalog
Catalog is like a refrigerator in the kitchen, and it store many types of VNFs imported/bought from the MKT Place.
Catalog is facing to Operators only. Operators select some appropriate VNFs to deploy them and combine them into a product, just like selecting some food material to from the refrigerator to cook a delicious dinner, ^_^
MKT Place is a actually MKF Place, while it is only for VNFs, not for vegetable, fruit, etc. ^_^
MKT Place if facing to Vendors and Operators. Vendors Show/Sell their VNFs in the MKT place, and Operators Import/Buy the VNFs from the MKT Place 3

15. OPNFV Functest Progress
PTL: Jose Lausuch (Ericcson)

16. Models in VNF SDK Reference OPEN-O Other Projects Modeling Project
Models Publish
Contribute
Including
VNF SDK Project
The other organizations/systems
(Open Source, ONOS, OSM, etc.)
(Commerce Product)
Model: Package Model, NSD Model, VNFD Model ……

17. Validate & Lifecycle Test
<Common TOSCA>
Parser
<NFVO>
LCF Mgr.
Validate
Lifecycle
Test
Running Time

18. Function Test
It is IMPOSSIBLE to do function testing by VNF SDK Project itself! For there are too many use cases, too many interfaces and all of them are different. What this project can do is:
Define one(or more) auto-test script
Define auto-test interfaces hooked by the project
Code/Select an auto-test framework to hook the interfaces
VNF SDK
VNF Vendors
reference
OPNFV
FuncTest Project in
Design Time
invoke ……
Auto-Test
Framework
Auto-Test
Scripts
test
Test Bed
VNFs

19. Market Place APP: Supplied by OPEN-O
Web Server(Cloud): Supplied by OPEN-O
Public Network IP: Supplied by OPEN-O
Public Network IP

20. Relationship with OPNFV
Design Time
VNF SDK reference OPNFV
Organization
VNF SDK is Up Stream Project of OPNFV
OPEN-O
VNF SDK
Project
OPNFV
FuncTest
Reference