Project

General

Profile

Actions

Feature #45263

closed

osdspec/drivegroup: not enough filters to define layout

Added by Joshua Schmid about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm/osd
Target version:
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Considering this layout:


Device Path               Size         rotates available Model name
/dev/nvme0n1              349.32 GB    False   True      INTEL SSDPED1K375GA <- db/wal
/dev/sdb                  1.82 TB      True    True      ST2000DM001-1ER1    <- data
/dev/sdc                  1.82 TB      True    True      ST2000DM001-1ER1    <- data
/dev/sdd                  1.82 TB      True    True      ST2000DM001-1ER1    <- data
/dev/sde                  1.82 TB      True    True      ST2000DM001-1ER1    <- data
/dev/sdf                  1.82 TB      True    True      ST2000DM001-1ER1    <- data
/dev/sdg                  223.57 GB    False   True      INTEL SSDSC2KG24    <- data
/dev/sdh                  223.57 GB    False   True      INTEL SSDSC2KG24    <- data
/dev/sda                  223.57 GB    False   False     SAMSUNG MZ7LM240

With the switch from wiring up the filters with OR to AND gates, this very scenario got impossible to describe with the available filters.
This would be theoretically possible with the usage of `slots`. But those are not implemented.

Consider this issue as a leaflet to implement slots or add a new filter like device_id.


Related issues 1 (0 open1 closed)

Related to Orchestrator - Bug #45861: data_devices: limit 3 deployed 6 osds per nodeResolvedJoshua Schmid

Actions
Actions

Also available in: Atom PDF