From: Florian Haas <florian@hastexo.com>
To: openstack@lists.launchpad.net
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [Openstack] Ceph + OpenStack [HOW-TO]
Date: Mon, 11 Jun 2012 00:51:54 +0200 [thread overview]
Message-ID: <4FD5250A.5090201@hastexo.com> (raw)
In-Reply-To: <CAOLwVUkXCJyvD3bjE3EyDwCTGHR_An7PCP2Y014hyN5O8noVhw@mail.gmail.com>
On 06/10/12 23:32, Sébastien Han wrote:
> Hello everyone,
>
> I recently posted on my website an introduction to ceph and the
> integration of Ceph in OpenStack.
> It could be really helpful since the OpenStack documentation has not
> dealt with it so far.
>
> Feel free to comment, express your opinions and share your personal
> experience about both of them.
This is mighty comprehensive. :) Thanks!
Cheers,
Florian
--
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
parent reply other threads:[~2012-06-10 22:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAOLwVUkXCJyvD3bjE3EyDwCTGHR_An7PCP2Y014hyN5O8noVhw@mail.gmail.com>]
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=4FD5250A.5090201@hastexo.com \
--to=florian@hastexo.com \
--cc=ceph-devel@vger.kernel.org \
--cc=openstack@lists.launchpad.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox