OPNFV Board Meeting 16 June 2017

Introduced CVP at the Summit Introduced CVP to the community at the Summit with our intent to launch later this year. Heather Kirksey Keynote Breakout session: Introducing the OPNFV Compliance Verification Program (Thursday, Jun 15 12:00PM - 12:30PM, Studio 2/3) Other keynotes also highlighted the importance of CVP The NFV/SDN Alliance in China expressed strong interest in utilizing CVP as part of their industry compliance testing program EUAG meeting at June 15: very positive support on CVP, to create a channel for feedbacks on future priorities to end users. Service providers, vendors, industry organizations we met this week gave strong endorsement on CVP and expressed interests to participate or collaborate. ETSI TST working group discussion on collaboration with Dovetail OPNFV Confidential 2

Dovetail Update Dovetail team had updated TSC and received a lot comments prior to the Summit. A Design Summit session was dedicated to come up with definitive action items, with an understanding that resolutions of these action items will meet TSC expectations. Have all ongoing documentation-related Gerrit reviews merged, documents finalized (no editor's notes, open actions etc.) Move HA tests from optional to mandatory Make Functest's vPing a mandatory test Dovetail also started on Euphrates planning with an initial list of work items Stress testing Include Doctor project (optional/mandatory is tbd) Include Models project test cases (e.g. launch a sample multi-VM VNF) Incorporate more OPNFV feature projects (e.g. SFC etc.) Other areas of interests include performance, resiliency at scale, security etc. OPNFV Confidential 3

C&C Update OPNFV Confidential 4

Decisions/Progress since last meeting Updated Danube Annex for the Governance document Alignment within the committee Will finalize when Dovetail is ready Consensus on CVP Processes Progress Starting to discuss future plans Marketing Committee EU-AG Synchronizing with Dovetail on the format of test results OPNFV Confidential 5

Design Summit Update Significant progress this week in planning future releases Recognize the need to move beyond feature testing Expanding to cover use cases vPing to test connectivity in current version of CVP Developing list of target use cases for future releases Also seeking EU-AG input OPNFV Confidential 6

Board support Recognizing need for a coordinator staff position Collect feedback and curate list of use cases Liaison with LF IT staff Program management (track registrations, monitor review SLAs, update website when we issue new logos, etc.) Will have detailed plan and budget by next meeting OPNFV Confidential 7

XCI: What do we aim to achieve? Late Integration -> Integrate Daily Slow Feedback -> Test Daily Lack of Visibility -> Push feedback to where they are needed High demand on limited no of people -> Increase the competence Too fragmented -> Have a simple way for developers Backporting changes are possible for certain projects and in some cases but it is not always possible. It also takes extra effort and time to do that. OPNFV Confidential 8

XCI Enablers + bifrost openstack-ansible OPNFV Confidential 9

XCI: Where are we? Completed Centos/SUSE support for Bifrost Increased stability for Bifrost Bifrost 3rd Party CI Developer sandbox Scenario os-nosdn-nofeature-ha Scenario os-odl-nofeature-ha ODL Integration In Progress – Pending SUSE support for OpenStack Ansible Tacker Integration OVS NSH Integration Scenario os-odl-sfc-ha virtual VPP Integration OpenStack Ansible 3rd Party CI CI Evolution (Promotion, staging) Backporting changes are possible for certain projects and in some cases but it is not always possible. It also takes extra effort and time to do that. OPNFV Confidential 10

Who is contributing to XCI? Ericsson Huawei Intel Orange Red Hat SUSE IBM (Bifrost) Rackspace (OpenStack Ansible) Backporting changes are possible for certain projects and in some cases but it is not always possible. It also takes extra effort and time to do that. OPNFV Confidential 11

Lab as a Service (LaaS) Towards better serving developers OPNFV scenarios are too heavy to run on a typical laptop Developers require access to at least one beefy server for a virtual deployment to develop on This “beefy server” is not always easy to find for an interested contributor Developers which are interested to advance features or test not always have the expertise to install the scenario they desire to enhance Getting a deployment as development environment ready requires significant cycles which a developer may not be able/ready to invest Community-level/joint development requires open access to a lab/installation Current situation Only very limited number community openly accessible servers available No “turn key” OPNFV scenario installations available as lab as a service / sandbox OPNFV Confidential 12

Lab Resources in OPNFV X CI/CD Environment (Semi-) Private Development Environment Public Development Environment X LF and community labs; sufficient capacity Community labs; sufficient capacity Openly accessible community labs: Lack of capacity OPNFV Confidential 13

Towards Lab as a Service for OPNFV Offer openly accessible server resources to developers Offer readily installed scenarios, per the choice of the developer OPNFV Confidential 14

What is OPNFV LaaS? provisioning deployment delivery decommissioning LaaS is a cloud/bare-metal environment, providing automatic provisioning deployment delivery decommissioning of resources, enabling the creation of one click development environment, supporting different use cases harmonization across environments used by developers ability to bring up any installer/scenario together with the other components of the stack possibility to provide end/new users to try out OPNFV without much time and effort reducing the burden on OPNFV Infra/Pharos and developers, end users OPNFV Confidential 15

How it would look? OPNFV Confidential 16

Initial Use Cases Spawn a deployment from snapshot Deploy certain OPNFV scenario from scratch from master using an existing artifact Deploy certain OPNFV scenario from scratch using a released OPNFV version Build the artifact and deploy certain OPNFV scenario for the given patch Deploy certain OPNFV scenario and provide additional scenarios to deploy/develop other components of the stack such as ONAP Provide a machine with OS installation only OPNFV Confidential 17

Resourcing an open OPNFV LaaS Community ask: 8 + 3 (Intel/ARM) PODs + 20 Standalone servers ~100 Servers (beefy servers – incl. 256-512 GB RAM) + Switch infra Hosting Senior IT/Lab-Engineer (create, evolve, maintain LaaS) Suggested starting point (1st phase): 50 Servers (~50% of community ask) Detailed approval once equipment BOM is available. OPNFV Confidential 18

More Info https://wiki.opnfv.org/display/INF/Lab+as+a+Service OPNFV Confidential 19

Updates on Mobile Edge 2 discussions during the Design Summit related to Mobile Edge Virtualization of Central office locations - Multi-Access edge project BoF: Edge technologies; distributing the control plane and constrained device considerations. OPNFV Confidential 20

Virtualization of Central office - Multi-Access edge OPNFV, vCO and CORD participants discussed central office virtualization topics. Focused on structuring the Multi-Acces edge project Three primary goals emerged: Extend Pharos to include integrated vOLT fabric, and further architectures Requires ordering the BOM for vOLT and fabric integration – CORD team to help Provision solutions for distributed control plane technologies (edge cloud) Including component deployment of OpenStack Including container technologies Application deployment automation and testing for remote and central workloads OPNFV Confidential 21

BoF: Edge technologies The edge BoF followed the vCO session Discussion turned to topics such as; Physical deployment footprints FPGA, GPU infrastructure integration Cloud distribution & decomposition Node roles through the network The BoF did not provide any grand conclusions however validated the conclusions of the Multi-Access edge discussion Further dialog will continue in; Pharos for physical node type definitions, OpenStack & CNCF for edge cloud and containerization OPNFV Confidential 22

EUAG  Technical community working process Started using Technical Community Discussion calls to explore/map EUAG pain points with OPNFV projects. Began the exercise with EUAG’s Reference VNF pain point that was well aligned with the new SampleVNF project Some clarification was requested/required on several items such as: “production quality” VNFs Non-open-source VNFs Refining the scope However, the SampleVNF team is/will addressing a number of items from the Reference VNF pain points such as: Null/Echo samples OPNFV Confidential 23

EUAG  Technical community working process EUAG identifies and prioritizes pain points Tech community reviews, resolves questions, transforms into technical requirements Propose Tech community identifies one or more likely projects and gains consensus for allocating requirements Refine Allocate OPNFV Confidential 24

TSC Composition In Q4’17, 5 committers-at-large members were added to the TSC. Today there are 22 total TSC members (17 Platinum representatives + 5 committers-at-large) In the past few months, there have been several discussions (incl. face-to-face at Plugfest, Design Summit, TSC calls) on the TSC composition Although there is a desire to move to an 100% elected TSC in the future, there are a number of questions that the community also wants to address Role of the TSC (e.g. is the TSC providing enough guidance on topics such as scenario consolidation, CVP testing, etc.?) How will we know if the new TSC is working better than today’s, etc.? OPNFV Confidential 25

TSC Composition The consensus is that OPNFV is not yet ready to move to an 100% elected TSC today However, there was a discussion on a hybrid approach to transition to an 100%-elected TSC Limit the size of the TSC to 15 members Have an election for 7 TSC members among Platinum representatives for 1-year term Second election for 8 TSC members among committers for 2-year- term At the end of Year 1, elect 7 new TSC members among committers OPNFV Confidential 26

TSC Composition Roughly ½ of the TSC would be elected every year for a 2- year term This prevents potential for a 100% turnover in the TSC There will still be a limit of 2 TSC members from each organization Platinum members Elected members Elected members Elected members Elected members Now + 1 year + 2 years + 3 years OPNFV Confidential 27

TSC Composition A question to the Platinum Board members: How valuable is the TSC seat for Platinum membership? OPNFV Confidential 28