Open Stack

In my opinion, we should ask ourselves how important it is than in the
transition from nova-network to quantum the same behaviour concerning the
default nic selection is preserved.
If this turns out to be important, then Quantum should just keep doing what
nova-network does at the moment if no --nic option is specified.
Otherwise, the best option for me is, as Ian suggests, to make the --nic
compulsory, and return a 400 is no network is specified at all.

Salvatore

On 28 August 2012 01:57, Ian Wells <ijw.ubuntu at cack.org.uk> wrote:

> On 27 August 2012 19:42, Dan Wendlandt <dan at nicira.com> wrote:
> > 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).
>
> Quite honestly (and inviting contention) - if you're changing the
> default 'nothing specified' behaviour from one thing to another, I'd
> just go the whole hog and make it an error not to specify any networks
> at all.  No default is sensible in all circumstances and what you're
> describing is really quite complex.
>
> --
> Ian.
>
> _______________________________________________
> 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/20120828/1b9c538b/attachment.html>