This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
pharos_rls_b_spec [2015/10/20 16:22] Trevor Cooper [Development] |
pharos_rls_b_spec [2015/10/20 16:52] Trevor Cooper [Test Lab Requirements] |
||
---|---|---|---|
Line 77: | Line 77: | ||
===== Test Lab Requirements ===== | ===== Test Lab Requirements ===== | ||
+ | Test lab resources have the same requirements as CI labs however ... | ||
+ | * Upgrades are planned around specific versions (i.e. not continuous) | ||
+ | * For release testing the lab will be approved as "compliant" for Rls B (Compliance is agreed by Octopus, Genesis, Functest and Pharos projects) | ||
===== Dev Lab Requirements ===== | ===== Dev Lab Requirements ===== | ||
+ | |||
+ | 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 | ||