[
https://issues.apache.org/jira/browse/LIBCLOUD-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Bishop resolved LIBCLOUD-825.
----------------------------------
Resolution: Fixed
PR-785 with update merged.
> CloudStack driver Volume creation extension
> -------------------------------------------
>
> Key: LIBCLOUD-825
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-825
> Project: Libcloud
> Issue Type: Improvement
> Environment: CloudStack v 4.8
> salt-cloud v 2015.8
> libcloud v 0.20 (but also in latest)
> Reporter: Greg Bishop
> Labels: easyfix, newbie
>
> 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 routine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
