Open Invention Network introductions (Kevin Huang): 15 mins.
CVP update (Chris Donley): 30 mins.
TSC composition (Tapio): 30 mins.
Status of End-User Advisory Group pain point list (Tapio/David McBride): 15 mins.
Update on how the OPNFV projects address the EUAG-identified Pain Points.
Other Updates: 45 mins.
XCI update (Fatih)
- OPNFV can now deploy OpenStack from master (Pike) on virtual and baremetal. (os-nosdn-nofeature-noha and os-nosdn-nofeature-ha scenarios)
- OPNFV XCI Sandbox has been created and being used by few OPNFV developers to improve it.
- ODL and Tacker integration on OpenStack master is going on. ( - RELENG-225Getting issue details... STATUS , - RELENG-226Getting issue details... STATUS )
- Basic way of working has been documented in order to find working versions of OpenStack components from master. Work is ongoing to enable this.
- Bifrost 3rd Party CI has been up and running. OpenStack Ansible 3rd Party CI will be enabled.
Mobile edge project convergence (Bryan, Chris Price)
Update from the discussions from the Summit
Release model (topic for a later discussion)
The OPNFV release model has been discussed since the beginning of OPNFV. Here are some references:
The main alternatives are
- Releases come at a regular 6 month cadence, they are well tested and documented, and install without difficulties.
- CI/CD: Software is released whenever it is ready without any defined cadence, and uses the latest and greatest upstream versions.
In Euphrates, the FDS project is following a different milestone model which is more flexible that the default one.
Also, the yet to be approved Scenario Description Format (see http://artifacts.opnfv.org/octopus/docs/scenario-lifecycle/index.html) distinguishes between generic and specific scenarios, and it has been discussed whether the release model could be different according to the maturity of the scenario.
The Cross-Domain CI project has started running tests with the latest stable OpenStack releases.
Kubernetes ( docker Containers ) vs OpenStack
From the beginning of OPNFV, OpenStack has been the VIM for the OPNFV stack. However, an alternative NFV infrastructure would be based on (Linux) docker containers with some container management tool (Kubernetes?). The OpenStack community and the OPNFV project OpenRetriever has been defining the ways how OpenStack can accommodate containers, but OPNFV can also work with Kubernetes directly without using OpenStack. This would imply some changes to eg. the OPNFV CI system.