Feature #44783: c-v's batch report doesn't show if the disk is going to be encrypted - ceph-volume - Ceph

Actions

Copy link

Feature #44783

closed

c-v's batch report doesn't show if the disk is going to be encrypted

Added by Joshua Schmid about 4 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Target version:

Ceph - v15.0.0

% Done:

Source:

Development

Tags:

Backport:

Reviewed:

Affected Versions:

Pull request ID:

34740

Description

/usr/sbin/ceph-volume lvm batch --no-auto /dev/vdb --dmcrypt --report --format json

gives

{
    "changed": true,
    "osds": [
        {
            "block.db": {},
            "data": {
                "human_readable_size": "24.00 GB",
                "parts": 1,
                "path": "/dev/vdb",
                "percentage": 100.0,
                "size": 24
            }
        }
    ],
    "vgs": []
}

which is missing the `encrypted` flag.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Jan Fajerski about 4 years ago

Subject changed from c-v's report doesn't show if the disk is going to be encrypted to c-v's batch report doesn't show if the disk is going to be encrypted

Actions

Copy link

Updated by Jan Fajerski about 4 years ago

Tracker changed from Bug to Feature

Changing this to a feature.

I'd like input on what you'd expect. An encrypted, but where? Under the 'data' key, under the OSD key? Should be be false in case of unencrypted or missing?

I'd propose an new 'encrypted' key under 'data' that is either false or true.

Actions

Copy link

Updated by Joshua Schmid about 4 years ago

I assume that --dmcrypt is a block key that will affect all provided disks.
If that's the case, it would suffice to put it one layer above, on the same level as "changed" and "osds"

I don't know how c-v treat external db/wals when this flag is provided. If these LVs are not encrypted we might be better off, being more granular by putting it into the 'data' struct.

Actions

Copy link