Feature #2498
closed
standardize keyring locations for daemons
Added by Sage Weil almost 12 years ago.
Updated almost 12 years ago.
Description
Currently keyring is controlled by g_conf->keyring, with a default search path that makes sense for clients but not much else.
The monitor now hard-codes the location to $mon_data/keyring. Our suggested configs do $osd_data/keyring and i forget what for the mds.
I suggest either:
- hard code to $whatever_data/keyring
- create a new $mds_data dir (eventually the mds may want to store other local data)
- Description updated (diff)
- Target version set to v0.49
- Translation missing: en.field_position deleted (
1)
- Translation missing: en.field_position set to 1
- Status changed from New to Fix Under Review
- Translation missing: en.field_position deleted (
13)
- Translation missing: en.field_position set to 1
- Target version deleted (
v0.49)
- Translation missing: en.field_position deleted (
1)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position deleted (
1)
- Translation missing: en.field_position set to 1
- Status changed from Fix Under Review to Resolved
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
3)
- Translation missing: en.field_position set to 3
- Target version set to v0.49
- Translation missing: en.field_position deleted (
3)
- Translation missing: en.field_position set to 1265
- Translation missing: en.field_story_points changed from 5 to 3
- Translation missing: en.field_position deleted (
1265)
- Translation missing: en.field_position set to 1265
- Translation missing: en.field_position deleted (
1281)
- Translation missing: en.field_position set to 2
- Project changed from Ceph to devops
- Target version deleted (
v0.49)
- Target version set to v0.49
Also available in: Atom
PDF