Scheduler hints ignore_hosts and force_hosts do not work

Oops, was on stable/essex. Here's patch against master.

Can you please submit this through gerrit?

http://wiki.openstack.org/HowToContribute
http://wiki.openstack.org/GerritWorkflow

After looking at the code, I'm still seeing this in filter_properties .... in any case, submit to gerrit and we can discuss the code there

I think the structure of filter_propertiesis is like this:
filter_properties: {
    scheduler_hints:{
    },
    ignore_hosts: [],
    force_hosts: [],
}

but user can only setting the scheduler_hints, rather than "ignore_hosts" and "force_hosts". So "ignore_hosts" and "force_hosts" not in scheduler_hints is correct.

You are correct, however using `nova boot --hint force_hosts=...` somehow worked a couple months ago-- not sure what changed. See https://bugs.launchpad.net/openstack-manuals/+bug/1061665 . A similar patch was suggested there but Vish closed wontfix, saying: "force_hosts is not a hint meant to be exposed to a user. if you want to force a host as an admin you can use the availability zone syntax". I haven't tested if that works in stable/Essex. It's now marked as a doc bug as the docs still advise using --hint force_hosts.

The force_hosts scheduler hint has been replaced by specifying an availability zone.

See the following post over on the Ubuntu launchpad: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1061665/comments/5

i.e. To deploy instance 'test1' to host 'nova-compute-1' in availability zone 'nova':
nova boot --flavor 1 --image {some-image-uuid} --availability-zone nova:nova-compute-1 test1

I'm not exactly sure what the intended replacement is for ignore_hosts but I'd expect that you should just use the FilterScheduler filters to separate your instances according to your requirements:
http://docs.openstack.org/trunk/openstack-compute/admin/content/scheduler-filters.html

It looks like the other bug has been triaged to update documentation, but otherwise the following documentation needs to be updated:
http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html

Confused now. Is it still a Nova issue ? A doc issue ?

Looks like just a doc issue