On 29 October 2013 11:56, haruka tanizawa <[email protected]> wrote: > Hi Joe! > > Thank you for your help. > I wrote BP > https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token again. > Could you review it when you have time. > > >>> >>> I like the idea but two comments: >>> >>> * Can you fill out the questions found in >>> http://justwriteclick.com/2013/09/17/openstack-docimpact-flag-walk-through/ >>> * Can you break down the blueprint into work items, so we can see what >>> steps are involved >>> * Since this is for OpenStack APIs only the name client-token makes me >>> think of keystone tokens, so I think we need a better name. > > About third point of this(about name), hmmm, I'm still thinking about it. > How about 'Tracking-id'?
We also need something that doesn't clash with the cross-service request id, as that is doing something slightly different. Would "idempotent-request-id" work better? Also, I assume we are only adding this into the v3 API? We should close the v2 API for additions I guess? John _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
