Clarification Needed: Changing scope of Primary Storage #11365
-
|
Hi everyone! I hope someone can explain this to me. Just want to be absolutely sure. I need to change scope of my primary storage from cluster to zone. I’m using Linstor. The goal is to add a cluster with different CPU types to the zone, while continuing to use and expand the same Linstor setup on the new cluster. 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? 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? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
After testing it practically, I can answer myself: yes, ‘disable’ only disables provisioning. I ended up changing the scope to ‘zone’ without any downtime.
Regarding this issue, has anyone done something similar? What potential problems could arise? |
Beta Was this translation helpful? Give feedback.
-
|
about the different servers in a cluster, it is not ideal but as long as they have the same OS it should work. Tagging should work and the deployment planner would avoid to small servers , but not too big ones. For neatness I’d say seperate them into different clusters. Especially now you have your zone wide primary storage. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @DaanHoogland ! Thank you so much for sharing your experience. This information is important to me. Closing this discussion.... |
Beta Was this translation helpful? Give feedback.
After testing it practically, I can answer myself: yes, ‘disable’ only disables provisioning. I ended up changing the scope to ‘zone’ without any downtime.