All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wes Dillingham <wes_dillingham-nRXb03v5zC6Vc3sceRu5cw@public.gmane.org>
Cc: "ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"ceph-users-Qp0mS5GaXlQ@public.gmane.org"
	<ceph-users-Qp0mS5GaXlQ@public.gmane.org>
Subject: Re: removing cluster name support
Date: Fri, 9 Jun 2017 09:11:05 -0400	[thread overview]
Message-ID: <CAMrEFZ62a7dToADh=-nbLy15Xx9=_mmJkmDjP-JY4mfarpd_5Q@mail.gmail.com> (raw)
In-Reply-To: <CAC-Np1wjRX99N4q69XfWY0m0fDETpRQZj5Hrgoe6kbrh7riE+A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


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

Similar to Dan's situation we utilize the --cluster name concept for our
operations. Primarily for "datamover" nodes which do incremental rbd
import/export between distinct clusters. This is entirely coordinated by
utilizing the --cluster option throughout.

The way we set it up is that all clusters are actually named "ceph" on the
mons and osds etc, but the clients themselves get /etc/ceph/clusterA.conf
and /etc/ceph/clusterB.conf so that we can differentiate. I would like to
see the functionality of clients being able to specify which conf file to
read preserved.

As a note though we went the route of naming all clusters "ceph" to
workaround difficulties in non-standard naming so this issue does need some
attention.

On Fri, Jun 9, 2017 at 8:19 AM, Alfredo Deza <adeza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

> On Thu, Jun 8, 2017 at 3:54 PM, Sage Weil <sweil-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> > On Thu, 8 Jun 2017, Bassam Tabbara wrote:
> >> Thanks Sage.
> >>
> >> > At CDM yesterday we talked about removing the ability to name your
> ceph
> >> > clusters.
> >>
> >> Just to be clear, it would still be possible to run multiple ceph
> >> clusters on the same nodes, right?
> >
> > Yes, but you'd need to either (1) use containers (so that different
> > daemons see a different /etc/ceph/ceph.conf) or (2) modify the systemd
> > unit files to do... something.
>
> In the container case, I need to clarify that ceph-docker deployed
> with ceph-ansible is not capable of doing this, since
> the ad-hoc systemd units use the hostname as part of the identifier
> for the daemon, e.g:
>
>     systemctl enable ceph-mon@{{ ansible_hostname }}.service
>
>
> >
> > This is actually no different from Jewel. It's just that currently you
> can
> > run a single cluster on a host (without containers) but call it 'foo' and
> > knock yourself out by passing '--cluster foo' every time you invoke the
> > CLI.
> >
> > I'm guessing you're in the (1) case anyway and this doesn't affect you at
> > all :)
> >
> > sage
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> _______________________________________________
> ceph-users mailing list
> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>



-- 
Respectfully,

Wes Dillingham
wes_dillingham-nRXb03v5zC6Vc3sceRu5cw@public.gmane.org
Research Computing | Senior CyberInfrastructure Storage Engineer
Harvard University | 38 Oxford Street, Cambridge, Ma 02138 | Room 102

[-- Attachment #1.2: Type: text/html, Size: 4556 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-09 13:11 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 [this message]
2017-06-09 15:58           ` 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
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='CAMrEFZ62a7dToADh=-nbLy15Xx9=_mmJkmDjP-JY4mfarpd_5Q@mail.gmail.com' \
    --to=wes_dillingham-nrxb03v5zc6vc3sceru5cw@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@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.