OASIS TOSCA Report for December ONAP Modeling Workshop OASIS TOSCA - Cloud Portability, Lifecycle Management and more! Michael Brenner, Cloudify - Presenting on behalf of the TOSCA TC

Agenda General updates from OASIS TOSCA 1.2 Areas in ONAP addressed by tosca-nfv-profile Updates from TOSCA NFV profile Collaboration discussion

Agenda General updates from OASIS TOSCA 1.2 Areas in ONAP covered addressed by tosca-nfv-profile Updates from TOSCA NFV profile Collaboration discussion

Simple Profile in YAML Version 1.2 updates: Artifacts processing Version 1.2 csd01 approved Aug 31, 2017: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile- YAML/v1.2/TOSCA-Simple-Profile-YAML-v1.2.pdf Substitution mappings grammar change – matching based on node type, plus properties and/or properties on capabilities Artifacts processingrecommendations (example for use of bash scripts): Identify Artifact Processor: The artifact processor for bash shell scripts is the “bash” program. Establish Execution Environment: The typical execution environment for bash scripts is the Compute node representing the Host of the node containing the artifact. Configure User Account: The bash user account is the default user account created when instantiating the Compute node. It is assumed that this account has been configured with sudo privileges. Deploy Artifact Processor: TOSCA orchestrators can assume that bash is pre-installed on all Compute nodes they orchestrate, and nothing further needs to be done. Deploy Dependencies: Orchestrators should copy all provided artifacts using a directory structure that mimics the directory structure in the original CSAR file containing the artifacts. Identify Target: The target for bash is the Compute node itself. Pass Inputs and Retrieve Outputs: Inputs are passed to bash as environment variables.

Agenda General updates from OASIS TOSCA 1.2 Areas in ONAP covered addressed by tosca-nfv-profile Updates from NFV profile Collaboration discussion

area in ONAP addressed by tosca-nfv-profile Mainly focus on design time data model for VNF descriptor and NS descriptor. Align with ETSI NFV terminology and information model. Latest draft of tosca-nfv-profile: Tosca-nfv-profile-wd05-rev03 https://www.oasis-open.org/committees/document.php?document_id=62125&wg_abbrev=tosca

Agenda General updates from OASIS TOSCA 1.2 Areas in ONAP covered addressed by tosca-nfv-profile Updates from TOSCA NFV profile Collaboration discussion

Namespace usage in tosca-nfv-profile Latest updates in tosca-nfv-profile-wd05-rev03: tosca_definitions_version : tosca_simple_yaml_1_2 TBD – v1.0 or 1.1 are still under consideration Namespace Alias : In the present document, the namespace alias is NOT used Namespace URI : http://docs.oasis- open.org/tosca/ns/simple/yaml/1.0/nf v/1.0/ Namespace Prefix : toscanfv

VNFD design example

DF discussion Proposal 1 Proposal 2 Two layers of service template DF as a capability Two layers of service template DF as a node type

DF discussion Proposal 3 Proposal 4 Two layers of service templates node filter based DF as a node template One layer of service template DF as a group type

Agenda General updates from OASIS TOSCA 1.2 Areas in ONAP covered addressed by tosca-nfv-profile Updates from TOSCA NFV profile Collaboration discussion – for creating a “telco tosca specification”.

Why? Multiple parallel efforts to define information and data models in the telecom space ETSI – IFA011/014 and SOL001 OASIS – Simple YAML and NFV profiles ONAP – based om ECOMP, TOSCA, ETSI, TMF and MEF “Code is King” ONAP models may become defacto standards if enough operators and suppliers endorse them ONAP is moving faster than SDOs Multiple parallel architectural approaches for MANO ETSI ONAP OSM Market desire to reuse and portability of network services and network functions

Proposal for Collaboration Jointly work to enhance and extend the set Simple YAML Profile normative types Jointly work to define a set of SDN/NFV normative types for the telecom space Use TOSCA OASIS as a point of upstream integration for work being done in the open source community (ONAP & OSM) Note: OASIS/TOSCA TC IPR policy is RF on limited terms – as such very friendly for cooperation with Open Source communities – e.g. OpenStack

Questions? Q&A