[
https://issues.apache.org/jira/browse/CLOUDSTACK-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841721#comment-13841721
]
ASF subversion and git services commented on CLOUDSTACK-5399:
-------------------------------------------------------------
Commit 3a6adb3c581c0b34f9b675de41fcf6a54a7c1452 in branch refs/heads/4.3 from
[~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3a6adb3 ]
CLOUDSTACK-5399: Add option to createVolume API to specify a VM, to place the
volume appropriately and attach immediately
Changes:
- Added 'virtualmachineid' parameter to the createVolume API to specify a
VM for the volume. The Vm should be in 'Running' or 'Stopped' state.
- This parameter is used only when createVolume API is called using
snapshotid parameter
- When this parameter is set, the volume is created from the snapshot in
the pod/cluster of the VM. Also the volume is then attached to the VM in the
same request
- If attach Volume fails but create has succeeded, the API errors out but
the Volume created remains available. User may attach the same volume later
- When Vm is provided, but if no storage pool is available in the VM's
pod/cluster then the volume is not created and API fails.
> 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)
