Like the idea, but think it would be more portable / user friendly if 'puppet-server' was in /etc/cobblet/settings.
If it is in settings then we could pull it in and make it usable via a snippet that could generate puppet.conf? Thoughts? On Tuesday, 16 April, 2013 10:20 EDT, "Leonid Flaks" <[email protected]> wrote: > On 04/16/2013 09:39 AM, Ronald J. Yacketta wrote: > > We are in the process of integrating Puppet into our Cobbler environment > > and have followed a couple guides to get the basics in place. > > Looking getks I see the bits in place to install Puppet and run it, but not > > seeing were puppet is configured. Seem to be missing a snippet or > > configuration to setup the clients puppet.conf with the puppet master > > server etc? > > > > What is the process to puppetize cobbler outside of enabling it in settings > > and adding it to the ks files? > > _______________________________________________ > > I am going through similar process too. I had to modify slightly the > snippet 'puppet_register_if_enabled' to pass to the client the > information about the server - using metadata. Something like this: > > #if $str($getVar('puppet_auto_setup','')) == "1" > # generate puppet certificates and trigger a signing request, but > # don't wait for signing to complete > #set $puppeteer = $getVar('puppet-server', '') > #if $puppeteer != '' > /usr/bin/puppet agent --test --server=$puppeteer --waitforcert 0 > #end if > # turn puppet service on for reboot > /sbin/chkconfig puppet on > > #end if > > > For that to work I set 'puppet-server=my.puppet.server.com' in meta data. > > Everything else is done on the puppet side - just like James said > minutes ago - signing of the cert, configuring the client. > > > -- > > Leon > > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
