* How are you dealing with hammer -> jewel upgrades?
@ 2016-05-10 15:29 Nathan Cutler
2016-05-10 17:13 ` Ken Dreyer
0 siblings, 1 reply; 4+ messages in thread
From: Nathan Cutler @ 2016-05-10 15:29 UTC (permalink / raw)
To: Ceph Development
Regarding $SUBJ, the release notes [1] provide instructions for manually
changing the ownership of the directories in /var/lib/ceph
I am exploring ways to automate the ownership change. The
/var/lib/ceph/osd tree seems to be the most problematic because it could
contain a very large number of files/directories.
Before I try to come up with a solution for automating it (perhaps by
hacking "ceph-disk activate", I thought I'd ask here if anyone has
already done any thinking/work in this area.
[1] https://github.com/ceph/ceph/blob/master/doc/release-notes.rst#L257-L295
Thanks!
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How are you dealing with hammer -> jewel upgrades?
2016-05-10 15:29 How are you dealing with hammer -> jewel upgrades? Nathan Cutler
@ 2016-05-10 17:13 ` Ken Dreyer
2016-05-10 23:49 ` Nathan Cutler
0 siblings, 1 reply; 4+ messages in thread
From: Ken Dreyer @ 2016-05-10 17:13 UTC (permalink / raw)
To: Nathan Cutler; +Cc: Ceph Development
I was thinking about handling it in the OSD directly, particularly
since it already has the UID from --setuid.
http://tracker.ceph.com/issues/15733
I haven't done any work on this, though :)
On Tue, May 10, 2016 at 9:29 AM, Nathan Cutler <ncutler@suse.cz> wrote:
> Regarding $SUBJ, the release notes [1] provide instructions for manually
> changing the ownership of the directories in /var/lib/ceph
>
> I am exploring ways to automate the ownership change. The /var/lib/ceph/osd
> tree seems to be the most problematic because it could contain a very large
> number of files/directories.
>
> Before I try to come up with a solution for automating it (perhaps by
> hacking "ceph-disk activate", I thought I'd ask here if anyone has already
> done any thinking/work in this area.
>
> [1] https://github.com/ceph/ceph/blob/master/doc/release-notes.rst#L257-L295
>
> Thanks!
>
> --
> Nathan Cutler
> Software Engineer Distributed Storage
> SUSE LINUX, s.r.o.
> Tel.: +420 284 084 037
> --
> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How are you dealing with hammer -> jewel upgrades?
2016-05-10 17:13 ` Ken Dreyer
@ 2016-05-10 23:49 ` Nathan Cutler
2016-05-11 0:09 ` Ken Dreyer
0 siblings, 1 reply; 4+ messages in thread
From: Nathan Cutler @ 2016-05-10 23:49 UTC (permalink / raw)
To: Ken Dreyer; +Cc: Ceph Development
On 05/10/2016 07:13 PM, Ken Dreyer wrote:
> I was thinking about handling it in the OSD directly, particularly
> since it already has the UID from --setuid.
> http://tracker.ceph.com/issues/15733
Thanks, Ken, for reminding me of that tracker issue! I would rather
implement the recursive ownership change for filestore-backed OSDs
(assuming it's not a totally insane thing to be doing) in ceph-disk than
in the OSD itself, for the following reasons.
ceph-disk already contains heuristics for determining the user/group to
pass to ceph-osd [1] and "--setuser ceph --setgroup ceph" is hardcoded
when starting ceph-osd via the systemd service [2].
If someone is passing a user/group other than "ceph" to the OSD via
--setuser/--setgroup, they will be doing the same with ceph-disk (which
also takes --setuser/--setgroup). Alternatively they will not be using
ceph-disk at all.
Right?
Nathan
[1]
https://github.com/ceph/ceph/blob/master/src/ceph-disk/ceph_disk/main.py#L951
[2] https://github.com/ceph/ceph/blob/master/systemd/ceph-osd%40.service#L12
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How are you dealing with hammer -> jewel upgrades?
2016-05-10 23:49 ` Nathan Cutler
@ 2016-05-11 0:09 ` Ken Dreyer
0 siblings, 0 replies; 4+ messages in thread
From: Ken Dreyer @ 2016-05-11 0:09 UTC (permalink / raw)
To: Nathan Cutler; +Cc: Ceph Development
On Tue, May 10, 2016 at 5:49 PM, Nathan Cutler <ncutler@suse.cz> wrote:
> If someone is passing a user/group other than "ceph" to the OSD via
> --setuser/--setgroup, they will be doing the same with ceph-disk (which also
> takes --setuser/--setgroup). Alternatively they will not be using ceph-disk
> at all.
Sure, I think that makes sense.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-05-11 0:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-10 15:29 How are you dealing with hammer -> jewel upgrades? Nathan Cutler
2016-05-10 17:13 ` Ken Dreyer
2016-05-10 23:49 ` Nathan Cutler
2016-05-11 0:09 ` Ken Dreyer
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.