deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-390) cimi: volume name is not set
Date Thu, 06 Dec 2012 00:42:58 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510982#comment-13510982
] 

Dies Koper commented on DTACLOUD-390:
-------------------------------------

You have reproduced it correctly. I was so focused on the name that I forgot to mention the
same issue with the capacity. Both are clearly not passed, so I would not be surprised there
is an issue with :snapshot_id too.

We see the issue with the fgcp backend; when I log in to the fgcp portal (i.e. not Deltacloud),
I can see that the name is a timestamp, not my specified name.

The Deltacloud cimi client (http://localhost:4001/cimi/volumes) returns to you what DC stored
in its database, not what it passed to the creation operation, so clearly not what the actual
situation is.
I thought it was obvious from showing the "p opts" that there is a problem, but if you're
not familiar with the code, please try with a live cloud provider to create a volume and then
log in to that provider's portal and see what has been created.

I hadn't noticed the id being displayed for the name (or actually, I noticed it before but
thought it was fixed). I suppose it was not.
                
> cimi: volume name is not set
> ----------------------------
>
>                 Key: DTACLOUD-390
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-390
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: CIMI/Frontend
>         Environment: any driver, reproducible with mock
>            Reporter: Dies Koper
>            Assignee: Joseph J. VLcek
>
> To reproduce, in mock driver, add debugging statement:
>     def create_storage_volume(credentials, opts={})
>     p opts # print passed-in options
> d:\>curl --user "mockuser:mockpassword" http://localhost:3001/cimi/volumes?format=xml
-X POST -H "Content-Type: application/json"  -d@create-volume.json
> with create-volume.json:
> { "resourceURI": "http://schemas.dmtf.org/cimi/1/VolumeCreate", "name": "myVolume1",
"description": "My first new volume", "volumeTemplate": { "volumeConfig": { "href": "http://example.com/vConfigs/small"
} } }
> server outputs:
> {:capacity=>0, :snapshot_id=>nil}
> Note no 'name'. Also note that doing a GET on volumes does list the name correctly, don't
let it fool you.

--
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

Mime
View raw message