[Starlingx-discuss] [ Test ] meeting notes - 06/09/2020
Liu, Yang (YOW)
yang.liu at windriver.com
Tue Jun 9 15:49:17 UTC 2020
Agenda for 6/9/2020
Attendees: Yang, Ruediger, GeorgeP, Mihail, Oliver, Nicolae, Andrew
· Sanity Status:
* Build issue in week of June 2nd. Today's sanity is ongoing and looking good so far.
* There was a discussion in vPTG to add force reboot controller test into sanity - it is currently in progress. ETA: end of this week.
· stx4.0 testing:
* Feature testing:
§ https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0
§ Centos8:
· Two issues/test cases unanswered - test team is not actively working on this. Will move back on this sometime this week.
§ Ceph - Rook - taken out from stx 4.0 - test activities paused
§ 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.
· Suggest to cover all openstack components as a minimum - e.g., nova, neutron, cinder, telemetry, glance, heat, etc
· Also should run some automated regression and update automation code if openstack client changed.
· Nicolae will contact Zhipeng for latest load for Ussuri
§ Windows Active directory completed
· Testing is completed with small add-on to support multiple-dex
§ Red fish virtual media support - testing completed
§ Kubernetes Upgrade Support
· Completed - feature spreadsheet updated.
§ Kata Containers
· Kata container test completed
· Nicolae to check with designer on this issue: "Check PID namespaces" - ETA: end of this week.
§ TSN
· Still setting it up - complicated setups
o Best case scenario: setup complete this week.
§ B&R with etcd database
· Feature testing completed, spreadsheet updated
· Weekly based regression is done - simplex system is passing
* Regression testing:
§ Regression started - Both teams are making good progress - will update the regression spreadsheet at end of week.
§ Some Robot tests don't have proper teardown - manually workaround it. e.g., reset mtu, deleting network, etc, some are affecting rest of the test cases
· Long term plan is to switch to pytest
§ Stability issues encountered
· Yang's team: leave host reboot tests to the end.
· Nic's team: sometimes have to reinstall system
o Saw issue in lock/unlock controller - passes in sanity, but sometimes fails in regression - need to report new LP if encountered again.
§ Telemetry test cases fail - openstack event list does not work, LP opened.
§ Will continue with Regression with latest green load - will wait for 0608's sanity results
§ Regression will be tight if Ussuri merges late
· 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 after stx4.0.
§ Nic will publish the robot regression test cases to github
· https://github.com/starlingx-staging/robot-tests
§ After stx4.0, put more effort on test automation
· Nic: move some robot regression to pytest
· Yang: automate new feature test cases
* Test in the open
§ Yang: coming up with VM requirement to send to opendev
· Will discuss with networking expert for interface requirement
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200609/cc979c5f/attachment-0001.html>
More information about the Starlingx-discuss
mailing list