pharos_rls_b_labs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pharos_rls_b_labs [2016/01/21 20:56] Fatih Degirmenci [Production CI Resources Reservation] |
pharos_rls_b_labs [2016/03/09 07:57] (current) Morgan Richomme [Table] |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| The references "stable" and "latest" mean the branches. PODs marked as "stable" will run against //stable/brahmaputra// branch and PODs marked as "latest" will run agains //master// branch. The testing will be done against both branches but the results from stable/brahmaputra counts when it comes to release candidate evaluation. | The references "stable" and "latest" mean the branches. PODs marked as "stable" will run against //stable/brahmaputra// branch and PODs marked as "latest" will run agains //master// branch. The testing will be done against both branches but the results from stable/brahmaputra counts when it comes to release candidate evaluation. | ||
| - | ^ POD ^ Installer ^ Stable/Latest ^ POD/Resources available & Tested with installer ^ POD has Jenkins configured for automated deploys and tested ^ Notes ^ | + | ^ POD ^ Installer ^ Stable/Latest ^ POD/Resources available & Tested with installer ^ POD has Jenkins configured for automated deploys and tested ^ Notes ^ |
| - | ^ LF POD 1 | Apex | stable | Yes - Fully operational \\ [[https://build.opnfv.org/ci/view/apex/job/apex-deploy-baremetal-master/|Jenkins: apex-deploy-baremetal-master]] | Jenkins: Yes, Deploy: No, Test: No | Still running against latest | | + | ^ LF POD 1 | Apex | stable | Yes - Fully operational \\ [[https://build.opnfv.org/ci/view/apex/job/apex-deploy-baremetal-master/|Jenkins: apex-deploy-baremetal-master]] | Jenkins: Yes, Deploy: No, Test: No | Still running against latest | |
| - | ^ Huawei SC POD1 | Compass | stable | Yes - Fully operational | Jenkins: Yes, Deploy: No, Test: No | N/A | | + | ^ Huawei SC POD1 | Compass | stable | Yes - Fully operational | Jenkins: Yes, Deploy: No, Test: No | N/A | |
| - | ^ LF POD 2 | Fuel | stable | Yes - Fully operational | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | | + | ^ Ericsson POD2 | Fuel | stable | Yes - Fully operational | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | |
| - | ^ Intel POD 5 | Joid | stable | Yes - Fully operational \\ [[https://build.opnfv.org/ci/job/joid-odl-intel-pod5-daily-brahmaputra/|Jenkins: joid-odl-intel-pod5-daily-brahmaputra]] | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | | + | ^ Intel POD 5 | Joid | stable | Yes - Fully operational \\ [[https://build.opnfv.org/ci/job/joid-odl-intel-pod5-daily-brahmaputra/|Jenkins: joid-odl-intel-pod5-daily-brahmaputra]] | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | |
| - | ^ Intel POD 2 | Apex | latest | Moved to new environment ... waiting for Tim Rozet (Apex) to test and confirm if he still sees any issues | Jenkins: No, Deploy: No, Test: No | Apex is currently only working on LF POD 1 but will get back to use Intel POD 2 | | + | ^ Intel POD 2 | Apex moved to POD 7 | dev | Yes - Fully operational | Jenkins: No, Deploy: No, Test: No | Apex moved to a new environment (Intel POD 7). POD 2 is being used by CPERF | |
| - | ^ Intel POD 8 | Compass | latest | Yes - Fully operational | Jenkins: Yes, Deploy: No, Test: No | N/A | | + | ^ Intel POD 7 | Apex | latest | Yes - Fully operational. Moved Apex environment from POD 2. https://jira.opnfv.org/browse/PHAROS-90 | Jenkins: Yes, Deploy: No, Test: No | Apex is currently using LF POD 1 for all jobs. Waiting for Apex to verify issues experienced with POD 2 are resolved. | |
| - | ^ Ericsson POD2 | Fuel | latest | Yes - Fully operational | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | | + | ^ Intel POD 8 | Compass | latest | Yes - Fully operational | Jenkins: Yes, Deploy: No, Test: No | N/A | |
| - | ^ Intel POD 6 | Joid | latest | Yes - Fully operational \\ [[https://build.opnfv.org/ci/job/joid-odl-intel-pod6-daily-master/|Jenkins: joid-odl-intel-pod6-daily-master]] | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | | + | ^ LF POD2 | Fuel | latest | Yes - Fuel8 reconfig is ongoing | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | |
| - | ^ Intel POD 4 | x5 Standalone Servers | N/A | Yes - Fully operational (Investigating increasing Internet bandwidth which is an issue for downloading large images frequently) | Jenkins: Yes, Deploy: N/A, Test: N/A | Build & virtual deploy resources | | + | ^ Intel POD 6 | Joid | latest | Yes - Fully operational \\ [[https://build.opnfv.org/ci/job/joid-odl-intel-pod6-daily-master/|Jenkins: joid-odl-intel-pod6-daily-master]] | Jenkins: Yes, Deploy: Yes, Test: Yes | N/A | |
| - | ^ LF POD 3 | x4 Standalone servers | N/A | No - WIP with 1 server | Jenkins: No, Deploy: N/A, Test: N/A | Build & virtual deploy resources \\ 1 server is reserved for Joid virtual and WIP to take it into operation | | + | ^ Intel POD 4 | x5 Standalone Servers | N/A | Yes - Fully operational (Investigating increasing Internet bandwidth which is an issue for downloading large images frequently) | Jenkins: Yes, Deploy: N/A, Test: N/A | Build & virtual deploy resources | |
| + | ^ LF POD 3 | x4 Standalone servers | N/A | No - WIP with 1 server | Jenkins: No, Deploy: N/A, Test: N/A | Build & virtual deploy resources \\ 1 server is reserved for Joid virtual and WIP to take it into operation | | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| See also: [[https://build.opnfv.org/ci/|Jenkins OPNFV Platform CI main page]] | See also: [[https://build.opnfv.org/ci/|Jenkins OPNFV Platform CI main page]] | ||
| Line 51: | Line 61: | ||
| All the communication regarding PODs should be done in respective IRC Channels: #opnfv-testperf, #opnfv-yardstick, #opnfv-apex, #opnfv-fuel, #opnfv-compass, #opnfv-joid. | All the communication regarding PODs should be done in respective IRC Channels: #opnfv-testperf, #opnfv-yardstick, #opnfv-apex, #opnfv-fuel, #opnfv-compass, #opnfv-joid. | ||
| - | ^ POD ^ Installer ^ Branch ^ Reserved for CI ^ Reserved for Troubleshooting | | + | ^ POD ^ Installer ^ Branch ^ Reserved for CI ^ Reserved for Troubleshooting ^ Notes ^ |
| - | ^ LF POD1 | Apex | master | 01:00UTC - 13:00UTC | 16:00UTC - 01:00UTC | | + | ^ LF POD1 | Apex | master | 01:00UTC - 13:00UTC | 16:00UTC - 01:00UTC \\ Booked for Yardstick: 16:00 UTC - 18:00UTC \\ Booked for Functest: 18:00 UTC - 20:00 UTC | | |
| - | ^ Huawei SC POD1 | Compass | stable | 10:00UTC - 22:00UTC | 22:00UTC - 10:00UTC | | + | ^ Huawei SC POD1 | Compass | stable | 10:00UTC - 22:00UTC | 22:00UTC - 10:00UTC \\ Booked for Yardstick: 02:00 UTC - 04:00 UTC | | |
| - | ^ LF POD2 | Fuel | stable | 17:00UTC - 08:00UTC | 11:00UTC - 17:00UTC | | + | ^ LF POD2 | Fuel | stable | 17:00UTC - 08:00UTC | 11:00UTC - 17:00UTC \\ Booked for Yardstick: 13:00 UTC - 15:00 UTC \\ Booked for Functest: 15:00 UTC - 17:00 UTC | **2016-01-28: Dedicated for Fuel8 Uplift until further notice** | |
| - | ^ Intel POD5 | Joid | stable | 17:00UTC - 05:00UTC | 05:00UTC - 17:00UTC | | + | ^ Intel POD5 | Joid | stable | 17:00UTC - 05:00UTC | 05:00UTC - 17:00UTC \\ Booked for Yardstick: 14:00 UTC - 16:00 UTC \\ Booked for Functest: 16:00 UTC - 17:00 UTC | | |
| - | ^ Intel POD2 | Apex | N/A | N/A | N/A | | + | ^ Intel POD2 | Apex | N/A | N/A | N/A | | |
| - | ^ Intel POD8 | Compass | master | 22:00UTC - 10:00UTC | 10:00UTC - 22:00UTC | | + | ^ Intel POD8 | Compass | master | 22:00UTC - 10:00UTC | 10:00UTC - 22:00UTC \\ Booked for Yardstick: 10:00 UTC - 12:00 UTC \\ Booked for Functest: 13:00 UTC - 15:00 UTC | | |
| - | ^ Ericsson POD2 | Fuel | master | 05:00UTC - 20:00UTC | 20:00UTC - 05:00UTC | | + | ^ Ericsson POD2 | Fuel | master | 05:00UTC - 20:00UTC | 20:00UTC - 05:00UTC \\ Booked for Yardstick: 20:00 UTC - 22:00 UTC | **2016-01-28: Dedicated for Fuel8 Uplift until further notice** | |
| - | ^ Intel POD6 | Joid | master | 05:00UTC - 17:00UTC | 17:00UTC - 05:00UTC | | + | ^ Intel POD6 | Joid | master | 05:00UTC - 17:00UTC | 17:00UTC - 05:00UTC \\ Booked for Yardstick: 17:00 UTC - 19:00 UTC \\ Booked for Functest: 19:00 UTC - 20:00 UTC | | |
| + | |||
| Notes: | Notes: | ||
| * It is assumed that the CI will run 3 scenarios per Installer/POD until the code freeze. | * It is assumed that the CI will run 3 scenarios per Installer/POD until the code freeze. | ||
| - | * The reservations are done based on the the locations of active contributors of installer and test projects. | + | * The reservations are done based on the locations of active contributors of installer and test projects. |
| * The table tries to leave 1 POD per installer for troubleshooting purposes mainly to be used by test projects. | * The table tries to leave 1 POD per installer for troubleshooting purposes mainly to be used by test projects. | ||
| * Approximate time to run full loop per scenario (deploy + functest + yardstick). These times are taken out from Jenkins jobs and might obviously be longer or shorter. | * Approximate time to run full loop per scenario (deploy + functest + yardstick). These times are taken out from Jenkins jobs and might obviously be longer or shorter. | ||
| Line 71: | Line 83: | ||
| * Joid : 4 hours per scenario | * Joid : 4 hours per scenario | ||
| - | Once the code freeze hits, time to do troubleshooting on the PODs dedicated for stable branch will go down drastically given the number of scenarios. Due to this, the troubleshooting work needs to be done on PODs running against master if the problem in question can be troubleshooting there. | + | Once the code freeze hits, time to do troubleshooting on the PODs dedicated for stable branch will go down drastically given the number of scenarios. Due to this, the troubleshooting work needs to be done on PODs running against master if the problem in question can be troubleshooted there. |
| It is also possible that installer teams might prefer test teams to use a certain POD longer than what is stated above and test teams get more time to work on certain POD for troubleshooting. But this should not result in not running CI for the branch on the POD in question or else this will increase the possibility of introducing faults to stable branch. The PODs must not turn into development resources! | It is also possible that installer teams might prefer test teams to use a certain POD longer than what is stated above and test teams get more time to work on certain POD for troubleshooting. But this should not result in not running CI for the branch on the POD in question or else this will increase the possibility of introducing faults to stable branch. The PODs must not turn into development resources! | ||
| Line 92: | Line 104: | ||
| | China Mobile (Beijing) | 1 | | POD 1 (Fuel) - dev for Functest and Yardstick tools | No | Yes | Yes | | | China Mobile (Beijing) | 1 | | POD 1 (Fuel) - dev for Functest and Yardstick tools | No | Yes | Yes | | ||
| | Dell (Santa Clara) | 3 | | POD 1 - available for CI allocation; POD 2 Qtip dev and test | No (TBD) | Yes | Yes | | | Dell (Santa Clara) | 3 | | POD 1 - available for CI allocation; POD 2 Qtip dev and test | No (TBD) | Yes | Yes | | ||
| - | | Enea | 1 | | non-HA server config with ARM servers | No | No | No | | + | | Enea | 1 | | HA server config with ARM servers | No | No | No | |
| | Ericsson (Montreal) | 2 | 4 Blades | POD 1 (Fuel) - Yardstick testing (proj CI); POD 2 (Fuel) - production CI; N servers used for Dev based on Demand | Yes | Yes | Yes | | | Ericsson (Montreal) | 2 | 4 Blades | POD 1 (Fuel) - Yardstick testing (proj CI); POD 2 (Fuel) - production CI; N servers used for Dev based on Demand | Yes | Yes | Yes | | ||
| | Huawei (Santa Clara) | 2 | 2 | POD 1 (Compass) - production CI; POD 2 - available for dev allocation; 2x servers - VMs available for dev allocation | No (TBD) | Yes | No | | | Huawei (Santa Clara) | 2 | 2 | POD 1 (Compass) - production CI; POD 2 - available for dev allocation; 2x servers - VMs available for dev allocation | No (TBD) | Yes | No | | ||
| Line 98: | Line 110: | ||
| | Intel (Portland) | 9 | 3 (POD 3 - VSPERF) | POD 1 - Apex dev/test; POD 2 - Apex production CI; POD 3 - VSPERF test environment with Ixia traffic generator, OVSNFV, kvm4nfv; POD 4 - CI builds and virt deploys; POD 5 (JOID) - production CI; POD 6 - JOID dev/test; POD 7 - Fuel dev/test; POD 8 - Compass production CI; POD 9 - STORPERF / Bottlenecks | Yes | Yes | Yes | | | Intel (Portland) | 9 | 3 (POD 3 - VSPERF) | POD 1 - Apex dev/test; POD 2 - Apex production CI; POD 3 - VSPERF test environment with Ixia traffic generator, OVSNFV, kvm4nfv; POD 4 - CI builds and virt deploys; POD 5 (JOID) - production CI; POD 6 - JOID dev/test; POD 7 - Fuel dev/test; POD 8 - Compass production CI; POD 9 - STORPERF / Bottlenecks | Yes | Yes | Yes | | ||
| | Orange (Paris) | 1 | | POD 1 (Fuel) - used for PoCs (vCPE), Functest dev, proj CI | No | Yes | Yes | | | Orange (Paris) | 1 | | POD 1 (Fuel) - used for PoCs (vCPE), Functest dev, proj CI | No | Yes | Yes | | ||
| - | | Orange (Lanion) | 1 | | POD 1 - dev for JOID and Functest | No | No | No | | + | | Orange (Lanion) | 1 | | POD 1 (odentified as Orange POD 2 in jenkins) - dev for JOID and Functest, temp use as CI POD for joid for B release | Yes | Yes | No | |
| | Spirent (San Jose) | | 12 | Individual servers are used for various dev activities | No | No | Yes | | | Spirent (San Jose) | | 12 | Individual servers are used for various dev activities | No | No | Yes | | ||
| | ZTE (Nan Jing) | 1 | | POD 1 - dev/test for Functest and Yardstick | No | No | Yes | | | ZTE (Nan Jing) | 1 | | POD 1 - dev/test for Functest and Yardstick | No | No | Yes | | ||
| + | |||
| Line 122: | Line 135: | ||
| 1. Cable labs – currently have 2 PODs that are currently private resources | 1. Cable labs – currently have 2 PODs that are currently private resources | ||
| 2. CENGN – waiting on hardware to complete build out | 2. CENGN – waiting on hardware to complete build out | ||
| - | |||
pharos_rls_b_labs.1453409793.txt.gz · Last modified: 2016/01/21 20:56 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
