Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Golden Configuration Catalyst 2018: Verizon, Infosys, Nuviso Networks

Download as pdf or txt
Download as pdf or txt
You are on page 1of 19

Golden

Configuration
Catalyst 2018
Verizon, Infosys, Nuviso Networks

© 2018 TM Forum | 1
Contributors

• Champion – Verizon Communications

• System Integrator – Infosys Limited

• Configuration Management Solution – Nuviso Networks

© 2018 TM Forum | 2
NFV Operational Characteristics
Dynamism - Virtualization aids on-demand changes, operation becomes more dynamic

Agility – Virtualization of Network Functions (vFW, vLB, vEPC, etc) - increases agility

Failure prevention – Address higher risks for triggering catastrophic failures

State Maintenance - Maintain network state – explosion of new variables


Scope of
this Catalyst
Auto healing – Need workflows to quickly restore network to last-known-good-state

© 2018 TM Forum | 3
NFV Challenges
Expanded Impact of Failures

Complex Root Cause Analysis

Lack of Standards

New Life Cycle Stages


© 2018 TM Forum | 4
Problem Statement and Requirements
Operator Concerns Expected Solution Capabilities
How do I configure a Network Service • NFVO should support features to perform Day0,
and baseline the config? Day1 configuration
• NFVO should invoke centralized config manager
API to trigger Day2 config based on templates

How to enable near real time • Change Notify Microservice within the VNF shall
configuration change updates & re- push the config changes to centralized
baseline the config? configuration manager in near real time

How to auto-heal the network service • NFVO shall re-instantiate the VNF and instruct
with right & latest base lined config manager to restore baseline configuration
configuration?

© 2018 TM Forum | 5
Key Drivers for the Catalyst
Key Driver Catalyst Solution
Lack of standardization in the config • Use a Config Management Solution that is built on
management space top of standards (TMF, IETF, OpenConfig)

Lack of scalability with centralized • Use a VNF based micro-service to report


config management systems incremental config changes
• Policy based orchestration directs automated
remediation leveraging config baselines

© 2018 TM Forum | 6
Golden Configuration – Key Building Blocks
NFV Orchestrator
Model-driven, Vendor-neutral
TM Forum Resource APIs Centralised Configuration Manager

Golden Config
data store

Virtualised Network Functions


with config microservice
© 2018 TM Forum | 7
Golden Configuration – Workflow
Model-driven, Vendor-neutral
NFV Orchestrator 2 POST:/api/resourceFunction Centralised Configuration Manager

1. Characteristic
2. Configuration
3
Rule Engine
4

7 Create Snapshot &


Mark Golden Cfg
1

Golden Config
data store

Direct Config Change to VNF 6 POST/api/resourceFunction/Notify


5
Virtualised Network Functions
with config microservice
© 2018 TM Forum | 8
TMF Assets used/enhanced (TR255-TMF664)
TR255A – Connectivity Patterns for Virtualization Management

TR255B –Requirements Specification for Resource Functions

TR255C – TOSCA Representation

Enhanced by
this Catalyst TMF664 – Resource Function Activation & Configuration API

TR262E – Context Management

Future scope for


this Catalyst TMF640 – Service Activation and Configuration API

© 2018 TM Forum | 9
APIs
TMF 664 Resource Configuration and Activation – R17.5.0
 Resource Function APIs (/api/resourceFunction) – Trigger Centralized Config Manager for VNF discovery &
pushing service level config.
✓ Proposed Enhancements to TMF 664 API:
1. API should support template based service configurations utilizing standard data models like YANG
2. VNF identifier (resource-id) to be present in all the APIs so as to allow the VNF microservice to identify the
resource function when notifying of changes. The same identifier used by other systems like the
orchestrator
 Resource Function Notification APIs (/api/resourceFunction/notify) – Trigger configuration changes notification
to Centralized configuration Manager
✓ Proposed Enhancements to TMF 664 API:
1. Configuration deltas to be captured as a part of the notification APIs. Further work may include using a
yang modelled abstraction of the data.
2. Resource Function Notification APIs should have a provision to notify whether config changes applied by
user on device should be considered as “Golden Config” or not. A Golden Config True/False field should be
added in API
3. Resource function API should have provision to supress the notification updates so that user can decide
whether to notify the changes or not

© 2018 TM Forum | 10
APIs (contd..)
TMF 664 Resource Configuration and Activation – R17.5.0

 Resource Function Heal APIs (/api/resourceFunction/heal) – This API is used via Orchestrator to trigger service
restoration lifecycle event to Centralized Configuration Manager to re-configure the VNF with stored golden config

✓ Proposed Enhancements to TMF 664 API:


1. VNF identifier (resource-id) to be present in all the APIs so as to allow the VNF microservice to identify the
resource function when notifying of changes. The same identifier used by other systems like the
orchestrator

© 2018 TM Forum | 11
POC Topology

Golden Config
data store

Golden Configuration Catalyst POD

LAN WAN Cloud LAN


Host-A VYOS CSR1000v Host-B

© 2018 TM Forum | 12
Demo
• Demo 1 - Service config & baseline the config in data store
• Instantiation of network service via OSM and push the day 0/day 1 configuration on VNFs
• OSM to invoke TMF 664 API to push day 2 configuration on VNF via Config Manager (resource creation API)
• Demo end-to-end traffic flow between two hosts
• Config Manager stores updates in golden configuration of VNF

• Demo 2 – Config change notify microservice


• Do manual configuration changes on VNF
• Change notify microservice in VNF triggers configuration change notification API (TMF 664 resource change
notification API)
• Config Manager saves the related configuration changes in golden configuration repository

• Demo 3 - Config restore during service outage scenario


• Manually induce fault in network service
• Trigger service restoration lifecycle event on OSM Orchestrator
• OSM re-instantiates & restores Day 0/1 configuration
• OSM Triggers Config Management API to restore last known golden configuration for the VNF (TMF 664 resource
heal API)
• Config manager restores configuration of VNF to activate end to end network service
• Demo end-to-end traffic flow between two hosts

© 2018 TM Forum | 13
Service Topology View on OSM

© 2018 TM Forum | 14
OSM Service primitives to Discover & Recover

© 2018 TM Forum | 15
Discovered VNFs on Config Manager

© 2018 TM Forum | 16
Golden Config in Config Manager

© 2018 TM Forum | 17
Config Delta triggered by Change Notify Microservice

© 2018 TM Forum | 18
Thanks!

© 2018 TM Forum | 22

You might also like