Actions
Feature #45655
openorchestrator: Host affinity/antiaffinity
Status:
New
Priority:
Low
Assignee:
-
Category:
cephadm/scheduler
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Maybe we should follow the design/"spirit" embedded in:
[[k8s's Assigning Pods to Nodes:https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity]]
It should be possible to indicate where to deploy a daemon taking into account:
- Nodes where certain resources are available:
- Other daemons are/or not running:
For example:
Host-affinity:
cpu: '>= 50'
ram: '>= 50'
available_devices: '>= 1'
labelSelector:
- label: daemon_type
operator: in
value: osd
Host-antiaffinity:
labelSelector:
- label: daemon_type
operator: in
value: mon
and this means:
Deploy this daemon in a host with more than 50% of cpu available, more than 50% free ram, more than one available_devices for OSds.
In this host must run at least another OSD and no Monitors
Updated by Sebastian Wagner almost 4 years ago
- Has duplicate Bug #45656: orchestrator: Host affinity/antiaffinity added
Updated by Sebastian Wagner almost 4 years ago
- Category changed from orchestrator to cephadm/scheduler
Updated by Sebastian Wagner over 3 years ago
- Related to Feature #44993: cephadm: Resource-aware daemons placement added
Updated by Sebastian Wagner over 3 years ago
- Related to Feature #45769: cephadm: Don't deploy on offline hosts added
Actions