From: Loic Dachary <loic@dachary.org>
To: Sebastien Han <sebastien.han@enovance.com>
Cc: Giulio Fidente <gfidente@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ceph & Cinder & HA
Date: Mon, 10 Nov 2014 11:51:49 +0100 [thread overview]
Message-ID: <546098C5.4070709@dachary.org> (raw)
In-Reply-To: <11F50ACF-55E9-4D2F-AD08-814FE5998089@enovance.com>
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
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.
Cheers
>
>> On 09 Nov 2014, at 22:54, Justin Erenkrantz <justin@erenkrantz.com> wrote:
>>
>> On Fri, Nov 7, 2014 at 4:35 AM, Giulio Fidente <gfidente@redhat.com> wrote:
>>> The architecture we're considering is as follows:
>>>
>>> keepalived
>>> haproxy
>>> ceph-mon
>>>
>>> where haproxy and ceph-mon are always up on all openstack 'controller' nodes
>>> (also running cinder) and keepalived is taking care of managing a virtual ip
>>> hosted on one of those
>>
>> For Ceph, you almost certainly don't need to use keepalived or haproxy
>> as all Ceph clients will fail over to the full set of monitor IPs (you
>> need a way of distributing those IPs to the cluster -
>> chef/puppet/ansible/etc/etc can handle that). Having
>> keepalived/haproxy in the loop for ceph-mon is one more thing that
>> could break.
>>
>> We do run cinder services behind the controller/headnodes nodes via
>> keepalived/haproxy - the "trick" such as it is for Ceph is to set all
>> the hostnames in cinder to being the same and it works okay. See:
>>
>> https://github.com/bloomberg/chef-bcpc/blob/master/cookbooks/bcpc/templates/default/cinder.conf.erb
>>
>> We haven't seen any issues in an active/active configuration; though
>> there are some MySQL schema deadlocks that aren't necessarily related
>> to Ceph sitting in Cinder.
>>
>> Cheers. -- justin
>> --
>> 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
>
>
> Cheers.
> ––––
> Sébastien Han
> Cloud Architect
>
> "Always give 100%. Unless you're giving blood."
>
> Phone: +33 (0)1 49 70 99 72
> Mail: sebastien.han@enovance.com
> Address : 11 bis, rue Roquépine - 75008 Paris
> Web : www.enovance.com - Twitter : @enovance
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-11-10 10: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 [this message]
2014-11-10 11:50 ` Giulio Fidente
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=546098C5.4070709@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gfidente@redhat.com \
--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.