Hi,
It looks like the following checking, broke things for me with DevStack +
Tempest on Ubuntu 11.10:
https://github.com/openstack/tempest/commit/051075a59642e0d2f98a4ab792a52523e3478159
I currently get the following errors:
==
> I pinged Anne Gentle about the docs missing this (apparently
> core) API server action and she will be working to get this added to the
> current docs -- especially since novaclient already has support for it...
Good good.
> The more I think about it, I believe a single migration API would be s
> > - historically XenAPI had migrate, Libvirt had live migrate
> > - But by end of Folsom we should have both having both
>
> Yes, but what is the difference between the two?
Got you. I think this is right:
Migration:
- shutdown the VM
- move current disk to the destination
- start VM
- user see
Hi,
> There are currently no tests for live migration. I imagine that the reason is
> because there is very poor documentation on the os-migrateLive API
> extension. I'd be happy to help you in writing the tests.
Cool, thanks.
> I'd love some help in identifying some documentation
> ...
> we need
Hi,
I am in the process of adding Live Migration support into the XenAPI driver.
Are there any current plans on how to test Live Migration, is it done already?
I was thinking of copying what has been done for Migration.
Thanks,
John
--
Mailing list: https://launchpad.net/~openstack-qa-team
Post
team@lists.launchpad.net
> Subject: Re: [Openstack-qa-team] Testing XenServer
>
>
>
> On 05/25/2012 08:38 AM, Jay Pipes wrote:
> > Including JimB, MontyT, and DanP for some related CI needs...
> >
> > On 05/25/2012 05:12 AM, John Garbutt wrote:
> >>
Hi,
An quick update on the Citrix XenServer CI efforts.
I have got some tests (based on DevStack) running tempest for trunk and
stable/essex with XenServer based DevStack deployments.
Once it proves to be stable, I will look into publishing the results on
submitted Gerrit changes (as per CI 3rd
+1 to this plan
> From the above, I would surmise that smoke tests should have all three of
> the following characteristics:
>
> * Test basic operations of an API, usually in a specific order that makes
> sense
> as a bare-bones use case of the API
> * Test only the correct action paths -- in o
tack-qa-team-bounces+john.garbutt=eu.citrix@lists.launchpad.net]
On Behalf Of Daryl Walleck
Sent: 02 April 2012 04:25
To: John Garbutt
Cc: openstack-xen...@lists.launchpad.net; openstack-qa-team@lists.launchpad.net
Subject: Re: [Openstack-qa-team] QA of XenServer features using Tempest
Hi John,
So
Including all XenAPI developers in the discussion.
From: John Garbutt
Sent: 29 March 2012 19:18
To: openstack-qa-team@lists.launchpad.net
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
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 som
11 matches
Mail list logo
