You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/storage.rst
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -617,6 +617,40 @@ To resize a volume:
617
617
618
618
#. Click OK.
619
619
620
+
Root Volume size defined via Service Offering
621
+
~~~~~~~~~~~~~~~~
622
+
623
+
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.
624
+
625
+
Service offering Root resizing constrains:
626
+
627
+
#. Users cannot deploy VMs with custom root disk size when using such offerings
628
+
629
+
#. Users cannot resize the VM root disk size when using such offerings
630
+
631
+
#. 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.
632
+
633
+
#. Users can change the VM offering to a service offering with a Root size of 0GB (default) and then customize the volume size.
634
+
635
+
The following table shows possible combinations of Service offering supported resizing based on the offering Root disk size:
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.
653
+
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.
0 commit comments