I'm testing against a bare metal installation of Openstack and since a few days
ago, an instance of Devstack as well. My team and I are mostly running Tempest
from OSX or Ubuntu. Some of the clutter in the Tempest project is due to a
merge of many projects to one. There are still some legacy por
On 2/27/2012 3:02 PM, Dean Troyer wrote:
On Mon, Feb 27, 2012 at 10:13 AM, Daryl Walleck
wrote:
I'm working on updating this document as I'm using Devstack so that I can
either smooth
over or enumerate issues that may come up when running the tests. If you run
into
anything though, please
On 2/27/2012 3:02 PM, Dean Troyer wrote:
On Mon, Feb 27, 2012 at 10:13 AM, Daryl Walleck
wrote:
I'm working on updating this document as I'm using Devstack so that I can
either smooth
over or enumerate issues that may come up when running the tests. If you run
into
anything though, please
Please note that the patch that fixes the Catalog name/type is now in
Tempest trunk.
Thanks,
-jay
On 02/27/2012 01:27 PM, Eoghan Glynn wrote:
1. Add catalog_name=compute to tempest.conf
2. Change "name" to "type" in rest_client.py
Yep, easiest to just apply this patch:
git fetch https:/
On 02/27/2012 11:13 AM, 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 devstack.
Actually, devstack + keystone redux... we've been having some weird
issues preventing us
On Mon, Feb 27, 2012 at 10:13 AM, Daryl Walleck
wrote:
> I'm working on updating this document as I'm using Devstack so that I can
> either smooth
> over or enumerate issues that may come up when running the tests. If you run
> into
> anything though, please make a report to the Tempest project
On Mon, Feb 27, 2012 at 9: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 devstack. I've made some merge prop
I have been using devstack and tempest quite well. There is a script in
tempest that will convert the devstack-created configuration to a
tempest.conf file. The thing that really got me over the hump was Jay's
writeup:
https://docs.google.com/a/qrclab.com/presentation/d/1M3XhAco_0u7NZQn3Gz53z9
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
> 1. Add catalog_name=compute to tempest.conf
> 2. Change "name" to "type" in rest_client.py
Yep, easiest to just apply this patch:
git fetch https://review.openstack.org/p/openstack/tempest
refs/changes/59/4259/1 && git format-patch -1 --stdout FETCH_HEAD
Cheers,
Eoghan
___
On Mon, Feb 27, 2012 at 7:49 AM, David Kranz wrote:
>
> There is still a bug in tempest and/or keystone. To run Tempest and devstack
> you have to:
>
> 1. Add catalog_name=compute to tempest.conf
> 2. Change "name" to "type" in rest_client.py
>
>
You can also use:
catalog_name = 'Compute Servic
> Right now I'm having trouble setting up running the tests against
> devstack (a configuration problem on my part I suppose, but I blame
> it on the lack of documentation).
Hi Ionut,
I'm currently working on getting tempest running on Fedora 16.
I'll follow up here with a recipe once I have
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 devstack.
I've made some merge prop's that will take care of a few of the issues. One
issue that wil
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
There is still a bug in tempest and/or keystone. To run Tempest and
devstack you have to:
1. Add catalog_name=compute to tempest.conf
2. Change "name" to "type" in rest_client.py
-David
On 2/27/2012 8:18 AM, Ionuț Arțăriși wrote:
On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:4
On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the T
On 02/22/2012 07:17 PM, Jay Pipes wrote:
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the T
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite rea
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite ready yet.
-Jim
David Kranz writes:
> There is
enstack-bounces+daryl.walleck=rackspace@lists.launchpad.net] on behalf
of David Kranz [david.kr...@qrclab.com]
Sent: Wednesday, February 22, 2012 8:24 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] running Tempest continuously in the openstack project?
There is curren
There is currently a bug https://bugs.launchpad.net/tempest/+bug/933845
that will prevent tempest from working with keystone. That ticket
provides a workaround but still not all of the tests are working at the
moment. I think the goal is for tempest to become actively run but we
are not there
Hello,
I'm trying to get started with Tempest and I would really like to be
able to see a running setup somewhere. I'm getting a lot of tests
failing and I don't know if it's because of my setup or because of bugs
in Tempest or incompatibilities with the current code in the other
components.
22 matches
Mail list logo
