If this feature is going to be added, I suggest it gets a different name. Force host is an admin command to force an instance onto a host. If you want to make a user-facing command that respects filters, perhaps something like requested-host might work. In general, however, the name of hosts are not exposed to users, so this is moving far away from cloud and into virtualization management.
Vish On Feb 12, 2015, at 1:05 AM, Rui Chen <chenrui.m...@gmail.com> wrote: > Hi: > > If we boot instance with 'force_hosts', the force host will skip all > filters, looks like that it's intentional logic, but I don't know the reason. > > I'm not sure that the skipping logic is apposite, I think we should remove > the skipping logic, and the 'force_hosts' should work with the scheduler, > test whether the force host is appropriate ASAP. Skipping filters and > postponing the booting failure to nova-compute is not advisable. > > On the other side, more and more options had been added into flavor, like > NUMA, cpu pinning, pci and so on, forcing a suitable host is more and more > difficult. > > > Best Regards. > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
