User Tools

Site Tools


pharos_rls_b_spec

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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 [CI Lab Requirements]
pharos_rls_b_spec [2015/10/20 16:52]
Trevor Cooper [Test Lab Requirements]
Line 53: Line 53:
     * It’s not yet clear what will be possible re. repurpose of Dev labs for CI at times when there is     * 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.       a critical shortage of CI resource.
-      
-    * "​Ready"​ criteria 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 
- 
 ===== CI Lab Requirements ===== ===== CI Lab Requirements =====
  
Line 87: 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
  
  
  
pharos_rls_b_spec.txt · Last modified: 2015/11/24 13:31 by Fatih Degirmenci