Jason van Zyl
2006-Jul-28 14:40 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
Hi, I was at the Puppet talk at Oscon and I would like to try using Puppet for PXE on RHEL machines and I was wondering if there are standard minimal Kickstart recipes from which Puppet can then take over. Thanks, Jason van Zyl jason at maven.org
Michael DeHaan
2006-Jul-28 14:51 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
Jason van Zyl wrote:> Hi, > > I was at the Puppet talk at Oscon and I would like to try using > Puppet for PXE on RHEL machines and I was wondering if there are > standard minimal Kickstart recipes from which Puppet can then take > over. > > Thanks, > > Jason van Zyl > jason at maven.org > > > > _______________________________________________ > Puppet-users mailing list > Puppet-users at madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >I''d suggest running system-config-kickstart to generate what you want or otherwise taking a minimal install you''ve already done and using /root/anaconda.ks that Anaconda saves as a starting point. You can do whatever you want in %post, including installing puppet and invoking it (say in local context). Assuming this is to be tied into PXE infrastructure and you want to do any system specific templating in that post action (i.e. deploy this recipe there, but not here), I happen to have a tool for that... http://et.redhat.com/page/Cobbler_%26_Koan_Provisioning_Tools (shameless plug -- let me know if you encounter any issues or have improvement ideas). For any advanced kickstart questions, try joining kickstart-list at redhat.com -- I am by no means an expert and usually rely on s-c-k and the "hack the file in /root" method. --Michael
David Lutterkort
2006-Jul-28 19:00 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
Hi Jason, how are things ? On Fri, 2006-07-28 at 17:40 -0400, Jason van Zyl wrote:> I was at the Puppet talk at Oscon and I would like to try using > Puppet for PXE on RHEL machines and I was wondering if there are > standard minimal Kickstart recipes from which Puppet can then take > over.I wrote a blog entry that outlines what needs to be done to provision puppet[1] - feel free to contact me to work this out in more detail. I have a sneaking suspicion that the entry is somewhat out of date, since puppet is now in Fedora Extras. David [1] http://watzmann.net/blog/index.php?title=provisioning_puppet&more=1&c=1&tb=1&pb=1
Luke Kanies
2006-Jul-31 09:04 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
On Jul 28, 2006, at 4:40 PM, Jason van Zyl wrote:> Hi, > > I was at the Puppet talk at Oscon and I would like to try using > Puppet for PXE on RHEL machines and I was wondering if there are > standard minimal Kickstart recipes from which Puppet can then take > over.I''d love to have standard scripts for installing Puppet on most standard platforms. Red Hat, Debian, and Solaris should be pretty easy to accommodate. I can create a separate section for this documentation or something, but it seems like there should be a better way. -- Luke Kanies http://madstop.com 615-594-8199
David Lutterkort
2006-Aug-07 17:29 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
On Fri, 2006-07-28 at 17:40 -0400, Jason van Zyl wrote:> I was at the Puppet talk at Oscon and I would like to try using > Puppet for PXE on RHEL machines and I was wondering if there are > standard minimal Kickstart recipes from which Puppet can then take > over.Attached is a kickstart config that installs puppet, enables puppetd to start after reboot, and tries to connect to the puppetmaster just enough to get the client certificate during installation. Comments more than welcome. I use it to provision Xen virtual machines quite happily. David -------------- next part -------------- install reboot #interactive url --url http://boot.example.com/fc5-i386/tree/ lang en_US.UTF-8 keyboard us network --device eth0 --bootproto dhcp rootpw --iscrypted $1$JkZO8v2t$2bxJbViwrcvvSDxJVDV0k0 firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --enforcing timezone --utc America/Los_Angeles bootloader --location=mbr --driveorder=xvda --append="rhgb quiet" #vnc clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup domu --pesize=32768 pv.2 logvol / --fstype ext3 --name=lv00 --vgname=domu --size=1024 --grow logvol swap --fstype swap --name=lv01 --vgname=domu --size=272 --grow --maxsize=544 %packages @base @core @editors @emacs cracklib-dicts rmt tzdata %post --nochroot test -f /tmp/netinfo && cp /tmp/netinfo /mnt/sysimage/tmp/ %post # Installing puppet from the standard yum config is fine, but a little # error prone. It would be better to pull a yum config that points to local # Fedora mirrors and install puppet from there /usr/bin/yum -y install puppet /sbin/chkconfig --level 345 puppet on # Run puppet just to get the client certificate; this works with DHCP, but # I haven''t tested it if the IP info is given statically. And obviously, # it''s not a very good idea for disconnected installs. In that case, puppet # will run when the achine is rebooted after the install. The reason I # pull the cert during installation is so that I can turn autosign for this # machine on while it''s being provisioned and then off again once # provisioning is finished. Don''t forget to run ''puppetca -c CLIENT'' on the # puppetmaster before reprovisioning the client if [ -f /tmp/netinfo ] ; then FQDN=`(source /tmp/netinfo; [ -n "$DOMAIN" ] && echo $HOSTNAME.$DOMAIN || echo $HOSTNAME)` # Run puppet, just to get the certs; the actual config update happens # on the next reboot hostname $FQDN # --fqdn has a bug in puppet <= 0.18.4 #/usr/sbin/puppetd --test --tag no_such_tag --waitforcert 600 --fqdn $FQDN /usr/sbin/puppetd --test --tag no_such_tag --waitforcert 600 fi
Jason van Zyl
2006-Aug-20 17:59 UTC
[Puppet-users] Minimal Kickstart setups to use with Puppet
On 7 Aug 06, at 8:29 PM 7 Aug 06, David Lutterkort wrote:> On Fri, 2006-07-28 at 17:40 -0400, Jason van Zyl wrote: >> I was at the Puppet talk at Oscon and I would like to try using >> Puppet for PXE on RHEL machines and I was wondering if there are >> standard minimal Kickstart recipes from which Puppet can then take >> over. > > Attached is a kickstart config that installs puppet, enables > puppetd to > start after reboot, and tries to connect to the puppetmaster just > enough > to get the client certificate during installation. Comments more than > welcome. > > I use it to provision Xen virtual machines quite happily. > > David >Hi David, Thanks for the KickStart configs, I''m going to give them a shot this week. Just wanted to let you know I haven''t forgotten! Jason.> <domU.cfg> > _______________________________________________ > Puppet-users mailing list > Puppet-users at madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-usersJason van Zyl jason at maven.org