GitHub user SviridoffA added a comment to the discussion: Clarification Needed: Changing scope of Primary Storage
> Currently, I’m aware of two ways to do this: first is to disable the primary > storage, and then change the scope from the UI (I’m using ACS 4.19.3). The > second method is to directly edit the database. My understanding is that > disabling the primary storage will simply disable provisioning and not cause > virtual machines to stop. Am I right? Or would it be better to directly make > edits to the database? After testing it practically, I can answer myself: yes, ‘disable’ only disables provisioning. I ended up changing the scope to ‘zone’ without any downtime. > And one more question: If I decide to use different types of servers > (different CPUs) within the same cluster, for example, I were to separate > them using tags associated with service offerings. Is this correct usage, and > is this even possible at all? Regarding this issue, has anyone done something similar? What potential problems could arise? GitHub link: https://github.com/apache/cloudstack/discussions/11365#discussioncomment-13952407 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
