From: David Clarke <davidc@catalyst.net.nz>
To: Christopher Kunz <chrislist@de-punkt.de>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Best practice with 0.48.2 to take a node into maintenance
Date: Wed, 05 Dec 2012 10:31:03 +1300 [thread overview]
Message-ID: <50BE6B97.1050808@catalyst.net.nz> (raw)
In-Reply-To: <50BDD1D7.3030904@de-punkt.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/12/12 23:35, Christopher Kunz wrote:
> Hey,
>> That has to be old information - we're using it in anger on 64 bit x86 machines, from both
>> Intel and AMD. I have no idea about ARM etc, however.
> just to make absolutely sure: Are you using kexec "in anger" to switch Ceph nodes to new
> kernels? I'm very doubtful that the approach will work seamlessly with Ceph, as it is rather
> picky regarding kernel state...
The normal shutdown cycle is activated, and Ceph on that node is stopped. However, at the end of
the rc.6 scripts is one to, instead of rebooting, exec a new kernel and then progress as normal
through the boot process, and Ceph started again.
Haven't encountered any major issues thus far.
- --
David Clarke
Systems Architect
Catalyst IT
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlC+a5cACgkQRgFDJLQLJc2SOwCeKCc9aV1z09acvA3vOIMjHpJ1
F5wAn32idJCPe4WNcu0smSNzUSZv634F
=JBvD
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-12-04 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 19:05 Best practice with 0.48.2 to take a node into maintenance Oliver Francke
2012-12-03 19:14 ` Josh Durgin
2012-12-03 19:21 ` Oliver Francke
2012-12-03 19:45 ` Smart Weblications GmbH - Florian Wiessner
2012-12-03 20:13 ` Oliver Francke
2012-12-03 20:22 ` Gregory Farnum
2012-12-03 19:49 ` Christopher Kunz
2012-12-03 20:39 ` David Clarke
2012-12-03 20:50 ` Smart Weblications GmbH - Florian Wiessner
2012-12-03 20:59 ` David Clarke
2012-12-04 10:35 ` Christopher Kunz
2012-12-04 21:31 ` David Clarke [this message]
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=50BE6B97.1050808@catalyst.net.nz \
--to=davidc@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=chrislist@de-punkt.de \
/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.