yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-rc1

-- 
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/1150250

Title:
  Nova should not require os-network extension to process
  requested_networks when running with quantum

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Server create will only process "networks" if the os-networks
  extension is loaded.

  When working with a quantum configuration and multiple networks you
  have to be able to pass in the requested network to avoid instances
  being attached to all networks, so this part of the request isn't
  really optional

  However the os-network extension is not fully compatible with quantum,
  and the operations do map very well.  For example:

  - Network creation has a set of options that are pretty nova-net centric (such as VLAN)
  - Network creation is limited to admins
  - Network association and dis-association from projects is not the quanum model
  - cidr from quantum is not shown correctly in the output of nova network-list and network-show

  
  Rather than needing os-networks loaded and thereby exposing a bunch of calls that don't really map to quantum, it would be better to also allow processing of "networks" when the network api is configured to be quantum

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