All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Fidente <gfidente@redhat.com>
To: Loic Dachary <loic@dachary.org>,
	Sebastien Han <sebastien.han@enovance.com>,
	justin@erenkrantz.com
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ceph & Cinder & HA
Date: Mon, 10 Nov 2014 12:50:27 +0100	[thread overview]
Message-ID: <5460A683.9040509@redhat.com> (raw)
In-Reply-To: <546098C5.4070709@dachary.org>

On 11/10/2014 11:51 AM, Loic Dachary wrote:
>
>
> On 10/11/2014 11:34, Sebastien Han wrote:
>> Indeed, that’s what we discussed with Giulio, using HAProxy for the Monitors is a bit overkill since the client is natively able to switch between different monitor source.
>>
>> Loic, maybe you can elaborate a bit more on the usage of HAProxy for the monitors?
>
> Hi Sebastien,
>
> I can't elaborate because I know nothing about HAProxy (well, close to nothing ;-). I'd like to learn more about how HA (via HAProxy or something else) can leverage Ceph in a meaningfull way thouhg, hence my interest for the topic.

Thanks all for helping.

Loic explained requests for the non-leader monitors go to the monitor 
anyway in which case I understand it makes more sense to avoid the 
complication of balancing the monitors.

-- 
Giulio Fidente
GPG KEY: 08D733BA
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-11-10 11:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:57 Ceph & Cinder & HA Loic Dachary
2014-11-07  8:46 ` David Moreau Simard
2014-11-07  9:35   ` Giulio Fidente
2014-11-07  9:50     ` David Moreau Simard
2014-11-07  9:56       ` Giulio Fidente
2014-11-07 10:08         ` Sebastien Han
2014-11-09 21:54     ` Justin Erenkrantz
2014-11-10 10:34       ` Sebastien Han
2014-11-10 10:51         ` Loic Dachary
2014-11-10 11:50           ` Giulio Fidente [this message]
2014-11-10 16:39             ` Gregory Farnum

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=5460A683.9040509@redhat.com \
    --to=gfidente@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=justin@erenkrantz.com \
    --cc=loic@dachary.org \
    --cc=sebastien.han@enovance.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.