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 heav
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 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
To: "openstack-qa-t...@lists.l
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 p
Hey Jay,
I'm seeing the same incorrect messaging. From what I've observed, this happens
when you exceed your quota. The failure is right but the message is wrong. I
opened a bug for this last week.
https://bugs.launchpad.net/nova/+bug/1006218
Original message
Subject: [Ope
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
(jayp
s possible.
Tim
From:
openstack-bounces+tim.simpson=rackspace@lists.launchpad.net<mailto:openstack-bounces+tim.simpson=rackspace@lists.launchpad.net>
[openstack-bounces+tim.simpson=rackspace@lists.launchpad.net<mailto:openstack-b
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 s
lementing the
clients for the sake of testing accomplish? Double 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 a
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 in
having.
Daryl
On Feb 27, 2012, at 11:03 AM, Ionuț Arțăriși wrote:
> On 02/27/2012 05:13 PM, Daryl Walleck wrote:
>> 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
>&
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 configure
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 li
Just a brief note, but the Swift QE guys are going to have their tests in
Tempest in the near future. I'm helping them work through getting it ready.
Daryl
From: openstack-bounces+daryl.walleck=rackspace@lists.launchpad.net
[openstack-bounces+daryl.wa
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 comprehensiv
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
Hi Gabe,
I think what Nachi is saying is that these parameters can be taken in a create
request, but are not documented (I say this also because I've seen this in
novaclient as well). I know they're not required, but I'm curious what their
purpose is.
Daryl
On Dec 2, 2011, at 12:16 PM, Gabe
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 Gen
stack-bounces+donald.ngo=hp@lists.launchpad.net<mailto:openstack-bounces+donald.ngo=hp@lists.launchpad.net>
[mailto:openstack-bounces+donald.ngo=hp@lists.launchpad.net<mailto:hp@lists.launchpad.net>]
On Behalf Of Brebner, Gavin
Sent: Wednesday, October 1
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 APIs,
20 matches
Mail list logo