Reviewed: https://review.openstack.org/46632 Committed: http://github.com/openstack/openstack-manuals/commit/1c436931a9b34a7aada868a991552c809b855a02 Submitter: Jenkins Branch: master
commit 1c436931a9b34a7aada868a991552c809b855a02 Author: annegentle <[email protected]> Date: Fri Sep 13 13:59:45 2013 -0500 Enhances and updates bare metal information Adds back in the section about booting to a specific node/host - points to correct wiki page - gives more use cases and context Change-Id: I71a85860108a4e7220a69c3e54b467dfc575f8c3 Closes-bug: 1226511 Closes-bug: 1188474 ** Changed in: openstack-manuals Status: In Progress => Fix Released -- 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/1226511 Title: The --availability-zone parameter will fail instance boot without honor imageproperties filter. Status in OpenStack Compute (Nova): Invalid Status in OpenStack Manuals: Fix Released Bug description: In current scheduler design, when --availability-zone zone:host is given, all of the configured filters will be ignored, in some cases it will fail instance boot due to the mismatch of host architecture, although this is a admin action, we assume that the cloud admin should aware it well, but in some cases it might be get confused when somebody doesn't know it. If we think this can be enhanced from robust perspective, we may solve it by honor the basic scheduler filters like imageproperties filter even the --availability-zone parameter being used, or we think this is work as design, at least we can update the admin doc to address it clearly. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1226511/+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
