OPNFV OPENO Opera Requirement Project Proposal Proposed name

OPNFV OPEN-O (Opera) Requirement Project Proposal Proposed name for the project: OPNFV OPEN-O Requirement for Integration Proposed name for the repository: Opera 1

Why the Proposal Ø OPNFV Board expended its scope to include NFV MANO in 2015. OPEN-O Juju/Tacker Open. Stack Ø Several Open Source MANO projects have been evolving like OPEN-O and OSM Ø All these open source MANO solutions are proposing integration with g. VNFM (Juju, Tacker, etc. ) and VIM (Open. Stack) Ø Risk of divergent requirements coming from different Open Source MANO project. Ø We take minimalist approach to define common integration requirements for OPEN-O as will be guided by MANO Workgroup in OPNFV.

Requirement for MANO Integration Ø Based on ETSI NFV MANO, VFNO, VIM, and NFVO must have corresponding NB APIs to support integration Ø The APIs for NFVO->VFNM, NFVO->VIM, and VNFM->VIM should be either Restful or RPC to be exposed by producer, which will be consumed by other components Ø Generic Information/Data Model is required for NSD, NFVD …

Prioritized Interfaces for MANO Integration (P 1 Green, P 2 Yellow) First Prioritized NB interfaces for NFVO is First Prioritized NB interfaces for VFNM is Ø VNF Package Management Ø VNF Lifecycle Operation Granting Ø Virtualized Resource Management Open. Stack available APIs will be used as it is.

Initial Integration of OPEN-O, Juju/Tacker and Open. Stack Global Service-O (GS-O) SDN-O Controller NE NE NE OPEN-O NFV-O VNFM Juju/Tacke r NOVA VIM Out of Scope Cinder Neutron ……. Ø Initial integration of OPEN-O will be NFV-O and Global Service-O Ø SDN-O is out of scope Ø Overlapped functionalities will be resolved by integration team Ø Function gaps and missing APIs will be identified and resolved by integration team Swift

Alignment of OPEN-O and ETSI NFV MANO

Required Priority APIs Over v. CPE Use Case OPEN-O VNFM APIs (Or-Vnfm) • VNF Lifecycle Mgmt G-VNFM 1 (Juju/v. FW, …) G-VNFM 2 (SFC/v. VAS) VIM APIs (Or-Vi, Vnfm-Vi) VIM 1 (OS 1) VNFO APIs (Or-Vnfm) • VNF Package Management • VNF Lifecycle Operation Granting • Virtualized Resource Management VIM 2 (OS 2) AP OS v. FW OS v. CPE OS Enterprise/Residential Site POP GW WAN PE 1 TOR PE 2 TOR AP OS Tenant Cloud for Enterprise

Use Cases and Testability • L 3 VPN as initial use case, based on which test cases will be created in Phase 1 – Basic scenario any-to-any use case provides layer 3 connectivity between VNFs in the same L 3 VPN while separating the traffic and IP address spaces of different L 3 VPNs belonging to different tenants – Detail use can be found at http: //artifacts. opnfv. org/netready/docs/requirements/use_cases/l 3 vpn_any_to_any. html#description • SFC (Service Function Chaining) as initial use case will be tested in Phase 2 – VNFs in test case will be selected along with Open-O being developed – Detail https: //tools. ietf. org/html/draft-ietf-sfc-architecture-09

Project Dependencies • Cross Project co-ordination with OPNFV projects will be relegated to OPNFV working group https: //wiki. opnfv. org/display/mano • Related standards referring Network Functions Virtualization (NFV); Management and Orchestration (ETSI GS NFV-MAN 001 V 1. 1. 1 (2014 -12)).

Accepted Committer & Contributors Committers • Huabing Zhao (zhao. huangbin@zte. com. cn) • Olga Havel (olga. havel@huawei. com) • Zhaoxing Meng (meng. zhaoxing 1@zte. com. cn ) • Narinder Gupta (narinder. gupta@canonical. com) • Byung Yun Lee (bylee@etri. re. kr ) PTL: Yingjun Li (yingjun. li@huawei. com ) Contributors � � � � Chris Donley ( Christopher. Donley@huawei. com ) Lingli Deng (dengli@chinamobile. com) Prakash Ramchandran (prakash. ramchandran@huawei. com) Ulas Kozat (ulas. kozat@huawei. com) Lizongbiao (lizongbiao@huawei. com) Artur Tyloch (artur. tyloch@canonical. com) Zengjianguo (zengjianguo@huawei. com) Deliverables: • OPNFV Release D: Requirement specification and Test specification • OPNFV Release E: ü Scenario definitions, ü Integrate with installers (Compass and Juju / Tacker), ü Testcases integrated to Functest and Yardstick. ü Test results

Questions? Please direct any questions or comments to yingjun. li@huawei. com 11