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
I made the doc edit based on this mailing list post from Phil Day.
https://lists.launchpad.net/openstack/msg19784.html
On Sun, Mar 31, 2013 at 9:03 PM, Lorin Hochstein
wrote:
> Vish:
>
> I suspect there's a Grizzly doc bug here.
>
> The Folsom docs say <
> http://docs.openstack.org/folsom/opens
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 com
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 th
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 wrote:
> I see that in grizzly an admin can use a scheduler hint to force a VM to
> launch on a particular hos
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-instance
6 matches
Mail list logo
