From: Loic Dachary <loic@dachary.org>
To: Neil Levine <neil.levine@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: OpenStack summit : Ceph design session
Date: Mon, 25 Feb 2013 11:04:21 +0100 [thread overview]
Message-ID: <512B3725.4040602@dachary.org> (raw)
In-Reply-To: <CANygib_m5h6F7u5ayzSTdZ2Y_8mO414dFXQup2w8NTWQtYWc9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
Hi Neil,
I've added "RBD backups secondary clusters within Openstack" to the list of blueprints. Do you have links to mail threads / chat logs related to this topic ?
I moved the content of the session to an etherpad for collaborative editing
https://etherpad.openstack.org/roadmap-for-ceph-integration-with-openstack
and it is now linked from
http://summit.openstack.org/cfp/details/38
Cheers
On 02/25/2013 07:12 AM, Neil Levine wrote:
> Thanks for taking the lead on this Loic.
>
> As a blueprint, I'd like to look at RBD backups to secondary clusters
> within Openstack. Nick Barcet and others have mentioned ideas for this
> now that Cinder is multi-cluster aware.
>
> Neil
>
> On Sun, Feb 24, 2013 at 3:16 PM, Josh Durgin <josh.durgin@inktank.com> wrote:
>> On 02/23/2013 02:33 AM, Loic Dachary wrote:
>>>
>>> Hi,
>>>
>>> In anticipation of the next OpenStack summit
>>> http://www.openstack.org/summit/portland-2013/, I proposed a session to
>>> discuss OpenStack and Ceph integration. Our meeting during FOSDEM earlier
>>> this month was a great experience although it was planned at the last
>>> minute. I hope we can organize something even better for the summit.
>>>
>>> For developers and contributors to both Ceph and OpenStack such as myself,
>>> it would be a great opportunity to figure out a sensible roadmap for the
>>> next six months. I realize this roadmap is already clear for Josh Durgin and
>>> other Ceph / OpenStack developers who are passionately invested in both
>>> projects for a long time. However I am new to both projects and such a
>>> session would be a precious guide and highly motivating.
>>>
>>> http://summit.openstack.org/cfp/details/38
>>>
>>> What do you think ?
>>>
>>
>> Sounds like a great idea!
>> Thanks for putting together the session!
>>
>> Josh
>>
>> --
>> 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 --]
next prev parent reply other threads:[~2013-02-25 10:04 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 [this message]
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
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=512B3725.4040602@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=neil.levine@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.