openstack-qa-team team mailing list archive

[John Garbutt <John.Garbutt@xxxxxxxxxx>]

Hi,

I have just given Tempest a spin on a XenServer DevStack install (using milestone-proposed/ Essex RC code), and after a bit of playing around, everything seemed to look OK in the end. I am looking at getting more involved with QA in Folsom.

I have two main areas I think I should invest some time into...


First, I am keen to get a server or two inside Citrix running tests against various versions of XenServer/XCP/Kronos, maybe every night, maybe every check-in. (Eventually against all the stable branches and trunk).

So I have a few questions to get this going:

*         Are there plans to start using Tempest to run (maybe nightly?) against trunk for Folsom?

*         I know we have smoketests running against XenServer, anything else at the moment that I might have missed?

*         How do you plan to get from baremetal -> OS, is that scripted already? I planned on PXE installing the appropriate versions on XenServer, and doing a reboot (using SSH, or whatever) to trigger the reinstall. I noticed some PXE config inside DevStack for Ubuntu.


Second there are two XenServer features for which I would like to write some tests:

XenServer live migration (and possibly non-live migration): presumably I could add an extra flag to allow you to disable the tests (similar to the one for resize). The API is the same (I hope) as KVM, so it should be able to share the same tests, with any luck. Am I right in saying there is nothing in the test suite for that right now?

Third, it would be nice to test XenServer host aggregates. This is an admin operation, currently only works on XenServer, and it requires multiple hosts, and knowing their hostnames. I guess this could all be specified in a host-aggregates configuration section?

Really just checking that Tempest is the right place to be doing these kinds of tests, and wondering where you guys think it is best to add the tests: into the main compute test suite, or into somewhere with a separate configuration section?

Thanks,
John