Hi Jordi, I just filed issue 1079<https://code.google.com/p/hypertable/issues/detail?id=1079>to track this one. It may take a month or so before we can get to it. If you could test it out for us and send feedback, that would be helpful. QFS is a derivative of KFS, which is a C++ implementation of the Google Filesystem. It's developed by Quantcast. I don't have any experience with it, but its gotten lots of use at Quantcast. We should have a broker ready for QFS soon.
- Doug On Mon, Jun 3, 2013 at 6:50 PM, Jordi Llonch <[email protected]> wrote: > Doug, > > One of the biggest requirements to use cephBroker today is the > authentication "cephx" introduced by default on recent Ceph versions. > > My plan is to use Ubuntu or a recent Fedora, but not CentOS because is > pretty outdated. > > What are your toughts on QFS? The main reason for me to use a DFS will be > hypertable which I am keen to hear about the future directions on this > subject. > > I have building & deploying experience with Opscode Chef and also slowly I > am creating a hypertable cookbook for a few use cases. > > How do you think I can help Hypertable? > > Thanks, > Jordi > > > > > 2013/6/4 Doug Judd <[email protected]> > >> Hi Jordi, >> >> Sorry for the late response, I just got back from vacation. We built the >> Ceph broker a while back and haven't updated it in a long time, so it >> probably needs to be updated to work with the latest version of Ceph. >> There are a couple of things about our build process that affect how we >> would build the Ceph broker: >> >> 1. Hypertable includes all of the dependent libraries in the packages. >> We do this because since there are quite a few Hypertable dependencies, >> this avoids dependency headaches during install. Hypertable ships with a >> wrapper script called 'ht' which sets up LD_LIBRARY_PATH to point to the >> $HYPERTABLE_INSTALL/lib directory (where the dependent libraries are >> located) so that the servers and command line tools know where to find the >> dependencies. We may have missed some of the dependencies with the Ceph >> broker which is why you're getting the link errors. >> >> 2. Because we include all of the dependent libraries, we can build >> generic "linux" packages that work on most variants of Linux. The only >> requirement that we have is that the system have glibc 2.4 or higher. The >> way we handle this is we have a set of build machines that run older >> versions of the OS (e.g. CentOS 5.2 and Debian ) and we build the packages >> on these older machines. >> >> Since it looks like Ceph only supports relatively modern versions of the >> OS, we can't really add it to our normal build process. However, we could >> set up some machines (AMIs) specifically for building the Ceph broker and >> ship the Ceph broker as a separate add-on. Do you have any interest in >> helping us out with this? If so, let us know platform are you are wanting >> to run on (e.g. OS and version). >> >> - Doug >> >> P.S. Another C++ distributed filesystem that we plan to add support for >> soon is QFS <http://quantcast.github.io/qfs/>. It's something you might >> want to consider as well. >> >> >> On Sun, May 26, 2013 at 7:13 PM, Jordi Llonch <[email protected]> wrote: >> >>> Hi, >>> >>> I assume that's the right place to post this, otherwise, my apologies. >>> >>> The rpm package for hypertable 0.9.7.6 includes the cephBroker binary. >>> And after installing it and trying to start Ceph DFS, DfsBroker.ceph.log >>> shows: >>> >>> /opt/hypertable/current/bin/cephBroker: error while loading shared >>> libraries: libcrush.so.1: cannot open shared object file: No such file or >>> directory >>> >>> Once this library is present in /opt/hypertable/current/lib/, starting >>> the DFS shows: >>> >>> /opt/hypertable/current/bin/cephBroker: error while loading shared >>> libraries: libcryptopp.so.1: cannot open shared object file: No such file >>> or directory >>> >>> I do not know the reason why those 2 libraries are included in the RPM >>> package. >>> >>> It will be interesting to fix this condition and also to include >>> cephBroker into deb and tgz binary packages. >>> >>> Thanks in advance, >>> Jordi >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Hypertable Development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/hypertable-dev?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Doug Judd >> CEO, Hypertable Inc. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Hypertable Development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/hypertable-dev?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Hypertable Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/hypertable-dev?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Doug Judd CEO, Hypertable Inc. -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hypertable-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
