Open Stack

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 features which do not yet exist (NFV, service insertion,
chaining and steering) I think there is no point in arguing over it.

In conclusion I think the idea makes sense, and is a minor twist in the
current design which should not either make the feature too complex neither
prevent any other use case for which the flavours are being conceived. For
the very same reason however, it is worth noting that this is surely not an
aspect which will cause me or somebody else to put a veto on this work item.

Another aspect to consider is how the flavours will work when the advanced
service type they refer to is not consumable through the neutron API, which
would be the case with an independent load balancing API endpoint. But this
is probably another story.

Salvatore



On 15 July 2014 21:21, Stephen Balukoff <sbalukoff at bluebox.net> wrote:

> 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 need it
> too.
>
> The proposal under discussion is here:
>
> https://review.openstack.org/#/c/102723/
>
> One of the things I've seen come up frequently in the comments is the idea
> that a single flavor would apply to more than one service type (service
> type being 'LBaaS', 'FWaaS', 'VPNaaS', etc.). I've commented extensively on
> this, and my opinion is that this doesn't make a whole lot of sense.
>  However, there are people who have a different view on this, so I would
> love to hear from them:
>
> Could you describe a specific usage scenario where this makes sense? What
> are the characteristics of a flavor that applies to more than one service
> type?
>
> Let's see if we can come to some conclusions on this so that we can get
> flavors into Juno, please!
>
> Thanks,
> Stephen
>
> --
> Stephen Balukoff
> Blue Box Group, LLC
> (800)613-4305 x807
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140715/b32075c6/attachment.html>