Project

General

Profile

Actions

Bug #58654

open

Add personalized configuration failed when deploying cluster using "cephadm bootstrap"

Added by Rongqi Sun about 1 year ago.

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

0%

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

Description

As I know, I could add conf file when using cephadm bootstrap like cephadm boootstrap --config my.conf .... With this way, configuration related with [global]/ [mon]/ [mgr] would work, but others with [osd]/ [mds]... would not. The reason is that even everything in my.conf would store in mon.database, when deploying a new OSD service, the process will generate minimal conf file with extra args instead of reading from database. In this condition, the only way I can consider to pass conf to OSD is using ceph cephadm set-extra-ceph-conf -i my.conf. That means cephadm bootstrap --config only works on configuration relates with mon/ mgr, and actually no configuration args are provided when using ceph orch daemon add osd....I am not sure if it is cephadm's design, cephadm's undeveloped feature or I miss something. Look forward to anyone's response.

No data to display

Actions

Also available in: Atom PDF