...
- CNTT ... reference implementations and compliance frameworks, etc.
- Serve and grow the community
- Grow awareness of OPNFV work and making sure we are delivering what carriers need.
- Collaborate with vendors and all stakeholders to ensure we are focused on areas of importance to them.
- Track use of OPNFV artifacts (infrastructure, test cases, etc.) both with upstream communities and commercial entities.
- Convince member companies to invest and prioritize developer resources
- When considering new projects for LF, avoid direct competition with existing ones (like OPNFV).
- Refocus what we deliver and refresh tools
- Modularity, loosely couple components, re-usable components: We’ve had two types of deliverables in the past: Scenarios (as “fully tested integrated solution stacks”) and Tools (to conduct that testing). While scenarios have been the focus, it is tools that have survived. Functest, NFVbench, Barometer, Dovetail, … If those would have been even more generic and reusable, we’d have greater reach.
- To achieve Modularity, encourage the various tools to evolve toward more common architecture. Defining an OPNFV target architecture would help, in areas where agreement is possible.
- Evolve to modern tool chains – cloud based solutions which are easy to leverage and replicate.
- Drive closer collaboration between LFN projects and communities – drive community building around sub-projects which are naturally associated, e.g. for OPNFV that would be OPNFV – ONAP Integration, MultiVIM/Cloud, etc.
3. What community asks have not been completed in a reasonable and timely manner?
...
- Yes
- OPNFV developed OVP including governance and process framework (CVC), test framework (Dovetail) and test tools / test cases (Functest, Yardstick, etc.)
- OPNFV is contributing to LFN level compliance program (NFVi and VNF compliance) through Dovetail and LFN compliance committee
- If OVP expands its scope to CNTT reference-implementation validation, OPNFV has bigger role to play in terms of performance testing
- From an FDS perspective, OVP is not immediately relevant. OVP might use NFVbench moving forward (as part of CNTT)
...