From owner-freebsd-fs@freebsd.org Wed Sep 9 02:26:01 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 000CAA008BF for ; Wed, 9 Sep 2015 02:26:00 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABA281FF8 for ; Wed, 9 Sep 2015 02:26:00 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by qgez77 with SMTP id z77so100011695qge.1 for ; Tue, 08 Sep 2015 19:25:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=sZxAh77LQTkt0+YM1iDdcMu5yRzThQK0vc2W9Pzy9YU=; b=BuE+l4P6Gw4dd099INcrlP6N7YgDdkL4L/J53Vtl/TFwOolR0uD9o/3l8/RHqJwUTA AJYcRLi03LER07BP6PdtE+3M1p3PxVv2CCF7Oj08U+D7pHsYIq8y4XcNjVUlhz9HFQtV NB6KZcmOH/7YPbXgfRBbd9DzgrQku4j7qQ7AST2N8e1aeCzUwAo4795MomENH6GWRON6 fUARBouxsTQnTApbSia0lxpORU5ZwipEFWY9QceU/N3whyQtNYRXcvuu+wbOmmEXhMiy q9gLzOIfJD3gnmVLiJc63Q2M7jJqAOOVLE1JDYj5rjImc4RaMM7h8UnkjKqVXZ4nXJ5o 0y8A== X-Gm-Message-State: ALoCoQkoqtjmbMQSOqt3ziaN2y/sodBNv2rSGkmFlPwqDygjzEIiBYr7u1B/wQ8LNzI6+etokn/C X-Received: by 10.140.151.212 with SMTP id 203mr43018119qhx.1.1441765553511; Tue, 08 Sep 2015 19:25:53 -0700 (PDT) Received: from ?IPv6:2600:1017:b417:a4b4:113a:e36f:3d61:2861? ([2600:1017:b417:a4b4:113a:e36f:3d61:2861]) by smtp.gmail.com with ESMTPSA id p29sm3069566qkp.48.2015.09.08.19.25.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Sep 2015 19:25:52 -0700 (PDT) Mime-Version: 1.0 (1.0) Subject: Re: CEPH + FreeBSD From: Mark Saad X-Mailer: iPhone Mail (12H321) In-Reply-To: Date: Tue, 8 Sep 2015 22:25:51 -0400 Cc: Rick Macklem , "freebsd-fs@freebsd.org" , Rakshith Venkatesh , Jordan Hubbard Message-Id: <8551C101-0E4B-4619-BF52-1B87BC6565D8@longcount.org> References: <100306673.40344407.1441279047901.JavaMail.zimbra@uoguelph.ca> <1564D4FA-9BE1-4E37-8E91-F14A009D6B62@icloud.com> <838814506.1858817.1441577912291.JavaMail.zimbra@uoguelph.ca> To: Outback Dingo Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 02:26:01 -0000 > On Sep 8, 2015, at 9:59 PM, Outback Dingo wrote: >=20 >=20 >=20 >> On Wed, Sep 9, 2015 at 11:31 AM, Mark Saad wrote= : >> All >> What about leofs. It's in ports has and s3 obj store and NFS support ou= t of the box >>=20 >>=20 >> http://www.freshports.org/databases/leofs/ >> http://leo-project.net >=20 > LeoFS supperts NFSv3 and does not have a lock manager....=20 >=20 Well, nlm it's not a hard requirement for most NFS things . NFS is there for= direct access of the data . So in its current form it's not a pnfs setup , b= ut there is no reason it could not be extended . =20 Well it could be worse , manta, joyent's compute and storage platform has a= NFS server written in node.js . Yes nfs in JavaScript , what else would you= expect from them . :) --- Mark Saad | nonesuch@longcount.org > =20 >>=20 >>=20 >>=20 >> --- >> Mark Saad | nonesuch@longcount.org >>=20 >> > On Sep 6, 2015, at 6:18 PM, Rick Macklem wrote: >> > >> > Jordan Hubbard wrote: >> >> >> >>> On Sep 3, 2015, at 4:17 AM, Rick Macklem wrote= : >> >>> >> >>> Slightly off topic but, btw, there is a port of GLusterFS and those f= olks >> >>> do seem >> >>> interested in seeing it brought "up to speed". I am not sure how matu= re it >> >>> is at >> >>> this point, but it has been known to build on amd64. (I don't have an= amd64 >> >>> machine, >> >>> so I haven't gotten around to building/testing it, but I do plan to t= ry and >> >>> use >> >>> it as a basis for a pNFS server, if I can figure out how to get the FH= info >> >>> out of it. >> >>> I'm working on that;-) >> >> >> >> There are at least two distributed (multi-node) object stores for Free= BSD >> >> that I know of. >> >> >> >> One is glusterfs, for which I=E2=80=99m not even really clear on the s= tatus of the >> >> ports for. I don=E2=80=99t see any glusterfs port in the master branc= h of >> >> https://github.com/freebsd/freebsd-ports (or >> >> https://github.com/freebsd/freebsd-ports/tree/branches/2015Q3 for that= >> >> matter). >> >> >> >> Our FreeNAS ports tree (https://github.com/freenas/ports), in which we= have a >> >> bit more latitude to add and curate our own ports, has both a net/glus= terfs >> >> and sysutils/glusterfs, from separate sources (looks like we need to c= lean >> >> things up) - net/glusterfs lists craig001@lerwick.hopto.org as the >> >> MAINTAINER and is at version 3.6.2. The sysutils/glusterfs port lists= >> >> bapt@FreeBSD.org as the MAINTAINER and is at version 20140811. >> >> >> >> I=E2=80=99m not really sure about the provenance since we were simply e= valuating >> >> glusterfs for awhile and may have pulled in interim versions from thos= e >> >> sources, but obviously it would be best to have an official maintainer= and >> >> someone in the FreeBSD project actually curating a glusterfs port so t= hat >> >> all users of FreeBSD can use it. It would also be fairly key to your o= wn >> >> efforts, assuming you decide to pursue glusterfs as a foundation techn= ology >> >> for pNFS. >> >> >> >> The other object store, which is pretty mature and is currently leadin= g the >> >> pack (of two :) ) for inclusion into FreeNAS is RiakCS from Basho. Th= ere is >> >> a port currently in databases/riak but it=E2=80=99s pretty out of date= at version >> >> 1.4.12 (the current version is 2.0.1, with 2.0 being a major upgrade o= f >> >> RiakCS). >> >> >> >> We are very interested in investigating various ways of shimming RiakC= S to >> >> NFS, using RiakCS a back-end store. Is that something you=E2=80=99d b= e amenable to >> >> discussing? I=E2=80=99d be happy to send you an amd64 architecture m= achine to >> >> develop on. :) >> > Hmm. =46rom a quick look at their web page (I looked once before as wel= l), I don't >> > think RiakCS has what I need to do pNFS in a reasonable (for me) amount= of effort. >> > Two things that glusterFS has that I am hoping to use (and I don't thin= k RiakCS has >> > either of these) are: >> > - A Fuse file system interface which allows the kernel nfsd to access t= he store as >> > a file system, so that it can provide the metadata services (NFS witho= ut the reads/writes). >> > - A userland NFSv3 server in each node which will allow the node to act= as a data server. >> > >> > If I am wrong and RiakCS does support a VFS file system interface (via = Fuse or ???), then >> > please correct me. With that, it might be a reasonable alternative. >> > I'll admit I've spent a little time looking at the glusterFS sources an= d haven't yet >> > solved the problem of how to generate the file handles I need, but that= sounds trivial >> > compared with an entire Fuse and/or VFS file system interface, I think?= >> > >> > In general, using a cloud object store to implement a pNFS server is a *= mis*use of >> > the technology, imho. I think it may be possible with glusterFS, since t= hat technology >> > seems to be based on a cluster file system, which is what a pNFS server= can also use. >> > >> > I think there would be a lot of work involved in mapping a POSIX file s= ystem onto the >> > Riak database and then exporting that via NFS, etc. It might also be mo= re practical to >> > do this via a userland NFS service than the kernel based one currently i= n FreeBSD. >> > (glusterFS is starting to use the NFS-ganesha server, but I believe it i= s pretty Linux specific, >> > so I doubt it would be useful for Riak running on FreeBSD?) >> > >> > rick >> > >> >> - Jordan >> > _______________________________________________ >> > freebsd-fs@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >=20