All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Stopping ceph daemons during the upgrade
Date: Mon, 18 Aug 2014 17:19:48 +0200	[thread overview]
Message-ID: <53F21994.5000202@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

Hi,

To not confuse the ceph daemons during a package upgrade ( see http://tracker.ceph.com/issues/9153#note-13 for instance ), it would be better to stop the ceph daemons while ceph is being upgraded. Does that sound reasonable ?

Here is how it could be done for .deb packages : https://github.com/dachary/ceph/commit/cf3a0e7bef25e5190f3cdb69e57cb6b868d806fa and there probably is a way to do something similar with RPM packages. 

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

             reply	other threads:[~2014-08-18 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 15:19 Loic Dachary [this message]
2014-08-18 15:31 ` Stopping ceph daemons during the upgrade Dan Van Der Ster
2014-08-18 16:00   ` Loic Dachary
2014-08-18 16:08     ` Sage Weil
2014-08-18 16:24       ` Loic Dachary

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=53F21994.5000202@dachary.org \
    --to=loic@dachary.org \
    --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.