Boards of OPNFV, ODL, fd.io and Open-O have agreed to increase collaboration between these communities to share and align CI/CD, infrastructure activities and practices including hardware, integration and deployment, testing and packaging across communities.
This page is intended to serve as a place to have links to information for these communities, plan how the work can be started, how the communities at wide can be informed regarding these activities and contribute to them.
The people listed in below table are expected to start collaboration work and make communities aware of the activities. This work is open to everyone who wants to take part and contribute.
|Community||Drivers||CSIT/Infra Web||Meeting Details||Maillist|
|OpenDaylight||Luis Gomez, Daniel Farrell||https://wiki.opendaylight.org/view/CrossProject:Integration_Group:CSITfirstname.lastname@example.org|
|Open-O||Gildas Lanilis||https://wiki.open-o.org/display/IN/Integration+Home||Integration Meetingemail@example.com|
|OPNFV||Fatih Degirmenci||https://wiki.opnfv.org/display/INF||Infra WG Weekly Meeting|
Links to Infra/Test Improvement Activities/Plans
The purpose of below list is to collect links to the pages where the ongoing/planned improvement activities per community is documented.
By making these activities visible, we can find synergies to collaborate further and avoid double work if/when we see overlapping activities.
|Community||Link to the wiki|
Cross Community Presentations
Proposed Content for the Community Presentations
The proposed content for the presentations
- Summary regarding projects involved in infra, CI/CD, testing
- How the CI/CD is setup
- What type of test activities the community has
- The infrastructure used for the activities (baremetal labs, Rackspace hosting, etc)
- The challenges
- The ongoing/planned improvement activities
- What is expected from other communities
Community Presentation Schedule
|Meeting||Date, Time, Meeting Details||Notes|
|OPNFV presentation to Open-O||2017-01-16, 06:30PST, Integration Meeting||Done|
|OPNFV presentation to ODL||2017-01-19, 16:00UTC, Integration Meeting||Done|
|fd.io presentation to OPNFV||2017-02-01, 16:00UTC, Infra WG Weekly Meeting||Done|
|ODL presentation to OPNFV||2017-02-01, 16:30UTC, Infra WG Weekly Meeting||Done|
|Open-O presentation to OPNFV||2017-02-01, 17:00UTC, Infra WG Weekly Meeting||Done|
|OPNFV presentation to fd.io||2017-02-01, 15:00UTC, CSIT Meeting||Done|
|OPNFV presentation to ONAP||TBD|
|ONAP presentation to OPNFV||TBD|
Collection of the Presentations
The table below is created based on the questions asked during the community presentations.
The items in the list needs to be reviewed by Infra Collaboration Team and brought into corresponding WG/project meetings for further discussions accordingly.
Please note that this is still work in progress and items below are subject to change.
|Topic||Brought up by||Area||Corresponding WG/Projects||Status|
|1||How Open-O community can request resources from OPNFV||Open-O||Labs|
|2||OPNFV plans regarding MANO testing||Open-O||Testing||Open-O Integration/Test|
OPNFV Test WG
|3||How OPNFV can consume the tests from Open-O and reuse/run them in OPNFV||OPNFV||Common CI Processes (Delivery)|
OPNFV Test WG, OPNFV Infra WG/Releng
|4||The importance/need of deploying latest OpenStack for Open-O||Open-O||Common CI Processes (Deployment)|
|5||Making Open-O stable versions available earlier/more frequently for early feedback purposes||OPNFV||Common CI Processes (Delivery)|
|6||Identification/clarification of the different types of feedback OPNFV can provide to Open-O||Open-O|
Common CI Processes (Feedback Loops)
|7||How OPNFV decides the versions of the different upstream projects||ODL||Release Management (Traceability, Reproducibility)|
Common CI Processes (Delivery)
OPNFV Infra WG, Release Management
|8||What is the difference among all the pharos labs||ODL||Labs||ODL CSIT|
OPNFV Infra WG/Pharos
|9||How OPNFV Artifact Repository (Google Storage) is used (what goes there, permissions, etc.)||ODL||Tools (Artifact Hosting)|
|10||How ODL is deployed on an official Pharos POD (3 ODL Instances?)||ODL||Common CI Processes (Deployment)||ODL CSIT|
OPNFV Infra WG/Installers
|11||How Pharos Specification can be updated (adding additional nodes to Pharos PODs via Pharos Change Request)||ODL||Labs|
|12||How patchset verification is done for the projects and what is run in scope of it||ODL||Common CI Processes (Feedback Loops)|
|13||What artifacts OPNFV produces||ODL||Common CI Processes (Build)|
|14||OPNFV Jenkins Sandbox||ODL||Tools (Jenkins)|
|15||OPNFV Testapi||ODL||Tools (Testing)|
|16||Performance Testing (Yardstick, vsperf)||fd.io||Testing||fd.io CSIT|
OPNFV Test WG
|17||Hardware resources and operations||fd.io||Labs||fd.io CSIT|
OPNFV Infra WG/Pharos
|18||Test Result Handling/Archiving, Analytics||fd.io||Tools (Test Dashboards)|
|19||Best practices/coding standards||fd.io||Best Practices||fd.io CSIT|
OPNFV Infra WG, OPNFV Test WG
|20||Nightly Autorelease Stability, Test Coverage||OPNFV||Testing||ODL CSIT|
OPNFV Test WG
|21||Log collection, analytics (ELK, Dashboard, etc)||ODL||Tools (Test Dashboards)||ODL CSIT|
OPNFV Test WG, OPNFV Infra WG
|22||Performance Testing on Baremetal||ODL||Labs, Testing|
Infra Collaboration Focus Areas
The Focus Areas are identified based on the conversations happening as part of Infra Collaboration activity.
The purpose of these focus areas is to go through findings, prioritize them, find possibilities of reuse between communities, and work on them collaboratively. Participation to focus areas is open to everyone.
Cross Community CI/CD
Cross Community Test Strategy