Project

General

Profile

Actions

Bug #45443

closed

ceph-volume: support mode-specific availability fields in inventory subcommand

Added by Satoru Takeuchi almost 4 years ago. Updated 5 months ago.

Status:
Won't Fix
Priority:
Normal
Target version:
-
% Done:

100%

Source:
Community (user)
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

There are two modes of OSD, the traditional "lvm mode" and the new "raw mode".
Although LVM mode can only be created on top of raw disk or its partition,
there is no such limitation in raw mode. However, the "available" field
of `ceph-volume inventory` doesn't consider raw mode at all. For example,
crypt type device is regarded as unavailable even though `ceph-volume raw prepare`
can create an OSD in this device. We should support mode-specific availability
fields in `inventory` subcommand.

Related discussion:
https://github.com/ceph/ceph/pull/34375#issuecomment-623301127


Related issues 1 (0 open1 closed)

Related to ceph-volume - Feature #44911: support dmcrypt device that is already encrypted by userResolved

Actions
Actions #1

Updated by Sebastian Wagner almost 4 years ago

  • Project changed from Ceph to ceph-volume
Actions #2

Updated by Jan Fajerski over 3 years ago

  • Status changed from New to Fix Under Review
  • Backport set to octopus
  • Pull request ID set to 34966
Actions #3

Updated by Jan Fajerski over 3 years ago

  • Related to Feature #44911: support dmcrypt device that is already encrypted by user added
Actions #4

Updated by Konstantin Shalygin 5 months ago

  • Status changed from Fix Under Review to Rejected
  • Assignee set to Satoru Takeuchi
  • Target version deleted (v16.0.0)
  • % Done changed from 0 to 100
  • Source set to Community (user)
Actions #5

Updated by Konstantin Shalygin 5 months ago

  • Status changed from Rejected to Won't Fix
Actions

Also available in: Atom PDF