Affinity Management - Githubissues

aenix-io / cozystack

Free and Open Source PaaS-platform for seamless management of virtual machines, managed Kubernetes, and Databases-as-a-Service

https://cozystack.io

Apache License 2.0

906 stars 51 forks source link

Affinity Management #293

Open matthieu-robin opened 3 months ago

matthieu-robin commented 3 months ago

Is it possible to manage the affinity by groups of nodes? and manage by tenant? ( taints, region, zone,...)

gecube commented 3 months ago

Hi! Yes, but please provide a more complete use-case. Example:

"Like a DevOps engineer I want to put a tenants on dedicated nodes of management cluster for the better isolation" ...

matthieu-robin commented 3 months ago

:-) The idea: 3 datacenters, multiples hosts per datacenter, stretch cluster between datacenters. When a user create a VM, DB, etc.. He should be able to select his datacenters, and from storage point of view, where are replication for High Availability beteween datacenter? in the DC or splited between DC?.. etc... Let me know if I'm not clear enough.

gecube commented 3 months ago

So you may run into different options. Like:

I don't care at all (so system will place the DB on the first appropriate node in any DC)
choose from one of DC: DC1, DC2, DC3
use local volume vs replicated volume (this option should be configurable even we are using particular DC).

Which ones do you need?

The idea to have cluster of DB stretched between DC is reasonable as it is the only option to have HA. But it is not the only use-case

matthieu-robin commented 3 months ago

if we have a VM in DC1 with replication storage. It should be interesting if we can select " Replication between DCs" or "replication between nodes in my DC". In the first case, the VM can restart on a second DC (in case of DC1 failure) In the second case, the VM can restart only on a node of the DC1, and no HA in case of DC1 failure. and the mixed version: I have 2 replicas of my VM on the same DC, and a third replica on a external DC (2 or 3).

The final idea is to purpose to our users to select the level of HA. What do you think?

gecube commented 3 months ago

we don't use VM for databases, queues, storage... tenant k8s service is working on top of VMs and you can still order VMs on your own and install something into it.