[jira] [Updated] (CLOUDSTACK-5399) Add option to createVolume API to specify a VM, to place the volume appropriately and attach immediately

["Prachi Damle (JIRA)" <ji...@apache.org>]

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

Prachi Damle updated CLOUDSTACK-5399:
-------------------------------------

    Priority: Critical  (was: Major)

> Add option to createVolume API to specify a VM, to place the volume appropriately and attach immediately
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5399
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5399
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Prachi Damle
>            Assignee: Prachi Damle
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> Currently we do not know where volume from snapshot will be created.
> Make it worse one only can attach that disk to VM after volume is created which is created randomly.Therefore volume should be migrated to SR in POD where vm is running which takes a lot of time,
> We can improve this by setting vm id in the API, in doing so volumes will be created where VM is running and be attached to VM right away.



--
This message was sent by Atlassian JIRA
(v6.1#6144)