opnfv: overview and approach to upstream integration

OPNFV: Overview and Approach to Upstream Integration

Heather KirkseyDirector, OPNFV

The networking industry is in transformation

Why NFV?

Converged 4G LTE Fixed Mobile Arch

Meanwhile the world was changing….

Rise of Open SourceVirtualization

CloudSoftware Defined

Networking

ETSI Architectural Framework

Why OPNFV?

We Need To Work Together

What is OPNFV?

OPNFV is a carrier-grade, integrated, open source platform to accelerate the introduction of new NFV products and services.

OPNFV Project Goals

• Develop and test an integrated open source platform

• Include participation of end users• Contribute to and participate in relevant

open source projects• Establish an ecosystem for NFV solutions

Governance

• A Business (Board) and Technical (TSC) governance structure separates business decisions from meritocratic, technical decisions

Financial oversight Oversight of all marketing: web, PR/AR, branding, etc.

Policy oversight

Projects drive code development, testing, integration and reference platform releases

TSC sets technical direction for the overall Project

Board sets business direction and scope for the Project

Certification and complianceoversight

Strategic direction oversight

OPNFV Membership ListPlatinum Members

Associate Members

Silver Members

OPNFV Platform Overview

Orchestration and Management

Virtual Network Functions

Infrastructure

Compute Virtualization

Control

Storage Virtualization

Control

Network Virtualization

Control

Compute Storage Network

Integration Testing New Features

Upstream Project

Collaboration Continuous Integration / Continuous Deployment

Documentation

How does OPNFV Work?

“Systems integration as an open community

effort.”

Scenario: “Deployment of a set of components and their configuration”

> Compose. Deploy. Test. Iterate.

OPNFV Composes Scenarios

Integrate and Evolve Upstream in lock-step

Hardware

Network Control

Operating Systems, virt. Infra

VIM Management System

Orchestration

Application Layer / App Server

IO Abstraction & Feature Path

Integrate/Install

Network Data Analytics

System Test & Security Audit

Infra control & CI/CD(Pharos, Releng, Octopus)

Installation, Upgrade(Apex, Joid, Fuel, Compass, Daisy,Escalator, Genesis)

Documentation(OPNFVdocs)

Create Scenarios/Stacks(IPv6, FastDataStacks, Armband, Apex, Daisy,ONOSFW, OpenContrail,, Joid, Fuel, Compass)

Storage Performance Test(Storperf)

System Testing(Yardstick, FuncTest, Qtip)

Dataplane Performance Test(Vsperf, Fastpath)

SDN Controller Performance Test(Cperf)

Dataplane Evolution & Test(DPACC, OVSDPDK, FastDataStacks)

Hypervisor for NFV(KVM4NFV)

Network Policy(FastDataStacks, Copper, PolicyTest)

Fault Management/Localization, Audit(Doctor, Pinpoint, Prediction, Bottlenecks, Inspector)

Model and Policy Driven Control(Copper, Movie, Models, Domino, Parser)

Resource Control/Scheduling(Promise, Resource Scheduler (RS))

NFV services (service chaining, VPN, ..)(VNFFG, SFC, SDNVPN)

NFV deployment architectures(Multi-Site, EdgeNFV)

Security(Moon)

NFV Telemetry Data Acquisition(VNF Event Stream)

A scenario is a system of multiple upstream components.

> Compose. Deploy.

Network Virtualization Control

Storage Virtualization Control

OPNFV Brahmaputra Release Stack

Compute Virtualization

Control

Orchestration and Management

Virtual Network Functions

OpenStack

KVM OpenDaylight

OVS

OpenContrail

Compute Storage Network

InfrastructurePharos Community Labs

OPNFV Bare Metal Lab

Data Plane Acceleration

Upstream Project

Collaboration:

Integration Testing New Features

ONOS

Ceph

ODPDPDK

Alignment

Installers

Scenarios

Functional

System

Performance

Fault Mgmt

IPv6

SFC

L3VPN

Reservation

Continuous Integration / Continuous Deployment

Documentation

A scenario is a system.Does it work?

> Test.

OPNFV Testing Approaches• Functional:

• Functest: base system functionality, component testing, VIM

• Performance/System: • Yardstick: End to end system level based on ETSI TST001• Bottlenecks: Verify OPNFV boundaries in staging before bringing VNFs• StorPerf: Storage performance for any VNF• VSPerf: Virtual Switch characterization • CPerf: Controller performance• PolicyTest: Policy testing • QTip: Bare metal focus (compute, network, storage)

• For discussion of testing ecosystem, see: https://wiki.opnfv.org/display/functest/Testing

Functional Testing: Project FuncTestA: ODL suite

Robot framework, ODL functional testing

B: ONOS suiteTestON framework

B: vIMSOpenSource solution by Clearwater

B: PromiseResource reservation and management project

B: DoctorFault management and maintenance project

B: BGPVPNOpenStack Neutron BGPVPN project integration

A: vPing SSHVerify private & public connectivity

A: vPing userdataVerify nova-metadata service and private connectivity

A: Tempest test OpenStack native tests (200+ tests)

A: Rally bench testsBenchmark the OpenStack deployment

Brahmaputra Additions

Brahmaputra Additions

FuncTest Results Database / Dashboardhttp://testresults.opnfv.org/kibana_dashboards/

24Credentials: opnfvuser/kibana

Example testing activity in OPNFV:System-Level testing: Project YardStick

Pre-Deployment validation of NFVI

Control plane/User planeMain componentsReal time constraintsHardware Metrics

Test cases 1 … NTest stimuliTest environment

ETSI GSNFV-TST001Chapter 6Pre-Deployment validationof NFV infrastructure

- System under Test (SUT)

- Deployment rules

- Execute benchmarks

- Trigger External scriptsfor SUT disturbances

- Collect results- Graphical

results- Assertion

- Generate template or

- External templates

YardStick Test-Framework

YardStick Test Suite

YardStick Results Database / Dashboardhttp://testresults.opnfv.org/grafana/

27

Missing Features/Components?

> Create

Building/evolving features means contributing upstream.Team Up To Drive Required Change Upstream

Swimming upstreamis hard

Team-up to increasethe likelihood to succeed

Swimming upstreamis dangerous

Feature Development Example: OPNFV Doctor Project – Fault Management“Doctor” creates a fault management and maintenance framework

See also: https://wiki.opnfv.org/display/doctor

Project Blueprint StatusCeilometer Event Alarm Evaluator Completed

(Liberty)

Nova

New nova API call to mark nova-compute down

Completed (Liberty)

Support forcing service down

Completed (Liberty)

Get valid server state Completed(Mitaka)

Add notification for service status change

Completed(Mitaka)

Feature Evolution Example: OPNFV SFC Project• Objective: Verify ODL SFC in

system level deployments• Brahmaputra Yardstick tests:

• TC029: VM Creation• Verify that only 2 Service Function

VMs are created for Service Chains Chain1 and Chain2

• TC030: Block HTTP• Verify that Client1 can not do

HTTP traffic, but can do SSH traffic• TC031: Block SSH

• Verify that Client2 can not do SSH traffic, but can do HTTP traffic

See also: https://wiki.opnfv.org/display/sfc

Components evolve. Systems follow.

> Iterate.

System Level CI/CD:OPNFV Octopus and Releng Projects

Install on reference system(s)

Test on reference system(s)

Lab1 Lab2 Lab3

Lab1 Lab2

Lab3

Integrate & build*

as a system

Choice of existing and new components,System state definition

Pharos ProjectGoals:•Facilitate collaborative testing•Provide developers with substantial resources•Ensure OPNFV applicability across architectures, environments and vendors•Create more robust, interoperable releases https://www.opnfv.org/developers/pharos

https://wiki.opnfv.org/display/pharos/Pharos+Home

Arno (June 4, 2015)

• First OPNFV Release• Nine Months after project launch

23-05-02

What’s next?

38

COLORADO

Come Join the Party

Get Involved

• OPNFV: https://www.opnfv.org/• OPNFV wiki: https://wiki.opnfv.org/ • OPNFV Brahmaputra release:

https://www.opnfv.org/brahmaputra• OPNFV stats:

http://projects.bitergia.com/opnfv/browser/

• Mailing lists:– opnfv-tech-discuss@lists.opnfv.org– opnfv-users@lists.opnfv.org

Questions?