I don't like tie them together either :) My way around it is to impose it as a ksmeta
variable (if I define package, install whatever is the package contents) - then I can get
around that more naturally.
----- Original Message -----
From: "Dan White" <ygor(a)comcast.net>
To: "cobbler mailing list" <cobbler(a)lists.fedorahosted.org>
Sent: Monday, August 20, 2012 10:59:05 AM
Subject: Re: [cobbler] Puppet configuration
http://lmgtfy.com/?q=cobbler+puppet+integration
Specific links:
(Old)
https://fedorahosted.org/cobbler/wiki/UsingCobblerWithConfigManagementSystem
(New)
https://github.com/cobbler/cobbler/wiki/Using%20cobbler%20with%20a%20conf...
Personally, I do not tie the two together too closely.
Mainly because I have systems that I have provisioned with Cobbler
but are not managed by Puppet (yet {insert evil laugh here})
I just have Cobbler install Puppet for me and then I have the
PuppetMaster take over once the new system is registered.
On Aug 20, 2012, at 10:16 AM, Bai Shen wrote:
> So I'm able to get my machine built using cobbler. However, it
> doesn't seem to have installed and set up puppet.
>
> Does anyone know of any good tutorials or documentation that I can
> look at? Most of the stuff I'm finding assumes you're just
> installing puppet, not continuing on from a cobbler kickstart.
>
> Thanks.
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler