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.
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
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 fromConfiguration File Alignment Discussions.
THE TABLE BELOW IS OUTDATED. PLEASE CHECK labs.opnfv.org.
Resources Used for CI Bare Metal Deployment and Testing
Running CI Bare Metal Deploys
|Pharos POD||x86||Apex||Yes||Participated in Colorado Release.|
|Pharos POD||x86||Fuel||Yes||Participated in Colorado Release.|
|ericsson-pod2||Pharos POD||x86||Fuel||Yes||Participated in Colorado Release.|
|Pharos POD||x86||Compass||WIP||Waiting confirmation from Compass.|
|Pharos POD||x86||Compass||Yes||Participated in Colorado Release.|
|huawei-pod2||Pharos POD||x86||Compass||WIP||Waiting confirmation from Compass.|
|intel-pod5||Pharos POD||x86||Joid||Yes||Participated in Colorado Release.|
|intel-pod6||Pharos POD||x86||Joid||Yes||Participated in Colorado Release.|
|arm-pod1||Pharos POD||ARM||Fuel||Yes||Participated in Colorado Release.|
Resources Used for Other CI Purposes
Running CI Bare Metal Deploys
|intel-pod2||Pharos POD||CPERF||Needs confirmation||No||Contacted CPERF.|
|intel-pod7||See note||Apex/fdio||Operational||No||POD is split to use for Apex virtual deployments and fdio development|
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|
ericsson-virtual2, ericsson-virtual3, ericsson-virtual4,
ericsson-virtual5, intel-virtual1, intel-virtual2
CI Build Servers
|List of Machines|
|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.|
See also: Slaves connected to Jenkins
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
For allocation of PODs for testing release B (there are 4 installers) see Brahmaputra Testing Page
Pharos compliant PODs
Type / Usage
Production CI operational
Project CI (Test) operational
Developer resources with access guide and process published
China Mobile (Beijing)
POD 1 (Fuel) - dev for Functest and Yardstick tools
Dell (Santa Clara)
POD 1 - available for CI allocation; POD 2 Qtip dev and test
HA server config with ARM servers
POD 1 (Fuel) - Yardstick testing (proj CI); POD 2 (Fuel) - production CI; N servers used for Dev based on Demand
Huawei (Santa Clara)
POD 1 (Compass) - production CI; POD 2 - available for dev allocation; 2x servers - VMs available for dev allocation
POD 1 - available for proj allocation; CI POD 2 - available for proj CI allocation; 4x servers - dev for Compass
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
POD 1 (Fuel) - used for PoCs (vCPE), Functest dev, proj CI
POD 1 (odentified as Orange POD 2 in jenkins) - dev for JOID and Functest, temp use as CI POD for joid for B release
Spirent (San Jose)
Individual servers are used for various dev activities
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)
|Nokia (Espoo)||1||POD 1 (Apex) Doctor and Functest dev & test||TBD||Yes||No|
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