Date: Thu, 3 Sep 2015 11:14:07 +0530 From: Rakshith Venkatesh <vrock28@gmail.com> To: Mike Carlson <mike@bayphoto.com> Cc: freebsd-fs@freebsd.org Subject: Re: CEPH + FreeBSD Message-ID: <CANw0z%2BXrwK=6y%2BLpoiewc_eLDBYB5UZ5XpU6-YP0-K2FKwSa5w@mail.gmail.com> In-Reply-To: <CA%2BKW7xQrN60kH37hu2Keja60a0huVjAyP6=SQNSrqus2EUMUMA@mail.gmail.com> References: <CANw0z%2BVhYCPNWrjByXLf8yO9wA0sc05_8eVJsM-McjcGNU9KQg@mail.gmail.com> <CA%2BKW7xQrN60kH37hu2Keja60a0huVjAyP6=SQNSrqus2EUMUMA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the reply Mike. Yeah, i think its time for Ceph folks to take this up. On Wed, Sep 2, 2015 at 11:24 PM, Mike Carlson <mike@bayphoto.com> wrote: > I recall that in earlier releases of Ceph, there was some code for FreeBSD > support. That has never made it into any production release though. > > This was the last solid reference on FreeBSD support, and the git feature > branch it links to is no longer around: > > https://wiki.ceph.com/Planning/Blueprints/Emperor/Increasing_Ceph_portability > > We have two ceph clusters, one for OpenStack as a VM backend, and another > larger one for long term storage (using CephFS) > > We are a FreeBSD heavy shop, having FreeBSD support in Ceph would have > been ideal. > > Mike C > > On Sun, Aug 30, 2015 at 11:33 PM, Rakshith Venkatesh <vrock28@gmail.com> > wrote: > >> Hi, >> >> Can someone help me out to understand if Ceph has been ported to FreeBSD >> as >> part of any project/POC done earlier. I basically was interested in how >> Ceph was integrated into the underlying File system via VFS. >> >> Any pointers here would be great! >> >> Thanks, >> Rakshith >> _______________________________________________ >> 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" >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANw0z%2BXrwK=6y%2BLpoiewc_eLDBYB5UZ5XpU6-YP0-K2FKwSa5w>