All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan van der Ster <dan-EOCVfBHj35C+XT7JhA+gdA@public.gmane.org>
To: Sage Weil <sweil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ceph-users <ceph-users-Qp0mS5GaXlQ@public.gmane.org>
Subject: Re: removing cluster name support
Date: Thu, 8 Jun 2017 21:55:15 +0200	[thread overview]
Message-ID: <CABZ+qqk-kSL4XsG=7F2zrnzaa552xLb=T7w_6dRTR6ST7amY-g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1706081936570.3646-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2623 bytes --]

Hi Sage,

We need named clusters on the client side. RBD or CephFS clients, or
monitoring/admin machines all need to be able to access several clusters.

Internally, each cluster is indeed called "ceph", but the clients use
distinct names to differentiate their configs/keyrings.

Cheers, Dan


On Jun 8, 2017 9:37 PM, "Sage Weil" <sweil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

At CDM yesterday we talked about removing the ability to name your ceph
clusters.  There are a number of hurtles that make it difficult to fully
get rid of this functionality, not the least of which is that some
(many?) deployed clusters make use of it.  We decided that the most we can
do at this point is remove support for it in ceph-deploy and ceph-ansible
so that no new clusters or deployed nodes use it.

The first PR in this effort:

        https://github.com/ceph/ceph-deploy/pull/441

Background:

The cluster name concept was added to allow multiple clusters to have
daemons coexist on the same host.  At the type it was a hypothetical
requirement for a user that never actually made use of it, and the
support is kludgey:

 - default cluster name is 'ceph'
 - default config is /etc/ceph/$cluster.conf, so that the normal
'ceph.conf' still works
 - daemon data paths include the cluster name,
     /var/lib/ceph/osd/$cluster-$id
   which is weird (but mostly people are used to it?)
 - any cli command you want to touch a non-ceph cluster name
needs -C $name or --cluster $name passed to it.

Also, as of jewel,

 - systemd only supports a single cluster per host, as defined by $CLUSTER
in /etc/{sysconfig,default}/ceph

which you'll notice removes support for the original "requirement".

Also note that you can get the same effect by specifying the config path
explicitly (-c /etc/ceph/foo.conf) along with the various options that
substitute $cluster in (e.g., osd_data=/var/lib/ceph/osd/$cluster-$id).


Crap preventing us from removing this entirely:

 - existing daemon directories for existing clusters
 - various scripts parse the cluster name out of paths


Converting an existing cluster "foo" back to "ceph":

 - rename /etc/ceph/foo.conf -> ceph.conf
 - rename /var/lib/ceph/*/foo-* -> /var/lib/ceph/*/ceph-*
 - remove the CLUSTER=foo line in /etc/{default,sysconfig}/ceph
 - reboot


Questions:

 - Does anybody on the list use a non-default cluster name?
 - If so, do you have a reason not to switch back to 'ceph'?

Thanks!
sage
_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[-- Attachment #1.2: Type: text/html, Size: 3811 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

  parent reply	other threads:[~2017-06-08 19:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 19:37 removing cluster name support Sage Weil
2017-06-08 19:48 ` [ceph-users] " Bassam Tabbara
2017-06-08 19:54   ` Sage Weil
2017-06-09 12:19     ` Alfredo Deza
     [not found]       ` <CAC-Np1wjRX99N4q69XfWY0m0fDETpRQZj5Hrgoe6kbrh7riE+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-09 13:11         ` Wes Dillingham
2017-06-09 15:58           ` [ceph-users] " Vasu Kulkarni
     [not found]             ` <CAKPXa=ZjsvhAMwdM9k47L4gaMGVispyJ7bMOyR7dVu0y7pb12A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-09 16:36               ` Dan van der Ster
2017-06-09 16:42                 ` [ceph-users] " Sage Weil
     [not found] ` <alpine.DEB.2.11.1706081936570.3646-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>
2017-06-08 19:55   ` Dan van der Ster [this message]
2017-06-11 13:41   ` Peter Maloney
2017-06-08 20:41 ` [ceph-users] " Benjeman Meekhof
2017-06-09 11:33   ` Tim Serong
2017-06-08 21:33 ` Vaibhav Bhembre
2017-06-09 16:07 ` Sage Weil
2017-06-09 16:16   ` Mykola Golub
2017-06-09 16:19   ` Erik McCormick
     [not found]     ` <CAHUi5cOM8zrnZ80RMqJhEwowE6XmM3dnAKJmxNf8E82fM7Nfbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-09 16:30       ` Sage Weil
2017-11-07  6:39         ` [ceph-users] " Erik McCormick
2017-06-09 16:10 ` Mykola Golub
2017-11-07 12:09 ` [ceph-users] " kefu chai
2017-11-07 12:45   ` Alfredo Deza
2017-11-07 19:38     ` Sage Weil
2017-11-07 20:33       ` Vasu Kulkarni
     [not found]         ` <CAKPXa=YDxV1G-sgFEsJ9WpUwDn5N0o3eB1=WZKyG3Cr2uTRXWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-07 21:08           ` Erik McCormick

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='CABZ+qqk-kSL4XsG=7F2zrnzaa552xLb=T7w_6dRTR6ST7amY-g@mail.gmail.com' \
    --to=dan-eocvfbhj35c+xt7jha+gda@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=sweil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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.