Project

General

Profile

Bug #50639

Request to provide an option to specify erasure coded pool as datapool while deploying cephfs using orchestration cli

Added by Sebastian Wagner 6 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm
Target version:
-
% Done:

0%

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

Description

[ceph: root@magna021 /]# ceph osd pool create cephfs-data-ec 128 erasure
pool 'cephfs-data-ec' created

[ceph: root@magna021 /]# ceph osd pool create cephfs-metadata-ec 128
pool 'cephfs-metadata-ec' created

[ceph: root@magna021 /]# ceph osd lspools
21 cephfs-data-ec
22 cephfs-metadata-ec

[ceph: root@magna021 /]# ceph orch apply mds cephfs-ec
Scheduled mds.cephfs-ec update...

[ceph: root@magna021 /]# ceph fs new cephfs-ec cephfs-metadata-ec cephfs-data-ec --force
Error EINVAL: pool 'cephfs-data-ec' (id '21') is an erasure-coded pool, with no overwrite support

[ceph: root@magna021 /]# ceph osd pool set cephfs-data-ec allow_ec_overwrites true
set pool 21 allow_ec_overwrites to true

[ceph: root@magna021 /]# ceph fs new cephfs-ec cephfs-metadata-ec cephfs-data-ec --force
new fs with metadata pool 22 and data pool 21

[ceph: root@magna021 /]# ceph fs ls
name: cephfs-ec, metadata pool: cephfs-metadata-ec, data pools: [cephfs-data-ec ]

I think we should change the order of things: making cephadm call ceph fs new. I mean, how many arguments to we want to add to ceph fs new??

History

#1 Updated by Sebastian Wagner 4 months ago

  • Category set to cephadm

Also available in: Atom PDF