Config management - Reinventing the wheel

[Andy Harrison]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGfBQiNTm8fWdRgmIRAr+AAKDl5IcsHrQB9jlVbGhgBHPln9ZJxQCg0tTU
Z2pfiBgJgnLLOMuacIygRGI=
=G1xZ
-----END PGP SIGNATURE-----

On 6/22/07, Jonathan Call <jcall at verio.net> wrote:
> I currently use nagiosweb (http://sourceforge.net/projects/nagiosweb/)
> to maintain a Nagios configuration for a central server in mysql. Based
> off of certain host groups I want to generate configuration files for
> distributed Nagios servers for that central server.
>
> Has anyone written code (for example, perl) to generate distributed
> Nagios 2.x configuration files based on a central Nagios server's
> configuration that is stored in a mysql database? It doesn't have to be
> nagiosweb. I believe that any db style would be easy enough to change to
> make it work.
>
> I thought I would ask to see if I could avoid reinventing the wheel.

Check out Monarch.  Best one I've tried yet.

http://sourceforge.net/projects/monarch

-- 
Andy Harrison
public key: 0x67518262

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null