openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #22315
Re: Forcing a VM to a specific node in grizzly
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 <lorin@xxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
Follow ups
References