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 Th
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
wrote:
> Hi Stephen,
>
> Thanks for your exhaustive comments!
>
I'm always happy to exhau
Hi Stephen,
Thanks for your exhaustive comments!
Some more replies from me inline.
Have a good evening,
Salvatore
On 16 July 2014 00:05, Stephen Balukoff wrote:
> Hi Salvatore and Eugene,
>
> Responses inline:
>
> On Tue, Jul 15, 2014 at 12:59 PM, Salvatore Orlando
> wrote:
>
>> I think I've
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
wrote:
> Some
Some comments inline:
> Agreed-- I think we need to more fully flesh out how extension list / tags
> should work here before we implement it. But this doesn't prevent us from
> rolling forward with a "version 1" of flavors so that we can start to use
> some of the benefits of having flavors (like
.
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
: 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 to
Hi Salvatore and Eugene,
Responses inline:
On Tue, Jul 15, 2014 at 12:59 PM, Salvatore Orlando
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 what people mean. It
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, it
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 on
10 matches
Mail list logo