Repository navigation
VM allocation on Primary Storage #8959
Description
ISSUE TYPE
- Enhancement Request
COMPONENT NAME
Primary Storage
CLOUDSTACK VERSION
N.R.
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
There should be better management regarding resource allocation on primary storages.
This could be done by allowing the user to be able to choose the disk offering when creating a VM via template via UI (as already happens when creating a VM via API).
Also the parameter "Preferred storage pool" (preferred.storage.pool) (The UUID of preferred storage pool for allocation.) should be configurable in the Cluster or Zone settings so the admin could always choose the preferred PS for every zone. This could be very useful also during storage migrations.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
Activity
DaanHoogland commentedon Apr 23, 2024
@cdfgallo , this sounds like more than one feature/enhancement request. Are you working on these? If not, and to enhance the chance of those getting implemented, can you split them and expand with screen shots/depiction of the desired situation.
cdfgallo commentedon Apr 23, 2024
@DaanHoogland you are right, this is an enhancement request.
Ok, I will split them.
Ty,
Fabio
shwstppr commentedon May 22, 2024
Not sure but could Flexible Tags functionality help in achieving a preferred pool allocation, @JoaoJandre?
JoaoJandre commentedon May 22, 2024
Hello @cdfgallo @shwstppr,
You could use flexible tags to finely choose which hosts receive which VMs and the same with storages and volumes. You can make rules to specifically allow only certain groups of tags into each host/storage. You can read a little more about tags and flexible tags in the documentation. Let me know if you do not understand the docs, and have further questions about flexible tags; I can try to answer them.
However, if you only want preferred and not exclusive hosts/storages, regular tags would do just fine as well.
vishesh92 commentedon Jun 12, 2024
@JoaoJandre I don't have much idea about flexible tags. Can you provide an example rule of how someone can use flexible tags in a way similar to
preferred.storage.poolbut per zone or cluster instead of an account?21 remaining items
nvazquez commentedon Aug 12, 2026
Hi @vishesh92 @DaanHoogland @JoaoJandre I can retake the work on PR #9564 after agreeing how we should proceed with this fix. As @weizhouapache has pointed out in the review, changing the scope of the existing setting may not be ideal.
Since now we have the option to extend some settings to multiple scopes, we can do the same for this setting: https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/configuration.html#granular-global-configuration-parameters. What do you think?