Bug #45656: orchestrator: Host affinity/antiaffinity - Orchestrator - Ceph

Actions

Copy link

Bug #45656

closed

orchestrator: Host affinity/antiaffinity

Added by Juan Miguel Olmo Martínez almost 4 years ago. Updated almost 4 years ago.

Status:

Duplicate

Priority:

Low

Assignee:

Category:

orchestrator

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Maybe we should follow the design/"spirit" embedded in:
k8s's Assigning Pods to Nodes

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

Related issues 1 (1 open — 0 closed)