Vish: I suspect there's a Grizzly doc bug here.
The Folsom docs say < http://docs.openstack.org/folsom/openstack-compute/admin/content/specify-host-to-boot-instances-on.html >: "With the Folsom release it is no longer possible to indicate a specific compute host to use to boot an instance with the --force_hosts parameter. See bug 1061665 for further discussion." However, the Grizzly docs say < http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html >: With the Grizzly release, the provider can change the policy to enable users to choose a specific host to launch a VM instance upon using the create:forced_host setting within policy.json on certain roles, such as an admin role. ... You can now select the host on which the instance would be spawned, using the "--hint" flag: $ nova boot --image 1 --flavor 2 --key_name test --hint force_hosts=server2 my-first-server --- Doc patch which introduced this change here: < https://review.openstack.org/25341> My guess is that the doc editor misunderstood the implication of the create:forced_host setting, and that --force_hosts still no longer works. I'm going to zap that and add the original author as reviewer to ensure things are OK. On Sat, Mar 30, 2013 at 10:56 PM, Vishvananda Ishaya <vishvana...@gmail.com>wrote: > I wasn't aware that force_hosts actually works. Someone should probably > verify. The availability zone method still works in grizzly. > > Vish > > On Mar 30, 2013, at 6:42 PM, Lorin Hochstein <lo...@nimbisservices.com> > wrote: > > I see that in grizzly an admin can use a scheduler hint to force a VM to > launch on a particular host, e.g.: > > nova boot --image 1 --flavor 2 --key_name test --hint force_hosts=server2 > my-first-server > (from: > http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html > ) > > In Folsom, an admin could do this with the availability zone flag: > > nova boot --image <uuid> --flavor m1.tiny --key_name test > --availability-zone nova:server2 > > (from: > http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-zone-to-boot-instances-on.html > ) > > Does the second method work in grizzly as well? If so, should we recommend > one approach over the other in the docs? > > Lorin > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > > -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
