libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-758) Consistent state attribute for VolumeSnapshots
Date Thu, 15 Oct 2015 10:07:05 GMT


ASF GitHub Bot commented on LIBCLOUD-758:

GitHub user allardhoeve opened a pull request:

    [LIBCLOUD-758] Standardize volumesnapshot state


You can merge this pull request into a Git repository by running:

    $ git pull standardize-volumesnapshot-state

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #602
commit 370e8cb10ecb72b83d92cc319944536c6bfb8775
Author: Allard Hoeve <>
Date:   2015-10-15T09:48:38Z

    Add standardized snapshot states to EC2

commit bb7365bf6cf17e8972de2119f6ca894fe26a18ef
Author: Allard Hoeve <>
Date:   2015-10-15T10:00:15Z

    Add standardized snapshot states to OpenStack


> Consistent state attribute for VolumeSnapshots
> ----------------------------------------------
>                 Key: LIBCLOUD-758
>                 URL:
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>            Reporter: Allard Hoeve
>            Priority: Minor
> Parsing snapshot states is a hairy business at the moment. EC2 has the snapshot state
in the extra dict as "state", while OpenStack has it as "status". This makes for a poor experience
of libcloud.
> We should have a VolumeSnapshotState with standardized states and we should have the
drivers parse their various state values into these standardized states, just as we do for
Nodes and StorageVolumes.

This message was sent by Atlassian JIRA

View raw message