cloudstack/engine
Prachi Damle 3a6adb3c58 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.
2013-12-06 13:18:37 -08:00
..
api CLOUDSTACK-5399: Add option to createVolume API to specify a VM, to place the volume appropriately and attach immediately 2013-12-06 13:18:37 -08:00
components-api CLOUDSTACK-4880: 2013-12-05 14:14:31 -08:00
network Updating pom.xml version numbers for release 4.3.0-SNAPSHOT 2013-08-01 10:35:00 -04:00
orchestration CLOUDSTACK-5399: Add option to createVolume API to specify a VM, to place the volume appropriately and attach immediately 2013-12-06 13:18:37 -08:00
schema CLOUDSTACK-5261: support for alert publishing via Root admin web api 2013-12-03 17:08:23 -08:00
service Fix a few xml wellformedness issues 2013-09-21 14:58:56 +08:00
storage CLOUDSTACK-5261: support for alert publishing via Root admin web api 2013-12-03 17:08:23 -08:00
pom.xml the cloud-engine-storage-integration-test sub-project should not depend 2013-09-02 14:32:25 +02:00