On Thu, 2016-09-08 at 10:36 +0200, Andreas Jaeger wrote:
>
> Toni, sorry, I wasn't clear. I'm not advocating for this, I wanted to
> bring Joe into this discussion to see whether the solution that John
> suggested will help them as well - I wanted to broaden the scope of
> this since it's not
Hi,
I am trying to run the EC2 tests in Tempest. On a devstack, here's what I run:
$ nosetests -sv tempest.thirdparty.boto.test_ec2_instance_run
SKIP: EC2 InstanceRunTest: requires ami/aki/ari manifest
--
Ran 0
: rahmu
On 24 Apr 2014, at 14:22, Sean Dague s...@dague.net wrote:
On 04/24/2014 07:39 AM, Joe Hakim Rahme wrote:
Hi,
I am trying to run the EC2 tests in Tempest. On a devstack, here's what I
run:
$ nosetests -sv tempest.thirdparty.boto.test_ec2_instance_run
SKIP: EC2 InstanceRunTest
On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote:
There are a number of patches up for review that make various changes to use
six apis instead of Python 2 constructs. While I understand the desire to
get a head start on getting Tempest to run in Python 3, I'm not sure it makes
I have only played with Glance v2 locally on a devstack, so take what I write
with a graing of salt.
What's new in API v2?
-
+ registry: You don't need to run glance-registry anymore. Unless you still
support v1.
+ tags: Every image has a tag list metadata. A tag can be
On 23 Dec 2013, at 21:16, Jeffrey Walton noloa...@gmail.com wrote:
I know Swift using RESTful services. Would you happen to know what
Ceph uses as its API?
For object storage Ceph has a component that implements both the Swift
API as well as AWS S3 API.
---
Joe H. Rahme
IRC: rahmu
On 06 Dec 2013, at 01:35, Sumit Gaur sumitkg...@gmail.com wrote:
Hi ,
I am a openstack user and I had faced a lot of problems in upgrading
my environment to newer versions of openstack releases. I need to know
if Openstack dev team is working on *smooth upgrade* process of
further release ?
I am in favor of class level exceptions for the obvious reasons:
+ It reduces code duplication. Copy/pasting a SkipIf decorator on every test
method in the class is tedious and possibly error prone. Adding the exception
as a guard in the setUpClass() makes for a more elegant solution
+
On 04 Dec 2013, at 17:05, Sean Dague s...@dague.net wrote:
That will require someone signing up to writing that though.
I could do that.
Since you know the code better than me, can you confirm that
tempest/test.py is the best place to define this decorator?
Thanks.
---
Joe H. Rahme
Thank you Sean.
In case someone checks this in the future, it's worth mentioning that any
new field added to the conf file has to be declared in tempest/config.py
first.
Joe
On Jul 12, 2013, at 8:26 PM, Sean Dague s...@dague.net wrote:
On 07/12/2013 02:15 PM, Joe Hakim Rahme wrote:
Hello
Hello,
I am trying to write a test in Tempest that would cover the behavior of
the Swift Account Quotas middleware. The use case I'm trying to cover
is that the test would create an account, put a quota on it, and try to
upload a file larger and a file smaller than the quota.
Here's what I have
Hello everyone,
I'm addressing this email to the dev list because I couldn't find a way
to get in touch with the testing team. Hopefully someone here will have
the answer to my question or can point me to the correct people to ask.
I am writing Tempest tests that cover the behavior of some
12 matches
Mail list logo
