Open Stack

Hi Gary,

I'm really glad you mentioned this.  This is something we were
planning on re-visiting after the initial nova/quantum v2 integration in F-2,
but we never did.  In Essex, which is that if no networks are
specified, the VM gets a NIC on each network it has access to (either
a private network owned by the tenant, or a 'public/shared' network).

Here's one possible approach: the cloud operator can specify an
ordered list of network-ids as part of Nova config.  A VM with no
networks specified via the API will get that ordered set of NICs.  If no such
networks are specified in the config, we could either give VMs no NICs
(probably not a great user experience) or default to giving a VM a NIC
on each shared network (would need a way to deterministically order
these shared networks for this to be reasonable).

Dan

On Mon, Aug 27, 2012 at 7:33 AM, Gary Kotton <gkotton at redhat.com> wrote:
> On 08/27/2012 05:21 PM, Nachi Ueno wrote:
>>
>> Hi Gary
>>
>> It is a spec.
>> Nova will create all vnic for networks assigned to the tenant by default.
>
>
> Thanks
>
>>
>> Nachi
>>
>> 2012/8/27 Gary Kotton<gkotton at redhat.com>:
>>>
>>> Hi,
>>> When running nova boot without specifically assigning Quantum networks to
>>> the virtual nics, the code creates a virtual nic for each Quantum
>>> network. I
>>> think that this is a bug and it would be interesting to know what the
>>> intended functionality should be.
>>> Thanks
>>> Gary
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~