1. TSC update to the Board
7 April 2017

2. TSC update: Danube Update
Danube 1.0 technical release completed on April 2, 2017
Original plan date was March 27, 2017
35 Scenarios are part of Danube 1.0
be+Scenario+Status
Danube 2.0 is scheduled for May 4th, 2017
OPNFV Confidential 2

3. TSC update: Euphrates Planning
Euphrates Timeline
OPNFV Confidential 3

4. TSC update: Euphrates Planning
Euphrates Priorities
Technical communities’ priorities being captured at
Conversations with the End User Advisory Group
Summary of EUAG pain points discussion(s) in the TSC + ONS forthcoming….
OPNFV Confidential 4

5. TSC update: Continuous Delivery/DevOps
CD/DevOps practices and principles are enablers for introducing new features faster & more frequently, thus bringing value to end users earlier.
These practices make it possible to release software at all times.
CD/DevOps require end-to-end approach, mindset change, and a cultural shift.
OPNFV Confidential 5

6. TSC update: Cross Community CI (XCI)
OpenStack
In the process of setting up first periodic virtual deployment from trunk using Bifrost and OpenStack-Ansible.
Work on baremetal progressing.
OpenDaylight
Patchset verification work will be completed soon.
Waiting for mini-ODL distro for OPNFV to be available.
fd.io
Started the discussions around setting up a prototype for OPNFV FDS scenario.
Open-O/ONAP
Met with the Open-O team at the December’2016 Plugfest, and planning more face-to-face discussions during ONS.
OPNFV Confidential 6

7. TSC update: Pod descriptor file
Dividing pod file into 2 parts
Hardware configuration file
Network configuration file
Translate pod descriptor files into installer configuration files
Load pod descriptor files in the Pharos Dashboard
Verify pod information through Pharos Verify tools
All the ZTE PODs have been adapted to the template approved
Installers like Apex and Fuel are similar to this way
OPNFV Confidential 7

8. TSC update: Scenario consolidation
Created dependency/compatibility tree of scenarios
Created scenario lifecycle document (first version)
Distinguish generic and specific scenarios
Generic scenarios for stable releases
Specific scenarios may prepare for DevOps usage, including independent quick release cycles
Parent-Child relations of scenarios
Child scenarios will plan for remerge after a few releases
Created template for scenario descriptor file SDF (under review)
Common scenario description across installers
Single point to document characteristics of scenarios for all different users (Owner, CI, deployment, test)
Stepwise introduction of dynamic CI
OPNFV Confidential 8

9. TSC update: OPNFV’s Way of Working (WoW), Needs, Required Changes
Current OPNFV’s WoW only supports stable releases and is not developer friendly.
OPNFV obviously need stable releases but this slows us down greatly for true CD.
OPNFV can go as fast as the slowest upstream, so we need to be closer to communities we work with and help them to also move towards CD.
Our community needs to change and adapt; we have to work together rather than only dealing with our own projects.
OPNFV Confidential 9

10. TSC update: Experimenting with flexible milestones in Euphrates
Summary forthcoming post discussions with fd.io/FDS teams
OPNFV Confidential 10

11. TSC update: Projects health metrics
Q4’2016
Projects “archived”
OPNFV Confidential 11

12. TSC update: Projects health metrics
Q1’2017 (draft)
New Projects
OPNFV Confidential 12

13. TSC update: Projects health metrics
Reasons for project terminations
Key project team members (incl. PTLs) changing jobs and no longer involved in OPNFV
Not able to attract new contributors after project formation
Projects were mostly led by a single member company
Decision to do the work in other OPNFV projects and/or in upstream communities
OPNFV Confidential 13