pharos_rls_b_spec
Differences
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:19] Trevor Cooper [Development] |
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. | ||
| - | + | ===== CI Lab Requirements ===== | |
| - | * "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 Resources ===== | + | |
| * **CI Dedicated Lab**: Labs are dedicated to CI, no sharing. | * **CI Dedicated Lab**: Labs are dedicated to CI, no sharing. | ||
| Line 84: | Line 74: | ||
| * 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 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. | * Shared labs shall be integrated into (yet to be defined/created) Pharos Dashboard so the availability of them can be tracked real-time. | ||
| + | |||
| + | ===== 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 | ||
| + | |||
| + | |||
pharos_rls_b_spec.txt · Last modified: 2015/11/24 13:31 by Fatih Degirmenci
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
