Hi,
please note that the openstack-qa distribution list is not used anywhere, we
only keep it for periodic tests notifications.
You should use openstack-dev instead.
Documentation is available at [0] and in the sample file [1].
Tempest configuration is uploaded to logs after each CI job - see
Thank you everyone for your votes and your trust.
I'm proud to join the tempest core team!
Andrea
Sent from my tiny device
Matthew Treinish wrote
So all of the current core team members have voted unanimously in favor of
adding Andrea to the team.
Welcome to the team Andrea.
-Matt
++
The ugly monkey patch approach is still working fine for my downstream
testing, but that's something I'd be happy to get rid of.
Something that may be worth considering is to have an abstraction layer on top
of tempest clients, to allow switching the actual implementation below:
- REST
There's a spec in progress related to this, I'd love to see your comments in
there:
https://review.openstack.org/#/c/94741/
Andrea
Sent from my tiny device
Daryl Walleck wrote
I really like this option, especially if it leaves a generic hook available for
validation. This could
+1, I would remove them as well, assignee and milestone probably do not need
to go through review, it something we can agree upon at QA meetings.
andrea
-Original Message-Cl@ud3D3bu$$y
From: David Kranz [mailto:dkr...@redhat.com]
Sent: 11 June 2014 20:18
To: OpenStack Development
Hi Ajaya,
Thanks for offer to help :)
Are you talking about tempest tests or in-tree keystone tests?
Verifying custom roles can be challenging via API only driven tests such as
tempest – as it requires to have the policies configured accordingly in the
cloud under test (i.e.
Thanks for bringing this up.
We won't be testing v3 in Juno, but we'll need coverage for v2.1.
In my understanding will be a v2 compatible API - so including proxy to
glance cinder and neutron - but with micro-versions to bring in v3 features
such as CamelCase and Tasks.
So we should be able to
From: Adam Young [mailto:ayo...@redhat.com]
Sent: 09 May 2014 04:19
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Hierarchical administrative boundary [keystone]
On 05/08/2014 07:55 PM, Tiwari, Arvind wrote:
Hi All,
Below is my proposal to address VPC use case using
Is there a bp to coordinate work on aligning all clients to the Session object?
Having a consistent implementation would make users and developers life so much
easier – not to mention QA :)
andrea
From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: 08 May 2014 21:55
To: OpenStack
I started an etherpad for people to put down QA topics we could discuss during
the summit at lunch or over a beer
https://etherpad.openstack.org/p/juno-summit-open-topics
Feel free to add anything that needs some good face to face brainstorming :)
andrea
--
Andrea Frittoli
QA
I will arrive Sunday late.
If you meet on Monday I’ll see you there ^_^
From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: 01 May 2014 17:28
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [qa] QA Summit Meet-up Atlanta
I arrive Sunday
In the QA meeting yesterday, we discussed about accounts, admin roles and
policies, and how we use them in tempest and in our test environments (e.g.
devstack and toci).
The conversation was triggered by a discussion on running tempest without admin
credentials – see [0], [1].
So we are
This is another example of achieving the same result (exclusion from a
list):
https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/element
s/tempest/tests2skip.py
https://git.openstack.org/cgit/openstack/tripleo-image-elements/tree/element
s/tempest/tests2skip.txt
andrea
Thanks David, +++
This is a strong dependency to devstack, and it would be nice if we could
lose it.
andrea
-Original Message-
From: David Kranz [mailto:dkr...@redhat.com]
Sent: 20 February 2014 21:32
To: OpenStack Development Mailing List
Subject: [openstack-dev] [qa] Does
Hi,
thanks for the update
Link to the tempest bp I’m working on:
https://blueprints.launchpad.net/tempest/+spec/multi-keystone-api-version-tests
The update of the python binding to use the keystone binding is targeted for
icehouse or juno?
andrea
From: Dolph Mathews
15 matches
Mail list logo
