Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions source/adminguide/service_offerings.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
34 changes: 34 additions & 0 deletions source/adminguide/storage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as you state below that shrinking is not supported, I think an extra remark on this line is in order. It certainly implies that shrinking is allowed.

+---+----------------------------+---------------------------+-------------------------------+

.. 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.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DaanHoogland does this disclaimer suffice your concerns?

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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down