Versions Compared

Old Version 3

changes.mady.by.user Frank Brockners

Saved on

compared with

New Version Current

changes.mady.by.user Fatih Degirmenci

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add laas and test collab topics

Table of Contents

Objectives

The objectives of this working group are

  • establish common understanding regarding the challenges we all face across the communities OPNFV collaborating with
  • increase the collaboration on existing Cross Community efforts by involving more people and communities who might be interested and willing to contribute
  • look for opportunies to have progress on key areas


Key Areas

Cross Community CI/CD and Infra

  • Establish 3rd party CI with upstream projects based on XCI. Candidates are 
  • Consider opening up OPNFV LaaS to other communities
  • Providing a container infrastructure as a test environment for projects that target cloud native is seen as very important. In addition to test environment, the CD toolchain is a must-have for containers and cloud native approach of developing and deploying VNFs.Create a dialog with ONAP - how much of OPNFV carries over, what extensions are needed?
  • Docs toolchain harmonization - leverage synergies across projects (tools, people, infrastructure)Testing harmonization?
  • https://openci.io/
  • Any new resource requirements?Making OPNFV relevant and useful to upstream projects?
  • Possibility on collaborating on Lab as a Service with OpenStack OpenLab
    • details will be added later on

Cross Community Collaboration on Test

  • Testing harmonization?
  • How to ensure the communities can (re)use the tools/test cases between each other?
    • details will be added later on
  • How the feedback can be provided properly?
    • details will be added later on

Community Building

  • Create active dialogs with OPNFV consumers. Example ONAP: How much of OPNFV carries over, what extensions are needed?
  • Expose OPNFV's values to upstream projects that OPNFV uses as building blocks.

Ideas for immediate next steps

  • ONAP-OPNFV community building
    • Create ONAP-OPNFV collaboration committee
    • "Persistent" OPNFV deployment (as part of XCI) to offer a NFVI-layer for ONAP for testing
    • OPNFV CI supporting ONAP system level CI
  • LaaS extenstion to other communities (ONAP, ODL) - Depends on LaaS evolution