The OPNFV collaborative development project has now delivered its second release, Brahmaputra. While the project continuous to grow, some confusion remains around what it is that the OPNFV community actually does. This session outlines and discusses the objectives and activities of the OPNFV community, the key values this provides to the industry and importantly activities the community avoids. In the context of the activity and challenges faced during Brahmaputra, as the community worked to integrate 38 parallel projects for the release, the session outlines the intentions activities and outcomes of this work; hard lessons learnt, achievements and future plans. The session was given at ONS 2016.

1. “What is OPNFV?”
“What does it deliver?”
Frank Brockners
Distinguished Engineer, Cisco
Chris Price
OpenSource strategist, Ericsson

2. Assembling a Platform for NFV
Enhancements
Additions

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

4. There is a selection of
components and features to
choose from.
> Compose “Scenarios”

5. Scenario: “Deployment of a
set of components and their
configuration”
Key Release Vehicle for OPNFV

6. VM control
Store Images
(VNFs)
Identity
Services /AAA
Message Bus
Cluster
Comms
HA &
Loadbalance
Portal
Network
Control
Hypervisor
Virtual
Forwarder
Virtual disks
(block storage)
Data-Base
OrchestrationObject store
Telemetry
Unit Test
System Test
Performance
InstallerVM control
Store Images
(VNFs)
Identity
Services /AAA
Message Bus
Cluster
Comms
HA &
Loadbalance
Portal
Network
Control
Hypervisor
Virtual
Forwarder
Virtual disks
(block storage)
Data-Base
OrchestrationObject store
Telemetry
Unit Test
System Test
Performance
Installer
Different Implementations of Components & Features
Compute Storage OperationsInfraNetwork Test
VM control
Store Images
(VNFs)
Identity
Services /AAA
Message Bus
Cluster
Comms
HA &
Loadbalance
Portal
Network
Control
Hypervisor
Virtual
Forwarder
Virtual disks
(block storage)
Data-Base
OrchestrationObject store
Telemetry
Unit Test
System Test
Performance
Installer
Deployment

7. Arno Release: Initial composition of 2 base scenarios
Fixed Set of Hardware Fixed Set of Components
Set of Tools
(some choice)
6 Servers
>= 3 Control nodes, >= 2
Compute nodes, 1 Provisioning
node (“jumphost”) (Centos 7, runs
test infra and installer VM)
Reference lab hosted by
the Linux Foundation
Blade servers with 80G
connectivity each (Cisco UCS-B),
CIMC management
Test
Tempest, Rally, Robot
Install
Options:
• Fuel
• Foreman/Quickstack
2 deployment scenarios
Compute
O/S Nova, KVM
Storage
O/S Glance, O/S Cinder
Network
OpenDaylight, OVS
Infra
RabbitMQ, Corosync, Pacemaker,
MySQL
See also: https://wiki.opnfv.org/get_started/get_started_system_state

8. OPNFV Deployment Scenario - Evolution
Compositions of components and their configuration
Apex
O/S – ODL
Baremetal
Fuel Compass JOID
O/S – ODL
Baremetal
O/S – ODL
VM
O/S – ODL
VM
O/S – ODL – L3
Baremetal
O/S – ODL – L3
Baremetal
O/S – ONOS
Baremetal
O/S – ONOS
Baremetal
O/S – ODL
Baremetal
O/S – ODL
Baremetal
O/S – OpenContrail
Baremetal
O/S – ODL – SFC
Baremetal
O/S – ODL – BGPVPN
Baremetal
O/S – OpenContrail
Baremetal
O/S – OpenContrail
Baremetal
O/S – ONOS
Baremetal
O/S – ONOS
Baremetal
Arno
Arno SR1
Brahmaputra
Note: Not all scenarios shown. For an up to date view on scenarios see https://build.opnfv.org/ci/view/OPNFV%20Platform%20CI%20-%20Alternative%20View/
20+ deployment scenarios

9. Brahmaputra makes scenarios available in phases
• Brahmaputra release is
phased (not all scenarios
available day 1)
• Scenarios released once they
become available
– Brahmaputra1: Feb/25
– Brahmaputra2: End of March
– Brahmaputra3: End of April
Scenarios in Brahmaputra1

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

11. Components evolve.
Systems follow.
> Iterate.

12. Install on
reference
system(s)
Test on
reference system(s)
Lab1
Lab2
Lab3
Lab1
Lab2
Lab3
Integrate & build*
as a system
*OPNFV currently composes builts from
existing artifacts (e.g. RPMs) rather
than builds from source
Choice of existing and new components,
System state definition

13. Missing
Features/Components?
> Create.

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

15. OPNFV is Up-Stream...
Create

16. ... and OPNFV is Down-Stream
Compose.Deploy.Test.

17. Up-stream + Down-stream: Mid-Stream
Compose.Deploy.Test.
Create

18. OPNFV is a Mid-Stream Project
> Rapid Feedback for Developers.

19. OPNFV focuses on
rapid feedback for developers
> OPNFV is less suited as an
end-user base installation.
> OPNFV isn’t a “product”

20. OPNFV is MANY Scenarios,
including YOURS!
> There is no one single OPNFV,
there are multiple.
> OPNFV isn’t a reference
system.

21. OPNFV is all NFV!
> Create.
> Compose.
> Deploy.Test.
> Iterate.

22. 16/03/2016

23. Brahmaputra (March 1, 2016)
• End-to-end NFV feature realization at System Level
• Massively Parallel Simultaneous Release Process
– 35 projects, 140+ developers
– Incremental monthly release drops
– Up from 2 to to 20+ deployment scenarios
• Significant increase in components tested and
component/feature/deployment environment combinations
• Advancements in infrastructure, processes, and upstream
collaboration

24. Network Virtualization
Control
Storage Virtualization
Control
OPNFV Brahmaputra Overview
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

25. Testing Enhancements
• Fivefold increase in testing projects
• Functest: component testing, increase in number
and types of tests
• Yardstick: System level testing based on ETSI TST
001 spec
• VSPerf: virtual switch characterization
• Qtip: Bottom-up system characterization
• Bottlenecks: bottleneck focused platform testing
framework
Yardstick
FuncTest
Qtip
VSPERF
Bottleneck
s

26. Increased Breadth in Deployment and Integration
• Breadth of Open Source Innovation
• Additional install/deploy tools
• OpenStack
• Additional SDN Controllers + native Neutron
networking
• 2, 4, -> 20+ scenarios supported
– Installer, SDN, bare metal vs. virtualized, HA,
features, framework options
Apex
Fuel
Compass
JOID
Genesis
ONOSFW
Contrail

27. Infrastructure and Testing Environments
• Advances in Pharos governance and
participation
– Pharos labs participating in release activities +
development
– First ARM-based lab joined Pharos
• Significant automation work on Jenkins-based
CI/CD toolchain
• Additional documentation and documentation
automation
Releng
Docs
Octopus
Pharos

28. Carrier Grade Feature Enhancements
• Significant Upstream Collaboration
• Fault Management
• SFC
• L3VPN
• IPv6
• Resource Reservation
• Performance Enhancements throughout
the platform (Data plane, KVM, OVS)
SWFPQM
Promise
Doctor
Availability
IPv6
SFC
OVS4NFV
SDNVPN
NFVKVM
DPACC

29. Collaborative Development Working Upstream
• OPNFV Requirements Gathering and Gap
Analysis
• Upstream and/or OPNFV Code Development
• New releases of Upstream Components
Available
• OPNFV Integration, Validation, and
Automation work
– Install/Deploy
– CI/CD and scenario definitions
– Testing (Functional, System, Performance)

30. Pharos Project
Goals:
• Facilitate collaborative testing
• Provide developers with substantial
resources
• Ensure OPNFV applicability across
architectures, environments and
vendors
• Create more robust, interoperable
releases

31. OPNFV by the numbers: 18 Months In
• 58 members (41 at founding)
• 12 end user member companies
• 10 operational OPNFV test-bed
infrastructure labs (Pharos Project) with 2
more planned
• 47 approved projects
• 168 code developers
• 161 code submitters
• 4,697 accepted code contributions
• 205 ticket participants
• 665+ IRC participants
• 87,998+ IRC messages
• 406 Mailing List Participants
• 5800+ unique Arno Downloads
• 5000+ unique Arno Docs downloads
• 5x increase in developer participation since
August 2015
• 2 Platform releases (Arno, Brahmaputra) +
1 stable release (Arno SR1)

32. Create.Compose.Deploy.Test.
Interate.

33. Thank you