...
Test | Robot case exists | Docker for AMD64 | Docker for ARM64 | Tested on x86_64/AMD64 | Tested on ARM64 | Works Integrated with Bluval |
---|---|---|---|---|---|---|
Redfish | Ok | Ok | Ok | Ran on OpenEdge hw (failures to be investigated) | NA | Waiting for testing to complete |
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 |
...
- Release 2: Redfish update https://gerrit.akraino.org/r/c/validation/+/1781
- FIx for LTP: https://gerrit.akraino.org/r/c/validation/+/1752
- Testing with OpenEdge is ongoing
- OpenStack integration: copy bluval-rec.yaml to bluval-unicycle.yaml and leave OpenStack tests out from bluval-rec.yaml
- Add remote session to etcd HA testcases CI jobs: https://gerrit.akraino.org/r/c/ci-managementvalidation/+/1657OpenStack Bluval integration 1793
- Will be modified to follow the The Principle: Whenever possible, use testing tools on the container to connect to the SUT. When this is not possible, ssh connection to the SUT can be used
- Indu will fix this so that the kubectl in the container will connect to the SUT using a modified kubeconfig file (replace localhost with real IP address)
- Fix for LTP: 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)
- 1752
Jira server Akraino JIRA serverId 604c99be-f414-323d-84e4-c9d70fa2bcdf key VAL-66 - Will build binaries out of the source files and using those for testing
- The binaries will be copied to the SUT, run, and deleted afterwards
- The full LTP requires sudo rights which is a security risk. Need to investigate if there is a subset of LTP that can work without special rights
- Versioning of Bluval code and Docker hub
- Use tags to mark releases
- Need separate Jenkins jobs for released/stable version and master
- The UI project needs separate versioning
- Could request a new repo for UI?
- CI jobs: 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 layerhttps://gerrit.akraino.org/r/c/taci-management/+/1657
- Still has a "-1" but getting there
- Need to create instructions once the patch is merged (AP: Vali)
- Does not cover uploading the results
- Logging container: cloudtaf/+/1489https://gerrit.akraino.org/r/c/ta/cloudtafvalidation/+/17281767
- Will be part of service layer
- NTP and DNS tests
- UI status update:
- Almost there, but some problems remain
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
...