1. What is OPNFV? Frank Brockners, Cisco

2. June 20–23, 2016 | Berlin, Germany

3. > Create. > Compose. > Deploy. Test. > Iterate. OPNFV is open source NFV

4. OPNFV Platform Overview Orchestration and Management Virtual Network Functions Infrastructure Compute Virtualization Control Storage Virtualization Control Network Virtualization Control Compute StorageNetwork Integration TestingNew Features Upstream Project Collaboration Continuous Integration / Continuous Deployment Documentation

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

6. OPNFV is Up-Stream... Create

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

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

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

10. Assembling a Platform for NFV Enhancements Additions

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

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

13. Example testing activity in OPNFV: System-Level testing: Project YardStick 1. Define infrastructure2. Identify VNF-type3. Select Test Cases4. Execute Tests5. Collect Results 6. Integrate VNF application 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 NFV-TST001 Chapter 6 Pre-Deployment validation of NFV infrastructure ConfigureDeployTestValidate -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

14. Missing Features/Components? > Create

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

16. Feature Development Example: OPNFV Doctor Project – Fault Management “Doctor” creates a fault management and maintenance framework See also: https://wiki.opnfv.org/display/doctorhttps://wiki.opnfv.org/display/doctor ProjectBlueprintStatus CeilometerEvent 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)

17. Doctor Project: Solution Brief Contents Fault Management Overview NFVI Maintenance Milestones and Goals Upstream Contributions Available at https://www.opnfv.org/resourceshttps://www.opnfv.org/resources

18. Components evolve. Systems follow. > Iterate.

19. 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 System Level CI/CD: OPNFV Octopus and Releng Projects

20. Community Labs: OPNFV Pharos Project 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

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

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

23. Network Virtualization Control Storage Virtualization Control OPNFV Brahmaputra Overview Compute Virtualization Control Orchestration and Management Virtual Network Functions OpenStack KVM OpenDaylight OVS OpenContrail Compute StorageNetwork Infrastructure Pharos Community Labs OPNFV Bare Metal Lab Data Plane Acceleration Upstream Project Collaboration: Integration TestingNew Features ONOS Ceph ODP DPDK Alignment Installers Scenarios Functional System Performance Fault Mgmt IPv6 SFC L3VPN Reservation Continuous Integration / Continuous Deployment Documentation

24. What’s next? 24 COLORADO

25. Next Steps – OPNFV Colorado Maturing the Infrastructure – CI/CD system Lab reservation system “Any location” deployment Common configuration files (testing, installer config) Hardware x86 and ARM labs Feature Evolution Multi-Site, Policy New Scenarios Focused on NFV forwarding performance and flexible deployments 25

26. Members & Governance

27. OPNFV: An Open Community Open Governance Model Open Technical Decision Making Open Design Discussion Open Source License Open to all

28. OPNFV Members https://www.opnfv.org/about/memberslist

29. Governance Structure Board and TSC A Business (Board) and Technical (TSC) governance structure separates business decisions from meritocratic, technical decisions OPNFV Bylaws: https://www.opnfv.org/about/bylaws-and-policies/bylawshttps://www.opnfv.org/about/bylaws-and-policies/bylaws

30. Create.Compose.Deploy.Test. Iterate.

31. References OPNFV: https://www.opnfv.org/https://www.opnfv.org/ OPNFV wiki: https://wiki.opnfv.org/https://wiki.opnfv.org/ OPNFV Brahmaputra release: https://www.opnfv.org/brahmaputra https://www.opnfv.org/brahmaputra OPNFV stats: http://projects.bitergia.com/opnfv/browser/ http://projects.bitergia.com/opnfv/browser/ Mailing lists: opnfv-tech-discuss@lists.opnfv.org opnfv-users@lists.opnfv.org

32. THANK YOU