1. Building a TSC vision for Danube
Support for discussion only….

2. Why?

3. Because what we do is great!

4. But…

5. Few people know what we are really doing!

6. Why?
Because what we are doing is still very fuzzy for lots of people even internally there are misunderstandings
We need to have a better view on the delta between the release (and not only in terms of number of feature projects/scenarios)
We need to know where we are going and identify our weakness
We need to give a realistic and consistent view of our projects

7. Misunderstanding?

8. Misunderstanding? “OPNFV creates a reference NFV platform”* However
We do not produce any platform….
We are dealing with 3 SDN controllers, different acceleration options, soon several MANO stacks…can we speak of “a reference” *:

9. Misunderstanding?
” OPNFV facilitates the development and evolution of NFV components across various open source ecosystems”* We are a catalyst of the ecosystem…
We identify gaps and leverage upstream to include new critical NFV features
We bring confidence on integration scenarios though our tests and our CI
We produce installation scripts, scenarios, test cases *:

10. Misunderstanding?
Sometimes we may believe that we address the problems but it is not because a project has been created that it is active

11. Technical Discussions
Features
Technical Discussions
Mano Working Group
Integration / CI
Installers
Tests
Infra Working group
Testing Workign Group

12. How?

13. A first Attempt… Arno: Proof of Concept
Brahmaputra: Lab ready => see infography
Colorado: ?????
Danube: ??????????

14. Goals 1 page white paper announcing Top 5 objectives for Release N+1
Answering what is OPNFV Danube
Giving a Realistic view of the project activity
Encouraging contributions in identified projects, creation of a project in areas that matter
Ensuring the Glue between the projects (resources follow interest in projects but glue is at the interfaces and poorly covered leading to inconsistencies)

15. How to define the priorities...
Rely on the working groups and the committees
Aggregate the view at the TSC level (with possible choices)
Give perspectives beyond version N+1
Organize a community vote

16. My view (example) Danube: « Real CI to support sustainable growth »
Top 5 priorities
Engage CI evolution (commitments from installers + test projects)
Create an aggregated Testing landing page based on test results in the DB (scenario status aaS)
Automatic cleaning of committers/projects when no activity since 6 months (as mentioned in By-laws)
Add First Stress tests to validate scenarios
Align installers on features: security tests, Doctor, ..

17. Questions

18. Credits openclipart