Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-17 Thread Eugene Nikanorov
Folks, Initial implementation is here: https://review.openstack.org/#/c/105982/ It's pretty much complete (in terms of code parts) but may require some adjustments and of course fixes. I'm working on the client to test this end-to-end. Thanks, Eugene. P.S. Almost got it under 1k lines! On

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-16 Thread Sumit Naiksatam
To the earlier question on whether we had defined what we wanted to solve with the flavors framework, a high level requirement was captured in the following approved spec for advanced services: https://review.openstack.org/#/c/92200 On Wed, Jul 16, 2014 at 5:18 AM, Eugene Nikanorov

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-16 Thread Stephen Balukoff
Hi Salvatore! Thank you for reading through my book-length e-mail and responding to all my points! Unfortunately, I have more responses for you, inline: On Wed, Jul 16, 2014 at 4:22 PM, Salvatore Orlando sorla...@nicira.com wrote: Hi Stephen, Thanks for your exhaustive comments! I'm

[openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Stephen Balukoff
Hi folks! I've noticed progress on the flavor framework discussion slowing down over the last week. We would really like to see this happen for Juno because it's critical for many of the features we'd also like to get into Juno for LBaaS. I understand there are other Neutron extensions which will

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Salvatore Orlando
I think I've provided some examples in the review. However, the point is mostly to simplify usage from a user perspective - allowing consumers of the neutron API to use the same flavour object for multiple services. There are other considerations which could be made, but since they're dependent

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Eugene Nikanorov
Hi Stephen, So, as was discussed, existing proposal has some aspects which better to be postponed, like extension list on the flavor (instead of tags). Particularly that idea has several drawbacks: - it makes public API inflexible - turning features on/off is not what flavors should be doing,

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Stephen Balukoff
Hi Salvatore and Eugene, Responses inline: On Tue, Jul 15, 2014 at 12:59 PM, Salvatore Orlando sorla...@nicira.com wrote: I think I've provided some examples in the review. I was hoping for specific examples. The discussion I've seen so far has been vague enough that it's difficult to see

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Eichberger, German
: Eugene Nikanorov [mailto:enikano...@mirantis.com] Sent: Tuesday, July 15, 2014 2:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Flavor framework proposal Hi Stephen, So, as was discussed, existing proposal has some aspects which better

Re: [openstack-dev] [Neutron] Flavor framework proposal

2014-07-15 Thread Eichberger, German
. Thanks, German From: Stephen Balukoff [mailto:sbaluk...@bluebox.net] Sent: Tuesday, July 15, 2014 3:06 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] Flavor framework proposal Hi Salvatore and Eugene, Responses inline: On Tue, Jul 15