An other option you might consider, is using munin-async. It requires modifications on all nodes, so it might not be an option, but I felt compeled to mention it. If you can’t easily have shared nfs, or if you might have connectivity issues between master and some node, async would probably be a better approach.
Munin-Master runs differents scripts via the cron script (munin-cron).
is the only part actualy connecting to the nodes. It gathers information and updates the rrd (you’ll probably need rrdcached, especialy via nfs).
takes the informations gathered by update and limits, and generate the actual html files (if don’t have cgi-html). It currently still generate some data needed by the cgi.
generate the graphs. If you are thinking about getting many masters, you probably have alot of graph, and don’t want to generate them every 5 minutes, but you would rather use cgi-graph.
have graph (cgi) and html (from file or cgi) served by either html-master, or specific presentation hosts.
Cange the munin-cron to only run munin-update (and munin-limits, if you have alerts you want to be managed directly on those masters). The cron should NOT launch munin-html or munin-graph.
In order to have munin-html to run correctly, we need to merge those dbdir into one.
In order to make that part easier, a munin-mergedb.pl is provided in contrib.