yahoo-eng-team team mailing list archive

[John Griffith <1262176@xxxxxxxxxxxxxxxxxx>]

Making a compatible version for EBS here isn't a terrible idea, however
i hardly see this as a bug.  This is most definitely a feature request
IMO, and it has almost nothing to do with Cinder.  As per my comments in
the review:

"If there's real value in emulating this, then I think this needs to include the work to provide the option on create as well as provide it in the get. However, there's only ONE option that I'm aware of in EBS today, so this should filter out anything that isn't that IO1 type.
In other words, if an admin creates a type with this name, fine... we can expose it and allow it to be selected for creation. But we shouldn't expose any of the other types and we most certainly should not require this type exist or be built by default."

** Changed in: cinder
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1262176

Title:
  EC2: 'io1' type volume should also return IOPS associated with it

Status in Cinder:
  Invalid
Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  This patch https://review.openstack.org/#/c/61041 exposes volume type
  in the EC2 API. Amazon's API documentation says that if the volume
  type is 'io1', that is, if the volume has guaranteed IOPS set for it,
  a 'DescribeVolumes' call should return the IOPS for such volumes. We
  need to add that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1262176/+subscriptions