yahoo-eng-team team mailing list archive

[Joe Cropper <jwcroppe@xxxxxxxxxx>]

Public bug reported:

With the switch to nova-conductor being responsible for building the
instances, the scheduler's select_destinations no longer has access to
the requested networks.

That is, when schedule_run_instance() was called in the nova-scheduler's
process space (i.e., as it was in Icehouse), it had the ability to
interrogate the networks being requested by the user to more intelligent
placement decisions.

This precludes schedulers from making placement decisions that are
affected by the networks being requested at deploy time.

** Affects: nova
     Importance: Undecided
     Assignee: Joe Cropper (jwcroppe)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Joe Cropper (jwcroppe)

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

Title:
  Nova scheduler no longer has access to requested_networks

Status in OpenStack Compute (Nova):
  New

Bug description:
  With the switch to nova-conductor being responsible for building the
  instances, the scheduler's select_destinations no longer has access to
  the requested networks.

  That is, when schedule_run_instance() was called in the nova-
  scheduler's process space (i.e., as it was in Icehouse), it had the
  ability to interrogate the networks being requested by the user to
  more intelligent placement decisions.

  This precludes schedulers from making placement decisions that are
  affected by the networks being requested at deploy time.

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