This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. If you decide to work on this consider using a blueprint [1] (maybe with a spec [2]). I'll recommend to read [3] if not yet done.
References: [1] https://blueprints.launchpad.net/nova/ [2] https://github.com/openstack/nova-specs [3] https://wiki.openstack.org/wiki/Blueprints ** Changed in: nova Status: Confirmed => Opinion -- 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): Opinion 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 (i.e., because the networks aren't associated with the VMs in any way at deploy time). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1363568/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
