This page captures requirements for OPNFV community labs that are hosted by community members. Current status of the community labs is here https://wiki.opnfv.org/pharos_rls_b_labs. Information about usage of the Linux Foundation lab is here https://wiki.opnfv.org/pharos/lf_lab.
The Pharos specification defines technical requirements which are consistent across labs. This is needed to facilitate development projects as well as provide CI resources and stable/well-understood test environments.
A community lab is defined as a lab providing community assets with a set of SLAs
(if we want to track this?)
* For build/deploy/testing that is continuously and automatically done * Connected/controlled by LF central CI toolchain * Dedicated and available 24/7 * Has specific scripts for automatic reconfiguration, can be deployed by different installers * Has a published support SLA
* OPNFV needs a number of stable test environments where upgrades are carefully controlled (not continuous) * Need environments with all deployment methods/tools + a variety of hw specs (for diversity) * LF connectivity is needed to control tests and collect results
* A wide range of capability/capacity options are needed including some specialized environments. (e.g. IPv6, HA, performance tools/testing, …) * It’s not yet clear what will be possible re. repurpose of Dev labs for CI at times when there is a critical shortage of CI resource.
High level CI requirements are listed below …
CI labs shall provide a SLA …
Test lab resources have the same requirements as CI labs however …
The following criteria define "Ready" for Dev labs:
1. Successfully deployed an OPNFV release (Arno, beta-Brahmaputra, …) 2. Successfully run default test suite from Functest (used for Arno) 3. Remote access per recommended methods (using OpenVPN) 4. Lab specs/config documented per Pharos spec. 5. At least one full (bare-metal) POD 6. Test capabilities documented 7. History of activities/tests supported (or planned to support) on Wiki