jeremy- did i hear right or are you volunteering to write a little documentation? :)
the docs for ganglia could really use some help. i know that when i wrote the documentation i made too many assumption about how things work. ganglia 3 is being built right now and when i return to the bay area in february i should have it ready for testing by the developers. once it solidifies into a release.. we are going to need to rewrite the docs. it would nice to have a person outside of the ganglia developer group who has great writing skills to write the docs. i'm commenting all the code using doxygen but that is geared more toward the developers out there. it would be great to have a set of docs geared toward the cluster admin in mind. would you be interesting in helping with the ganglia 3 docs? how much time would you have to dedicate to the project? also.. can you think of any specific part of the current documentation that misled you to believe that gmetad needed to be installed everywhere? i'll rewrite it in order to help the next installer. any help you can offer will be appreciated! -matt Dec 14, Jeremy Weatherford wrote forth saying... > Hello, > > I recently set up Ganglia to be distributed in RPM form to the nodes of a > small cluster, and was absolutely delighted to have it working very > quickly. I had gotten the impression that gmetad needed to run on each > node in the cluster, which made the install more troublesome than it would > have been otherwise. > > Seeing gstat in action, and hearing bits and pieces about gexec got me > excited about having a cluster execution tool that was smart enough to > know which nodes were up. After installing authd and figuring out how to > generate keys, gexec worked great with hardcoded machine lists, but what I > really wanted was for it to pull the machine list from gmetad. This was > the most frustrating part of the install, since it took quite a while (and > looking through README files which were only available in the source > package) to discover that gmond needed to be compiled with --enable-gexec. > Rebuilding the RPMs was easy enough, and I finally got gexec working > -most- of the time. > > Why isn't --enable-gexec on by default? As far as I can tell from the > gmond source, the corresponding flag is only checked in one place in > gmond, to determine whether or not to report a host as support gexec. Am > I missing something there? > > Also, the documentation linked from Sourceforge can use a -lot- of work... > or am I missing some hidden repository? > > Thanks for a great tool, I look forward to learning more about it, and > possibly helping with documentation. > > Jeremy Weatherford > [EMAIL PROTECTED] > http://xidus.net > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Ganglia-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ganglia-general >
