Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-12-04 Thread haruka tanizawa
Thank you for your reply. I chould understand instance-tasks-api more clearly. 2013/12/4 Andrew Laski andrew.la...@rackspace.com This is something that's entirely contained within Nova. It's just adding a different representation of what is already occurring with task_states on an

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-12-03 Thread Adam Young
On 11/27/2013 12:45 AM, Takahiro Shida wrote: Hi all, I'm also interested in this issue. Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I checked this BP and the following review. https://review.openstack.org/#/c/29480/ There are

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-12-03 Thread Andrew Laski
On 11/29/13 at 03:56pm, haruka tanizawa wrote: Thank you for your reply. I completely misunderstood. You're correct on request_id and task_id. What I'm planning is a string field that a user can pass in with the request and it will be part of the task representation. That field will have no

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-28 Thread haruka tanizawa
Thank you for your reply. I completely misunderstood. You're correct on request_id and task_id. What I'm planning is a string field that a user can pass in with the request and it will be part of the task representation. That field will have no meaning to Nova, but a client like Heat could use it

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-27 Thread haruka tanizawa
Hi, all!! I've just summarized mail until now. How to implement request identification ? === 1. Enable user to provide his/her own request identification within API request. e.g) Using instance-tasks-api 2. Use correlation_id in oslo as request

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-27 Thread Andrew Laski
On 11/22/13 at 10:14am, haruka tanizawa wrote: Thanks for your reply. I'm working on the implementation of instance-tasks-api[0] in Nova and this is what I've been moving towards so far. Yes, I know. I think that is good idea. The API will accept a string to be a part of the task but it

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-26 Thread Takahiro Shida
Hi all, I'm also interested in this issue. Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I checked this BP and the following review. https://review.openstack.org/#/c/29480/ There are many comments. Finally, this review looks rejected

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-22 Thread Mitsuru Kanabuchi
On Tue, 19 Nov 2013 12:03:57 -0500 Adam Young ayo...@redhat.com wrote: On 11/19/2013 08:21 AM, Dolph Mathews wrote: Related BP: Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I interested in cross-service-request-id because it

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-21 Thread Andrew Laski
On 11/19/13 at 08:04pm, haruka tanizawa wrote: Hi stackers!! I'd like to ask for your opinions about my idea of identifying request. Challenges == We have no way to know the final result of an API request. Indeed we can continuously get the status of allocated resources, but this is

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-21 Thread haruka tanizawa
Thanks for your reply. I'm working on the implementation of instance-tasks-api[0] in Nova and this is what I've been moving towards so far. Yes, I know. I think that is good idea. The API will accept a string to be a part of the task but it will have meaning only to the client, not to Nova.

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-20 Thread Ji2-3
Related BP: Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id In order to realize that she wanted to do it, in addition to the included in the request a unique ID. It seems that the ID is persisted as essential. Including a unique ID in

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-19 Thread Dolph Mathews
Related BP: Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id On Tue, Nov 19, 2013 at 5:04 AM, haruka tanizawa harube...@gmail.comwrote: Hi stackers!! I'd like to ask for your opinions about my idea of identifying request.

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing request identification

2013-11-19 Thread Adam Young
On 11/19/2013 08:21 AM, Dolph Mathews wrote: Related BP: Create a unified request identifier https://blueprints.launchpad.net/nova/+spec/cross-service-request-id And we have discussed workplans as well, which would be data to be carried along with the request id