Hi Nick- Chatted with Yehuda a bit about this today and one solution here is to have a different option that lets you specify a file where the secret is stored. The permissions on that file can then be set appropriately. This is similar to the --key vs --keyfile vs --keyring options. I think that's simpler than doing a #include type function... sage On Mon, 4 Mar 2013, Dan Mick wrote: > Nothing I'm able to find. You can specify a file with -c or > with CEPH_CONF, though, so you could always glue together a temp > file from pieces yourself. -c and CEPH_CONF can also be a list > of files to try (the first one that parses successfully will > be the configuration), if that's helpful. > > You may also be interested to know about "ceph --admin-daemon <admin socket> > config show". > > On 03/04/2013 01:53 PM, Nick Bartos wrote: > > Since radosgw requires the keystone admin token stored in ceph.conf, > > and certain unprivileged services we run need access to ceph.conf, I'm > > going to have to make a separate ceph.conf just for radosgw. However, > > it would be nice if I didn't have to duplicate things in the main > > ceph.conf. Is there any sort of "include another file" or similar > > functionality supported by the ceph.conf config file parser? > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |