cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9088) migrateto parameter associated with migrateVirtualMachineWithVolume API needs an example
Date Fri, 22 Apr 2016 05:07:12 GMT

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

Koushik Das updated CLOUDSTACK-9088:
------------------------------------
    Fix Version/s: 4.9.0

> migrateto parameter associated with migrateVirtualMachineWithVolume API needs an example
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9088
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9088
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Doc
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>             Fix For: 4.9.0
>
>
> ISSUE:
> API docs for migrateVirtualMachineWithVolume API does not clearly state the format for
parameter "migrateto". The doc suggests that it accepts volume/pool pair but fails to mention:
> 1. Format.
> 2. If value for volume/pool should be name, ID or UUID.
> 3. Whether "pool" referenced here is source or target.
> It may be difficult for users to perceive that the format needs to something like ...&migrateto[0].volume=<UUID>&migrateto[0].pool=<UUID>&...
> We need to provide example for better understanding like we have done for "iptonetworklist"
parameter associated with deployVirtualMachine API.



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

Mime
View raw message