Before to set per daemon options, is there an approach to get a full set of effective options for configuration? -yaguang -----Original Message----- From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of John Spray Sent: Wednesday, January 20, 2016 6:42 PM To: Sage Weil Cc: Ceph Development Subject: Re: /var/lib/ceph/*/*/config On Tue, Jan 19, 2016 at 3:15 PM, Sage Weil <sweil@xxxxxxxxxx> wrote: > I think we should add an optional 'config' file location to the config > search path. This would allow you to put customized options for an > individual daemon in the daemon data directory. Or, you could avoid > putting a config in /etc/ceph entirely, so that the daemon data is > completely self-contained on the device. That would streamline boot > disk failure (just reinstall OS and ceph package) or drive swaps > between failed host hardware. > > What do you think? Seems very reasonable. In a related thought, I've been wishing that we could store a config in the data directory for a different reason. It would be nice if daemons could self-set persistent configuration, so that we could make options set over `tell` (optionally) persistent. The idea is that if a management tool wanted to e.g. configure log verbosity, it could do it purely over ceph commands, rather than needing out-of-band (SSH) access to modify files on disk (and to reconcile its changes with the human-editable ceph.conf). What if we had two (optional) config files in the data dir, one for human consumption (to makes drive swaps and host rebuilds simpler), and one machine generated for the daemon to update itself when requested to remotely? John -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
