On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> I would suggest that it would be:
> /etc/ceph/$cluster.conf
> /etc/ceph/$cluster.d/00-a.conf
> /etc/ceph/$cluster.d/01-b.conf
Yeah
> If it is like other config files, options later in the file override options
> earlier in the file. That makes it easy
I would suggest that it would be:
/etc/ceph/$cluster.conf
/etc/ceph/$cluster.d/00-a.conf
/etc/ceph/$cluster.d/01-b.conf
To make sure there is no conflict with anything else in /etc/ and it is
easy to always find the ceph configs instead of being mixed in with
everything else. I also like the idea
On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> If cluster is specified in /etc/default/ceph than I don't have any other
> reservations to your proposal.
Great. I like it much better than putting something in /var/lib/ceph/*
(because it's bad policy) and this nicely sidesteps the 'include '
issue.
If cluster is specified in /etc/default/ceph than I don't have any other
reservations to your proposal.
On Wed, Dec 10, 2014 at 1:39 PM, Sage Weil wrote:
> On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> > I guess you would have to specify the cluster name in
> /etc/ceph/ceph.conf?
> > That would b
On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> I guess you would have to specify the cluster name in /etc/ceph/ceph.conf?
> That would be my only concern.
ceph.conf is $cluster.conf (default cluster name is 'ceph').
Unfortunately under systemd it's not possible to parameterize daemons with
two var
I guess you would have to specify the cluster name in /etc/ceph/ceph.conf?
That would be my only concern.
On Wed, Dec 10, 2014 at 1:28 PM, Sage Weil wrote:
> On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> > I'm a big fan of /etc/*.d/ configs. Basically if the package maintained
> > /etc/ceph.conf
On Wed, 10 Dec 2014, Robert LeBlanc wrote:
> I'm a big fan of /etc/*.d/ configs. Basically if the package maintained
> /etc/ceph.conf includes all files in /etc/ceph.d/ then I can break up the
> files however I'd like (mon, ods, mds, client, one per daemon, etc). Then
> when upgrading, I don't have
I'm a big fan of /etc/*.d/ configs. Basically if the package maintained
/etc/ceph.conf includes all files in /etc/ceph.d/ then I can break up the
files however I'd like (mon, ods, mds, client, one per daemon, etc). Then
when upgrading, I don't have to worry about the new packages trying to
overwrit
Sage Weil writes:
[..]
> Thoughts? Suggestions?
>
[..]
Suggestion:
radosgw should handle injectargs like other ceph clients do?
This is not a major annoyance, but it would be nice to have.
--
Abhishek
signature.asc
Description: PGP signature
___
c
Suggestion: can we look at normalizing custom cluster names as well for
RHEL-like systems?
/etc/init.d/ceph: how do you pass --cluster myname at system startup?
systemd service file uses EnvironmentFile.
What about
. /etc/sysconfig/ceph #near the top
and /etc/sysconfig/ceph contains
cluster=myna
On 07/12/14 07:39, Sage Weil wrote:
Thoughts? Suggestions?
Would kit make sense to include radosgw-agent package in this
normalization too?
Regards
Mark
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/c
On Sat, Dec 6, 2014 at 10:39 AM, Sage Weil wrote:
> Several things are different/annoying with radosgw than with other Ceph
> daemons:
>
> - binary/package are named 'radosgw' instead of 'ceph-rgw'.
>
> This is cosmetic, but it also makes it fit less well into the
> new /var/lib/ceph/* view of thi
12 matches
Mail list logo