libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gertjan Oude Lohuis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LIBCLOUD-618) Openstack create_volume should return StorageVolume
Date Thu, 25 Sep 2014 07:44:33 GMT

     [ https://issues.apache.org/jira/browse/LIBCLOUD-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gertjan Oude Lohuis updated LIBCLOUD-618:
-----------------------------------------
    Description: 
The create_volume call in the OpenStack driver returns a bool to signify whether the call
succeeded. This call should return a StorageVolume object, as other drivers already do (ec2,
cloudstack, gce, etc).

The fix is trivial, I'll create a pull request. I choose priority Major, since this flaw makes
the create_volume call next to unusable, because it is impossible to know which volume was
created by the call (since name is not unique).

  was:
The create_volume call in the OpenStack driver returns a bool to signify whether the call
succeeded. This call should return a StorageVolume object, as do other drivers (ec2, cloudstack,
gce, etc).

The fix is trivial, I'll create a pull request. I choose priority Major, since this flaw makes
the create_volume call next to unusable, because it is impossible to know which volume was
created by the call (since name is not unique).


> Openstack create_volume should return StorageVolume
> ---------------------------------------------------
>
>                 Key: LIBCLOUD-618
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-618
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.13.3
>            Reporter: Gertjan Oude Lohuis
>
> The create_volume call in the OpenStack driver returns a bool to signify whether the
call succeeded. This call should return a StorageVolume object, as other drivers already do
(ec2, cloudstack, gce, etc).
> The fix is trivial, I'll create a pull request. I choose priority Major, since this flaw
makes the create_volume call next to unusable, because it is impossible to know which volume
was created by the call (since name is not unique).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message