On 20/01/12 19:09, Garrett Honeycutt wrote: > My cobbler module[1] is pretty old and I imagine crusty by now. You > mentioned that the module was basic and implied you wanted to manage > other things. > > What other things should a cobbler module be managing?
Well, as I said, there's a limit to what you can set up. I was hoping to be able to: - write a node definition manifest for a new machine - include dhcp, dns, hostname and network definitions - commit to Git - deploy via Puppet - have the provisioning server pick the config up and set up PXE, DHCP, and DNS accordingly - shortly after, boot a new machine, and during the PXE boot either - have its MAC address recognised - select the system from a menu - have the provisioned with puppet and an appropriate hostname - have puppet configure it in the pre-assigned role To be able to do that with Cobbler, I'd need to be able have puppet configure the distros, repos, profiles, and systems known to it. Ideally, I'd be able to re-deploy a new Cobbler server in exactly the same way as another node. Of course, this is an idea - I'd probably settle for much less in the short term. > Perhaps we could > work together on updating this module to offer more functionality and > flexibility. I might be up for that later, but I've probably not got the luxury right now - I need as much off-the-shelf stuff as I can get. Judging by James Turnbull's blog post [1] on writing new types/providers, it might be fairly easy to do such a thing for Cobbler, but I'm not primarily a Ruby developer nor very far into Puppet, so the learning curve and risk of getting bogged down in some detail is fairly high. Cheers, N 1. http://www.kartar.net/2010/02/puppet-types-and-providers-are-easy/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
