Hi Rohit,
I'm glad to see so much interest in getting testing done right. So here's my
thoughts. As far as the nova client/euca-tools portion, I think we absolutely
need a series of tests that validate that these bindings work correctly. As a
nice side effect they do test their respective
Hi everyone,
This is just my opinion, but I've only found WADLs very useful when use tool
based automation. To me they're a huge headache to read. To me, the current dev
guide style of documentation has been far more helpful in developing automation.
Daryl
On Oct 25, 2011, at 3:24 PM, Anne
That time still works for me. Would be starting that this week (tomorrow)?
Daryl
On Feb 21, 2012, at 1:45 PM, Jay Pipes wrote:
Hi QA Team,
Unfortunately, I have another meeting happening at the same time as our
weekly IRC meeting in #openstack-meeting, and it's a meeting I really need to
We're running Tempest as part of our continuous build. For the bug you're
referring to David, there is a configuration in Tempest where the name of the
Nova/Compute project can be set, so I don't think its fair to say that Tempest
is currently broken. However, I am working on a more
I'm actively looking into any issues. I have all these tests passing locally in
my environment, so the issues seem to be focused around people using devstack.
I've made some merge prop's that will take care of a few of the issues. One
issue that will certainly come up is that if you have rate
This isn't really a bug in either project, but a configuration issue. The name
of the endpoint isn't static, so making it 'nova' or 'compute' may not always
be correct. If you check the name of your Compute project that's returned in
the Keystone auth request, you can find the name and
So my first question is around this. So is the claim is that the client tools
are the default interface for the applications? While that works for coders in
python, what about people using other languages? Even then, there's no
guarantee that the clients in different languages are implemented
the maintenance effort for
the same result, imho.
Cheers,
Maru
On 2012-05-03, at 12:54 PM, Daryl Walleck wrote:
So my first question is around this. So is the claim is that the client tools
are the default interface for the applications? While that works for coders in
python, what about people
This is great news! Thanks Jay for all the hard work you've put into getting
this up and running.
Daryl
On May 4, 2012, at 8:34 AM, Jay Pipes wrote:
All,
A momentous event has occurred. We now have all Tempest integration tests
passing against the devstack-deployed test environment spun
-bounces+tim.simpson=rackspace@lists.launchpad.netmailto:openstack-bounces+tim.simpson=rackspace@lists.launchpad.net
[openstack-bounces+tim.simpson=rackspace@lists.launchpad.netmailto:openstack-bounces+tim.simpson=rackspace@lists.launchpad.net]
on behalf of Daryl Walleck
[daryl.wall
Weekly team meeting
The OpenStack QA Team holds public weekly meetings in #openstack-meeting,
Thursday at 13:00 EST (17:00 UTC). Everyone interested in testing, quality
assurance, performance engineering, etc, should attend!
Agenda for next meeting
* Review of last week's action items
The weekly QA Team meeting takes place at 17:00 UTC on IRC (#openstack-meeting
on Freenode). We invite anyone interested in testing, quality assurance and
performance engineering to attend the weekly meeting.
The agenda for this week is as follows:
* Status of Swift tests (Jose)
* Status of
I can verify that rescue is a non-race state. The transition is active to
rescue on setting rescue, and rescue to active when leaving rescue.
Original message
Subject: Re: [Openstack-qa-team] wait_for_server_status and Compute API
From: Jay Pipes jaypi...@gmail.com
To:
As part of my work on Tempest, I've created an alternate backend configuration
to use XML requests/responses. This right now mostly covers Nova, but could
easily be extended to test other projects as well. I hadn't pushed it yet
because it seemed to be low priority, but I'd be more than glad to
I certainly use them daily. I actually use an interesting wrapper called
Supernova (http://rackerhacker.github.com/supernova/) which allows for
multi-user/multi-environment configurations. While the clients may not be as
critical as the APIs themselves, they're something I certainly rely on
Good question. We had a discussion awhile back on whether SSHing into an
instance broke the line between black and white box testing. We had people on
both sides, but the discussion was tabled for a bit while we dealt with other
issues. It's definitely something I'd like to talk about again.
I've heard KVM/libvert support was added in Essex. I can confirm resize is
still working with Xen Server, so the issue must be with those implementations.
Daryl
On Feb 24, 2012, at 2:58 PM, David Kranz wrote:
I am not sure why the resize tests are failing but there is an error in the
I think what you mention is a good test. However, I wouldn't be able to run it
in most of my test environments. Maybe there should be an invalidate token
admin API functionality? I could see reasons for wanting it for functional
reasons, and would still allow you to write a test like this.
the maintenance effort for
the same result, imho.
Cheers,
Maru
On 2012-05-03, at 12:54 PM, Daryl Walleck wrote:
So my first question is around this. So is the claim is that the client tools
are the default interface for the applications? While that works for coders in
python, what about people
-bounces+tim.simpson=rackspace@lists.launchpad.netmailto:openstack-bounces+tim.simpson=rackspace@lists.launchpad.net
[openstack-bounces+tim.simpson=rackspace@lists.launchpad.netmailto:openstack-bounces+tim.simpson=rackspace@lists.launchpad.net]
on behalf of Daryl Walleck
[daryl.wall
Weekly team meeting
The OpenStack QA Team holds public weekly meetings in #openstack-meeting,
Thursday at 13:00 EST (17:00 UTC). Everyone interested in testing, quality
assurance, performance engineering, etc, should attend!
Agenda for next meeting
* Review of last week's action items
The weekly QA Team meeting takes place at 17:00 UTC on IRC (#openstack-meeting
on Freenode). We invite anyone interested in testing, quality assurance and
performance engineering to attend the weekly meeting.
The agenda for this week is as follows:
* Status of Swift tests (Jose)
* Status of
I can verify that rescue is a non-race state. The transition is active to
rescue on setting rescue, and rescue to active when leaving rescue.
Original message
Subject: Re: [Openstack-qa-team] wait_for_server_status and Compute API
From: Jay Pipes jaypi...@gmail.com
To:
While I was doing some assorted maintenance on the Nova tests tonight, I
noticed some inconsistencies in the license header of time files. While most
attribute the work to OpenStack, LLC, I also see some where IBM is mentioned
instead. I'm guessing this might be a copy/paste error, or are
Gotcha, that makes sense. Thanks!
Daryl
From: annegen...@justwriteclick.com [annegen...@justwriteclick.com] on behalf
of Anne Gentle [a...@openstack.org]
Sent: Wednesday, October 10, 2012 10:28 PM
To: Daryl Walleck
Cc: openstack-qa-team
Hi everyone,
After our discussions earlier today about being more vocal about what's being
worked on, I wanted to raise awareness of what I'm currently working to avoid
duplication of efforts. This is the first blueprint I've submitted, so if
there's any additional detail that I'm missing, I'm
26 matches
Mail list logo
