From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Sage Weil <sage@inktank.com>
Cc: f wiessner <f.wiessner@smart-weblications.de>,
Ross Turk <ross@inktank.com>,
ceph-devel <ceph-devel@vger.kernel.org>,
Tren Blackburn <tren@eotnetworks.com>
Subject: Re: How are you using Ceph?
Date: Tue, 18 Sep 2012 12:21:32 -0400 (EDT) [thread overview]
Message-ID: <1696200491.44.1347985292864.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209180912060.10642@cobra.newdream.net>
Hi Sage,
----- "Sage Weil" <sage@inktank.com> wrote:
> Hi Matt,
>
> On Mon, 17 Sep 2012, Matt W. Benjamin wrote:
> > Hi
> >
> > Just FYI, on the NFS integration front. A pnfs files
> (RFC5661)-capable
> > NFSv4 re-exporter for Ceph has been committed to the Ganesha NFSv4
> > server development branch. We're continuing to enhance and
> elaborate
> > this. We have had on our (full) plates for a while to return Ceph
> > client library changes. We've finished pullup and rebasing of
> these,
> > are doing some final testing of a couple things in preparation to
> push a
> > branch for review.
>
> This is great news! I'm interested to hear how the Ganesha bits map
> pNFS
> server instances to OSDs.. is it just matching IP addresses or
> something?
The returned pnfs layouts together with a set of pseudo devices mentioned in it express a striping pattern. The devices indicate the location of each OSD, each of which is running a Ganesha data server. We're in the process of deepening our integration here, potentially switching to the next draft version of the pnfs object layout. This will increase the expressiveness of the stripe mappings we can do--as it is now, there is some impedence.
Regards,
Matt
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2012-09-18 16:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1784724793.100.1347938272315.JavaMail.root@thunderbeast.private.linuxbox.com>
2012-09-18 3:19 ` How are you using Ceph? Matt W. Benjamin
2012-09-18 5:44 ` Ian Pye
2012-09-18 6:06 ` Yehuda Sadeh
2012-09-18 16:13 ` Sage Weil
2012-09-18 16:21 ` Matt W. Benjamin [this message]
2012-09-17 23:57 Nick Couchman
2012-09-18 6:35 ` John Axel Eriksson
-- strict thread matches above, loose matches on Subject: below --
2012-09-17 23:55 Nick Couchman
2012-09-17 22:14 Ross Turk
2012-09-17 22:47 ` Nick Couchman
2012-09-17 22:53 ` Mark Nelson
2012-09-17 23:26 ` John Axel Eriksson
2012-09-18 7:47 ` Plaetinck, Dieter
2012-09-18 14:34 ` John Axel Eriksson
2012-09-18 14:51 ` Plaetinck, Dieter
2012-09-18 14:56 ` Mark Nelson
2012-09-18 15:19 ` Plaetinck, Dieter
2012-09-18 15:27 ` Mark Nelson
2012-09-18 15:46 ` Plaetinck, Dieter
2012-09-18 16:20 ` Xiaopong Tran
2012-09-18 17:09 ` John Axel Eriksson
2012-09-18 0:05 ` Smart Weblications GmbH - Florian Wiessner
2012-09-18 0:18 ` Tren Blackburn
2012-09-18 2:32 ` Sage Weil
2012-09-18 11:48 ` Smart Weblications GmbH - Florian Wiessner
2012-09-18 16:20 ` Sage Weil
2012-09-18 16:35 ` Tren Blackburn
2012-09-18 17:00 ` Sage Weil
2012-09-18 16:01 ` Travis Rhoden
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=1696200491.44.1347985292864.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=ceph-devel@vger.kernel.org \
--cc=f.wiessner@smart-weblications.de \
--cc=ross@inktank.com \
--cc=sage@inktank.com \
--cc=tren@eotnetworks.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.