Page tree
Skip to end of metadata
Go to start of metadata

[NOTE: These goals are a summary of community discussions at https://etherpad.opnfv.org/p/TSC-backlog

  1. Address new use cases and hardware deployments (e.g. cloud native, Edge, C-RAN/vCO)
    1. Support cloud native apps in the reference platform (integrate and test Kubernetes & related components)
    2. Create/integrate Edge-specific stacks (e.g. Akraino, OpenStack Edge) and define & obtain appropriate hardware environments for testing them in Pharos and LaaS
    3. Create/integrate C-RAN and vCO specific stacks and test them on appropriate hardware environments in Pharos and LaaS
  2. Re-evaluate, and if needed update & communicate, OPNFV's mission, deliverables and ways of working/processes
    1. Update our understanding of key user groups and their needs
    2. Identify which artifacts and deliverables OPNFV should produce
    1. Define a release process that addresses the needs of our key user groups
    2. Use lab resources more efficiently through dynamic resource allocation for CI pipeline
  3. Refine OPNFV output/artifacts so that OPNFV is more use-case driven and easier to consume
    1. Scenario consolidation
    2. LaaS evolution
    3. Better packaging/consumability of test tools
  4. Closer collaboration with other LFN projects through e.g. XCI, Lab-as-a-Service
  5. Evolve the OPNFV Verified Program and support creation of LFN-level umbrella program
  6. Maintain and grow our healthy community
    1. Continuing to have venues/events (both face-to-face and virtual) for OPNFV community members to collaborate effectively 
    2. Growing the contributor community

High-level budget needs:

  • Two Plugfests/Hackfests
  • Two developer summits (not counting ONS North America)
  • Running cost of LF-hosted hardware (LF CI pods and servers for general IT)
  • Software licenses for currently used IT services (git/Gerrit, Confluence/Jira, Bitergia, etc.)
  • Project and IT support staff as current


  • No labels

4 Comments

  1. Why two developer summits?  We used to have one Design Summit/year.  

    1. Two release cycles per year - one developer summit per release cycle. The idea of having them offset from the market awareness/business conference is to lighten the load for people who have to go to both, the problem with colocating is that the developer event tends to get squeezed in the main conference.

      1. Our Plugfest/Hackfest is timed shortly after each release, so we didn't have to have a separate DDF-type event like in ODL.  In 2016 & 2017 OPNFV had 3 major developers events per year with 2 Plugfests/Hackfests and the Design Summit.

    2. We can expect an increased need for information exchange/presentation across projects due to collaboration within LFN, hence it makes sense to create additional room for presentation of project work.