This is an automated email from the ASF dual-hosted git repository.
dahn 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 5d6ef85 Configure Root disk size via Service Offering (#162)
5d6ef85 is described below
commit 5d6ef85bc1586e01853fe50079093d62a83848d7
Author: Gabriel Beims Bräscher <[email protected]>
AuthorDate: Fri Dec 11 15:17:57 2020 -0300
Configure Root disk size via Service Offering (#162)
---
source/adminguide/service_offerings.rst | 3 +++
source/adminguide/storage.rst | 34 +++++++++++++++++++++++++++++++++
2 files changed, 37 insertions(+)
diff --git a/source/adminguide/service_offerings.rst
b/source/adminguide/service_offerings.rst
index 93c84f5..be8fde5 100644
--- a/source/adminguide/service_offerings.rst
+++ b/source/adminguide/service_offerings.rst
@@ -135,6 +135,9 @@ offerings. The compute service offering specifies:
- Guest Networking type (virtual or direct)
+- Root Disk size (optional). If not defined by CloudStack administrator,
+ users can set a custom Root disk size.
+
- Tags on the root disk
The disk offering specifies:
diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
index 9757d45..9993c29 100644
--- a/source/adminguide/storage.rst
+++ b/source/adminguide/storage.rst
@@ -617,6 +617,40 @@ To resize a volume:
#. Click OK.
+Root Volume size defined via Service Offering
+~~~~~~~~~~~~~~~~
+
+If a Service Offering is created with a root disk size, then resizing the Root
volume is possible only by resizing the VMs service offering.
+
+Service offering Root resizing constrains:
+
+#. Users cannot deploy VMs with custom root disk size when using such offerings
+
+#. Users cannot resize the VM root disk size when using such offerings
+
+#. The Root Volume of such VMs can only be resized when changing to another
Service Offering with a Root disk size equals or larger than the current one.
+
+#. Users can change the VM offering to a service offering with a Root size of
0GB (default) and then customize the volume size.
+
+The following table shows possible combinations of Service offering supported
resizing based on the offering Root disk size:
+
++---+----------------------------+---------------------------+-------------------------------+
+| # | Service Offering Root size | new Service Offering Root | Does support
offering resize? |
++---+----------------------------+---------------------------+-------------------------------+
+| 1 | 0GB (default) | Any | YES
|
++---+----------------------------+---------------------------+-------------------------------+
+| 2 | 5GB | 5GB | YES
|
++---+----------------------------+---------------------------+-------------------------------+
+| 3 | 5GB | 10GB | YES
|
++---+----------------------------+---------------------------+-------------------------------+
+| 4 | 10GB | 5GB | NO
|
++---+----------------------------+---------------------------+-------------------------------+
+| 5 | Any | 0GB | YES
|
++---+----------------------------+---------------------------+-------------------------------+
+
+.. note::
+ Shrinking the Root disk is not supported via the service offering resizing
workflow. All the combinations above assume a transition to Root disks with
size equals or bigger than the original.
+ Service Offerings with Root size of 0GB do not change the disk size to Zero
and indicates that the offering do not enforces a Root disk size.
Reset VM to New Root Disk on Reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
