[Bug 217046] net/ceph-devel: Development version for Ceph, a distributed object, block, and file storage platform

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Feb 13 20:17:16 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217046

--- Comment #4 from Willem Jan Withagen <wjw at digiware.nl> ---
Hi Alan,

Why have portlint, if you are way much more useful in suggestions? ;-)
Thanx for the very detailed review.
I will address your questions/suggestion and more.

The port started out with a different approach so some things are left over.
And next to that it is a work in progress, as is the Ceph-port.
So some things are there as a reminder for future things to do.
Otehr thigns are there because the "just seemed to work". Even with the ports
handbook I still feel writing a ports fileset is sort of a black art.
And yes, it took me a while to get this portset cooked up.

And yes it runs thru both portlint and poudriere.
poudriere testport complains mainly about work/stage containing all kinds of
different files that the ceph install puts there but are mostly used for
testing. And I do not want to compilcate the ceph part of the port even more
with messing in the install things. If too much time left over, I'll perhaps
spend a odd weekend to sort this out.  

I might need some hand holding, but I'll checkout reviews.freebsd.org.

And as to your question what is working/tested in the port:
  Mon
  OSD
  RadosGW
  rados
  rbd
  init-ceph, and etc/rc.d/ceph on top of that
  ceph-disk {prepare, activate}

So all in all enough to build a multi server, multi osd cluster fully running
on FreeBSD and do some testing...
I still need to write up some notes on that.

Somethings are still left to the user. :)
I have not tried MDS, but would expect that not to be anything harder that
getting MONs and OSDs ported. There is also the (lib)cephfs that needs
attention. And my personal interest is in getting RBD working with bhyve.

--WjW

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list