availability zone ignored when creating volume

Somehow we lost the parameter in the volume api to specify a zone. This should be added back in.

it's also ignored when start up an instance.
euca-run-instances ami-00000002 -k mykey -t m1.tiny --availability-zone=zoneone

please fix this error soon.

if you are use:
--scheduler_driver=nova.scheduler.zone.ZoneScheduler
you should be able to create an instance with an availability zone.
and with
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
if you are an admin you can specify a specific host for an instance with --availability-zone=nova:<hostname>

Vish

On Aug 22, 2011, at 3:21 AM, Do Dinh Thang wrote:

> it's also ignored when start up an instance.
> euca-run-instances ami-00000002 -k mykey -t m1.tiny --availability-zone=zoneone
>
> please fix this error soon.
>
> --
> You received this bug notification because you are a member of Nova Bug
> Team, which is subscribed to OpenStack Compute (nova).
> https://bugs.launchpad.net/bugs/803654
>
> Title:
> availability zone ignored when creating volume
>
> Status in OpenStack Compute (Nova):
> Confirmed
>
> Bug description:
> pre-requisite:
> Run the commands as admin
>
> Steps to reproduce:
> 1. create a volume on a host
> euca-run-instances -k <keypair> -z <zone>:<host> <image_id>
> 2. euca-describe-volumes <vol_id>
> 3. verify
>
> Actual:
> The zone is ignored
>
> Expected:
> Volume should be created on the zone/host specified
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nova/+bug/803654/+subscriptions

thanks Vish. In my case, I choice to use SimpleScheduler and that solved my problem.

I believe this was fixed in the vsa branch that went in.