[cloudstack-documentation] branch master updated: Volumes from snaps doc update (#59)

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

andrijapanic pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new 8eb4862  Volumes from snaps doc update (#59)
8eb4862 is described below

commit 8eb48626eeb08746c5ffbb2d36f714aa56a19d9b
Author: Andrija Panic <45...@users.noreply.github.com>
AuthorDate: Fri May 1 18:38:13 2020 +0200

    Volumes from snaps doc update (#59)
    
    * offering required for volumes created from snaps
    
    * image added
    
    * spell check
    
    * Update source/adminguide/storage.rst
    
    Co-Authored-By: Paul Angus <pa...@shapeblue.com>
    
    * Update source/adminguide/storage.rst
    
    Co-Authored-By: Paul Angus <pa...@shapeblue.com>
    
    Co-authored-by: Paul Angus <pa...@shapeblue.com>
---
 source/_static/images/volume-from-snap.PNG | Bin 0 -> 8404 bytes
 source/adminguide/storage.rst              |  12 +++++++++++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/source/_static/images/volume-from-snap.PNG b/source/_static/images/volume-from-snap.PNG
new file mode 100644
index 0000000..5eb9a5e
Binary files /dev/null and b/source/_static/images/volume-from-snap.PNG differ
diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 44f5fcb..1254931 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -230,6 +230,15 @@ are not allocated on the physical storage device until you attach the
 volume. This optimization allows the CloudStack to provision the volume
 nearest to the guest that will use it when the first attachment is made.
 
+When creating a new volume from an existing ROOT volume snapshot,
+it is required to explicitly define a Disk offering (UI will offer only Disk
+offerings whose disk size is equal or bigger than the size of the snapshot).
+
+|volume-from-snap.PNG|
+
+When creating a new volume from an existing DATA volume snapshot, the disk offering
+associated with the snapshots (inherited from the original volume) is assigned
+to the new volume.
 
 Using Local Storage for Data Volumes
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -657,7 +666,6 @@ to a VM.
 A completed snapshot is copied from primary storage to secondary
 storage, where it is stored until deleted or purged by newer snapshot.
 
-
 How to Snapshot a Volume
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -802,3 +810,5 @@ snapshot data.
    :alt: Detach Disk Button.
 .. |Migrateinstance.png| image:: /_static/images/migrate-instance.png
    :alt: button to migrate a volume.
+.. |volume-from-snap.PNG| image:: /_static/images/volume-from-snap.PNG
+   :alt: Offering is needed when creating a volume from the ROOT volume snapshot.