Release Candidates scheduling

With Release one, Arno, an OPNFV developer should be able to access a build that integrates the baseline components from upstream projects including; Open Daylight, Open Stack, and KVM which has undergone a basic level of testing. The developer should be able to deploy that build to a Pharos test lab infrastructure and then build their own VNF applications on top of it. The development, integration, and deployment processes are prepared and usable in the scope of this baseline.

For an integrated setup of Virtual Infrastructure Management, SDN control, Hypervisor, virtual switching, OPNFV release #1 is provide the following Selection of most important upstream projects:

• OS Juno
• ODL Helium (Neutron ML2-OVSDB proxy)
• Ceph orchestrated by Cinder
• OVS
• CentOS 7.0 (if possible) or Ubuntu 14.04

Necessary scripts for deployment etc. will be included.

Scope

• Integrated NFVI + VIM solution
  Defined fixed hardware configuration (5 servers) provides resources
• Ability to run example simple VNFs on top of the deployed platform

Automatic and repeatable deployment and installation to the defined hardware configuration of bare metal servers

• Select deployment engine
• Minimal hardware configuration
• HA configuration with separated control and compute nodes
  (use HA configuration of the components that support it)
• Automatic component and system-level testing to prove the installation is operational
  • Use tempest test suites

Platform documentation can refer to documentation by upstream projects. Nevertheless OPNFV release #1 needs to provide all necessary starting points and links.

Software and hardware environment hosted by the LF for OPNFV to:

• Continuously integrate the OPNFV created artifacts that constitute the OPNFV platform.
  CI workflows for development projects defined and implemented
• Continuously perform the above mentioned automatic deployment and installation
• Continuously run the above mentioned component and system level function tests.

Upon release, the artifacts / documentation which constitute release should be accessible by developers and consumers on the day publishing release #1.

There will be no Alpha, Beta, and final release #1, but one single release with limited quality.