All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Neil Levine <neil.levine@inktank.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: OpenStack summit : Ceph design session
Date: Thu, 07 Mar 2013 23:21:36 +0100	[thread overview]
Message-ID: <513912F0.80402@dachary.org> (raw)
In-Reply-To: <CAC-hyiEDiTNgdkNjc0Jd5hpY-vDELDhD0Xy7VPwhyAP4Yf37Jw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

Hi Yehuda,

I'm not sure if one keystone for all zones would be better than one keystone per zone. If you think it's worth discussing during the OpenStack summit and you create a session http://summit.openstack.org/cfp/create in the keystone track, I will definitely attend :-). Or I can do it if you like. But there is no way to share the edit permissions.

Cheers

On 03/07/2013 12:12 AM, Yehuda Sadeh wrote:
> On Wed, Mar 6, 2013 at 3:05 PM, Neil Levine <neil.levine@inktank.com> wrote:
>> On Wed, Mar 6, 2013 at 2:45 PM, Loic Dachary <loic@dachary.org> wrote:
>>> Hi Neil,
>>>
>>> On 03/06/2013 08:27 PM, Neil Levine wrote:
>>>> I think the multi-site RGW stuff is somewhat orthogonal to OpenStack
>>>
>>> Even when keystone is involved ?
>>
>> Good question.
>>
>> Yehuda: how would the asynchronously replicated user metadata interact
>> with Keystone?
> 
> Depends. Are there any special requirements? From what I understand,
> you'd define the keystone backend every zone interact with per-zone,
> and the fact that it's a replicated region/zone doesn't change much.
> 
>>
>>>> Who approves the session at ODS and when is this decision made?
>>>
>>> I suspect Josh knows more than I do about this. During the cinder meeting earlier today J. Griffith said that if the nova track is too busy to host the "Roadmap for Ceph integration with OpenStack" session he was in favor of having it in the cinder track. Following his advice I suggested to Thierry Carrez to open a "Cross project" track ( http://lists.openstack.org/pipermail/openstack-dev/2013-March/006365.html )
>>
>> I don't think Cinder is such a bad place for it to be as presumably
>> the interaction to copy the block device to a secondary location would
>> be triggered through a Cinder API call no?
>>
>> Neil
>> --
>> 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
> --
> 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

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2013-03-07 22:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23 10:33 OpenStack summit : Ceph design session Loic Dachary
2013-02-24 17:05 ` Sébastien Han
2013-02-24 23:16 ` Josh Durgin
2013-02-25  6:12   ` Neil Levine
2013-02-25 10:04     ` Loic Dachary
2013-02-26 16:56       ` Neil Levine
2013-03-03  9:37       ` Loic Dachary
2013-03-06 19:27         ` Neil Levine
2013-03-06 22:45           ` Loic Dachary
2013-03-06 23:05             ` Neil Levine
2013-03-06 23:12               ` Yehuda Sadeh
2013-03-07 22:21                 ` Loic Dachary [this message]
2013-02-25  9:34   ` Loic Dachary

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=513912F0.80402@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=neil.levine@inktank.com \
    --cc=yehuda@inktank.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.