<div dir="ltr"><div>Hi, all!!<br></div>I've just summarized mail until now.<br><div><div><br><br>How to implement "request identification" ?<br>===============================================<br>1. Enable user to provide his/her own "request identification" within API request.<br>
   e.g) Using instance-tasks-api<br>2. Use correlation_id in oslo as "request identification".<br>3. Enable keystone to generate "request identification" (we can call it 'request-token', for example).<br>
   Like Keystone identifies 'User'.<br><br>Feedback<br>===============================================<br>There are already these blueprints.<br>* cross-service-request-id<br>* delegation-workplans<br>* instance-tasks-api<br>
<br>My conclusion<br>===============================================<br>However, the following opinions also have failed to resolve the problem what I want to solve.<br>1. Cross component<br>2. User can know before user put request API<br>
3. User can see how their create request is going<br><br>* cross-service-request-id<br>-> Lack of point of 'User can know before user put request API'.<br>-> Or is something missing? Any plan?<br>* delegation-workplans<br>
-> Lack of point of 'User can see how their create request is going'.<br>-> Does it return state of 'requests'?<br>* instance-tasks-api<br>-> Lack of point of 'User can know before user put request API'.<br>
-> How do we know task_id when nova-api downs before we get task_id?<br><br>So, I think that 'Idempotency for OpenStack API'[0] is still valid because of requirement.<br>（Yes, I think word 'Idempotency' is appropriate...）<br>
<br>If you have any thoughts on that please share it with me.<br><br><br></div><div>Sincerely, Haruka Tanizawa<br><br>[0] <a href="https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token">https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token</a></div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/27 Takahiro Shida <span dir="ltr"><<a href="mailto:shida.takahiro@gmail.com" target="_blank">shida.takahiro@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:arial,sans-serif;font-size:14px"><p>Hi all,</p><p>I'm also interested in this issue.</p><p></p><div class="im">> Create a unified request identifier<br>> <a title="" href="https://blueprints.launchpad.net/nova/+spec/cross-service-request-id" target="_blank">https://blueprints.launchpad.net/nova/+spec/cross-service-request-id</a><br>

<br></div>I checked this BP and the following review.<br><a title="" href="https://review.openstack.org/#/c/29480/" target="_blank">https://review.openstack.org/#/c/29480/</a><br><br>There are many comments. Finally, this review looks rejected by "user specified correlation-id" is useless and insecure.<div class="im">
<br>
<br>>> 3. Enable keystone to generate "request identification" (we can call it 'request-token', for example).<br></div>> -2<br><br>So, this idea will be helpful to solve the "cross-service-request-id" problem.<br>

Because the correlation-id specified by keystone.<br><br>How about nova guys and keystone guys ?<p></p><div><br></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>