Hi John
I'm so sorry replying late to your message.
However, to ensure the v3 API gets released in Icehouse, I would love
to close the v2 API for changes, but perhaps I am being too harsh, and
we should certainly only do that after the point where we promise not
to back backwards
On 30 October 2013 01:51, haruka tanizawa harube...@gmail.com wrote:
Hi John!
Thank you for your reply:)
Sorry for inline comment.
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
On Tue, 29 Oct 2013 10:32:18 +
Joe Gordon joe.gord...@gmail.com wrote:
* Can you fill out the questions found in
http://justwriteclick.com/2013/09/17/openstack-docimpact-flag-walk-through/
I guess, ClientToken(Idempotent) implementation is nice idea for API requester.
In my opinion, after
Hi Mitsuru-san!
Thank you for your comment.
I guess, ClientToken(Idempotent) implementation is nice idea for API
requester.
In my opinion, after POST requested, A requester have to stop processing
when it cannot get response, because requester doesn't know what the
resouce created
Hi all!
I proposed 'Idempotency for OpenStack API' as before.
In this time, I rewrote BP(
https://blueprints.launchpad.net/nova/+spec/idempotentcy-client-token ) and
I implemented proto of it.
I image below use-case.
User can't know instance ID when the client has gone away before user get
Hi Joe!
Thank you for your reply and sharing the information.
I am going to rewrite blueprint from many point of view.
Sincerely,
Haruka Tanizawa
2013/10/29 Joe Gordon joe.gord...@gmail.com
On Tue, Oct 29, 2013 at 8:50 AM, haruka tanizawa harube...@gmail.comwrote:
Hi all!
I proposed
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
On 29 October 2013 11:56, haruka tanizawa harube...@gmail.com 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
Hi John!
Thank you for your reply:)
Sorry for inline comment.
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?
Oh, yes.
Did you say about this BP(
