libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Bishop (JIRA)" <>
Subject [jira] [Created] (LIBCLOUD-825) CloudStack driver Volume creation extension
Date Fri, 27 May 2016 18:56:12 GMT
Greg Bishop created LIBCLOUD-825:

             Summary: CloudStack driver Volume creation extension
                 Key: LIBCLOUD-825
             Project: Libcloud
          Issue Type: Improvement
         Environment: We have a CloudStack implementation with a variety of "Disk Offerings."
The current libcloud create_volume implementation does not allow selection of a specific "Disk
Offering," only by specifying size. When a customizable offering exists, this offering is
selected, even if it is not the expected offering.
            Reporter: Greg Bishop

With a CloudStack implementation with the following Disk Offerings:
- "Offering-1" defined as 50 GB on local disk
- "Offering-2" defined as a variable size volume on shared storage
- "Offering-3" defined as a 64 GB on local disk

When using libcloud to create a new 64 GB volume, the "Offering-2" above is chosen, but because
it isn't on the local disk, the deployment isn't as expected. In addition, managing the order
of enumeration for Disk Offerings from CloudStack is very cumbersome, as one needs to remove
all offerings that would be below the one being added then add the new one followed by the
deleted offerings. Not a good experience for a customer trying to use a offering that doesn't
exist during that window.

I propose adding an optional argument "ex_volume_type" (to match the name in the OpenStack
driver) to the create_volume function in the CloudStack driver that allows specifying the
"Disk Offering" to ensure that a volume with the correct performance characteristics is chosen.

The change is fairly small but significantly increases the flexibility of the create_volume

This message was sent by Atlassian JIRA

View raw message