Skip to content

Commit 8a7f0c5

Browse files
Add doc for importing and unmanaging volumes (#390)
Co-authored-by: Andrija Panic <45762285+andrijapanicsb@users.noreply.github.com>
1 parent 7f8c887 commit 8a7f0c5

File tree

4 files changed

+80
-0
lines changed

4 files changed

+80
-0
lines changed
68.5 KB
Loading
182 KB
Loading
51.7 KB
Loading

source/adminguide/storage.rst

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1011,6 +1011,79 @@ Following is the example for checkVolume API usage and the result in the volume
10111011
},
10121012
}
10131013
1014+
1015+
Importing and Unmanaging Volumes from Storage Pools
1016+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1017+
1018+
Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from primary storage pools are supported.
1019+
1020+
.. note::
1021+
Currenty the supported storage types are: NFS, Ceph and Local storage for KVM hypervisor.
1022+
1023+
#. Log in to the CloudStack UI as an administrator.
1024+
1025+
#. In the left navigation bar, click *Tools > Import DATA Volumes* section.
1026+
1027+
#. Select the scope of the storage pool (Zone, Cluster, Host).
1028+
1029+
#. Select the zone/pod/cluster/host of the storage pool.
1030+
1031+
#. Select the storage pool.
1032+
1033+
#. The unmanaged volumes on the storage pool are listed on the left panel.
1034+
1035+
#. The managed volumes on the storage pool are listed on the right panel.
1036+
1037+
|list-unmanaged-managed-volumes.png|
1038+
1039+
To import a volume:
1040+
1041+
#. select a unmanaged volume from the left panel, click "Import Volume" icon.
1042+
1043+
#. In the Import Volume pop-up, select the Account Type, Domain/Account/Project and a disk offering.
1044+
1045+
#. Click OK.
1046+
1047+
|import-volume.png|
1048+
1049+
.. note::
1050+
- The volume to be imported must be placed in the root directory of the storage pool.
1051+
1052+
- The format of the volume must be QCOW2 on NFS/Local storage, and RAW on Ceph storage.
1053+
1054+
- The volume must not be encrypted.
1055+
1056+
- The volume must not be locked.
1057+
1058+
- The volume must not have a backing file.
1059+
1060+
1061+
.. note::
1062+
By default, the volume is imported for the caller if Domain/Account/Project are not set. By default, the imported volumes use the default disk offering "Default Custom Offering for Volume Import"
1063+
(on Shared storages) or "Default Custom Offering for Volume Import - Local" (on Local storages).
1064+
1065+
To unmanage volume(s):
1066+
1067+
#. select the volumes to be unmanaged from the right panel
1068+
1069+
#. click "Unmanage Volume" or "Unmanage Volumes" icon
1070+
1071+
#. click OK in the confirmation dialog.
1072+
1073+
|unmanage-volume.png|
1074+
1075+
.. note::
1076+
- The volume to be unmanaged must not be attached to any VM as ROOT disk or DATA disk.
1077+
1078+
- The volume to be umnanaged must be at Ready state.
1079+
1080+
- The volume must not be encrypted.
1081+
1082+
- The volume must not be locked by another process.
1083+
1084+
- The volume must not have a backing file.
1085+
1086+
10141087
Working with Volume Snapshots
10151088
-----------------------------
10161089
@@ -1342,3 +1415,10 @@ Deleting objects from a bucket
13421415
:alt: Upload button
13431416
.. |adding-local-pool-via-ui.png| image:: /_static/images/adding-local-pool-via-ui.png
13441417
:alt: Adding Local Storage Pool via UI
1418+
.. |list-unmanaged-managed-volumes.png| image:: /_static/images/list-unmanaged-managed-volumes.png
1419+
:alt: List of Unmanaged and Managed Volumes
1420+
.. |import-volume.png| image:: /_static/images/import-volume.png
1421+
:alt: Import Volume
1422+
.. |unmanage-volume.png| image:: /_static/images/unmanage-volume.png
1423+
:alt: Unmanage Volume
1424+

0 commit comments

Comments
 (0)