> My view is basically that you have three entities: > > OS setup -> Config Setup -> Monitoring > > The thing that owns OS setup also owns the way that control is > transferred to the next, similar to the way that many configuration > tools can also help you set up monitoring. They don't own monitoring, > but they own the setup of the next tool in the chain
Well and good, but now imagine a tornado comes and wipes all three away. Now you need to reconstitute your network, and you need to start with your Cobbler server, because you're about to kickstart a whole bunch of machines. You have to install the OS manually on that server, but then installing and configuring Cobbler the way you run it at your site is an item of "config setup," which you want Puppet to know about and do. (In order to reconstruct a working Cobbler server, Puppet may not need to know each thing in Cobbler's database, but merely where a copy of Cobbler's VCS repo is, so it can put it in place before starting Cobbler up.) The scenario I have described may not be what Nick nor Gerhardus are trying to do, but it's a big part of what I'm trying to use Puppet for. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
