2014-11-21 16:13:50 |
Denis M. |
description |
Trove-taskamager isn't able to create volumes in different AZs.
Cinder API allows to pass AZ as one of parameters on volume scheduling.
CLI view:
cinder help create
usage: cinder create [--snapshot-id <snapshot-id>]
[--source-volid <source-volid>] [--image-id <image-id>]
[--display-name <display-name>]
[--display-description <display-description>]
[--volume-type <volume-type>]
[--availability-zone <availability-zone>]
[--metadata [<key=value> [<key=value> ...]]]
<size>
Creates a volume.
Positional arguments:
<size> Volume size, in GBs.
Optional arguments:
--snapshot-id <snapshot-id>
Creates volume from snapshot ID. Default=None.
--source-volid <source-volid>
Creates volume from volume ID. Default=None.
--image-id <image-id>
Creates volume from image ID. Default=None.
--display-name <display-name>
Volume name. Default=None.
--display-description <display-description>
Volume description. Default=None.
--volume-type <volume-type>
Volume type. Default=None.
--availability-zone <availability-zone>
Availability zone for volume. Default=None.
--metadata [<key=value> [<key=value> ...]]
Metadata key and value pairs. Default=None.
As you can see, '--availability_zone' can be passed through. |
Trove-taskamager isn't able to create volumes in different AZs.
Cinder API allows to pass AZ as one of parameters on volume scheduling.
CLI view:
cinder help create
usage: cinder create [--snapshot-id <snapshot-id>]
[--source-volid <source-volid>] [--image-id <image-id>]
[--display-name <display-name>]
[--display-description <display-description>]
[--volume-type <volume-type>]
[--availability-zone <availability-zone>]
[--metadata [<key=value> [<key=value> ...]]]
<size>
Creates a volume.
Positional arguments:
<size> Volume size, in GBs.
Optional arguments:
--snapshot-id <snapshot-id>
Creates volume from snapshot ID. Default=None.
--source-volid <source-volid>
Creates volume from volume ID. Default=None.
--image-id <image-id>
Creates volume from image ID. Default=None.
--display-name <display-name>
Volume name. Default=None.
--display-description <display-description>
Volume description. Default=None.
--volume-type <volume-type>
Volume type. Default=None.
--availability-zone <availability-zone>
Availability zone for volume. Default=None.
--metadata [<key=value> [<key=value> ...]]
Metadata key and value pairs. Default=None.
As you can see, '--availability_zone' can be passed through.
Here's some context:
We have couple AZs in one deployment: when booting Trove's instance we can pass --availability-zone. But when trying to attach volume to instance through block_mapping_device Nova tells that: Invalid volume: Instance and volume not in same availability_zone (HTTP 400)
Raizing bug priority to HIGH. |
|