-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev
into different patches.
Me too agree.
Thanks
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
DISCLAIMER
(200,
207), https://review.openstack.org/#/c/90655/ implement the test for that and
Schema for this API response validation should have multiple return code check.
Thanks
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
-house gate test fails),
response validation code
will be untested on gate.
My question is how I should go on these-
1. Should I wait for implementation of Branchless tempest to complete?
2. OK to merge even this is going to be untested on gate.
Thanks
Ghanshyam Mann
DISCLAIMER
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Ghanshyam Mann
On Mon, May 19, 2014 at 9:39 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Mon, May 19, 2014 at 9:12 PM, David Kranz dkr...@redhat.com wrote:
On 05/19/2014 01:24 PM, Frittoli, Andrea (HP Cloud) wrote:
Thanks for bringing this up.
We won't be testing v3 in Juno, but we'll
I agree to continue work on bp/ nova-api-test-inheritance. As its reduce
the duplication code and later will help to remove the V2 tests easily.
V2.1 tests can be written on same design of inheritance.
--
Thanks
Ghanshyam Mann
On Mon, May 19, 2014 at 9:32 PM, Kenichi Oomichi
oomi
).
To fix/stop these kind of issue, one solution is to have some policy for
Tempest not to name non test function with test_, Test_ etc so that nose
would not consider those as test case.
Looking forward to have more opinions on this.
--
Thanks
Ghanshyam Mann
idea.
On Fri, May 23, 2014 at 11:12 AM, Matthew Treinish mtrein...@kortar.orgwrote:
On Fri, May 23, 2014 at 09:34:35AM +0900, GHANSHYAM MANN wrote:
Tempest API’s XML test will run with 1 test failure when run with
Nosetest.
When we run the tempest with nosetest command (ex -nosetest –v
://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
Sent: Wednesday, November 26, 2014 7:58:06 AM
Subject: Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for
Tempest Core
+1
Am 22.11.2014 um 15:51 schrieb Andrea Frittoli
andrea.fritt...@gmail.com :
+1
On 21 Nov 2014 18:25, Ken1 Ohmichi ken1ohmi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
to add an item to the agenda.
To help people figure out what time 22:00 UTC is in other timezones
tomorrow's meeting will be at:
18:00 EDT
07:00 JST
07:30 ACST
0:00 CEST
17:00 CDT
15:00 PDT
--
Thanks Regards
Ghanshyam Mann
-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
.
People who want to help in bug triage, feel free to put your name in
https://etherpad.openstack.org/p/qa-bug-triage-rotation
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
. It looks something like -
https://review.openstack.org/#/c/162016/
--
Thanks Regards
Ghanshyam Mann
On Fri, Mar 6, 2015 at 7:00 AM, Sean Dague s...@dague.net wrote:
On 03/04/2015 07:48 PM, GHANSHYAM MANN wrote:
Hi Sean,
Yes having V3 directory/file names is very confusing now.
But current v3
config.
1- ERROR (BadRequest): Block Device Mapping is Invalid: You specified more
local devices than the limit allows (HTTP 400) (Request-ID: req-3ef100c7-
b5c5-4a2d-a5da-8344726336e2)
--
Thanks Regards
Ghanshyam Mann
free to put your name in
https://etherpad.openstack.org/p/qa-bug-triage-rotation
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List
)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage
/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On Fri, Jun 26, 2015 at 3:43 PM, Dmitry Tantsur divius.ins...@gmail.com wrote:
26 июня 2015 г. 2:47 пользователь GHANSHYAM MANN ghanshyamm...@gmail.com
написал:
On Sat, Jun 20, 2015 at 9:14 AM, Devananda van der Veen
devananda@gmail.com wrote:
Almost all of our discussions so far
On Fri, Jun 26, 2015 at 3:46 PM, Dmitry Tantsur divius.ins...@gmail.com wrote:
26 июня 2015 г. 2:48 пользователь GHANSHYAM MANN ghanshyamm...@gmail.com
написал:
On Thu, Jun 25, 2015 at 5:18 PM, Ken'ichi Ohmichi ken1ohmi...@gmail.com
wrote:
Sorry for late response here,
2015-06-20 9:14
)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
(not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
__
OpenStack
ackalytics.com/?module=nova-group_id=xuhj=all
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinf
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Thanks Regards
Ghanshyam Mann
lient/+bug/1491325
https://bugs.launchpad.net/nova/+bug/1491511
[2]: http://developer.openstack.org/api-ref-compute-v2.1.html#attachVolume
--
Thanks & Regards
Ghanshyam Mann
__
OpenStack Development Mailing List (not for usage
to the agenda.
To help people figure out what time 9:00 UTC is in other timezones,
meeting will be at:
04:00 EDT
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
--
Thanks & Regards
Ghanshyam Mann
__
OpenStack Develop
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
--
Regards
Ghanshyam Mann
+81-8084200646
r-m...@cq.jp.nec.com> wrote:
> Hi Ghanshyam,
>
>
>
> Thanks for your response.
>
> It seems that I'm headed in the right direction.
>
> One more question. - Should we migrate from 'service_client' to 'rest_client'
> in tempest-lib?
>
>
>
> Best regards,
> Ryota
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Regards
Ghanshyam Mann
+81-8084200646
iew.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/consistent-service-method-names,n,z
>>
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: opensta
;
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ck.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.
.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
https://github.com/openstack/tempest/blob/master/tempest/api/compute/admin/test_keypairs_v210.py
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> __
>
> OpenStack Development Mailing List (not for usage questio
Big +1 for that which makes pre-provisioned cred testing more thoroughly.
And at the end we should divide the existing jobs among dynamic and
pre-provisioned account so that we would not leave any of them less tested.
Thanks
gmann
From: Andrea Frittoli [mailto:andrea.fritt...@gmail.com]
Sent:
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
On Wed, Jun 15, 2016 at 6:12 AM, Matthew Treinish wrote:
> On Tue, Jun 14, 2016 at 12:19:54PM -0700, Chris Hoge wrote:
>>
>> > On Jun 14, 2016, at 11:21 AM, Matthew Treinish
>> > wrote:
>> >
>> > On Tue, Jun 14, 2016 at 10:57:05AM -0700, Chris Hoge
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
Regards
Ghanshyam Mann
On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu <sou...@gmail.com> wrote:
> If we support 2.x.y, when we bump 'x' is a problem. We didn't order the API
> changes for now, the version of API change is just based on the order of
> patch merge. For support 2.x.y,
/openstack/ec2-api
Regards
Ghanshyam Mann
On Tue, Feb 16, 2016 at 11:24 AM, Anne Gentle <annegen...@justwriteclick.com
> wrote:
>
>
> On Mon, Feb 15, 2016 at 6:03 PM, 少合冯 <lvmxhs...@gmail.com> wrote:
>
>> I guess others may ask the same questions.
>>
>> I
+1 Sounds good to separate those to different repo.
Regards
Ghanshyam Mann
On Wed, Feb 17, 2016 at 4:55 AM, Matthew Treinish <mtrein...@kortar.org> wrote:
> On Fri, Feb 12, 2016 at 10:21:53AM +0100, Koderer, Marc wrote:
>> I know that there are folks around that are using it
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
Thanks Matt for your great leadership and hardwork around QA world.
It has been great working in your leadership and provided a smooth &
cool environment during
those period.
There lot of key things we achieved and with diversity of ideas. You
have been always very active
and present to help
Thanks a lot John for great leadership and all achievements. You have
been very encouraging and helpful always.
Regards
Ghanshyam Mann
On Sat, Mar 12, 2016 at 4:22 AM, John Garbutt <j...@johngarbutt.com> wrote:
> Hi,
>
> It has been greatly rewarding serving you all a
On Thu, Mar 31, 2016 at 10:39 AM, Matt Riedemann
wrote:
>
>
> On 3/30/2016 8:20 PM, Matt Riedemann wrote:
>>
>>
>>
>> On 3/30/2016 7:56 PM, Matt Riedemann wrote:
>>>
>>>
>>>
>>> On 3/30/2016 7:38 PM, Matt Riedemann wrote:
On 2/25/2016 5:31 AM,
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
+1, That make sense.
Also as Ceilometer and Aodh will be running tests from plugin, I have
initiated patch to remove those from Tempest.
- https://review.openstack.org/#/c/304992/
Regards
Ghanshyam Mann
+818011120698
On Tue, Apr 12, 2016 at 9:47 PM, Chris Dent <cdent...@anticdent.org>
configuration in detail-
http://docs.openstack.org/developer/tempest/configuration.html
Regards
Ghanshyam Mann
On Tue, Apr 12, 2016 at 2:46 PM, Anusha Ramineni <anusha.ii...@gmail.com> wrote:
> Hi Bryan,
>
> Yes, tempest can be run outside devstack deployments. Please check the
&g
On Fri, Mar 18, 2016 at 9:06 AM, Ken'ichi Ohmichi wrote:
> 2016-03-17 4:05 GMT-07:00 Andrea Frittoli :
>> On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi
>> wrote:
>>>
>>> 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen
On Thu, Mar 17, 2016 at 3:24 PM, Kairat Kushaev wrote:
>
> Also curious about this. It seems weird to separate the 'positive' and
> the 'negative' ones, assuming those patches are mostly contributed by
> the same group of developers.
>
>
> Yeah, agree. This approach leads
redirect API services at top level top and do
what all conversion, consume difference etc.
[1] https://github.com/aviator/aviator
Regards
Ghanshyam Mann
On Wed, Mar 16, 2016 at 9:58 PM, zs <okay22m...@163.com> wrote:
> Hi Gordon,
>
> Thank you for your suggestion.
>
> I thin
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
://docs.openstack.org/developer/nova/
Regards
Ghanshyam Mann
On Tue, Apr 5, 2016 at 6:49 PM, Shashi Kant
<shashi.k...@nectechnologies.in> wrote:
> Dear All,
>
>
>
> I am newbie for openstack development and trying to understand the flow
> using code base.
>
> As the code base
On Thu, Mar 31, 2016 at 4:47 AM, Matthew Treinish wrote:
> On Wed, Mar 30, 2016 at 03:26:13PM -0400, Sean Dague wrote:
>> During the Nova API meeting we had some conversations about priorities,
>> but this feels like the thing where a mailing list conversation is more
>>
that on tempest patch.
..[1] https://review.openstack.org/#/c/299830/1
On Thu, Mar 31, 2016 at 11:29 AM, Matt Riedemann
<mrie...@linux.vnet.ibm.com> wrote:
>
>
> On 3/30/2016 9:14 PM, GHANSHYAM MANN wrote:
>>
>> On Thu, Mar 31, 2016 at 10:39 AM, Matt Riedemann
>> &
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the
next meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Regards
Ghanshyam Mann
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the next
meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Thanks & Regards,
Ghanshyam
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: 27 July 2016 02:36
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [nova] Next steps for proxy API deprecation
>
>
Thanks Matt for bringing this up.
On Thu, Jul 14, 2016 at 11:55 AM, Matt Riedemann
wrote:
> There are several changes in Tempest right now trying to add response schema
> validation for the 2.26 microversion which added server tags to the server
> GET response. This
On Thu, Jul 14, 2016 at 12:08 PM, Matthew Treinish wrote:
> On Wed, Jul 13, 2016 at 09:55:33PM -0500, Matt Riedemann wrote:
>> There are several changes in Tempest right now trying to add response schema
>> validation for the 2.26 microversion which added server tags to the
> -Original Message-
> From: Andrew Laski [mailto:and...@lascii.com]
> Sent: 04 August 2016 22:18
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Some thoughts on API microversions
>
>
>
> On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote:
> > On
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
Sorry for delay in mail.
To help people figure out what time 9:00 UTC is in other timezones the next
meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Thanks & Regards,
Ghanshyam
ween the QA team
> and a project team: https://bugs.launchpad.net/glance/+bug/1656183,
> https://review.openstack.org/#/c/420038/,
> https://review.openstack.org/#/c/425487/
>
> I have myself no strong opinion on the matter, that why I need a leader
> here :)
>
> Note,
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Jan 9th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
Thanks Alex for writing in details.
On Tue, Jan 24, 2017 at 6:05 PM, Alex Xu wrote:
> Unfortunately the device tag support in the API was broken in the old
> Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks
> to Kevin Zheng to find out that.
>
>
Sorry, forgot to mention tempest patch -
https://review.openstack.org/#/c/424572/1 (but broken cases seems clear
without that patch also)
Regards
Ghanshyam Mann
+818011120698
On Tue, Jan 24, 2017 at 7:34 PM, Ghanshyam Mann <ghanshyamm...@gmail.com>
wrote:
> Thanks Alex for writing i
On Sun, Jan 29, 2017 at 10:12 AM, Alex Xu wrote:
>
>
> 2017-01-29 1:31 GMT+08:00 Matt Riedemann :
>
>> On 1/27/2017 3:37 AM, Alex Xu wrote:
>>
>>> The patches about validation the filters and sorts for servers API are
>>> merged [0]. But we still have
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Jan 26th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
*
On Wed, Jan 25, 2017 at 1:18 AM, Matt Riedemann wrote:
> On 1/24/2017 2:05 AM, Alex Xu wrote:
>
>> Unfortunately the device tag support in the API was broken in the old
>> Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks
>> to Kevin Zheng to find out
> -Original Message-
> From: Hayes, Graham [mailto:graham.ha...@hpe.com]
> Sent: 23 February 2017 03:25
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [qa] Tempest Stable plugin interface change
>
r destructive testing of OpenStack cloud is on
> review
> >> [1].
> >> 2) The spec for a new framework which will focus on HA/failover and
> >> destructive testing is no review [2].
> >> 3) The commit for the new repository is on review [3] as well.
> >
Hi All,
First and foremost would like to wish you all a successful 2017 ahead and with
this I'm announcing my PTL candidacy of the Quality Assurance team for the Pike
release cycle.
I am glad to work in OpenStack community and would like to thank all the
contributors who supported me to
Yea, manage snapshot tests should be skipped on ceph backend.
I disabled those tests for *-ceph-* jobs and glance-store will be unblocked
after that merged.
- https://review.openstack.org/#/c/421073/
There is discussion going on whether to enable the manage snapshot false by
default on
Or how about just disable the flag which will skip snapshot manage tests
for CI where it should not run.
Flag in Devtsack is TEMPEST_VOLUME_MANAGE_SNAPSHOT which can be set to
False on CI.
I added the same on ceph gate jobs [1] and similarly can be added on CI
side if ok?
..1
On Tue, Jan 17, 2017 at 2:37 PM, Alex Xu wrote:
>
>
> 2017-01-17 10:26 GMT+08:00 Matt Riedemann :
>
>> On 1/16/2017 7:12 PM, Zhenyu Zheng wrote:
>>
>>> Hi Nova,
>>>
>>> I just discovered something interesting, the tag has a limited length,
>>> and in
Thanks Kenichi for all your hardwork and nice leadership.
Its been very good and lot of things we finished under your leadership. You
managed all the activities in a very cool and polite way (Japanese style
:)).
-gmann
On Fri, Jan 20, 2017 at 4:16 AM, Ken'ichi Ohmichi
For other failure on "expected_attr" error, we need this to merge -
https://review.openstack.org/#/c/422323/ on nova side.
-gmann
> -Original Message-
> From: Matt Riedemann [mailto:mriede...@gmail.com]
> Sent: 20 January 2017 12:17
> To: openstack-dev@lists.openstack.org
> Subject:
Yea, there is no doubt we should refactor scenario tests but even those are
internal interface it breaks plugins. We can argue that plugins should not
be using those but before that tempest should have all required
interface/class/helper as stable interface for plugins. which is what
scenario
Doing gradual refactoring and fixing plugins time to time needs lot of wait
and sync.
That needs:
1. Plugins to switch from current method usage. Plugins to have some other
function or same copy paste code what current scenario base class has.
2. Tempest patch to wait for plugin fix.
3. Plugins
.280900_UTC.29
Anyone is welcome to add an item to the agenda.
To help people figure out what time 9:00 UTC is in other timezones the next
meeting will be at:
04:00 EST
18:00 JST
18:30 ACST
11:00 CEST
04:00 CDT
02:00 PDT
Thanks & Regards,
Ghanshyam
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday,
Oct 20th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
Thanks a lot alaski for your incredible contribution in Nova. You were a great
learning guide and mentor.
Very best of luck for your new responsibility and hoping to work together in
community again.
Thanks & Regards,
gmann
> -Original Message-
> From: Andrew Laski
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday,
Nov 17th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
I like os-faults library which can provide the abstraction over different
destructive actions like reboot/poweroff node etc.
But not much clear about Stepler that what all tests it will contain. Tempest
do have scenario tests which can hit the production env with significant way of
testing
do not prefer of adding the automapping in tempest side.
[1] will fix the issue and unblock the sahara tests. And I saw sahara plugin
is also branchless so should be ok with just this patch ?
..1 - https://review.openstack.org/#/c/385701/
Thanks & Regards,
Ghanshyam Mann
> -O
Hi All,
Recently all gate heat gate jobs were switched to use heat devstack plugin
and heat code was removed from devstack tree.
During that tempest layer 4 job is missed and blocked the tempest gate[1].
Also another heat job had issue for enabling plugin [2].
Fixes are up for both job fix,
1 - 100 of 349 matches
Mail list logo