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:00]
Trevor Cooper [Requirements for Pharos Labs]
pharos_rls_b_spec [2015/11/24 13:31] (current)
Fatih Degirmenci Removed CI shared labs for the timebeing.
Line 8: Line 8:
   * Focus is on base level requirements. Implementations will differ in features/​capabilities and scale.   * Focus is on base level requirements. Implementations will differ in features/​capabilities and scale.
   * Individual lab specifications need to be machine readable for automation of deployments.   * Individual lab specifications need to be machine readable for automation of deployments.
 +  * Templates to be filled by labs will help labs determine compliance (for CI/Test/Dev requirements)
   ​   ​
  
 ==== Community Lab ==== ==== Community Lab ====
  
-A community lab is defined as lab providing community assets with a set of SLAs+A community lab is defined as lab providing community assets with a set of SLAs
   * Fulfills the technical requirements i.e. configured in a way to meet OPNFV’s requirements.   * Fulfills the technical requirements i.e. configured in a way to meet OPNFV’s requirements.
-  * Is either +  * Is either: 
-    * accessible to the OPNFV community ​to reserve time and run activities on and/or +    * accessible to the OPNFV community ​for Dev (can reserve time and run activities on) ... and/​or ​... 
-    * integrated with CI +    * integrated with CI toolchain (used for CI and Test activities) 
-  * Is possible to be monitored with the Pharos/LF tools.+  * Is possible to be monitored with the Pharos/LF tools
   * Is able to report back to LF infrastructure on test outputs etc.   * Is able to report back to LF infrastructure on test outputs etc.
-  * Is supported by a Pharos project contributor.+  * Is supported by a Pharos project contributor ​(SLA is documented)
  
-==== Private Lab ====+==== Private Lab ====  
 + 
 +//(if we want to track this?)//
  
   * Fulfills the technical requirements   * Fulfills the technical requirements
   * Has a running deployment of OPNFV   * Has a running deployment of OPNFV
  
-//(if we want to track this?)//+
  
 ===== Types of lab resources ===== ===== Types of lab resources =====
Line 50: 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.
-    * For Dev labs these are criteria for "​ready":​ +===== CI Lab Requirements =====
-      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 Requirements on CI Dedicated ​Resources =====+  * **CI Dedicated ​Lab**: Labs are dedicated to CI, no sharing.
  
-  * **CI Dedicated Lab**: Dedicated to CI, no sharing. +High level CI requirements are listed below ...
-  * **Shared Lab**: The labs that can be used for offloading CI activities for short period of time when the resource shortage occurs/​demand peaks. +
- +
-Based on above descriptions,​ initial/​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 labs shall be connected to CI using meaningful names stating the purpose of the lab explicitly. 
 + 
 +CI labs shall provide a SLA ... 
   * 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 labs 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. 
-  ​* ​CI dedicated and shared ​labs shall be connected to CI using meaningful names stating the purpose of the lab explicitly+ 
-  * Shared labs shall be integrated to (yet to be defined/​created) Pharos Booking System so they be booked by CI or individual developers+===== Test Lab Requirements ===== 
-  * Shared labs shall be integrated to (yet to be defined/​created) Pharos ​Dashboard so the availability of them can be tracked realtime.+ 
 +Test lab resources have the same requirements as CI labs however ..
 +  * Upgrades are planned around specific versions ​(i.enot 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 
 + 
  
pharos_rls_b_spec.1445356817.txt.gz · Last modified: 2015/10/20 16:00 by Trevor Cooper