Jason Edgecombe schrieb:
Would some type of flag file that specified the department and college
be a better way? That way, departmental and college admins can add a
new machines to their cfengine group without having to involved the
cfengine root admin.
This is a possibility. You could work with "FileExists" in the
groups-section that checks for the existence of e.g. /etc/college1.
And if you write the cfengine configuration in a reversible way, you can
actually reconfigure a computer simply by changing the flag file when
you shuffle the computer around between the departments. But this
requires a lot of discipline for the admins....
College's might have their own servers for load-balancing purposes.
All machines in a college could talk to that college's cfengine
server, but all cfengine server's would mirror from the master.
This is a possible way for the reduction of the load on the individual
master servers.
Alex
_______________________________________________
Help-cfengine mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-cfengine
