Re: [gomd-devel] Stuff to monitor

[johnycsh]

Heya Matt
Hows openmosixview? Ive decided to actually install
my own little oM cluster at home to be able to develop
more on this. Hopefully ill get that done pretty soon.
Ive sepnt > 2 days trying to fix my windows install so
i can do some homework that needs it. *sigh*

I was wondering if you guys have any other ideas on what to monitor?
i mean, everything in /proc + uptime seems good. Is there anything
significant that /proc doesnt cover?

Also, i was curious about the ability to run command through gomd?
I considered making mosstatd more generalized and perhaps able to handle
scenarios like this but instead i opted for the exteremly simple model
of jsut sending out a fixed structure every interval. I did this to
keep any possibility of remote exploits of mosstatd at bay. if it never
issues a read() it cant possibly read in malicious data. Anyway, i just
hope you keep things like that in mind. While i do think that gomd will
defintely have to take on a more complicated model than mosstatd, i hope
that the ability to execute commands remotely is defintely easy to turn
off (perhaps by default)

Anyway i hope to have my little cluster up by this weekend.
Wish me luck in that regard

-Jc




 On Sun, 2 Mar 2003, Matthias Rechenburg wrote:

> Hey Johnny ;)
>
> On Samstag, 1. M?rz 2003 20:37, address@hidden wrote:
> > Hey guys, ive been lurking on this list and admittedly havent even played
> > with the code yet. Getting access to a cluster isnt as easy as it used to
> > be for me. Anyway I've been curious as to what sorts of things that you
> > are intending to monitor outside of the /proc filesystem? Im just curious,
> > i couldnt really think of anything that needs a daemon running to keep
> > track of. Everything i could think of could be accomplished by reading
> > /mfs/X/proc/XXXX
>
> no, you are wrong here ;)
> 1) you cannot be sure that everybody is using MFS
> 2) you cannot access /proc and /dev on the remote nodes using MFS !
>
> On the other hand you are (mostly) right. We are all very happy about the
> cluster-wide /proc filesystem from openMosix and we want to get
> some of the informations+values from there too ........
> ......... but we want much more ;)
> We also want to be able to monitor values which are not in the
> openMosix /proc interface but only local on every system .e.g uptime
>
> The gomd should/could also act as a replacement for "rsh" and "ssh"
> because we want it to execute openMosix-related admin commands on
> the nodes (from remote).
>
> The most important part of the gomd-project is to my mind the libgomd.
> This library will be for developers to use it in their own programs.
> The plan is to have a clean and documentated interface to get
> all wanted values from the gomd (from the openMosix nodes)
> by using "easy" methods from the libgomd.
> We will implement all kinds of methods for getting informations about
> every node in you cluster (and the cluster at all) in a simple way so
> you do not have to "re-invent the wheel" everytime.
> e.g. right now we have (about) 3-5 very nice GUI applications for openMosix
> .......... but every app is using its own way (and has its own functions) to
> get the values from the node(s).
>
> btw: we are looking into the mosstatd code too to learn from it.
>
> .... and we want to implemt libgomd "plugins" for other languages than C too,
> e.g Java, PHP, shell ....
>
> >
> > Just Curious
> > -Johnny Cache
> <snip>
>
> Many thanks for you comments and as you know every feedback
> or feature re-quest is welcome.
>
> have a nice weekend Johnny,
>
> Matt
> ....... another good reason for the gomd project is that we
> all want to learn more about c/c++ ;)
> --
> E-mail        :  address@hidden
> www   : http://www.openmosixview.com
> an openMosix-cluster management GUI
>
> If you can dream it, you can do it!
>
>
>
> _______________________________________________
> gomd-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/gomd-devel
>