From the beginning, OPNFV has made releases with roughly 6 months intervals. After the forth release is out after 2.5 years, it is a good time to reconsider the release model.
OPNFV deliverable is a set of installer instances that have a pre-determined release dates and that are pre-tested. All installer instances use mostly the same versions of the upstream packages that they install.
Continuous integration (CI) model
OPNFV delivers an installer that pulls in the latest (stable?) versions of upstream components and configures them. Installations on different days may be different, since the upstream can change. The upstream versions are tested in OPNFV labs.
Pros and cons
The release model allows to test the installers, the components and the configuration before release. This way anyone who downloads and installs OPNFV will have some guarantees that the installation will work.
In case of difficulties, the installation is the same as anyone else's installation, so it is possible to get help from others.
Each release has overhead in testing and documentation. The more frequent the releases are, the more overhead there is, but with less frequent releases, the upstream components get old.
The OPNFV release lags the upstream development. Any bugs have to be fixed both in upstream and in the OPNFV release.
In the CI model, all fixes upstream are available to OPNFV. This makes it easier to work with fast moving upstream projects. All new features upstream are also available to OPNFV sooner.
In case of difficulties, it is hard to give precise fixes since the installations can be slightly different.
- Some projects follow the release model and other the CI model
- OPNFV releases are more frequent, once a month?
- There are stable and experimental OPNFV installations, and each project can choose to join either or both