From: Laurent W. <lw...@hy...> - 2010-07-14 15:52:44
|
On Wed, 14 Jul 2010 11:13:17 -0400, Steve Huff <sh...@ve...> wrote: <snip> > > maybe; certainly a dedicated user would limit potential damage more, but > on the other hand: > > * the daemon user already is a non-interactive user > * as a personal preference, i prefer to avoid making local user accounts > needlessly when there's an OK alternative > * nothing stops a security-conscious admin from making a mfs user > themselves and changing the config; the config files are marked as > %config(noreplace), so later versions of the package won't clobber the > admin's changes agreed, fine with me. > <snip> > yes; my officemate and i are running a little 2-node MFS cluster using > these packages, i on i386 and he on x86_64. i'm the metadata server, and > we're both chunkservers. i had to power-cycle my workstationm recently, > and i successfully did a mfsmetarestore afterwards. MooseFS really is > pretty neat; i've recommended it to a few colleagues already. my bosses > are currently looking into deploying HDFS in our cluster, since we may be > deploying Hadoop as well, but i'm offering MooseFS as another candidate. Nice to know :) Another heavy advantage is that codes don't need to be changed to be able to use moosefs, contrary to hdfs, AFAIK. > > i'd like to run a larger-scale test on our cluster, so that i can see how > uid/gid mapping works when the clients and servers are all looking at LDAP > for directory information instead of using local users, but i haven't > gotten around to that yet. if you're using MooseFS in production now, i'd > like to hear how well it's working out for you. It's still in testbed for me, no problem up to now. I'll deploy it on about 70TB by the end of summer. We're not using LDAP but NIS, works like a charm. > >> Do you plan to maintain the rpm for a long time ? Do you need help for >> version updates and such ? > > if you're going to be following the moosefs-users list, i'd appreciate it > if you'd forward to <su...@li...> any announcements of > version updates; it doesn't look like they have a list just for > announcements or an RSS feed, and i'm not excited at the prospect of > joining another users list :) but yes, i'm happy to continue maintaining > the mfs packages in RPMforge. OK, I'll forward version updates to that list. Thanks for maintaining the package ! > <snip> > > i don't want to do that sort of thing automatically; since the local admin > needs to make some decisions when configuring each service, i don't want > the services to be able to start up until the admin has at least looked at > the config files (the same reason why i don't chkconfig all the services on > by default). also, this way package updates will replace the *.cfg.dist > files (if there are any changes to the default configs) but not replace the > running *.cfg files. > > does that answer your questions? my goal (as is generally the case with > RPMforge) is to provide you with a package that's good enough that you > don't have to make your own custom package. Everything is fine for me. > > -steve > > p.s. in case you had overlooked it, i also made a mfs-cgi package, which > takes the MooseFS management cgi and installs it so that it can be served > out by Apache instead of the little standalone webserver. Actually, I saw it ;) Just having nothing special to tell about it, as it's a nice addon to be able to run that cgi under apache. Regards, -- Laurent Wandrebeck HYGEOS, Earth Observation Department / Observation de la Terre Euratechnologies 165 Avenue de Bretagne 59000 Lille, France tel: +33 3 20 08 24 98 http://www.hygeos.com GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D 2A62 54E6 EF2C D17C F64C |