From: "Sławomir Skowron" <szibis@gmail.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Best practice - upgrade ceph cluster
Date: Fri, 20 Apr 2012 21:00:12 +0200 [thread overview]
Message-ID: <5934003767531706998@unknownmsgid> (raw)
Maybe it's a lame question, but is anybody knows simplest procedure,
for most non-disrubtive upgrade of ceph cluster with real workload on
it ??
It's most important if we want semi-automate this process with some
tools. Maybe there is a cookbook for this operation ?? I know that
automate this is not simple, and dangerous, but even in manual upgrade
it's important to know what can we expect.
Regards
Slawomir Skowron
next reply other threads:[~2012-04-20 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:00 Sławomir Skowron [this message]
2012-04-20 19:34 ` Best practice - upgrade ceph cluster Greg Farnum
2012-04-20 20:18 ` Sławomir Skowron
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=5934003767531706998@unknownmsgid \
--to=szibis@gmail.com \
--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.