OPNFV Lab Resources
This Pharos page explains the current status of Labs for support of development, test and CI activities. For future we plan to have dashboards with live information.
Tracking actual capabilities, status and ongoing usage of our diverse community lab resources is non-trivial ... however its needed to support projects and releases with accurate planning. To achieve this we need easy visibility of our lab resources, their capabilities as well as current and past usage.
Information on Linux Foundation lab access and usage is found here.
Status of Production CI Resources
Production CI Resources are the resources (full baremetal PODs or standalone machines) that are tied to CI on 24x7 basis with no manual intervention. These resources are used for
- running bare metal deployment and testing on Jenkins automatically
- running virtual deployment and testing in order to gate commits
- builds, unit tests
Information on test combinations and allocations/combinations/hardware dependencies can be seen from Colorado Scenario Inventory.
Discussions regarding alignment of configuration for POD-layout/Build/Deploy/Test can be seen from Configuration File Alignment Discussions.
THE TABLE BELOW IS OUTDATED. PLEASE CHECK labs.opnfv.org.
Resources Used for CI Bare Metal Deployment and Testing | ||||||
|---|---|---|---|---|---|---|
Resource Name | Resource Type | Architecture | Purpose/Installer | Operational Status | Running CI Bare Metal Deploys | Notes |
lf-pod1 | Pharos POD | x86 | Apex | OK | Yes | Participated in Colorado Release. |
lf-pod2 | Pharos POD | x86 | Fuel | OK | Yes | Participative in Colorado Release. |
| lf-pod4 | Pharos POD | x86 | OSA with XCI | OK | WIP | Testing Baremetal deployment of installer OSA with XCI |
| ericsson-pod2 | Pharos POD | x86 | OSA with XCI | OK | WIP | Testing Baremetal deployment of installer OSA with XCI |
| ericsson-pod3 | Pharos POD | x86 | Fuel | OK | Yes | |
| ericsson-pod4 | Pharos POD | x86 | Fuel | OK | Yes | |
intel-pod8 | Pharos POD | x86 | Compass | WIP | WIP | Waiting confirmation from Compass. |
huawei-pod1 | Pharos POD | x86 | Compass | OK | Yes | Participated in Colorado Release. |
| huawei-pod2 | Pharos POD | x86 | Compass | WIP | WIP | Waiting confirmation from Compass. |
| intel-pod5 | Pharos POD | x86 | Joid | OK | Yes | Participated in Colorado Release. |
| intel-pod6 | Pharos POD | x86 | Joid | OK | Yes | Participated in Colorado Release. |
| arm-pod1 | Pharos POD | ARM | Fuel | OK | Yes | Participated in Colorado Release. |
CI Servers Used for Virtual Deployments | ||||||
| Project | List of Machines | Notes | ||||
| Apex | intel-virtual3, intel-virtual4, intel-virtual5 | |||||
| Compass | huawei-virtual1, huawei-virtual2, huawei-virtual3 | |||||
| Fuel | ericsson-virtual2, ericsson-virtual3, ericsson-virtual4, ericsson-virtual5, intel-virtual1, intel-virtual2 | |||||
| Multisite | intel-virtual6 | |||||
CI Build Servers | ||||||
OS | List of Machines | Projects | Notes | |||
| Ubuntu | ericsson-build4, ericsson-build5, arm-build2, lf-build2 | compass, fuel, vsperf, yardstick, functest, storperf, fsqm, parser, qtip | Resources marked red are not taken into operation fully even though they are connected to Jenkins. This is due to maintenance reasons. | |||
| CentOS | intel-build1, lf-build1 | ovsnfv | ||||
See also: Slaves connected to Jenkins
Community Lab Resources
Labs listed here are operational and being actively used for either development (features and/or tools), test (feature testing or dedicated to test project), production (dedicated with 24/7 SLA). Note a community lab can provide one or more of these capabilities.
Information on project needs from labs was collected from lab owners by a survey (closed 16 Oct 2015) ... https://www.surveymonkey.com/results/SM-CYC35WH2
- 13 community labs currently are used by projects and releng activities
- Labs that are not Pharos compliant may still provide servers as dev resources
- Some labs still need to publish developer access process and guides
- Some labs are not yet setup under Jenkins control
- Labs that suffer from low bandwidth or unstable connections can still be used for specific project activities
For allocation of PODs for testing release B (there are 4 installers) see Brahmaputra Testing Page
Lab | Pharos compliant PODs | Stand-alone servers | Type / Usage | Production CI operational | Project CI (Test) operational | Developer resources with access guide and process published |
|---|---|---|---|---|---|---|
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 | |
Enea | 1 | HA server config with ARM servers | No | No | No | |
Ericsson (Montreal) | 2 | 36 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 (Xia-an) | 2 | 4 | POD 1 - available for proj allocation; CI POD 2 - available for proj CI allocation; 4x servers - dev for Compass | No | No | No |
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 (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 | |
| ZTE(Shanghai) | 3 | POD 1 - CI of Functest and Yardstick based on Fuel(os-odl_l2-nofeature-ha) POD 2 - CI of Functest and Yardstick based on Fuel(os-odl_l2-nofeature-ha) and Qtip and Parser dev/test POD 3 - CI of Functest and Yardstick based on Fuel(os-nosdn-kvm-ha) | No | Yes | Yes | |
| Nokia (Espoo) | 1 | POD 1 (Fuel) Doctor CI | TBD | Yes | No |
Community Lab Resources - Upcoming
The following organization are actively working on providing additional OPNFV community labs ...
1. Cable labs – currently have 2 PODs that are currently private resources 2. CENGN – waiting on hardware to complete build out
{group3}
1 Comment
Steven Wright
AFAIK, all the current CI/CD processes and scenarios target the same Pharos POD architecture.
Some of the EUAG pain points identified in Infrastructure and the OPNFV Reference Platform seem to suggest a need for assurance that the OPNFV platform is portable across different NFVI architectures. Not sure if this can be captured completely in scenario descriptors or if some infrastructure variants are required?