yahoo-eng-team team mailing list archive

[dan wendlandt <1042348@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1042348

Title:
  default NICs for Nova VMs with Quantum

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  from an email on the ML from garyk:

  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.

  Dan's Response:

  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).

  Another option would be to keep the current behavior if no default
  networks is specified in the nova config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1042348/+subscriptions