...
https://zoom.us/j/459272075
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
+1 877 369 0926 US Toll-free
+1 855 880 1246 US Toll-free
Meeting ID: 459272075
Find your local number: https://zoom.us/u/acimKOClJk
Introductory webcast recording
Notes
Release 2 readiness
| Test | Robot case exists | Docker for AMD64 | Docker for ARM64 | Tested on AMD64 | Tested on ARM64 | Works with Bluval |
|---|---|---|---|---|---|---|
| Redfish | ||||||
| LTP | Ok | Ok | Ok | Works with Airship | Works | |
| k8s | Ok | Ok | Ok | Works with k3s and Rover | Works with IEC | Works |
| OpenStack (Tempest) | Ok | Ok | Ok | Works with Airship |
...
October 1, 2019
- Updated "Release 2" table
- The documentation on how to use Bluval is incomplete but it is now no longer "Work in Progress"
- Cristina has written a blog post about how to do Kubernetes testing with Bluval; this should be linked to from somewhere (link is
https://www.lfedge.org/2019/09/26/running-k8s-conformance-tests-in-akraino-edge-stack/)
- Jenkins job for running Bluval is being reviewed in the ci-management project (see https://gerrit.akraino.org/r/c/ci-management/+/1657)
- The OpenStack + Bluval integration patch still needs end-to-end testing (https://gerrit.akraino.org/r/c/validation/+/1602)
- VAl-53
- This will be a separate layer instead of part of Kubernetes
- Deepak will update the ticket
September 25, 2019
- Plan is to use MySQL and AWS ECS for the Validation UI, Ioakeim will update the LF ticket IT-16700
- Blueprint Validation pre-requisites were presented in the Akraino Technical Community Call held on 9/19; meeting was recorded
- Naga is validating ETCD testing which was completed by Indu and will integrate with BluVal
- Tempest robot test verified on Airship by Indu, Naga is testing integration with BluVal
- Discussion on OpenStack layer: Tempest and Refstack are complementary. If projects don't support certain features the tests should detect the missing components and skip those tests (we need to test this functionality). As a backup we can also blacklist tests. Indu is working on VAL-51 which was created to test this functionality.
- LTP tests need root access to run; options are either sudo or create a group with privileges as opposed to using root password. Question if they can be ran without root access; Ioakeim has been assigned VAL-50, and is investigating. One consideration is to create a special group with the right capabilities. This group must be created on every lab.
- Discussion on security: we need a development guide documentation
- Discussion on how to handle the situation where the nodes don't have access to internet and we need the test images to be in a local repository inside the cluster
- A ticket was created for Cristina VAL-53, to create a Container for the Logging and Monitoring Layer
...