1. © 2016 TM Forum | 1 NFV Ecosystem Enabler: A well-enabled VNF package Catalyst Theater Presentation, May 10, 2016

2. © 2016 TM Forum | 2 Problem Statement Procurement When I buy a Network Service or VNF What is in the box? How do I determine it is fit for purpose? How do I acceptance test it? And when should I pay for it? Operations When a Network Service or VNF is delivered, how do I manage and onboard into my organization? What management tools does it support? And how will I manage it automatically within my IT and network operations? Service providers are faced with some simple, but surprisingly hard to answer business questions in NFV transformation:

3. © 2016 TM Forum | 3 Catalyst Participants Champions: Solution Providers: Collaboration Communities:

4. © 2016 TM Forum | 4 User Stories - Smart City NFV Ecosystem

5. © 2016 TM Forum | 5 Solution Approach & Project Scope Develop Design Develop Test Deliver Package Validate Accept and catalogue (onboard) Deploy Combine Assemble Configure (software) Use Service design Configure (service) Instantiate Manage Monitor Update Upgrade Retire Migrate User Template-based, well-enabled packages for automated onboarding 1 Network DevOps principles & governance for service design & creation Autonomic computing blueprint approach for deployment orchestration & lifecycle management 2 3 VNF SupplierVNF Supplier/ Service provider (procurement) Service provider (Service design) Service provider (Service Delivery) Service provider (Service Assurance)

6. © 2016 TM Forum | 6 Technology Highlights Focus: Business layer abstraction & orchestration

7. © 2016 TM Forum | 7 7 ScopeGovernanceStandards Procurable VNF PackageService ProvidersTo be defined by the TM Forum Supplier VNF PackageSuppliersETSI VNF Package/IFA011, TOSCA, Docker, Other standards Supplier Run time Deployment Module Suppliers + Service ProvidersStandard for Containers Packaging Layer of Abstraction & Scope TM Forum IG1141 scope Catalyst scope

8. © 2016 TM Forum | 8 A well-enabled package = OASIS/TOSCA template + additional metadata Metadata: Attributes to support procurement decisions & lifecycle management, examples :  Make, Buy, Rent model  Pricing  SLA  Maturity/Trust  Metrics  Licensing model  Entitlement  Capacity  …  SLA  KPI/KQI

9. © 2016 TM Forum | 9 Demo - Onboarding Develop Design Develop Test Deliver Package Validate Accept and catalogue (onboard) Deploy Combine Assemble Configure (software) Use Service design Configure (service) Instantiate Manage Monitor Update Upgrade Retire Migrate User Template-based, well-enabled packages for automated onboarding 1 Network DevOps principles & governance for service design & creation Autonomic computing blueprint approach for deployment orchestration & lifecycle management 2 3 VNF SupplierVNF Supplier/ Service provider (procurement) Service provider (Service design) Service provider (Service Delivery) Service provider (Service Assurance)

10. © 2016 TM Forum | 10 10 Introducing Network DevOps Accelerate Network Service delivery – for faster time to value Balance speed, cost, quality and risk – for increased capacity to innovate Reduce time to customer feedback – for improved customer experience Continuous Customer Feedback & Optimization Collaborative Network Development Continuous Network Release and Deployment Continuous Monitoring Continuous Network Business Planning Continuous Testing through development and deployment Operate Develop/ Test Deploy Fulfillment Design End-to-End Service Delivery Design Develop Test Package Validate Accept and catalogue (onboard ) Combine Assemble Configure (software) Service design Configure (service) Instantiate Monitor Update Upgrade Service provider (Service Assurance) Service provider (Service Delivery) Service provider (Service Design) VNF Supplier/ Service provider (procurement) VNF Supplier

11. © 2016 TM Forum | 11 Demo – Deployment & LCM Develop Design Develop Test Deliver Package Validate Accept and catalogue (onboard) Deploy Combine Assemble Configure (software) Use Service design Configure (service) Instantiate Manage Monitor Update Upgrade Retire Migrate User Template-based, well-enabled packages for automated onboarding 1 Network DevOps principles & governance for service design & creation Autonomic computing blueprint approach for deployment orchestration & lifecycle management 2 3 VNF SupplierVNF Supplier/ Service provider (procurement) Service provider (Service design) Service provider (Service Delivery) Service provider (Service Assurance)

12. © 2016 TM Forum | 12 12 Service Chaining & Deployment 12 NFV Package is chosen in UrbanCode Add to catalog - UrbanCode posts TOSCA blueprint to AMP AMP tests blueprint in OpenStack NFV Package listed in AMP catalog for use by blueprint authors Blueprint authors compose applications Use NFV Package as part of larger app; or Service Chaining of NFV packages Deploy app to OpenStack multi- region environment Cloudsoft Automated Workflow

13. © 2016 TM Forum | 13 Leveraging Standards and Open Sources OASIS/TOSCA Deployment Templates NFV Infrastructure & VIM OPNFV Brahmaputra Release with associated tools. Service chaining, Deployment & Management TM Forum APIs: Onboarding, Catalogue APIs

14. © 2016 TM Forum | 14 14 User Experience Dynamic 3D Model of Cloudsoft Managed Cloud Application Visualize the NFV Ecosystem Enablers Business Scenario

15. © 2016 TM Forum | 15 Example: Ambulance App App composed of:  NFV Packages: load balancer, firewall, IPS  Front-end load balancer + firewall + IPS  HA app-server cluster  Riak multi-region  Sensor ingress to app-server cluster (via load balancer + firewall) Elements shown as ”child” buildings

16. © 2016 TM Forum | 16 Project Contributions ZOOM IG1141: VNF Package Metadata ZOOM IG1139: Autonomic Computing Pattern-based Orchestration & LCM TM Forum APIs Monitor Analyze Plan Execute State SensorsEffectors Enrich Delegate Autonomic Manager* SensorsEffectors Escalate Managed Element

17. © 2016 TM Forum | 17 Future Plan - Smart City NFV Ecosystem Smart CitiesLocal Government VNF SuppliersService Providers Innovation. Agility. Experience Refined procurement & onboard requirements, metadata to support smart city/IoT scenarios e.g. maturity model, software/device & license management Refined package LCM, run time configuration, toolchain and standards recommendations Additional collaborations with other SDOs and open source implementations.

18. © 2016 TM Forum | 18 Thank You!