ONAP SD-WAN Proposal Use Case v0.9

ONAP SD-WAN Use Case Proposal

 Architecture Basic UC: • •

ZTP. VPN connectivity over WAN1 interfaces (Edge1-VL-Edge2)

OSS/BSS Applications

SD-WAN Orchestrator 

SD-WAN Controller 

WAN 1

ISP1

Next UC: 2. Acti Active ve/S /Sta tand ndby by 3. Activ ctive e/Activ ctive e 4. Star Star Topol opolog ogy y 5. Full Full-M -Mes esh h Topol opolog ogy y 6. On-S On-Site ite SFC: SFC: FW FW and and NA NAT 7. On-Cloud On-Cloud SFC: DPI and Applicatio Application-aw n-aware are routing routing 8. WAN Opti Optimi miza zati tion on

WAN 1

vBG pBG

vBG WAN 2

SD-WAN Edge 1

ISP2

WAN 2

pBG

SD-WAN Edge 2

Flow Diagram

1) ZTP 2) Configuration Management

SD-WAN Proposal to ONAP

Scope • Name of Use Case: SD-WAN Use Case • Use Case Authors: Netcracker  • Description • Users and Benefit • Use Case Flows • Virtual Network Function: [TDB] • ONAP Flows: [TDB] • Project Impact: [TDB]

Description • SD-WAN is an emerging technology for Large Enterprises with highly distributed locations, where each location can have one or several connections to internet from different Network Inf rastructure Providers with Bes Effort quality, rather then expensive MPLS, Dedicated Optical lines or Satellite services. • SD-WAN currently under standardization in different SDOs, like MEF, ONF, BBF, but several vendors already exist on the market, offering proprietary SD-WAN solutions. • To be Open, ONAP SD-WAN Use Case will refer to following standards: -

MEF LSO API, SD-WAN Use Cases

-

BBF: WT-328

-

IETF: draft-ietf-netconf-zerotouch

• ONAP SD-WAN Use Case will be divided on series of Sud-Use Cases ranged by complexity, providing more and more capabilities and features for every next Sud-Use Case, based on top the previous: 1.

Basic VPN connectivity between two Locations (vBNG1-VL-vBNG2)

2.

A ct iv e/ St an dby

3.

Active/Active

4.

Star Topolog y

5.

Full-Mesh Topology

6.

On-Site SFC: FW and NAT

7.

On-Cloud SFC: DPI and Application-aware routing

8.

W AN O pt im iz at io n

Users and Benefit: • From the user perspective, SD-WAN solution is an overlay technology, which allow refuse expensive dedicated MPLS lines from Network Providers.

• From the Network Providers perspective, SD-WAN is a solution to be not just a “pipe” for OTT providers, but also take role of “Network Service Provider” and chance to earn money on additional services for the Customers.

• From the ONAP perspective, SD-WAN Use Case is demonstrate Orchestration capabilities for Distributed VNFs, Configuration Management, Policy Enforcement for Overlay Traffic, Standard ZTP and APIs.

Use Case Flows: • SubuseCase#1: Architecture 1.

Before initial VPN service will be provided, ONAP will demonstrate initial device configuration (ZTP, Zero Touch Provisioning), based on a https://datatracker.ietf.org/doc/html/draft-ietf-netconf-zerotouch .

2.

Configuration Management on the Edges as a simplest scenario for VPN Service creation.

Manufacturer Redirect Server

OSS/BSS Applications

SD-WAN Orchestrator 

Specified Bootstrap Server

SD-WAN Controller 

vBG pBG

SD-WAN Edge 1

vBG WAN 1

ISP1

WAN 1

pBG

SD-WAN Edge 2

Use Case Flows (2/4) • SubuseCase#1: ZTP Flow Diagram • Preconditions steps described in Draft, Chapter 6.1 and 6.2 • “Power” button is on. See Draft, Chapter 6.3: 1.

Upon power being applied, the device's bootstrapping logic first checks to see if it is running in its factory default state. If it is in a modified state, then the bootstrapping logic exits and none of the following interactions occur.

2.

For each source of bootstrapping data the device supports, preferably in order of closeness to the device (e.g., removable storage before Internet based servers), the device checks to see if there is any bootstrapping data for it there.

3.

If onboarding information is found, the device initializes itself accordingly (e.g., installing a boot-image and committing an initial configuration). If the source is a bootstrap server, and the bootstrap server can be trusted (i.e., TLS-level authentication), the device also sends progress notifications to the bootstrap server.

4.

Otherwise, if redirect information is found, the device iterates through the list of specified bootstrap servers, checking to see if there is any bootstrapping data for it on them. If the bootstrap server returns more redirect information, then the device processes it recursively. Otherwise, if the bootstrap server returns onboarding information, the device processes it following the description provided in (3) above.

5.

After having tried all supported sources of bootstrapping data, the device MAY retry again all the sources and/or provide manageability interfaces for manual configuration (e.g., CLI, HTTP, NETCONF, etc.). If manual configuration is allowed, and such configuration is provided, the device MUST immediately cease trying t o obtain bootstrapping data, as it would then no longer be in running its factory default configuration.

Use Case Flows (3/4) • SubuseCase#1: Configuration Management Flow Diagram OSS/BSS Applications

User

{Login}

SD-WAN Orchestrator

SD-WAN Controller

Edge1

{Get Service Instance}

{Display Landing Page} {Add Branch to VPN} {Update Service Instance} {In Progress Response} {Display Information Message} {Create Config} {Deploy Config}

{Response} {Response}

{Response}

{Apply Config} {Response}

Use Case Flows (1/4) • SubuseCase#1: ZTP Flow Diagram - ZTP (https://datatracker.ietf.org/doc/html/draft-ietf-netconf-zerotouch) - Precondition: Device Owner complete purchasing, installation and press “power” button. ManufacturerRedirect Server

OSS/BSS Applications

SpecifiedBootstrap Server

SD-WAN Controller

Edge1

{Request Redirect} {Response Redirect} {Notification Ready to be managed} {Request Bootstrap} {Response Bootstrap}

{Request Redirect} {Response Redirect} {Notification Ready to be managed}

{Request Bootstrap} {Response Bootstrap}

Edge2

Virtual Network Function • [TDB] VNF vBG1 vBG2 Manufacturer Redirect Server Specified Bootstrap Server

PNF pBG1 pBG2

ONAP Flows: Based on experience with previous Use Cases, we can assume this ONAP Flows should cover: 1. Service Onboarding 2. Infrastructure Service Instantiation 3. Edge Service Instantiation 1. PNF Configuration: ZTP 2. VNF Configuration: vBG Instantiation

What we plan to achieve in ONAP R2 • Orchestration of SD-WAN Infrastructure Service – ZTP Server Capabilities - Manufacturer Redirect Server - Specified Bootstrap Server 

• Orchestration of SD-WAN Edge Service for a customer - Onboarding and Instantiation of vBG VNF at Edge NFVI through an Openstack VIM - Customer Edge boot-up with standard Zero Touch Provisioning (ZTP) - Provisioning of Overlay network across Edges with single WAN link - Connectivity across hosts connected behind Edges Note: “SD-WAN Orchestration” better to implement on “SD -WAN Controller” level, as pruned ONAP instance, specified exactly for vBG LCM. Such “SD -WAN MANO” add complexity for ONAP, but will close to reality. (Need discussion)

Note : Underlay connectivity across edges will be reused from Enterprise vCPE use case

Use Case Flows: Simplified View for ONAP R2 Initial Boot-Up Sequence for ZTP Flow SD-WAN Management

OSS/BSS OSS/BSS Applications Applications

NFVI Infrastructure Management ZTP Infrastructure Service Bring up

1 VIM

ONAP

ONAP

1. 2.

ZTP Server Manufacturer Redirect Server

VIM

3.

SD-WAN Controller 

Specified Bootstrap Server

3

5

4. 5. 6.

6

2

ZTP Infrastructure bring up SD-WAN Edge Boot-up and associated ZTP Server interactions PNF and Underlay Configuration by SD-WAN Controller VNF bring up at Edges VNF Configuration by SD-WAN Controller Configuration of WAN interfaces by SD-WAN Controller

2 4

Host 1

vBG pBG

SD-WAN Edge 1

vBG WAN 1

ISP1

WAN 1

Host 2

pBG

• •

SD-WAN Edge 2

•

The key difference between E-vCPE and SD-WAN use case is the placement of vBG. In SD-WAN use case

pBG is a hosting PNF  – For R2 we have a single vBG VNF hosted on pBG WAN connection is assumed to be available across edges and the scope for R2 is limited to configuring underlay at Edges It is assumed that underlay configuration for WAN is carried out through E-vCPE use case

SD-WAN Use Case : Service Onboarding

SD-WAN Use Case : Infrastructure Service Instantiation

SD-WAN Use Case : Edge Service Instantiation

Project Impact: Candidates Components for SD-WAN implementation SD-WAN Orchestrator Management Plane

   r    o     f    s    e    i    t    i     l    a   e    n   s    a    c    o    i    t    e    c    s    n   u    u   N     f    t    A    n   W    e      m   D    e   S    g    g    a   n    n   i    z    a    l    i    m   a     d   e    e   r    t    c    e    p    x    E

Accounting Management

vAAA VNF from R-vCPE

Fault Management

DCAE

Performance Management

DCAE

Configuration Management

SDNC with NetConf Plugin

Provisioning

Using external ZTP VNF

ZTP

VNFM

VF-C or App-C

VIM

OpenStack

    d    e    z    i     l    a    e    r    e    r    a    s    e    i    t    i     l    a    n    o    i    t    c    n    u     f    e    s    e     h    t    w    o    H

As we can see here, SD-WAN Management Plane can be covered mostly by ONAP existing components as external instances. But, SD-WAN Control Plane looking for Opensource or Vendor specific components, which is point for discussion. As well as vBG Implementation. CPE VNF (vBG)

vRouter FlexVNF, Vyatta?

Hypervisor

KVM, ESXI ?

REST

   c    i     f    i    c    N   r    e    e     l    A    l    p    s    W   o    r    r   -    t    o    n    o     d   D    S    n    C    e    V

Netconf 

SD-WAN Controller Control Plane MP-BGP Rout Reflector

Quagga?

NFVI

ZTP can be as VNF, and also looking for Development.

Project Impact: Interface appearance

SD-WAN Service Orchestration

Fault and Performance Management

ZTP Server

Provisioning

SD-WAN Orchestrator and Controller

SD-WAN VIM

SD-WAN Specific-VNFM

ONAP Project Impact 1.

9 7 6

1

2

5 10

8

3

4

SD-WAN Fault and Performance Monitoring  – Collection, Analytics , Integration with ZTP for receiving discovery notification 2. SD-WAN specific service workflow execution (infrastructure and customer specific) 3. SD-WAN CPE, Overlay Configuration based on Directed Graph actions 4. Adaptors for SD-WAN S-VNFM and interaction for deployment of vBG on CPE directly to S-VNFM or via Multi-VIM 5. Policy for handling the notifications related to ZTP or alarms/statistics events 6. Inventory model for SD-WAN Service and vBG/vPG as well as infrastructure resources. 7. VID updates for SD-WAN infrastructure deployment 8. Additional custom types as required for modelling SD-WAN Services and associated Resources 9. SD-WAN Use case specific portal enhancements 10. SD-WAN VIM Specific Adaptation / Plugins

R-vCPE Use Case

Harmonization R-vCPE/E-vCPE/SD-WAN use cases harmonization. ONAP Managed entities: ONAP E-vCPE Use Case vAAA LAN

BRG1

   E    P    C    v      R

vDHCP

vBNG

LAN

vG_MUX

vG vG

BRG2 Web Server

   E    P    C    v      E

LAN

pBG

FW

vBG IPRAN

vAAA

MPLS

vDHCP

   N    A    W      D    S

LAN

vBG pBG

Customer Premises

vBG pBG

Access Network

Edge Cloud

Backbone Network

Core Cloud

Internet

SD-WAN Use Case LAN

Customer Premises

s

Thanks