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
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
.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
___
> 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
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,
>
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
__
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
.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
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
_
> 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
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
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
_
>> 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.
; ______
> 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,
>
> Matt Riedemann
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.o
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
_
> 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
___
n
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev
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
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 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
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,
>>
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
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
__
> 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
>
>
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] http://www.lokigames.com/hack/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack
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
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
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.
>
>
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
.
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
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
___
> 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
>>>> used for gating job definitions and just call the new entry-point
>>>> instead of
>>>> testr directly.
>>>>
>>>> >
>>>> > BR,
>>>> > Angelo
>>>> >
>>>> > [1]
>>>> http://docs.o
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
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
>>> "/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
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-
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
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
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
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
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
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
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
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
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
#/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
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
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
_
301 - 352 of 352 matches
Mail list logo
