All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Dreyer <kdreyer@redhat.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: systemd unit files and multiple daemons
Date: Wed, 22 Apr 2015 15:57:12 -0600	[thread overview]
Message-ID: <55381938.7010600@redhat.com> (raw)

I could really use some eyes on the systemd change proposed here:
http://tracker.ceph.com/issues/11344

Specifically, on bullet #4 there, should we have a single
"ceph-mon.service" (implying that users should only run one monitor
daemon per server) or if we should support multiple "ceph-mon@" services
(implying that users will need to specify additional information when
starting the service(s)). The version in our tree is "ceph-mon@". James'
work for Ubuntu Vivid is only "ceph-mon" [2]. Same thing for ceph-mds vs
ceph-mds@.

I'd prefer to keep Ubuntu downstream the same as Ceph upstream.

What do we want to do for this?

How common is it to run multiple monitor daemons or mds daemons on a
single host?

- Ken


[1] https://github.com/ceph/ceph/tree/master/systemd
[2]
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ceph/vivid/files/head:/debian/lib-systemd/

             reply	other threads:[~2015-04-22 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 21:57 Ken Dreyer [this message]
2015-04-22 22:26 ` systemd unit files and multiple daemons Gregory Farnum
     [not found]   ` <CAC6JEv_PkZf-5kHEExdOci=S1so3LXp3y39wQ6NFFuraO1W1gw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-23  8:19     ` HEWLETT, Paul (Paul)** CTR **
     [not found]       ` <B1C372F943D5614C80F90CC0D60D421048597544-9GBTwW6/wuQ9TqmaN4UESsmi8k7hvqCr0x5PJ/hMzaDby3iVrkZq2A@public.gmane.org>
2015-04-23 15:14         ` Sage Weil

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=55381938.7010600@redhat.com \
    --to=kdreyer@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@lists.ceph.com \
    /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.