Oh, nice! Thanks for the hint! -jay On 01/03/2013 08:03 AM, Day, Phil wrote: >> Note this is an admin-only ability by default and can oversubscribe the compute node the instance goes on. > > It is now controlled by a policy (create:forced_host) - so if you want to extend it to other users you can, for example, set up the policy file to control this via a Keystone role > > Phil > > -----Original Message----- > From: openstack-bounces+philip.day=hp.com at lists.launchpad.net [mailto:openstack-bounces+philip.day=hp.com at lists.launchpad.net] On Behalf Of Jay Pipes > Sent: 27 December 2012 22:39 > To: openstack at lists.launchpad.net > Subject: Re: [Openstack] How to create vm instance to specific compute node? > > No. > > Use nova boot --availability_zone=nova:hostname where nova: is your availability zone and hostname is the hostname of the compute node you wish to put the instance on. > > Note this is an admin-only ability by default and can oversubscribe the compute node the instance goes on. > > Best, > -jay > > On 12/27/2012 02:45 PM, Rick Jones wrote: >> Does the convention of adding --onhost--computenodename to the instanc >> name being created still work? >> >> rick jones >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack at lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >