← Back to team overview

openstack team mailing list archive

Re: Forcing a VM to a specific node in grizzly

 

Anne:

I read that as meaning you can now control who has access to do this via
policy.json, but the UI for doing it still uses the --availability-zone
flag. I documented my understanding here: <
https://review.openstack.org/25804>, but we should wait for Phil Day's
response.

Lorin



On Sun, Mar 31, 2013 at 10:06 PM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:

> Woops, hit send too soon.
>
> I made the doc change based on this mailing list post by Phil Day.
> https://lists.launchpad.net/openstack/msg19784.html
>  Which was in this doc bug:
> https://bugs.launchpad.net/openstack-manuals/+bug/1096168
>
> Phil, can you verify on a grizzly install and post the correct commands
> and results?
>
> Thanks,
> Anne
>
>
> On Sat, Mar 30, 2013 at 9:56 PM, Vishvananda Ishaya <vishvananda@xxxxxxxxx
> > 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 <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
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com

References