GitHub user rajujith added a comment to the discussion: [Feature Request] Allow Importing Instances Tied to Domains Without Account Requirement
> ### The required feature described as a wish > > Hi, > > Good day to you. > > I have a question regarding instance management in CloudStack. Is there a way > to import instances into a domain or sub-domain without associating them with > a specific account? Unfortunately not. According to the current design, virtual resources in CloudStack are owned by either an Account or a Project, not a Domain. You can also explore projects. > In my setup, I use multiple domains and sub-domains to separate instances > based on the type of datastore they use—specifically SSD and HDD. These have > different performance profiles and are subject to different quotas. To manage > this, I’ve been using domains to isolate the workloads by datastore type. For this use case, typically, different service offerings with tags are created. You may consider this. > However, CloudStack currently requires me to create a separate account for > each domain or sub-domain, which feels redundant for my use case. Ideally, > I’d like to manage instances directly at the domain level without needing to > create and manage multiple accounts. > > Additionally, I’ve noticed that CloudStack allows setting storage limits only > at the primary storage level in general, rather than per individual > datastore. Is there a way to enforce or separate primary storage quotas per > datastore, instead of applying a single limit across all datastores in a > domain? That level of granularity would be very useful for environments like > mine. > > Thank you for your time and assistance. Yes, https://www.shapeblue.com/hardware-specific-resource-limits/ GitHub link: https://github.com/apache/cloudstack/discussions/11338#discussioncomment-14042303 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
