[openstack-dev] [neutron] What does flavor mean for a network?

Kyle Mestery mestery at mestery.com
Wed Jul 15 16:25:15 UTC 2015

On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram <Neil.Jerram at metaswitch.com>

> I've been reading available docs about the forthcoming Neutron flavors
> framework, and am not yet sure I understand what it means for a network.
In reality, this is envisioned more for service plugins (e.g. flavors of
LBaaS, VPNaaS, and FWaaS) than core neutron resources.

> Is it a way for an admin to provide a particular kind of network, and then
> for a tenant to know what they're attaching their VMs to?
I'll defer to Madhu who is implementing this, but I don't believe that's
the intention at all.

> How does it differ from provider:network-type?  (I guess, because the
> latter is supposed to be for implementation consumption only - but is that
> correct?)
Flavors are created and curated by operators, and consumed by API users.

> Thanks,
>     Neil
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20150715/dae9028e/attachment.html>

More information about the OpenStack-dev mailing list