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
pharos_rls_b_spec [2015/10/20 16:21]
Trevor Cooper [CI Lab Resources]
pharos_rls_b_spec [2015/11/24 13:31] (current)
Fatih Degirmenci Removed CI shared labs for the timebeing.
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 =====
  
   * **CI Dedicated Lab**: Labs are dedicated to CI, no sharing.   * **CI Dedicated Lab**: Labs are dedicated to CI, no sharing.
-  * **CI Shared Lab**: Labs that can be used for offloading CI activities for short period of time when the resource shortage occurs/​demand peaks. 
  
 High level CI requirements are listed below ... High level CI requirements are listed below ...
  
   * CI dedicated labs shall be excluded from the list of labs that serve/made available towards the OPNFV community as development resources.   * CI dedicated labs shall be excluded from the list of labs that serve/made available towards the OPNFV community as development resources.
-  * CI dedicated ​and shared ​labs shall provide means/​utilities to (re)configure them automatically when necessary. +  * CI dedicated labs shall provide means/​utilities to (re)configure them automatically when necessary. 
-  * CI dedicated ​and shared ​labs shall be connected to CI using meaningful names stating the purpose of the lab explicitly.+  * CI dedicated labs shall be connected to CI using meaningful names stating the purpose of the lab explicitly.
  
 CI labs shall provide a SLA ... CI labs shall provide a SLA ...
Line 78: Line 67:
   * CI dedicated labs shall be up and running 24x7 except the planned maintenance work.   * CI dedicated labs shall be up and running 24x7 except the planned maintenance work.
   * If maintenance work needs to be carried out, advance notification shall be sent to community and to other infrastructure projects so the lab can be taken out from CI during this time.   * If maintenance work needs to be carried out, advance notification shall be sent to community and to other infrastructure projects so the lab can be taken out from CI during this time.
-  * CI dedicated ​and shared ​labs shall provide contacts in order to troubleshoot issues that might block CI from performing its activities.+  * CI dedicated labs shall provide contacts in order to troubleshoot issues that might block CI from performing its activities. 
 + 
 +===== 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 ===== 
 + 
 +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
  
-Shared lab additional requirements 
  
-  * Shared labs shall be integrated into (yet to be defined/​created) Pharos Booking System so they be booked by CI or individual developers. 
-  * Shared labs shall be integrated into (yet to be defined/​created) Pharos Dashboard so the availability of them can be tracked real-time. 
  
pharos_rls_b_spec.1445358093.txt.gz · Last modified: 2015/10/20 16:21 by Trevor Cooper