[Beowulf] How do people keep track of computers in your cluster(s)?

[Mike Davis]

In the old days, when a  machine was a machine and the internet was 
arpanet, we kept a logbook for each machine. It had much of the data 
that you would want to keep, plus a log of all changes made to the system.

These days, we generally use a wiki for this. You could do it in a db, 
but the wiki is a much friendlier format.


Mike



Carsten Aulbert wrote:

>Hi all,
>
>we are currently looking into the problem, how to keep track of
>computers which we are going to buy. On the one hand there are the
>standard tools to monitor a running cluster like ganglia, nagios,
>zenoss, ... but these are - to my understanding - just for monitoring
>the current status.
>
>However, I would like to have something where we have something like a
>large table about the hardware in question. In there information like
>
>* vendor
>* serial number
>* MAC addresses (eth0, eth1,..., IPMI, RAID,...)
>* maybe even firmware versions and serial numbers of exchangeable
>internal hardware (hard disks)
>* basically all physical information of the box
>
>another table should hold the current setup, i.e. a mapping between the
>hardware and the "logical" setup, e.g.
>
>Hardware box number #1234 from above table has in the current setup the
>following...
>
>* hostname
>* IP addresses
>* running services
>* ...
>
>And finally, another table where special problems, like memory errors
>and the like can be entered.
>
>I know this sounds just like three medium sized SQL tables, but at least
>I wanted to ask what people are using if more than a single person is
>working on the cluster. One person can probably do this with a simple
>text file and a set of papers in a filing cabinet.
>
>Thanks a lot for any answers
>
>Carsten
>
>_______________________________________________
>Beowulf mailing list, Beowulf at beowulf.org
>To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
>  
>