All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: How are you dealing with hammer -> jewel upgrades?
Date: Tue, 10 May 2016 17:29:36 +0200	[thread overview]
Message-ID: <5731FE60.1090704@suse.cz> (raw)

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

             reply	other threads:[~2016-05-10 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 15:29 Nathan Cutler [this message]
2016-05-10 17:13 ` How are you dealing with hammer -> jewel upgrades? Ken Dreyer
2016-05-10 23:49   ` Nathan Cutler
2016-05-11  0:09     ` Ken Dreyer

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=5731FE60.1090704@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    /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.