The OPNFV project—a common integration and testing platform to facilitate NFV deployments that defines a consistent, functional stack—differs from more traditional code-based open source projects in that its work is focused upstream. Rather than re-event many wheels, the project leverages a variety of existing code bases from leading open source projects across compute, storage, and networking and fills gaps where needed to meet strict carrier-grade end user requirements. This approach is difficult and requires an extremely complicated set of requirements, but the result is a much needed common, de facto platform for the industry to test and build NFV products and services. OPNFV director Heather Kirksey spoke during LinuxCon North America 2016 on why the community chose to take this integrated approach, what’s been successful, and key lessons learned from this unique project.

1. OPNFV: Overview and
Approach to Upstream
Integration
Heather Kirksey
Director, OPNFV

2. The networking industry is in
transformation

3. Why NFV?

4. Converged 4G LTE Fixed Mobile Arch

5. Meanwhile the world was changing….
Rise of Open Source
Virtualization
Cloud
Software Defined
Networking
Rise of Open Source
Virtualization
Cloud
Software Defined
Networking

6. ETSI Architectural Framework

7. Why OPNFV?

8. We Need To Work Together

9. What is OPNFV?

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

11. 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

12. 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
compliance
oversight
Strategic
direction
oversight

13. OPNFV Membership List
Platinum Members
Associate Members
Silver Members

14. 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

15. How does OPNFV
Work?

16. “Systems integration as
an open community
effort.”

17. Scenario:
“Deployment of a set of
components and their
configuration”
> Compose. Deploy. Test. Iterate.
OPNFV Composes Scenarios

18. Integrate and Evolve Upstream in lock-step
HardwareHardware
Network ControlNetwork Control
Operating Systems, virt. InfraOperating Systems, virt. Infra
VIM Management SystemVIM Management System
OrchestrationOrchestration
Application Layer / App ServerApplication Layer / App Server
IO Abstraction & Feature PathIO Abstraction & Feature Path
Integrate/InstallIntegrate/Install
Network Data AnalyticsNetwork Data Analytics
System Test & Security AuditSystem 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)

19. A scenario is a system
of multiple upstream
components.
> Compose. Deploy.

20. 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
Infrastructure
Pharos 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

21. A scenario is a system.
Does it work?
> Test.

22. 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

23. Functional Testing: Project FuncTest
A: ODL suite
Robot framework, ODL
functional testing
B: ONOS suite
TestON framework
B: vIMS
OpenSource solution by
Clearwater
B: Promise
Resource reservation and
management project
B: Doctor
Fault management and
maintenance project
B: BGPVPN
OpenStack
Neutron BGPVPN project
integration
A: vPing SSH
Verify private & public
connectivity
A: vPing userdata
Verify nova-metadata
service and private
connectivity
A: Tempest test
OpenStack native tests
(200+ tests)
A: Rally bench tests
Benchmark the OpenStack
deployment
Brahmaputra Additions
Brahmaputra Additions

24. FuncTest Results Database / Dashboard
http://testresults.opnfv.org/kibana_dashboards/
24Credentials: opnfvuser/kibana

25. Example testing activity in OPNFV:
System-Level testing: Project YardStick
Pre-Deployment
validation of NFVI
Control plane/User plane
Main components
Real time constraints
Hardware
Metrics
Test cases 1 … N
Test stimuli
Test environment
ETSI GS
NFV-TST001
Chapter 6
Pre-Deployment
validation
of NFV
infrastructure
- System under Test
(SUT)
- Deployment rules
- Execute benchmarks
- Trigger External
scripts
for SUT disturbances
- Collect results
- Graphical
results
- Assertion
- Generate template
or
- External templates
YardStick Test-Framework

26. YardStick Test Suite

27. YardStick Results Database / Dashboard
http://testresults.opnfv.org/grafana/
27

28. Missing
Features/Components
?
> Create

30. Building/evolving features means contributing upstream.
Team Up To Drive Required Change Upstream
Swimming upstream
is hard
Team-up to increase
the likelihood to succeed
Swimming upstream
is dangerous

31. 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 Status
Ceilometer 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)

32. 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

33. Components evolve.
Systems follow.
> Iterate.

34. 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

35. Pharos Project
Goals:
•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

36. Arno (June 4, 2015)
• First OPNFV Release
• Nine Months after project launch

37. 08/24/16

38. What’s next?
38
COLORADO

39. Come
Join the
Party

40. 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

41. Questions?