1. TSC Update at December Board Meeting

2. TSC Update Colorado 2.0 & 3.0
Colorado 2.0: Release slipped from October 27 to Nov 10 to accommodate resolution of a problem with the Fuel installer
Release contents:
2 scenarios
TripleO ISO
Fuel ISO (x86)
Joid repo (git clone command)
Documentation
No changes to Compass ISO or Fuel ISO for ARM
Colorado 3.0: Software download page will be updated today
Release contents:
19 scenarios
Includes previously unreleased fd.io scenarios
TripleO ISO
Fuel ISO (x86)
Fuel ISO (ARM)
Compass ISO
No updates to the Joid repo
OPNFV Confidential

3. Danube Release Scheduled for release March 27, 2017
41 projects have expressed intent to participate and have submitted release plans (MS1)
58 scenarios have been declared
Risks
New installer, Daisy4NFV, has not yet met MS3 (integration with OpenStack on OPNFV CI)
This has also created a risk for the Escalator project, which is exclusively dependent on Daisy for deployment
The Movie, Orchestra, and Opera projects have not yet met MS2 (test requirements)
OPNFV Confidential 3

4. TSC action point #1: OPNFV architecture
From board minutes:
“There was a consensus that the TSC should develop an architectural framework and map OPNFV release scenarios to the framework. This artifact could be a vehicle for communicating OPNFV’s value and progress to the industry and also as an internal tool to measure against goals. Mr. Tallgren took an action item to provide an update on this artifact during the December Board meeting.”
OPNFV Confidential 4

5. Status of OPNFV architecture
Initial draft exists
Next steps discussed in TSC meeting on December 6th
Link here (to be updated)
OPNFV Confidential 5

6. TSC action point #2: Danube priorities
From Board meeting minutes:
Mr. Richomme thought that it is important to provide a technical vision and priorities for future releases to the technical community via a whitepaper. This would also be a good way to communicate planned activates from Infrastructure and Testing Working Groups, and Mr. Degirmenci added that this could be a good vehicle to highlight resource/support needs to TSC & Board.
OPNFV Confidential 6

7. Status of Danube priorities
Priorities have been discussed in Infra and Testing working groups
This has also been discussed in the technical call and TSC call
Responses from the working groups and feature projects are in the Etherpad and in edited form in the OPNFV wiki page
OPNFV Confidential 7

8. New projects
Rescuer was discussed in technical community call on Nov. 3rd, no updates
OpenRetrieve was announced on Nov. 21; discussed on technical community call on Dec. 1
Not yet ready for approval
Focus on containers
OPNFV Confidential 8

9. Other technical activities
Common naming strategy for scenarios and common installer format proposals exist and have been discussed
Discussions will continue in the Plugfest/Hackfest
Common installer format would allow to describe a POD in a single configuration file and then use any installer
OPNFV Confidential 9