Transcript - the OPEN

OPEN-O VNF Supplier APIs &
SDK Project Proposal
Zongbiao Li([email protected])
Alex Vul([email protected])
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…
2
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
3
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
4
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
5
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
Vendor
VNF Marketplace
(VNF Onboarding)
upload
VNF
Package
Operator Production
Environment
download
Operator
6
Relations between VNF SDK and the other Projects
Common TOSKA
<Model Designer>
Modelling
NFV-O
reference
invoke
reference
Models
Models
VNF
Design & Package
Tool
other
Function
Test
invoke
None
invoke
hook
Validate
Lifecycle
Test
Function
Test
Market
place
VNF Onboarding
other Function Test: OPNFV FuncTest Project, Operator Function Test System, …
Self
Development
5
APIs & Interfaces
Function Test Hook
GUI
SDK
VNF
Design & Package
Tool
Models
CLI
Upload
hook
Validate
Lifecycle
Test
Function
Test
Market
place
Download
VNF Onboarding
5
Architecture Alignment
Portal
GUI Portal
…
Common Service
Orchestrator Service
Micro-Service Bus
O-Common
GS-O
External System
Register
Abstract NBI
Service
Lifecycle Mgr.
Analytics
HA
Template Mgr.
Inventory
Catalog
Auth.
Workflow Engine
Parser
Driver Mgr.
Model Designer
Service
Parser
SDN
Driver
Project Scope
SDN-O
NFV-O
Abstract NBI
Abstract NBI
SDN Lifecycle Mgr.
SDN
Monitor
SDN Res.
Mgr.
…
Protocol Stack
Legend:
Service
Decomposer
Policy
Log
…
Marketplace
(Onboarding)
VPN
VAS Mgr.
Traffic
Optimize
…
Abstract SBI
ACCESS/WAN SDN
Controller Drivers
Project Reference
EMS/NMS
Driver
VIM
Drivers
Project Invoked
NFV Monitor
NS Lifecycle Mgr.
Test
&
Lab
NFV Res. Mgr.
Abstract SBI
NFV
Driver
NFV SDN
Controller Drivers
VNFM
Drivers
VIM
Drivers
5
Testing & Integration Plans
 Unit testing (functional & API)
 End-to-end, round trip testing using “emulator” functions
 Integration testing
 TBD
5
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
5
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 [email protected]
 Tal Liron [email protected]
 Alex Vul
 Uri Elzur
 Amir Levy
 Danny Zhou
 Project Roles (RACI)
 TBD
5
s
谢谢
Thank you
For more information about VNF SDK:
https://wiki.open-o.org/view/VNF_Supplier_APIs_and_SDK
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
14
3
OPNFV Functest Progress
https://wiki.opnfv.org/display/functest/danube+functest+tests
PTL: Jose Lausuch (Ericcson)
Models in VNF SDK
Reference
OPEN-O
Other
Projects
Contribute Modeling
Project
Including
VNF SDK Project
 Model: Package Model, NSD
Model, VNFD Model ……
Models Publish
The other organizations/systems
(Open Source, ONOS, OSM, etc.)
(Commerce Product)
5
Validate & Lifecycle Test
<Common TOSCA>
Parser
<NFVO>
LCF Mgr.
Lifecycle
Test
Validate
Running Time
5
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
……
Auto-Test
Framework
VNF Vendors
invoke
Auto-Test
Scripts
test
VNFs
Test Bed
reference
OPNFV
FuncTest
Project
in
Design
Time
4
Market Place
Marketplace
Public Network IP
Market Place APP: Supplied by OPEN-O
Web Server(Cloud): Supplied by OPEN-O
Public Network IP: Supplied by OPEN-O
5
Relationship with OPNFV
Design Time
VNF SDK reference OPNFV
OPEN-O
VNF SDK
Project
Organization
VNF SDK is Up Stream Project of OPNFV
OPEN-O
VNF SDK
Project
Reference
OPNFV
FuncTest
Project
OPNFV
5