VNF SDK Design and Packaging issues

Slides:



Advertisements
Similar presentations
White House New Media & Open Source Software Macon Phillips White House New Media.
Advertisements

OSCAR Project Proposed Project for OPNFV
StudioSysAdmins 2 nd Annual SIGGRAPH Birds-of-a-Feather John Hickson - 08/09/2011 StudioSysAdmins 2 nd Annual SIGGRAPH Birds-of-a-Feather John Hickson.
 Linux Mint is a computer operating system designed to work on most modern systems, including typical x86 and x64 PC’s. Linux Mint can be thought of.
BoF: Open NFV Orchestration using Tacker
1 Adopting and Embracing Open Source for NFV Guy Shemesh Senior Director for Cloud Solutions, CloudBand October 2015.
© 2016 TM Forum | 1 NFV Ecosystem Enabler: A well-enabled VNF package Catalyst Theater Presentation, May 10, 2016.
OSM - Open Source MANO An open-source project hosted by ETSI
Linux Kernel Security (SELinux vs AppArmor vs Grsecurity)
FreeBSD ports & packages. FreeBSD ports & packages - overview Different UNIX distributions use differents package systems for distributing software Debian.
SDN-O LCM for Mercury Release Key Points and Overview
Open-O SFC.Mgr Proposal
OPEN-O VNF Supplier APIs & SDK Project Proposal
ARC: Definitions and requirements for SO/APP-C/VF-C discussion including call notes Chris Donley July 5, 2017.
Bryan Sullivan, AT&T June 13, 2017
Open Network Automation Platform (ONAP) Controller Architecture Proposal DRAFT.
SP Business Suite Deployment Kick-off
OPEN-O VNF-SDK Planning Release 2
Core, Device Service, Application Breakout
ONAP security meeting
ONAP SDC VoLTE Model Support
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
Defining ONAP VNF Package Model
Tina Tsou, Bryan Sullivan,
Aligning Orchestration and Controller Per Merger Agreement Vimal Begwani – AT&T Jamil Chawki – Orange Alla Goldner -- Amdocs.
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
VoLTE VNF Descriptor gaps
INCOSE Usability Working Group
ARC: Definitions and requirements for SO/APP-C/VF-C discussion Chris Donley Date , 2017.
Domino Release D Planning
ONAP SDC TOSCA Import Gap Analysis
NFV Updates Deepanshu Gautam.
ARC 5: Deployment Options Chris Donley
Zongbiao OPEN-O VNF SDK Design Zongbiao
The Internet of Things (IoT) and Analytics
Cross Community CI (XCI)
Introduction to OPNFV CVP
5GCOM Report to Board# review and 2017/2018 objectives
Dovetail project update
ETSI NFV POCS and PLUGTESTS
ONAP security meeting
Core, Device Service, Application Breakout
Approach to finalize the TOSCA NFV profile
Clarification of CSAR format Thinh Nguyenphu, Nokia thinh
Critical issues with TOSCA NFV profile direction
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
Enhanced Platform Awareness (EPA) Alex Vul Intel Corporation
OASIS TOSCA Report for December ONAP Modeling Workshop
VF-C R2 Feature Planning & Implementation Yan Yang
Usecase 1 – Upgrade Image
ONAP Amsterdam Architecture
Consideration of Modeling Evolution in ONAP Michela Bevilacqua Peter Wörndle and Tara Cummings 13 December , 2017.
TOSCA NFV profile: short vs long-term approach
Artifact Properties Use cases and Examples to demonstrate the need of artifact properties July 2018.
Defining ONAP VNF Package Model
ONAP modeling report shitao.
5G RAN Deployment – Casablanca PNF software and configuration management Huawei,
NFV adhoc Shitao li.
Draft Proposal for an Eclipse Mobile Development Suite Architecture
FreeBSD ports & packages
ETSI TTCN-3 Test Suites QUALITY IMPROVEMENT
Open Source Projects Collaborations with ONAP
For Community and TSC Discussion Bin Hu
NFV adhoc Shitao li.
Implementation Discussion Bin Hu
Proposed Approach for ONAP Runtime Support of Network Service Onboarding Gil Bullard, AT&T.
Common NFVI Telco Taskforce Paris Face-To-Face Sessions Compliance & Verification Heather, Kirksey LFN Rabi Abdel, Vodafone Group; July 2019.
Title: Robust ONAP Platform Controller for LCM in a Distributed Edge Environment (In Progress) Source: ONAP Architecture Task Force on Edge Automation.
VNF Validation Project (VVP) Governance Model – Preliminary Views Sandeep Shah November 9, 2017.
Module 02 Operating Systems
Presentation transcript:

VNF SDK Design and Packaging issues Christopher.donley@Huawei.com

Largest addressable market VNF Landscape OSM Telefonica, BT, etc. VNF What VNF Vendors want: Standard format Largest addressable market Easy to use tooling What OPEN-O wants: Largest VNF ecosystem Most operators VNF VNF marketplace OPEN-O CMCC, CT, HKT, etc. VNF VNF VNF ECOMP AT&T, Orange, etc.

They build their own tools (hopefully built around our format) VNF SDK role We don’t care about these communities directly, but we want them to use our format so that we get more VNFs OSM Telefonica, BT, etc. VNF SDK VNF VNF VNF marketplace OPEN-O CMCC, CT, HKT, etc. VNF VNF They build their own tools (hopefully built around our format) VNF ECOMP AT&T, Orange, etc.

Packaging formats Linux Orchestration .deb -> Debian, Ubuntu, Mint, Raspbian, etc. .rpm -> Redhat, Fedora, Centos, Suse, etc. .apk -> Android Orchestration OPEN-O: defined by VNF SDK Big advantage if we define an extensible format first OSM, ECOMP: ??? – best if they use our format All will draw from {ETSI, TOSCA, internal} specs We want to influence the mix and lead on supplying internal extensions

General Process from VNF Plan to Marketplace Vendor’s general Process from Plan to Marketplace optional mandatory optional optional upload Plan Design & Package Dry Run Self Test Marketplace VNF Vendor <<use>> <<use>> <<use>> <<use>> OPEN-O VNF SDK VNF Design & Package Tool Other VNF Design & Package Tool OPEN-O Some vendors will use our tool Some will design their own but will use our libraries We want to encourage EVERYONE to use our FORMAT Vendors develop for OPEN-O first We have less work to align with industry format

VNF Package CSAR VNFD Node Type Capabilities Requirements CSAR Pack ETSI TOSCA OPEN-O VNF Metadata CSAR Validate

Issues from TSC call Design tool Dry Run VNF SDK contains a VNF supplier deliverable – a set of TOSCA template/CSAR utility functions for integration with supplier’s devops environment Both Common TOSCA and Model Designer contain candidate functionality for this deliverable Potential code duplication, which code to use for deliverable? Can we use both? Dry Run VNF SDK supplier deliverables contain a “dry run install” utility function for use by VNF suppliers, as part of their DevOps toolchains The purpose of this function is to simulate a VNF instantiation based on the VNF design time model specification This utility function may be better suited for environments where simulation can be done against real OPEN-O infrastructure, as part of the Marketplace and during VNF on-boarding

Issue 1 (Design tool) Model Designer Common TOSCA Accept both Provides package management, model design, workflow design Common TOSCA Provides a set of TOSCA template/CSAR “utility tools”: template reader/writer/parser, CSAR reader/writer/validator, and “dry run” installer Accept both Code speaks louder than powerpoint Yes, we would have duplicate code (but most of it is already written) Collect VNF vendor feedback after Mercury Refactor for Venus

Issue 2: Dry Run Situation Solution 1: use NFV-O and gVNFM VNF SDK proposes “dry run install” utility that VNF vendors integrate into their DevOps toolchains (e.g., Jenkins) Purpose: simulate a VNF instantiation based on the VNF design time model specification Solution 1: use NFV-O and gVNFM Solution 2: use Common TOSCA/ARIA Solution 3: Defer “dry run” to Venus (Release 3) Use next few months to consider impacts of both proposals Both groups schedule time on ARC call to discuss Consider moving “dry run” functionality to both Marketplace and/or VNF onboarding workflow in NFV-O LCM

Time is short -> M2 is tomorrow (Thursday) Issue 1 (design tool) Recommendation Time is short -> M2 is tomorrow (Thursday) Issue 1 (design tool) Invite BOTH ZTE and Gigaspaces to contribute code Functionality MUST be ‘stubbed out’ this week Data models/APIs locked down by M3 Issue 2 (dry run) Defer until R3 (Venus) Spend more time thinking about the solution