Page History

...

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

September 18, 2019

• The UI VM discussion (MariaDB vs MySQL DB): waiting for LF to provide the quotation for MariaDB
• Discussion on blueprint validation prerequisites (what we request from users with regards to infra and logs)
• Update from Indu: completed the etcd testing, validated in Airship and REC (ready to merge). Tempest robot test verified on Airship and integrated 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.
• 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.
• 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

...