OpenStack DBaaS (Trove)

  1. Bug #1395016
  2. Activity log

Activity log for bug #1395016

Date Who What changed Old value New value Message
2014-11-21 14:28:23 Denis M. bug added bug
2014-11-21 14:28:46 Denis M. summary Trove-taskamager isn't able to create volumes in different AZs Trove-taskamager can't create volumes in different AZs
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.
2014-11-21 16:13:54 Denis M. trove: importance Low High
2015-01-20 13:26:50 Denis M. trove: assignee Denis M. (dmakogon)
2015-01-20 13:47:07 OpenStack Infra trove: status New In Progress
2015-08-18 15:18:10 Gilles Mocellin bug added subscriber Gilles Mocellin
2016-04-05 10:47:09 Amrith Kumar trove: milestone ongoing newton-1
2016-04-05 10:47:13 Amrith Kumar trove: assignee Denis M. (dmakogon)
2016-04-05 10:47:24 Amrith Kumar trove: status In Progress Triaged
2016-04-05 10:47:51 Amrith Kumar trove: assignee Morgan Jones (6-morgan)
2016-09-18 02:13:57 Amrith Kumar trove: milestone newton-1 ongoing