cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-5651) deployVm: customparameters param name has to be changed
Date Fri, 10 Jan 2014 18:08:53 GMT

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

Alena Prokharchyk resolved CLOUDSTACK-5651.
-------------------------------------------

    Resolution: Fixed

> deployVm: customparameters param name has to be changed
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-5651
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5651
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.0
>            Reporter: Alena Prokharchyk
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> deployVm API got a new param in 4.3 -“customparameters”. The description of the parameter
is very vague and generic “used to specify the custom parameters”.
> Is it just the metadata in form of value/key pairs? If so, please change the name to
“details” - the generic name used when specify key/value metadata in other API commands.

> Also you need to save this information in the “user_vm_details” table, and return
it in the UserVmResponse, “details” map parameter. I don’t see “custom parameters”
key map being returned anywhere in the UserVmResponse. Its very confusing, because whatever
is passed to the Create/Update call, should be returned in the response as well.
> It all has to be fixed in 4.3 branch.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message