...
- Mandatory tests were discussed in PTL/TSC meeting on July 23
- Sonobuoy works also on ARM64
- Sonobuoy works also on ARM64 except for one test case
- Requires some patches to run
- Target is to check by end of week if that issue can be fixed
Public UI VM
- LF has sent out a quote for two xlarge VMs on AWS, load balancer and 10G extra storage space
- The extra storage will be used for database for UI
- The two VMs are running the UI code
- It is possible to scale down the proposal but let us go with this
Blueprint
Open gerrits
- [UI] Support UI partial control - are reviews needed or do we wait and see?this is work in progress
- Add resources for building cord-tester image - has a "-1"
- sonobuoy testing – waiting for DANM4.0
- Juha K will be back from holiday on August 5
Old APs - not discussed
- Using k8s on our deployments
- Using versioning for our releases
- Moving the UI to a new git repo
Jiras
...
July 17, 2019
- Update about Sonobuoy testing on ARM64: with the latest Sonobuoy version, almost all test cases (except for one) seem to pass
- Bluval UI:
- First item was about the Bluval UI implementation hosted at LF. LF has already a MySQL instance running in AWS as an elastic DB, and if it can be used, then the UI will only need to have the web server and the code to update the data in the database. This means that the UI can be stateless and all state will be in the DB. To be followed up
- Second issue was about how to check whether bluval has ran all the mandatory tests. The test log will have results of all tests that it has run, but the UI cannot know what tests it was supposed to run (since it is possible to disable tests). The tentative solution is to create a file from bluval.yaml that has all tests that were supposed to be run, and store it in the logs. Bluval.py needs to do that
- We discussed the Redfish testing. Redfish testing is currently mainly checking that the implementations confirm to the schemas that have been defined. The DMTF has also defined a few interoperability profiles, such as for OCP. It would be useful to define inside Akraino a profile that the different hardwares could be tested against, to make sure that all implementations have common functionality implemented in the same way
- Recording is here. Unfortunately, it only covers a part of the Redfish discussion
...