weizhouapache commented on code in PR #390:
URL: 
https://github.com/apache/cloudstack-documentation/pull/390#discussion_r1572690092


##########
source/adminguide/storage.rst:
##########
@@ -1011,6 +1011,60 @@ Following is the example for checkVolume API usage and 
the result in the volume
    },
    }
 
+
+Importing and Unmanaging Volumes from Storage Pools
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Since Apache CloudStack 4.19.1.0, importing and unmanaging volumes from 
primary storage pools are supported.
+
+.. note::
+   Currenty the supported storage types are: NFS, Ceph and Local storage for 
KVM hypervisor.
+
+#. Log in to the CloudStack UI as an administrator.
+
+#. In the left navigation bar, click *Tools > Import DATA Volumes* section.
+
+#. Select the scope of the storage pool (Zone, Cluster, Host).
+
+#. Select the zone/pod/cluster/host of the storage pool.
+
+#. Select the storage pool.
+
+#. The unmanaged volumes on the storage pool are listed on the left panel.
+
+#. The managed volumes on the storage pool are listed on the right panel.
+
+|list-unmanaged-managed-volumes.png|
+
+To import a volume: 
+
+#. select a unmanaged volume from the left panel, click "Import Volume" icon. 
+
+#. In the Import Volume pop-up, select the Account Type, 
Domain/Account/Project and a disk offering.
+
+#. Click OK.
+
+|import-volume.png|
+
+.. note::
+   The volume to be imported must be placed in the root directory of the 
storage pool.
+   The format of the volume should be QCOW2 on NFS/Local storage, and RAW on 
Ceph storage.
+   Encrypted volumes cannot be unmanaged or imported.

Review Comment:
   ```suggestion
      The following volumes cannot be unmanaged or imported: (1) volume is 
encrypted; (2) volume is locked; (3) volume has a backing file.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to