...
| Test | Robot case exists | Docker for AMD64 | Docker for ARM64 | Tested on AMD64 | Tested on ARM64 | Works with Bluval |
|---|---|---|---|---|---|---|
| Redfish | Ok | Ok | Ok | Ran on OpenEdge hw (failures to be investigated) | NA | |
| LTP | Ok | Ok | Ok | Needs to be installed by the test setup phase | Works | |
| k8s | Ok | Ok | Ok | Works with k3s, Rover and REC | Works with IEC | Works |
| OpenStack (Tempest) | Ok | Ok | Ok | Works with Airship | https://gerrit.akraino.org/r/c/validation/+/1602 |
October 23, 2019
- Release 2: Redfish update https://gerrit.akraino.org/r/c/validation/+/1781
- FIx for LTP: https://gerrit.akraino.org/r/c/validation/+/1752
- CI jobs: https://gerrit.akraino.org/r/c/ci-management/+/1657
- OpenStack Bluval integration https://gerrit.akraino.org/r/c/validation/+/1602
- Add remote session to etcd HA testcases https://gerrit.akraino.org/r/c/validation/+/1793
- Logging container: https://gerrit.akraino.org/r/c/validation/+/1767
- Discussion if this should be a separate layer, or include them in the existing layers (k8s, docker)
- The logging is an integrated system so it seems hard to separate it (elastic search logging)
- NTP and DNS tests were developed for TA, but they seem generic tests. We decided to create a services layer to include those and we will move the logging inside this layer instead of having its own layer
- UI status update:
October 16, 2019
- LTP - no updates, will try install the tests through binaries built at the time when we build the container
- We need to keep in mind that there might be different OS installed on the cluster
- CI jobs: https://gerrit.akraino.org/r/c/ci-management/+/1657
- We had a couple of sync sessions; work is still in progress
- OpenStack Bluval integration https://gerrit.akraino.org/r/c/validation/+/1602 - no updates, patch needs to be tested on REC
- Sonobuyo ARM64 patch has been merged: https://github.com/heptio/sonobuoy-plugin-systemd-logs/pull/5 - no updates, low priority
- Logging container: patch was merged, test was moved to the validation project
- Discussion if this should be a separate layer, or include them in the existing layers (k8s, docker)
- The logging is an integrated system so it seems hard to separate it (elastic search logging)
- NTP and DNS tests were developed for TA, but they seem generic tests. We decided to create a services layer to include those and we will move the logging inside this layer instead of having its own layer
- UI status update: LF team informed us that the UI will be deployed in AWS by the end of this week
...