TM Forum Live! 2017 Using Future OSS Orchestration to Enhance Operations and Service Agility

Size: px

Start display at page:

Download "TM Forum Live! 2017 Using Future OSS Orchestration to Enhance Operations and Service Agility"

Chastity Harris
6 years ago
Views:

1 TM Forum Live! 2017 Using Future OSS Orchestration to Enhance Operations and Service Agility 2017 TM Forum 1

2 Presenters Roberto Kung Senior Vice President, Network Operations & Performance Orange Pierre Muller Vice President, OSS & Operations Processes Orange Tom Archer Solution Architect, Future OSS Technical Director Huawei 2017 TM Forum 2

3 Content 1 Orange Strategy and Expectations 2 Future OSS Concepts and Architecture 3 Take Away and Benefits 2017 TM Forum 3

customer This implies overall transformation, in particular for

4 Orange digital transformation strategy plan Essentials2020 To be always responsive and in touch with what is essential for the customer This implies overall transformation, in particular for Operation Agility A digital, efficient and responsible company 2017 TM Forum 4

5 Orange expectations 1. Fast adaptation Agility 2. Full automation 3. Openness 2017 TM Forum 5

Collaboration Design systems Recipes Policies Design systems:

6 1. Fast adaptation Vendor Software Product Recipes Policies Operator Operation Package From 18 months to 6 days Incubation Validation Collaboration Design systems Recipes Policies Design systems: DesignOps, Model-driven Processes and Catalogue-based Definition 2017 TM Forum 6

7 2. Full automation Fulfillment Master Service Orchestrator Orchestration Assurance Real-time Policy Product Service Resource Receipts Policies IaaS controller Network controller Application controller Telemetry Control Loops, Knowledge Plane, Real-time Analytics, Policy-based Decision 2017 TM Forum 7

8 3. Openness Openness through APIs & Adaptation layer: legacy OSS, Infra, partners 2017 TM Forum 8

9 Content 1 Orange Strategy and Expectations 2 Future OSS Concepts and Architecture 3 Take Away and Benefits 2017 TM Forum 9

Agility Enablers Future OSS - Achieving the Goals of OSS Agility Providing the AGILITY to support digital operations transformation of hybrid networks Low Agility Features Future OSS Features

10 Agility Enablers Future OSS - Achieving the Goals of OSS Agility Providing the AGILITY to support digital operations transformation of hybrid networks Low Agility Features Future OSS Features Separated Design, Development, Rapid Operations DevOps DesignOps Development Hard wired code based processes Processes Model-driven processes and definitions Open Ecosystem Proprietary/static APIs Technology/business based silos Open APIs Federation of systems Everything-as-a-Service (XaaS) OSS Automation and Autonomics OSS Adaptability Limited, low level rule base Siloed, completely open-loop systems Monolithic systems Multiple Incompatible Views End to End Closed Loop Orchestration Analytics Policy-based decision making Common Information Model/ Model Transformation Cloud-based platform Microservice-based FMO architecture 2017 TM Forum 10

11 Future OSS High Level Functional Architecture Providing the AGILITY to support digital operations transformation of hybrid networks Design Systems Service Design Fulfillment Pre-Ordering Assurance Visualization Design Systems enables DevOps and DesignOps using a Visual Design Studio to support integrated model development Policy Design Analytics Design Resource Design Order Management Orchestration Data Collection Analytics Operations Decision Implementation Support Systems provide multi-domain catalogue, dynamic inventory and policy management, acting as a bridge between design-time and run-time Orchestration leverages the models, policies, and metadata required to support end-to-end closed loop fulfillment and assurance. Adaptation Support Systems Catalogue Policy Management Cloud / PaaS Dynamic Inventory Fulfillment interacts with external order processes performing order lifecycle management and status tracking Assurance provides automation tools, and guides manual operations in the event of fall out from Orchestration. Cloud/PaaS provides the cloud-based platform of the Future OSS 2017 TM Forum 11

12 Achieving Automation and Autonomics: Closed Loop Operation Based on the OODA Principle (Observe, Orient, Decide, Act) Design Systems Fulfillment Support Systems Cloud / PaaS Orchestration Assurance Orchestration Data Collection Analytics Decision Implementation External Events and Information Observe Orient (Context Based Analysis) Decide (Plan) Act Feed Forward Process Data Collection reacts to new events Analytics gathers and generates context - develops understanding using knowledge-based techniques Decision adopts one or more possible courses of action Implementation carries out the action Policy provides guidance at each stage Hybrid Network (Cloud, Physical/Virtual Devices and Connectivity) Feedback Process Analytics, Decision and Implementation may generate direct feedback/guidance that changes the way that the system reacts to data More complex internal loops may be necessary e.g. for self-configuring, self-healing, self-optimising, and self-protecting behaviour 2017 TM Forum 12

13 Achieving Automation and Autonomics: Full Automation Data Collection receives Analytics uses event and goal based Decision creates new goal Implementation a series of resource policy plus predictive analysis to and determines optimum configures the changes, performance events anticipate future service issues course of action based on and tests and verifies all Orchestration utility function policy and related policies analysis Data Collection Analytics Decision Implementation Resource Performance Events Event Based Policy handle resource performance events Goal Policy - Increase Resource Capacity (change state) Design and Configure resource changes Resource D Type Y State A dependency Service C Type x Goal Policy - resource type y utilisation is < 60% Goal Policy Service type x Response Time is < 5s Predictive Service/ Resource Performance Analysis Utility Function Policy Utility (goodness) of state transition A-B = (..) etc. Resource State A Utility = 3 Utility = 2 Utility = 1 Resource State B Resource State C Resource State D Resource D Type Y State B Test Changes and Verify associated policies 2017 TM Forum 13

14 Achieving Automation and Autonomics: Blending Human and Machine Operations Orchestration loops may need closing through human intervention with progressive automation 8 Fulfillment Assurance Design Systems Orchestration Support Systems Cloud / PaaS Orchestration Data Collection Decision 1 Analytics Implementation Operations Incident Management Problem Management... Test & Diagnosis Assurance Visualization Flexible View Presentation Configuration Data Orientation Analytic Notebooks 7 1. Data Collection and Analytics find a novel situation for which there is no policy based resolution 2,3. Decision falls out to Operations for human investigation 4,5,6. Operations applications including Incident and Problem Management, and Test and Diagnostics may be used by teams to address both incident resolution and root cause analysis 7. Visualization supports current and historical views and collaborative problem solving 8. Design Systems receives updates to policy/analytics Then Orchestration responds to future similar events in an autonomic way based on new policy/historical resolution details 2017 TM Forum 14

15 Achieving an Open Ecosystem Co-ordinated knowledge plane distribution supporting control plane interaction Design Systems Adaptation Domain 1 Future OSS Fulfillment Assurance Cloud / PaaS Orchestration Support Systems Control Plane Knowledge Plane Orchestration of multi domain environment, between & within CSPs: Hierarchy of closed/open loops with delegation Intent based processes Co-ordinated distribution of the knowledge plane via Resource Management Service Management Domain 2 Legacy OSS Fault Management Domain 3 Future OSS Design Systems Fulfillment Assurance Orchestration Open APIs Data federation Common Event Bus Interface Management Adaptation Support Systems Cloud / PaaS The Knowledge Plane is formed by the Support Systems: federated Catalogue, Inventory, Policy and cognitive data 2017 TM Forum 15

16 Content 1 Orange Strategy and Expectations 2 Future OSS Concepts and Architecture 3 Take Away and Benefits 2017 TM Forum 16

17 Future OSS in a Nutshell 1. Common Digital Platform for Hybrid Networks and Services 2. Framework Architecture to Enable AGILITY in Digital Operations Transformation FULFILLMENT Transforming business requests into agile and cost effective solutions DESIGN SYSTEMS Enabling DevOps & DesignOps through Model-Driven Design SUPPORT SYSTEMS The bridge supporting hybrid end-to-end Service Design (Think, Build) and Service Operations (Run) ASSURANCE Assuring Service Quality through a combination of manual and automated operations ORCHESTRATION The Automation and Autonomics Engine of hybrid end-to-end Service Management CLOUD / PaaS Providing a Cloud-native, Dynamic, Secured, Open and Extensible OSS environment 2017 TM Forum 17

Future OSS key Concepts Provides a blueprint from which CSPs can begin their digital operations transformation Enables agility by creating an operating model for CSPs with intelligent and progressive

18 Future OSS key Concepts Provides a blueprint from which CSPs can begin their digital operations transformation Enables agility by creating an operating model for CSPs with intelligent and progressive operational automation, self-management, and selfconfiguration Provides a holistic approach that defines the management of hybrid networks (virtual, physical and legacy) Is a truly cloud-native and resilient platform to achieve OSS-as-a-Service 2017 TM Forum 18

19 Future OSS White Paper Take Away - Orange From NetOps to DesignOps Operations will focus on closing loops with DesignOps utilizing the Future OSS Design Systems. Network Operations Teams need to develop new skills with the ability and appropriate model-driven tools to work on design. Implementation path Future OSS provides flexible paths for its own introduction. To protect existing investments, Future OSS allows current systems (e.g. Inventory, etc.) to be incorporated through federation TM Forum 19

Orange believe ONAP is a good example of an implementation of part of the Future OSS for SDN/NFV

20 Future OSS Benefits - Orange For Orange, the Future OSS acts as a standardized framework that can be adopted by the whole industry, including CSPs and Open Source communities. Orange believe ONAP is a good example of an implementation of part of the Future OSS for SDN/NFV /oss/orangehuaweifutureosswhitepaperfinal.pdf 2017 TM Forum 20

21 Thank You Copyright Orange S.A. and Huawei Technologies Co., Ltd. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Orange S.A. and Huawei Technologies Co., Ltd TM Forum 21

Executive Summary. Providing the AGILITY to support digital operations transformation of hybrid networks

Executive Summary. Providing the AGILITY to support digital operations transformation of hybrid networks 1 2 3 Executive Summary Providing the AGILITY to support digital operations transformation of hybrid networks Advances in technology and competition from agile Over-The-Top (OTT) players means that Communication