Documentation #53997
closedcephadm spec: document "config" key
0%
Description
Users can specify config options for a particular service:
service_type: mds
service_id: fsname
placement:
count: 2
config:
mds_cache_memory_limit: 8Gi
This is also going to be cleaned up properly. Let's document it!
Updated by Sebastian Wagner over 2 years ago
- Tracker changed from Bug to Documentation
Updated by Redouane Kachach Elhichou almost 2 years ago
- Status changed from New to In Progress
- Assignee set to Redouane Kachach Elhichou
- Pull request ID set to 46926
Updated by Redouane Kachach Elhichou almost 2 years ago
- Status changed from In Progress to Pending Backport
Updated by Redouane Kachach Elhichou almost 2 years ago
- Backport set to quincy,pacific
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56504: pacific: cephadm spec: document "config" key added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56505: quincy: cephadm spec: document "config" key added
Updated by Redouane Kachach Elhichou almost 2 years ago
- Related to Documentation #50883: cephadm: mds_cache_memory_limit added
Updated by Backport Bot over 1 year ago
- Tags changed from low-hanging-fruit to low-hanging-fruit backport_processed
Updated by Adam King over 1 year ago
- Status changed from Pending Backport to Resolved
Updated by Voja Molani 11 months ago
This configuration mechanism doesn't seem to work with config parameters like mgr/cephadm/device_enhanced_scan
- I guess it might only work with parameters missing the service/something/
part, such as the example mds_cache_memory_limit
?
It would be nice and save head-scratching & useless attempts if this was actually documented. The documentation at https://docs.ceph.com/en/quincy/cephadm/services/#service-specification makes it seem like there are no restrictions. But unless I am doing something wrong on 17.2.6 I could not set on the MGR service spec:
config: mgr/cephadm/device_enhanced_scan: true
Additionally, this fails at ceph orch apply
stage and it does not raise health warnings as documented.
It is as if these service/something/param
parameters are completely forgotten by this feature and the documentation - or I am doing something wrong which wouldn't be the first time.
Of course it would be even better if these parameters could be set in service specification (along with config-key
parameters!)
I guess I should open a new issue for this but I'm afraid it's just me doing it wrong again...