openstack-qa-team team mailing list archive

[John Garbutt <John.Garbutt@xxxxxxxxxx>]

Hi

Thanks for the clarifications. Being hypervisor agnostic (as much of possible) makes a lot of sense.

Where would the Jenkins tests for all this go? I guess in here:
https://github.com/openstack/openstack-ci

>From what you say, to process to get from baremetal -> hypervisor -> OpenStack is out of scope for Tempest.

Does anyone know who is doing that bit? Is that a combination of openstack-ci and devstack? I noticed cobbler looks to be used in openstack-ci.

Thanks,
John

From: openstack-qa-team-bounces+john.garbutt=eu.citrix.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-qa-team-bounces+john.garbutt=eu.citrix.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Daryl Walleck
Sent: 02 April 2012 04:25
To: John Garbutt
Cc: openstack-xenapi@xxxxxxxxxxxxxxxxxxx; openstack-qa-team@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack-qa-team] QA of XenServer features using Tempest

Hi John,

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?

We're finishing making sure everything is stable, but I think we're pretty close. I think Jay has been working on getting Tempest on a scheduled build with the OpenStack CI and hopefully soon after, begin gating on it.


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

The Tempest tests are for the most part hypervisor agnostic. The general plan to make sure this suite can run and configure itself on the fly to run against any implementation.


*         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.

Pretty much the same as before. The tests are implementation agnostic and black box, so regardless of how the environment is deployed, there should be no issues. As we come across more hypervisor specific behavior, we've already started adding toggles to tests to run or skip tests based on the environment.

Daryl

On Mar 29, 2012, at 1:26 PM, John Garbutt wrote:


Including all XenAPI developers in the discussion.

From: John Garbutt
Sent: 29 March 2012 19:18
To: openstack-qa-team@xxxxxxxxxxxxxxxxxxx<mailto:openstack-qa-team@xxxxxxxxxxxxxxxxxxx>
Subject: QA of XenServer features using Tempest

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
--
Mailing list: https://launchpad.net/~openstack-qa-team
Post to     : openstack-qa-team@xxxxxxxxxxxxxxxxxxx<mailto:openstack-qa-team@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help   : https://help.launchpad.net/ListHelp