Re: cobbler as a monitoring "provider"
On Thu, Aug 04, 2011 at 11:16:50AM +0100, Gerhardus Geldenhuis wrote:
I am toying with the idea to write an addon for cobbler that will
allow it
to become an authorative source of servers in the same way as cobbler
can/does provide a list of servers to a configuration management system like
puppet.
You actually want to
a) either use the cobbler database as source for the other
services (monitoring software, configmanagement)
b) alternatively you can decide to have other databases
(one in monitoring software, one in configmanagement)
c) or one cmdb (master) that is interacting with the databases of
cobbler/monitoring/configmanagement
Probably you want b) or c) since most tools like i.e. nagios are easiest to
setup when using an own database.
You then have to decide on ways the information should flow.
I.e. you could always start servers live in cobbler and feed the cmdb (or the
separate monitoring/configmanagement etc. databases) directly from cobbler.
Or a cmdb becomes the 'master', info is entered here and are triggering
creation of the objects in the cobbler/monitoring/.. databases.
Also to decide is if you want to use hooks (whenever a new server is entered
into cmdb it gets pushed into cobbler/.. immediately) or if you want to use
syncscripts that grok the cmdb and cobbler data, compare them and create
missing datasets.
Christian