t; > 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/listi
he response object is accessible if needed to examine headers.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/m
On Tue, 06 Nov 2018 05:50:03 +0900 Dmitry Tantsur
wrote
>
>
> On Mon, Nov 5, 2018, 20:07 Julia Kreger *removes all of the hats*
> *removes years of dust from unrelated event planning hat, and puts it on for
> a moment*
>
> In my experience, events of any nature where conve
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
Un
Thanks Jens.
As most of the base jobs are in QA repo, QA team will coordinate this migration
based on either of the approach mentioned below.
Another point to note - This migration will only target the zuulv3 jobs not the
legacy jobs. legacy jobs owner should migrate them to bionic when they w
On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski
wrote
> Hi,
>
> > Wiadomość napisana przez Jeremy Stanley w dniu
> > 06.11.2018, o godz. 22:25:
> >
> > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> > [...]
> >> also add jobs like "devstack-xenial
On Wed, 07 Nov 2018 07:07:33 +0900 Clark Boylan
wrote
> On Tue, Nov 6, 2018, at 2:02 PM, Ghanshyam Mann wrote:
> > Thanks Jens.
> >
> > As most of the base jobs are in QA repo, QA team will coordinate this
> > migration based on either of t
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
- TC
__
OpenStack Development Mailing List (not for usage questions)
Uns
Hello everyone,
Along with project updates & onboarding sessions, QA team will host QA feedback
sessions in berlin summit. Feel free to catch us next week for any QA related
questions or if you need help to contribute in QA (we are really looking
forward to onbaord new contributor in QA).
Be
2018 11:02:54 +0900 Ghanshyam Mann
wrote
> Hello everyone,
>
> Along with project updates & onboarding sessions, QA team will host QA
> feedback sessions in berlin summit. Feel free to catch us next week for any
> QA related questions or if you need help to contr
List (not for usage questions)" <
> openstack-dev@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
>>>> used for gating job definitions and just call the new entry-point
>>>> instead of
>>>> testr directly.
>>>>
>>>> >
>>>> > BR,
>>>> > Angelo
>>>> >
>>>> > [1]
>>>> http://docs.o
___
> 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
me 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
nd the combination in the same patch >would make reviews
>difficult. In current Nova API test implementations, we are separating them
>into different patches.
Me too agree.
Thanks
Ghanshyam Mann
_
heck at client side in JSON schema.
Currently we do not have any schema validation of any such API which return
multiple success code.
For example server external events API returns multiple success code (200,
207), https://review.openstack.org/#/c/90655/ implement the test for that and
Schema for th
#/c/85666/ adds the response validation for
this API in tempest.
As API tempest tests are skipped (cannot unskip as ice-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 tem
the
same. I have put this in review comment also.
>
>
> >
> > I hope we can get agreement to move response checking to the client.
> > There was no opposition when we started doing this in nova to check
> > schema. Does any one see a reason to not do this? It would both
> > simplify the code and make sure responses are checked in all cases.
> >
> > Sean, do you have a concrete example of what you are concerned about
> > here? Moving the check from the value returned by a client call to
> > inside the client code should not have any visible effect unless the
> > value was actually wrong but not checked by the caller. But this would
> > be a bug that was just found if a test started failing.
> >
>
> Please draft a spec/bp for doing this, we can sort out the implementation
> details in the spec review. There is definitely some overlap with the
> jsonschema work though so we need to think about how to best integrate
> the 2 efforts. For example, for projects that don't use jsonschema yet
does it
> make sense to start using jsonschema files like we do for nova tests to
veriy
> the status codes. Just so we can have a common path for doing this. I
think
> there may be value in doing it that way. We can discuss it more during the
> jsonschema summit session.
>
>
> -Matt Treinish
--
Thanks & Regards
Ghanshyam Mann
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
n 2 days.
> >
> > (Gerrit Query: status:open label:Verified>=1,jenkins NOT
> > label:Workflow<=-1 NOT label:Code-Review<=2 age:2d)
> >
> >
> > In all cases it filters out patches that you've commented on in the most
> > recently revision. So as you vote on th
Ghanshyam Mann
On Mon, May 19, 2014 at 9:39 PM, Christopher Yeoh wrote:
> On Mon, May 19, 2014 at 9:12 PM, David Kranz wrote:
>
>> On 05/19/2014 01:24 PM, Frittoli, Andrea (HP Cloud) wrote:
>>
>> Thanks for bringing this up.
>>
>> We won't be testin
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
wrote:
> Hi Da
t implemented (as expected).
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
idea.
On Fri, May 23, 2014 at 11:12 AM, Matthew Treinish wrote:
> 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
consistency.
If *strictly* testing, we should not have any wait for 204 response. If any
operation still in progress and return 204 then its a false return and
tempest should be able to catch those as it can break user app also.
Tempest should report fail so that specific project can fi
27;d be willing to head up the working group... or at least
> participate in it.
>
> Best,
> -jay
>
> _______
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-
>>> "/opt/stack/tempest/tempest/services/volume/json/snapshots_client.py", line
>>> 126, in wait_for_snapshot_status
>>> > value = self._get_snapshot_status(snapshot_id)
>>> > File
>>> "/opt/stack/tempest/tempest/services/volume/json/snapshots_client.py", line
>>> 99, in _get_snapshot_status
>>> > snapshot_id=snapshot_id)
>>> > SnapshotBuildErrorException: Snapshot
>>> 6b1eb319-33ef-4357-987a-58eb15549520 failed to build and is in
>>> > ERROR status
>>>
>>> What happens if running the same operation as Tempest by hands on your
>>> environment like the following ?
>>>
>>> [1] $ cinder create 1
>>> [2] $ cinder snapshot-create
>>> [3] $ cinder create --snapshot-id 1
>>> [4] $ cinder show
>>>
>>> Please check whether the status of created volume at [3] is "available"
>>> or not.
>>>
>>> Thanks
>>> Ken'ichi Ohmichi
>>>
>>> ___
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openst...@lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>
>>
>
> ___
> 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/cgi-bin/mailman/listinfo/openstack-dev
ment.
> >
> > Of course it would be in Gerrit. I just put it up on GitHub first
> > because I can't just add a repo into the openstack/ code
> > namespace... :)
>
> I've submitted a patch to add an api-wg project using your repository
> as the initial cont
_
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listi
s.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> htt
.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
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: 15
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 wrote:
>> >> Last year, in response to Nova mic
.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
aster/tempest/api/compute/keypairs/test_keypairs.py#L22
3 ..
https://github.com/openstack/tempest/blob/master/tempest/api/compute/admin/test_keypairs_v210.py
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
> __
> ___
.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
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, Takashi Natsume wrote:
>
>
tempest patch.
..[1] https://review.openstack.org/#/c/299830/1
On Thu, Mar 31, 2016 at 11:29 AM, Matt Riedemann
wrote:
>
>
> On 3/30/2016 9:14 PM, GHANSHYAM MANN wrote:
>>
>> On Thu, Mar 31, 2016 at 10:39 AM, Matt Riedemann
>> wrote:
>>>
>>>
>&
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
>> inclusive to get agreement
://docs.openstack.org/developer/nova/
Regards
Ghanshyam Mann
On Tue, Apr 5, 2016 at 6:49 PM, Shashi Kant
wrote:
> Dear All,
>
>
>
> I am newbie for openstack development and trying to understand the flow
> using code base.
>
> As the code base is very huge need your support to understand 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
refer 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 wrote:
> Hi Bryan,
>
> Yes, tempest can be run outside devstack deployments. Please check the
> README in https://git
+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 wrote:
> On Tue, 12 Apr 2
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
gt;> https://review.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)
> U
ailing 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
__
rote:
> 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,
>
___
> 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
Ghans
.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
.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
point?
>
> I am on between both now, and I'd like to get feedback about this
> before changing them.
Thanks a lot for driving service clients towards good interface :)
> Any comments are welcome :)
>
> Thanks
> Ken ohmichi
>
> _
On Thu, Jul 9, 2015 at 9:39 AM, Ken'ichi Ohmichi wrote:
> 2015-07-08 16:42 GMT+09:00 Ken'ichi Ohmichi :
>> 2015-07-08 14:07 GMT+09:00 GHANSHYAM MANN :
>>> On Wed, Jul 8, 2015 at 12:27 PM, Ken'ichi Ohmichi
>>> wrote:
>>>>
>>>> By
n
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev
_
> 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
___
ongGuanCun Software Park, Haidian District,
> Beijing 100193, PRC
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.opensta
Thanks,
>
> Matt Riedemann
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.o
; ______
> 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
>> Nova on each project.
>> The above Tempest log is written on tempest-lib side and that is
>> common way between projects.
>> So we can use this way for all projects as a common/consistent way, I
>> imagine now.
>>
>> I will make/write the detail of this idea later.
scussion.
[1]: https://bugs.launchpad.net/python-novaclient/+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
_
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
__
> 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
>
>
gt;> I remember, however, Devananda didn't like the idea.
>>
>> And it definitely makes a quick start guide a bit harder to follow. I
>> already imagine how many people will forget about this pinning
ng backwards compatible changes on
> lower microversion.
> I guess this is the difference between Nova and Ironic on
> interoperability discussion.
>
> I cannot/don't want to enforce Ironic way at all, and it's fine to
> find the best way on each project as OSS projects.
> But only my concern he
On Fri, Jun 26, 2015 at 3:46 PM, Dmitry Tantsur wrote:
>
> 26 июня 2015 г. 2:48 пользователь "GHANSHYAM MANN"
> написал:
>>
>> On Thu, Jun 25, 2015 at 5:18 PM, Ken'ichi Ohmichi
>> wrote:
>> > Sorry for late response here,
>>
On Fri, Jun 26, 2015 at 3:43 PM, Dmitry Tantsur wrote:
>
> 26 июня 2015 г. 2:47 пользователь "GHANSHYAM MANN"
> написал:
>>
>> On Sat, Jun 20, 2015 at 9:14 AM, Devananda van der Veen
>> wrote:
>> > Almost all of our discussions so far on this topic
Regards
Ghanshyam Mann
On Mon, Feb 15, 2016 at 12:07 PM, Alex Xu 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, we need
mp?
[1].. https://github.com/openstack/ec2-api
Regards
Ghanshyam Mann
On Tue, Feb 16, 2016 at 11:24 AM, Anne Gentle wrote:
>
>
> On Mon, Feb 15, 2016 at 6:03 PM, 少合冯 wrote:
>
>> I guess others may ask the same questions.
>>
>> I read the nova API doc:
>> s
+1 Sounds good to separate those to different repo.
Regards
Ghanshyam Mann
On Wed, Feb 17, 2016 at 4:55 AM, Matthew Treinish 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.
>> +1 to move it to
.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 all.
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 wrote:
> Hi,
>
> It has been greatly rewarding serving you all as Nova PTL over the
> Liberty and Mita
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 Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>>> >>
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 to situation when I nee
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 wrote:
> Hi Gordon,
>
> Thank you for your suggestion.
>
> I think jacket is different
.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
.
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 quest
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 questio
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 wrote:
On 03/04/2015 07:48 PM, GHANSHYAM MANN wrote:
> Hi Sean,
>
> Yes having V3 directory/file names is very confusing now.
>
>
itted.
>
> Decision Time
> =
>
> Anyway, this is a decision we should make before freeze. The 'no
> decision' case gives us the slow roll. I think from an upstream
> perspective the full monty will probably serve us a little
> better. Especially with robust release notes that expla
re on Nova 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
> [1] http://www.lokigames.com/hack/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack
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-
>> [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.
> >>
> >> [1] https://review.openstack.org/#/c/396142
> &
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 tests
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 to
Thanks. +1. i added my list in ethercalc.
Left put scenario tests can be run on periodic and experimental job. IMO on
both ( periodic and experimental) to monitor their status periodically as
well as on particular patch if we need to.
-gmann
On Fri, Mar 3, 2017 at 4:28 PM, Andrea Frittoli
wrote
On Sat, Mar 4, 2017 at 6:01 AM, Andrea Frittoli
wrote:
>
>
> On Fri, Mar 3, 2017 at 7:38 PM Matt Riedemann wrote:
>
>> I've got a change proposed to disable glance v1 by default in devstack
>> for Pike [1].
>>
>> The glance v1 API has been deprecated for awhile now. Nova started
>> supporting gl
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Mar 9th at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_March_9th_2017_.280900_UTC.29
A
ource_cleanup vs teardown (clean after each test
> case).
>
> #1670693 Tests in
> tempest.api.network.test_routers.RoutersTest don't clean up network
> resources <https://bugs.launchpad.net/tempest/+bug/1670693>
>
>
>
> Ple
On Fri, Mar 10, 2017 at 7:23 AM, Lance Bragstad wrote:
>
>
> On Thu, Mar 9, 2017 at 3:46 PM, Doug Hellmann
> wrote:
>
>> Excerpts from Andrea Frittoli's message of 2017-03-09 20:53:54 +:
>> > Hi folks,
>> >
>> > I'm trying to figure out what's the best approach to fade out testing of
>> > de
On Sun, Mar 12, 2017 at 7:40 AM, Matt Riedemann wrote:
> On 3/10/2017 3:02 PM, Andrea Frittoli wrote:
>
>>
>> We had a couple of sessions related to this topic at the PTG [0][1].
>>
>> We agreed that we want to still maintain integration tests only in
>> Tempest, which means that API micro versio
On Sat, Mar 11, 2017 at 12:10 AM, Andrea Frittoli wrote:
>
>
> On Fri, Mar 10, 2017 at 2:49 PM Andrea Frittoli
> wrote:
>
>> On Fri, Mar 10, 2017 at 2:24 PM Doug Hellmann
>> wrote:
>>
>> Excerpts from Ghanshyam Mann's message of 2017-03-10 10:55:25 +0900:
>> > On Fri, Mar 10, 2017 at 7:23 AM, L
6 test_get_volume_absolute_limits
> fails with no admin credentials
> <https://bugs.launchpad.net/tempest/+bug/1671256>
>
> 1 reviewing – not sure if it is a valid bug or working as
> designed – Related to resource_cleanup vs teardown (clean after each test
> case).
>
>
On Mon, Mar 13, 2017 at 7:37 PM, Andrea Frittoli
wrote:
> On Sat, Mar 11, 2017 at 10:45 PM Matt Riedemann
> wrote:
>
> On 3/10/2017 3:02 PM, Andrea Frittoli wrote:
> >
> > We had a couple of sessions related to this topic at the PTG [0][1].
> >
> > We agreed that we want to still maintain integr
+1.
Yea, Felipe is doing great work.
-gmann
On Fri, Mar 17, 2017 at 3:28 AM, BARTRA, RICK wrote:
> Felipe has done a tremendous amount of work stabilizing, enabling gates,
> contributing new tests, and extensively reviewing code in the Patrole
> project. In fact, he is the number one contributo
Noted.
Also added redirect link on old wiki
https://wiki.openstack.org/wiki/OpenStack_University
-gmann
On Fri, Mar 17, 2017 at 6:47 AM, Ildiko Vancsa
wrote:
> Hi All,
>
> Due to some issues around the name OpenStack University we unfortunately
> had to pick a new one.
>
> The new name of the
On Thu, Mar 23, 2017 at 7:02 AM, Ken'ichi Ohmichi
wrote:
> 2017-03-22 14:32 GMT-07:00 Andrea Frittoli :
> >
> >
> > On Wed, Mar 22, 2017 at 8:31 PM Sean McGinnis
> wrote:
> >>
> >> On Wed, Mar 22, 2017 at 01:08:23PM -0700, Ken'ichi Ohmichi wrote:
> >> > Hi,
> >> >
> >> > Now we need to update Te
Hello everyone,
Please reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, Mar 23rd at 9:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_March_23rd_2017_.280900_UTC.29
Hi All,
Tempest is testing SG rule creation and pinging scenario tests with
ethertype='IPv6' and protocol='icmp' [0].
In case of ethertype='IPv6', currently neutron accept protocol type
as 'icmp', 'icmpv6' and 'ipv6-icmp' which again seems like duplication of
SG rules bug on neutron side but not s
On Sun, Mar 26, 2017 at 9:31 PM, Sridhar Gaddam wrote:
>
>
> On Fri, Mar 24, 2017 at 7:27 PM, Brian Haley wrote:
>
>> On 03/24/2017 06:41 AM, Ghanshyam Mann wrote:
>>
>>> Hi All,
>>>
>>> Tempest is testing SG rule creation and pinging scenario
Hi All,
We have weekly Nova API meeting tomorrow. The meeting is being held
Wednesday UTC1300 and irc channel is #openstack-meeting-4.
The proposed agenda and meeting details are here:
https://wiki.openstack.org/wiki/Meetings/NovaAPI
Please feel free to add items to the agenda.
-gmann
1 - 100 of 352 matches
Mail list logo
