| Team | Lab | Notes | Refresh HW in-place? | Redfish- equipped |
|---|---|---|---|---|
| RI-1 | Intel Pod 10 |
| BIG Upgrade in progress. | |
| ViNePerf | Intel Pod 12 | Testing and development, includes IXIA HW Both Baremetal and Kubernetes Setups. Access to Ixia/Keysight Hardware Traffic-generator. Dependency on Pod-0 | Not Required. | No |
| RI-2 | Intel Pod 18 | Reference Deployment RI-2 Kuberef or (Airship) | Not Required | No |
| Kuberef | Intel Pod 19 | Testing and Development, GitLab CI | ||
| Barometer | Intel Pod 13 | Testing and Development, Jenkins/CI node | ||
| Airship (RI-1) | Intel pod 17 | Airship RI-1 Dev and Testing, CI | half of the RAM of other PODs | |
| RI-1 (Airship) | Intel pod 15 | Airship RI-1, RC-1 CI and community reference. | ||
| Airship RI-2 | LaaS HPE POD | Airship RI-2 Dev/Gate | Yes |
Input from Cedric Ollivier follows:
Here is the Functest hardware resource summary.
All Functest OpenStack SUTS are all installed in LF POD4 and POD5 (2*6) moving to OSUOSL (byw thank you for the migration and I do reinstall all of them due to the shutdown of the servers).
No single resource management here, I simply asked Tim and Fatih if I could leverage them once Apex and XCI dropped what they kindly accepted.
- 2 servers to verify Hunter (CNTT RC1 Field Trial)
- 2 servers to verify Iruya (Airship, CNTT RI1)
- 2 servers to verify Jerma (CNTT RC1)
- 2 servers to verify Kali
- 2 servers to verify Leguer
- 2 servers to verify Master (CNTT RC1 + 1?)
I request to 2 additional servers to verify Wallaby (L-Release) which is coming fast.
Ideally I do verify OVN for RC1 interopability as I did when I maintained less active branches.
http://testresults.opnfv.org/functest/vevent202004/
See the following agents in Jenkins all running Functest jobs.
- https://git.opnfv.org/releng/tree/jjb/functest/functest.yaml#n14
- https://build.opnfv.org/ci/computer/lf-pod4/
- https://build.opnfv.org/ci/computer/lf-pod4-2/
- https://build.opnfv.org/ci/computer/lf-pod4-3/
- https://build.opnfv.org/ci/computer/lf-virtual4/
- https://build.opnfv.org/ci/computer/lf-virtual6/
- https://build.opnfv.org/ci/computer/lf-virtual9/
LF-virtual1 which hosts all K8s SUT, runs all Xtesting gates, unit testing and docker builds is being dropped which would simply retire/archive Functest.
I’m leveraging Kind which allows deploying 6 Kubernetes clusters in one server.
But the less I can say, it would have deserved one or 2 additional servers as it’s under huge memory and CPU pressure…
See the following agents in Jenkins all running jobs in lf-virtual1.
- https://git.opnfv.org/releng/tree/jjb/functest/xtesting.yaml#n14
- https://git.opnfv.org/releng/tree/jjb/functest/functest-kubernetes.yaml#n14
- https://build.opnfv.org/ci/computer/lf-virtual1/
- https://build.opnfv.org/ci/computer/lf-virtual1-1/
- https://build.opnfv.org/ci/computer/lf-virtual1-2/
- https://build.opnfv.org/ci/computer/lf-virtual1-3/
- https://build.opnfv.org/ci/computer/lf-virtual1-4/
- https://build.opnfv.org/ci/computer/lf-virtual1-5/
- https://build.opnfv.org/ci/computer/lf-virtual1-6/
I request to 2 additional servers to verify next CNTT RC2 which is coming fast and to share the workload in a normal way.
Then one POD (6 servers) is needed for Functest (nothing new here).
The last LFN POD (XCI) was allocated to Functest but it’s fully broken and has never been repaired by LFN as far as I understand.
I would logically split it for optimizing the gates.
I have a clear view of all the use or not of the server especially since I cleant Releng.
Let’s say I’m too kind not to detail it.
But the less I can write here is I simply second the point raised by Trevor in TSC.
We all know all the resources were fully allocated to OPNFV Installers and they now all dropped for one new entry.