g List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] What does flavor mean for a network?
Neil,
flavor:network is for Metaplugin. It is unrelated to flavor framework.
FYI, Metaplugin will be removed in liberty.
https://review.openstack.org/#/c/192056/
Thanks.
Itsuro Oda (oda-g)
Neil,
flavor:network is for Metaplugin. It is unrelated to flavor framework.
FYI, Metaplugin will be removed in liberty.
https://review.openstack.org/#/c/192056/
Thanks.
Itsuro Oda (oda-g)
On Thu, 16 Jul 2015 10:44:01 +0100
Neil Jerram wrote:
> Thanks everyone for your responses...
>
> On 1
Thanks everyone for your responses...
On 15/07/15 21:01, Doug Wiegley wrote:
That begins to looks like nova’s metadata tags and scheduler, which is
a valid use case. The underpinnings of flavors could do this, but it’s
not in the initial implementation.
doug
On Jul 15, 2015, at 12:38 PM, Kev
That begins to looks like nova’s metadata tags and scheduler, which is a valid
use case. The underpinnings of flavors could do this, but it’s not in the
initial implementation.
doug
> On Jul 15, 2015, at 12:38 PM, Kevin Benton wrote:
>
> Wouldn't it be valid to assign flavors to groups of pro
Wouldn't it be valid to assign flavors to groups of provider networks? e.g.
a tenant wants to attach to a network that is wired up to a 40g router so
he/she chooses a network of the "fat pipe" flavor.
On Wed, Jul 15, 2015 at 10:40 AM, Madhusudhan Kandadai <
madhusudhan.openst...@gmail.com> wrote:
> On Jul 15, 2015, at 9:54 AM, Neil Jerram wrote:
>
> 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.
>
> Is it a way for an admin to provide a particular kind of network, and then
> for a tenant
On Wed, Jul 15, 2015 at 9:25 AM, Kyle Mestery wrote:
> On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram
> wrote:
>
>> 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 envisi
On Wed, Jul 15, 2015 at 10:54 AM, Neil Jerram
wrote:
> 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
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.
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?
How does it diff
