[openstack-dev] [nova] Add scenario tests based on multiple cells environment

2017-11-21 Thread koshiya maho
Hi, all Multiple cells (Nova-Cells-v2) is supported in Pike release. It is necessary to confirm that existing APIs work appropriately in the multiple cells environment. We will post multiple patches, so I created BluePrint[1] to make it easier to keep track of those patches. Please check the con

[openstack-dev] [python-keystoneclient] Return request-id to caller

2016-11-07 Thread koshiya maho
Hi Keystone devs, Blueprint [1] related to request-ids is approved for Mitaka and its implementation [2] is up for review for quite a long time. And, I have submitted a blueprint about logging [3]. I would like to include these patch in Ocata. Could you review it? [1] https://blueprints.launchp

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

2016-07-13 Thread koshiya maho
koshiya maho wrote: > Hi, keystone devs, > > Thank you for your many opinions about request id mapping. > I fixed this patch [1] by the way that Brant and Cao gave me suggestions [2]. > Could you review it? > > [1] https://review.openstack.org/#/c/261188/ > [2] http://

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

2016-05-31 Thread koshiya maho
2016 16:37:31 -0700 Morgan Fainberg wrote: > On Wed, Apr 13, 2016 at 6:07 AM, David Stanek wrote: > > > On Wed, Apr 13, 2016 at 3:26 AM koshiya maho > > wrote: > > > >> > >> My request to all keystone cores to give their suggestions about the same. > &

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

2016-04-19 Thread koshiya maho
Hi Brant, David, Thank you for your opinions. On Wed, 13 Apr 2016 13:07:55 + David Stanek wrote: > On Wed, Apr 13, 2016 at 3:26 AM koshiya maho > wrote: > > > > > My request to all keystone cores to give their suggestions about the same. > > > > >

[openstack-dev] [python-keystoneclient] Return request-id to caller

2016-04-13 Thread koshiya maho
Hi All, I have submitted patches [1] for returning request-id to the caller on which Brant has raised his concerns [2]; Brant’s concern: We've tried a couple of times to have the client return metadata for the lists returned and we wound up reverting the change both times because it broke some

[openstack-dev] [python-keystoneclient] Return request-id to caller

2016-04-05 Thread koshiya maho
Hi Keystone devs, Blueprint [1] related to request-ids is approved for Mitaka and its implementation [2] is up for review for quite a long time. I would like to apply for a goal for this blueprint so that it can be included in Newton. [1] https://blueprints.launchpad.net/python-keystoneclient

[openstack-dev] [python-keystoneclient] return-request-id-to-caller

2015-12-22 Thread koshiya maho
Hi, I want to add support for returning 'x-openstack-request-id' in python-keystoneclient as per the design proposed in cross-project specs. Cross-project spec has been already approved. : https://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html So, I'd like you to app

[openstack-dev] [Keystone][Tempest] OS-INHERIT APIs were skipped by Jenkins because "os_inherit" in keystone.conf was disable.

2015-12-09 Thread koshiya maho
Hi all, I pushed the patch set of OS-INHERIT API tempest (keystone v3). https://review.openstack.org/#/c/250795/ But, all API tests in patch set was skipped, because "os_inherit" in keystone.conf of Jenkins jobs was disable. So, it couldn't be confirmed. Reference information : http://logs.op

Re: [openstack-dev] [QA][Tempest][Keystone] Re: [openstack-qa] [tempest][keystone]Inherit API was not found in API tempest.

2015-11-18 Thread koshiya maho
2015年11月18日(水) 16:31 koshiya maho : > > > > Hi all, > > > > I'm creating a tempest that conforms to operational environment > > of OpenStack that we have built. > > > > So far as I've seen the API tempest in the community, > > Inherit API of K