[
https://issues.apache.org/jira/browse/DTACLOUD-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571050#comment-13571050
]
Dies Koper commented on DTACLOUD-453:
-------------------------------------
I was meaning to raise a JIRA for this and forgot. Thanks.
When I did a grep on def create_storage_volumes, only a few drivers appeared:
ec2, fgcp, mock and openstack.
With def storage_volumes, two more: rhevm and aruba.
The DC documentation lists the ec2 states (creating, available, in-use,
deleting, deleted, error) which are pretty close to the cimi ones (CREATING,
AVAILABLE, CAPTURING, DELETING, ERROR and provider extended ones).
I was thinking the easiest way to converge would be to use the ec2 states (in
uppercase) for the Deltacloud API.
In a recent patch I translate IN-USE to AVAILABLE for the cimi front-end (I
didn't consider IN-USE a vendor extension, it's just a shortcut of a
configuration that can be retrieved using cimi in another way) and have aligned
the fgcp driver too.
Looking at the code, the openstack and mock drivers only uses AVAILABLE and
IN_USE.
rhevm only AVAILABLE, aruba only IN-USE.
If everyone's okay with that, we could just update that sentence in the DC
documentation and make them the DC standard states.
Do we need to add code to the ec2 driver to ensure no other states are returned
from the backend? (and map those to ...?). Do we really need a DELETED state or
can such resources just be filtered out?
> Document possible volume states and restrict possible values in API
> -------------------------------------------------------------------
>
> Key: DTACLOUD-453
> URL: https://issues.apache.org/jira/browse/DTACLOUD-453
> Project: DeltaCloud
> Issue Type: Bug
> Reporter: David Lutterkort
>
> Right now, different drivers follow different strategies for how to set the
> state of a volume. We need to document the possible values for the DC
> frontend, and make sure that all drivers only return those documented values.
> In particular, no driver can just return state values received from the
> backend (as the EC2 driver does right now)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
