Page History

Volumes

Status

Attaching Volumes

1.navigate to Storage-volumes
2.select the detached data disk
3.click on "Actions" and select "Attach Disk" to attach to a particular instace
4. select the instance and click "Ok" button  to attach the disk to selected instance in the "Attach Disk" pop-up window

1.shows list of volumes
3."Attach Disk" pop-up box will display with list of  instances
4. disk should be  attached to instance successfully and both UI and database(volumes table) should reflect the changes( i.e attached disk details should be updated with  attached vm_instance ID and device id )

Passed

Detaching Volumes

1.navigate to Storage-volumes
2. selected the data disk which is attached to instance
3.click "Actions" and select the "Detach Disk"

data disk should be detached from instance and detached data disk details should be updated properly(i.e Instance Name -detached and Device ID is null)

Passed

Download volumes

1.navigate to Storage-volumes
2. selected the data disk which is attached to instance
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f2b78bcbdda30222-cd4fd20b-4a7642b6-851db72a-d2013855bd1b5e70f026fdb2"><ac:plain-text-body><![CDATA[[some fundamental steps here are missing. in each os after attaching disk, you need to format and mount it before writing to it. downloading a blank volume would probably fail]
]]></ac:plain-text-body></ac:structured-macro>
3.perform download volume
4.select another data disk with is not attahced instance
5.perform "download volume "

3. download volume will fail with proper error message "Failed - Invalid state of the volume with ID: . It should be either detached or the VM should be in stopped state"
.
5. able to download the volume when its not attached to instace

Passed

Delete Volumes

case 1
1.navigate to Storage-volumes
2. selected the data disk
3.click on 'Actions" menu and select the "Delete volume"

case 2
4.select another data disk with is  attahced instance
5.clcik on "Actions" menu and check for "Delete Volume"

case 1:
volume should be deleted successfully and listVolume should not contain the deleted volume details.

Case 2:
"Delete Volume" menu item not shown under "Actions" menu.
(UI should not allow  to delete the volume when it is attahced to instance by hiding the menu Item)

Passed

Create Volume

1. Perform "Add volume" by provinding name, availability zone and disk offering details.(i.e go to Storage-Volumes-)
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="8b2aa9d485478143-17b2a4e2-43b54972-b0d183d3-6a186674b5f19bc92edd61fc"><ac:plain-text-body><![CDATA[[we shoudl execute this against every storage size, sanity check against that but also a few custom sized disk offerings]

volume should be created successfully and listVolumes should  contain the created volumes. Database should reflects with new created volume details(volumes table)

Passed

]]></ac:plain-text-body></ac:structured-macro>

1

Upload a data disk

call upload volume API with following parameters

• HTTP URL of the data disk,
• Zone ID,
• Name,
• Description,
• Hyper visor

Upload volume is successful

P1

2

upload volume when disk type is not compatible with hyper visor type

call upload volume API with following parameters

• HTTP URL of the data disk,
• Zone ID,
• Name,
• Description,
• Hyper visor
  Such that URL contains Xen compatible data disk but hyper visor mentioned is KVM/VMWare

Error should be reported

P2

Passed

3

Upload a Volume when maximum volume for the account is reached

call upload volume API with following parameters

• HTTP URL of the data disk,
• Zone ID,
• Name,
• Description,
• Hyper visor

Error saying max limit is reached should be reported

P1

  Passed

4

upload a volume having size greater than max allowable size

call upload volume API with following parameters

• HTTP URL of the data disk,
• Zone ID,
• Name,
• Description,
• Hyper visor

Error saying size exceeded should be reported

P2

5

upload a volume with same name as one already existing

Volume is created successfully

P3

6

upload a volume with the name that's  already deleted

upload a volume
delete this volume
upload another volume with the same name as the one in step 1

upload should be successful

P3

7

upload data disk with different format for xenserver

 Upload volume should be successful for all the formats

P1

8

upload data disk with different format for VMware

 Upload volume should be successful for all the formats

P1

9

upload data disk with different format for KVM

 Upload volume should be successful for all the formats

P1

upload data disk with different format for OVM

 Upload volume should be successful for all the formats

P1

10

Attach a uploaded data disk

call attach volume api with following parameter

• Volumeid
• VM

• Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm.

P1

11

Attach the uploaded data disk with different format for xenserver

Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format.

P1

12

Attach the uploaded data disk with different format for VMware

Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format.

P1

13

Attach the uploaded data data disk with different format for KVM

Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format.

P1

Attach the uploaded data data disk with different format for OVM

Passed

Verify Attach Volume API will move (and not Copy) the volume from secondary storage to primary storage and attach to the vm for the disk format.

P1

14

List volume showing states of volumes

call list volumes api

Verify the response shows different states of the volumes likeNOT_DOWNLOADED, DOWNLOAD_IN_PROGRESS, DOWNLOADED

P1

  Passed

15

list volumes showing volume residing on secondary or primary

call list volumes api

Verify the response shows where the volume is residing

P1

  Passed

16

delete volume residing in secondary storage

call delete volume api with volume id

volume should be deleted

P1

  Passed