René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"No method to apply quota on storage tags","articleBody":"### problem\n\nA domain admin can add a data disk to their instance depending on quota but not on tags. If I am tagging a primary storage as \"sas 10k iops\" and another as \"sata 1k iops\" and I am offerign a different price for each, the quota offered to the tenant has no way to understand which of the two tags (or storage classifications) it should use. It only knows it is primary storage. Is there any way to tackle this already in place that I am missing?\n\n### versions\n\nCloudstack management 4.20, KVM hosts based on redhat 8.\n\n### The steps to reproduce the bug\n\n1. add tags to primary storages based on performance\n2. set the tags to new storage offerings\n3. create instance for a tenant based on specific storage tag\n4. assign the VM to the tenant and add additional storage quota so he can add data disk\n5. customer adds data disk based on any of the available offerings, even more expensive than the one originally purchased\n\n\n### What to do about it?\n\nIncorporate TAGS in quota. Alternatively I was thinking maybe I can set the disk offering to not be \"public\" or choose specific domain for a disk offering. This way we will create too many offerings to assign wherever needed and we still will have no way to limit how many gigs are used per TAG. Only which domain has access to whichever offering for quota based on primary or secondary, not tag.","author":{"url":"https://github.com/alsko-icom","@type":"Person","name":"alsko-icom"},"datePublished":"2025-02-13T09:04:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/10382/cloudstack/issues/10382"}