All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Dreyer <kdreyer@redhat.com>
To: John Spray <jspray@redhat.com>
Cc: Tim Serong <tserong@suse.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: subpackages for mgr modules
Date: Mon, 22 May 2017 09:45:53 -0600	[thread overview]
Message-ID: <CALqRxCzJr4UAXQ4=KAE260=geE3bDsnoc7nCqVzDcj+1bDwhVg@mail.gmail.com> (raw)
In-Reply-To: <CALe9h7eXUq-aRdOPLjDtRMFg_0bEUEHNuLR7G=QaONPZgFXOKg@mail.gmail.com>

On Sun, May 21, 2017 at 4:31 PM, John Spray <jspray@redhat.com> wrote:
> My preferred solution would be mon commands for toggling modules "ceph
> mgr module [enable|disable] <module>", and a record in the MgrMap that
> says which are enabled.

Sure. It's just another command users have to do to get to a preferred state.

The classic response on these things has been "ceph setup is hard,
let's wrap it in ceph-ansible" (or whatever higher-level tool will do
all these tricky steps). Then ceph-ansible becomes more and more
complex, and I wonder whether the complexity could be addressed
elsewhere by simply scaling down the flexibility.

- Ken

  parent reply	other threads:[~2017-05-22 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  6:19 subpackages for mgr modules Tim Serong
2017-05-19 12:14 ` Sage Weil
2017-05-19 18:25 ` Ken Dreyer
2017-05-20  0:24   ` kefu chai
2017-05-21 22:31   ` John Spray
2017-05-22  8:22     ` Tim Serong
2017-05-22  8:51       ` Willem Jan Withagen
2017-05-22 15:45     ` Ken Dreyer [this message]
2017-05-24 20:15       ` Alfredo Deza
2017-05-24 20:53         ` John Spray

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='CALqRxCzJr4UAXQ4=KAE260=geE3bDsnoc7nCqVzDcj+1bDwhVg@mail.gmail.com' \
    --to=kdreyer@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jspray@redhat.com \
    --cc=tserong@suse.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.