From: Giulio Fidente <gfidente@redhat.com>
To: David Moreau Simard <dmsimard@iweb.com>, Loic Dachary <loic@dachary.org>
Cc: Florian Haas <florian.haas@hastexo.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Ceph & Cinder & HA
Date: Fri, 07 Nov 2014 10:35:58 +0100 [thread overview]
Message-ID: <545C927E.9010807@redhat.com> (raw)
In-Reply-To: <DAB091EE-E314-40D3-99F3-710E91ECC4D2@iweb.com>
On 11/07/2014 09:46 AM, David Moreau Simard wrote:
> Loic,
>
> Was there an etherpad ? I'm curious as I didn't attend that one.
>
> HA with Cinder mostly revolves around setting up multiple cinder-api and cinder-volume servers. Was there something else involved ?
> I can probably contribute my knowledge on that..
hi David,
indeed it would be great if we could get in touch! I'm still at the
summit, in the TripleO room, in case you are around too.
So yes there is an etherpad and also a TripleO spec which goes a bit
more into the details (linked from the etherpad):
https://etherpad.openstack.org/p/tripleo-kilo-l3-and-cinder-ha
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
--
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo
next prev parent reply other threads:[~2014-11-07 9:37 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 [this message]
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
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=545C927E.9010807@redhat.com \
--to=gfidente@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dmsimard@iweb.com \
--cc=florian.haas@hastexo.com \
--cc=loic@dachary.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.