SysDirector is a template driven configuration management system that allows administrators to deliver content to machines in a protocol independent fashion. Currently supported protocols include HTTP, TFTP, Puppet, and Cfengine.

Why should I use SysDirector?

SysDirector is a tool that makes managing groups of systems simpler. Think about how many configuration files on your systems are identical except for a handful of lines. Now imagine being able to customize those lines automatically based on system attributes: physical or logical (i.e. network) location, function of the machine, etc.

SysDirector allows you to template these files using the Cheetah template engine, and store them in a Subversion repository. When the system requests one of these templated files, the context of the system -- it's name, the groups it belongs to, the operating system it is running -- is taken into account as the file is generated on the fly and sent to the system. This allows for a tremendous amount of flexibility in your ability to customize what each system receives.

Because SysDirector is backed by Subversion, you get a log of who made what change, when, and why. This can be an essential tool for your use to comply with auditing requirements for your systems.

How do I get SysDirector?

NEW! SysDirector can also be download as an rPath (R) appliance from http://www.rpath.org/rbuilder/project/sysdirector/. Details on using the appliance can be found here

SysDirector source can be downloaded from www.sysdirector.org/download/, or checked out of the Subversion repository via:

svn checkout svn://svn.sysdirector.org/sysdirector

Where can I learn more about SysDirector?

Documentation is available online, or you may be interested in an overview of SysDirector's Features and Benefits. Mailing lists are available for those using or developing SysDirector, as well as a wishlist of future features.