From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: /var/lib/ceph/*/*/config
Date: Tue, 19 Jan 2016 16:34:40 +0100 [thread overview]
Message-ID: <569E5790.1090905@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1601191009320.28274@cpach.fuggernut.com>
On 19-01-16 16:15, Sage Weil 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?
I think that's an awesome idea. Simply plug in the disk, mount it and run!
Yes, this would make life a lot easier.
Wido
> sage
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-01-19 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 15:15 /var/lib/ceph/*/*/config Sage Weil
2016-01-19 15:34 ` Wido den Hollander [this message]
2016-01-19 15:48 ` /var/lib/ceph/*/*/config Allen Samuels
[not found] ` <CACJqLyaMC-UaAhTnzCeUqPCoY3HcoqLwHg3tpWW0H-+6AN6C7Q@mail.gmail.com>
2016-01-19 16:46 ` /var/lib/ceph/*/*/config Sage Weil
2016-01-19 16:55 ` /var/lib/ceph/*/*/config Haomai Wang
2016-01-27 14:59 ` /var/lib/ceph/*/*/config Sage Weil
2016-01-27 15:24 ` /var/lib/ceph/*/*/config Wido den Hollander
2016-01-27 15:45 ` /var/lib/ceph/*/*/config Sage Weil
2016-01-27 16:03 ` /var/lib/ceph/*/*/config Wido den Hollander
2016-01-27 16:29 ` /var/lib/ceph/*/*/config Haomai Wang
2016-01-20 10:42 ` /var/lib/ceph/*/*/config John Spray
2016-01-21 6:15 ` /var/lib/ceph/*/*/config Wang, Yaguang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569E5790.1090905@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.