Re: [openstack-dev] [Heat][Neutron] Refactoring heat LBaaS architecture according Neutron API

2014-02-20 Thread Mitsuru Kanabuchi
we should consider what resource model is appropriate from heat's perspective. Targeting Juno would be appropriate timing to consider refactoring LBaaS model. > Your feedback and other ideas about better implementation plan are welcome. > > Regards, > Sergey. Regards,

Re: [openstack-dev] [Ceilometer] time consuming of listing resource

2014-02-18 Thread Mitsuru Kanabuchi
se the > > >clustered index (primary key) in aggregation (for an example, see the > > >particular line of code that we comment out of Ceilometer above). A > > >better performing schema would consolidate slim, frequently accessed > > >fields into the main meter table

Re: [openstack-dev] [heat] Stack convergence first steps

2013-12-08 Thread Mitsuru Kanabuchi
r stacks and their resources then perhaps > > deprecate and use "status" in the accepted way in the v2 API? > > Well, my point is that it's done inconsistently. Yes, it's mostly used as > an object status, but no

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

2013-11-22 Thread Mitsuru Kanabuchi
; > Sincerely, Haruka Tanizawa > > > > [0] https://blueprints.launchpad.net/nova/+spec/instance-tasks-api > > [1] https://wiki.openstack.org/wiki/Support-retry-with-idempotency > > [2] https://blueprints.launchpad.net/nova/+spec/cancel-swap-volume > >

Re: [openstack-dev] [Heat]Updated summit etherpad: API-retry-with-idempotency

2013-11-18 Thread Mitsuru Kanabuchi
#x27;m thinking for easily way to implement idempotency token. In my idea, idempotency token has to: - be String (Don't use UUID) # for avoiding UUID generate problem - isolate per tenant # for avoiding uniqueness check leaks is appropriate. What do you think about that? -

Re: [openstack-dev] [Heat]Updated summit etherpad: API-retry-with-idempotency

2013-11-13 Thread Mitsuru Kanabuchi
Thank you for comments! On Thu, 14 Nov 2013 11:02:34 +1300 Steve Baker wrote: > On 11/12/2013 07:40 PM, Mitsuru Kanabuchi wrote: > (snip) > Just to confirm, my understanding of the outcome of that session was > that pythonclients should implement retries of failed reque

[openstack-dev] [Heat]Updated summit etherpad: API-retry-with-idempotency

2013-11-11 Thread Mitsuru Kanabuchi
f I'm misunderstanding. I will also update the detail of API-retry-with-idempotency here. https://etherpad.openstack.org/p/kgpc00uuQr I will email after it updated. Regards ---- Mitsuru Kanabuchi NTT Software Corporation E-Mail : kanabuchi.mits...@po.

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

2013-10-30 Thread Mitsuru Kanabuchi
nk we need a better name. > > > Sincerely, > > Haruka Tanizawa > > > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de

Re: [openstack-dev] [Heat]Blueprint for retry function with idenpotency in Heat

2013-10-18 Thread Mitsuru Kanabuchi
On Fri, Oct 18, 2013 at 12:13:45PM +1300, Steve Baker wrote: > > On 10/18/2013 01:54 AM, Mitsuru Kanabuchi wrote: > > > Hello Mr. Clint, > > > > > > Thank you for your comment and prioritization. > > > I'm glad to discuss you who feel same issue. > &g

Re: [openstack-dev] [Heat]Blueprint for retry function with idenpotency in Heat

2013-10-17 Thread Mitsuru Kanabuchi
etry-failed-update > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Mitsuru Kanabuchi NTT Software Corporation E-Mail : kanabuchi.mits.

[openstack-dev] [Heat]Blueprint for retry function with idenpotency in Heat

2013-10-16 Thread Mitsuru Kanabuchi
Hi all, We proposed a blueprint that supports API retry function with idenpotency for Heat. Prease review the blueprint. https://blueprints.launchpad.net/heat/+spec/support-retry-with-idempotency Any comments will be gratefully appreciated. Regards. Mitsuru