[Starlingx-discuss] [ Test ] meeting notes - 05/26/2020
Liu, Yang (YOW)
yang.liu at windriver.com
Tue May 26 15:55:38 UTC 2020
Agenda for 05/26/2020
Attendees: Yang, Nicolae, Ruediger, GeorgeC, GeorgeP, Bruce, Mihail
· Sanity Status:
* May16-24 sanity failed. Sanity with May25th' layered build looks okay.
· stx4.0 testing:
* Feature testing:
§ https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0
§ Centos8:
· Mostly done, a few issues to report/investigate.
§ Ceph - Rook
· Development still in progress, will provide another load by May29th.
· Test plan needs update (system CLIs won't be supported) - in discussion with developers while waiting for new load
§ Upversion Openstack services used by flock components on host:
· Test completed - feature spreadsheet updated.
§ Upgrade Containerized OpenStack to Ussuri (and OpenStack helm rebase)
· Planned sanity is completed. IPv6 is not covered.
· Test coverage question raised in community, may need followup on that in terms of test plan.
§ Windows Active directory completed
· Testing in progress with small add-on to support multiple-dex
§ Red fish virual media support - testing completed
§ Kubernetes Upgrade Support
· Completed - feature spreadsheet updated.
§ Kata Containers
· ETA end of May29th week or early in following week
· Issue encountered after activating kata runtime - need to confirm with developer, may be by design.
§ TSN
· Rudiger started the setup
§ B&R with etcd database
· Feature testing completed, spreadsheet updated
· Weekly based regresssion is done - all failing
* Regression testing:
§ Regression started - used May16th load due to no good build in past week.
§ Automated robot regression ran in virtual env and various types of failures encountered
· Some caused system to be unusable - openstack cmd no longer works
· Needs to investigate and report LPs
§ Telemetry test cases fail - openstack event list does not work, LP to be opened
§ Will continue with Regression using May25+ load
§ Regression at risk - need to scope down regression testing to high priority test cases to see if we can meet current schedule
* Build issue
* Number of failures encountered
* Test team will down size
· Open topic
* Test automation
§ Need automated installation script
· Robot framwork installation scripts are used in daily sanity with basic setup and provisioning - needs libvert and qemu installed
o https://opendev.org/starlingx/test/src/branch/master/automated-robot-suite
o Nic: Look into adding to Docs/Wiki. Perhaps after stx4.0.
§ Suggest to priorize the features without hardware depency - timeline after stx4.0 release
· Yang to add column to existing feature spreadsheet to identify automation candidates
§ Teams are loaded with stx4.0 testing
* Test in the open
§ Will take the strategy to bring up simplex system in one VM
· Before 4.0: talk to OpenDev to get VM
· After 4.0: set up the vm
· TBD: Zuul component
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200526/822f72da/attachment-0001.html>
More information about the Starlingx-discuss
mailing list