All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Fidente <gfidente@redhat.com>
To: David Moreau Simard <dmsimard@iweb.com>
Cc: Loic Dachary <loic@dachary.org>,
	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:56:26 +0100	[thread overview]
Message-ID: <545C974A.2090609@redhat.com> (raw)
In-Reply-To: <A6E8431B-9D66-4545-96A9-56E2C27AB9ED@iweb.com>

On 11/07/2014 10:50 AM, David Moreau Simard wrote:
> Giulio,
>
> Right. The volume part is tricky because the volume is ultimately tied to one cinder-volume instance.
> I don't have a magic solution for that yet.

yep but this can be worked around by customizing the host= setting in 
Cinder so all instances of cinder-volume look like a single 'host'

this was discussed with Cinder guy here, which I am in touch with too, 
and is known to expose some issues due to multiple cinder-volume 
instances potentially trying to get access to the same volume when 
multiple tasks are queued ... yet this is 'known stuff' and they are 
already working on a 'state machine' for Cinder which will fix the a/a 
scenario

until then, the idea is to deploy cinder-volume in a a/p scenario, yet 
customizing the host= setting
-- 
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo

  reply	other threads:[~2014-11-07  9:57 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 [this message]
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=545C974A.2090609@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.