Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add: Finding Primary storage for migration #325

Merged
merged 5 commits into from
Jan 17, 2024
Merged

Add: Finding Primary storage for migration #325

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5c98464
Find primary storage
rajujith Jun 29, 2023
98e878a
Update source/adminguide/storage.rst
rajujith Dec 7, 2023
0d21ad9
Update source/adminguide/storage.rst
rajujith Dec 7, 2023
beae481
Update source/adminguide/storage.rst
rajujith Dec 7, 2023
90405ce
Merge branch 'main' into main
rajujith Dec 7, 2023
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
19 changes: 12 additions & 7 deletions source/adminguide/storage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -638,13 +638,18 @@ be restarted.

Finding Primary Storage for Migration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When you click on migrate volume, CloudStack lists the available primary storage. CloudStack uses its storage pool allocators to identify the primary storages that are available and returns a list that is suitable for the selected volume's migration.
The list also could include primary storages that are mentioned as 'Not suitable'. The criteria for which the primary storages are not suitable are:
- Storage tag mismatch with the volume's Disk offering's storage tag
- Doesn't have enough capacity.
- Reached its disable threshold
- Disabled.
- Mismatch in the type of storage such as Shared /Local.

When you click on migrate volume, CloudStack lists the available primary
storage. CloudStack uses its storage pool allocators to identify the primary
storages that are available and returns a list that is suitable for the selected
volume's migration.
The list also could include primary storages that are mentioned as
'Not suitable'. The criteria for which the primary storages are not suitable are:
- Storage tag mismatch with the volume.
- Doesn't have enough capacity.
- Reached its disable threshold.
- Disabled.
- Mismatch in the type of storage such as shared /Local.

Resizing Volumes
~~~~~~~~~~~~~~~~
Expand Down