Good Evening I just wanted to ask a question here, is it possible to build a static binary that I could sep to a client machine, and have it do it''s first run to connect to a puppet master? My plan is to use a static binary as a sort of installer for particular systems, as I don''t really want to have to install puppet client on 70 systems by hand! These are all production servers already, so I''m not getting the opportunity to build them from the ground up. Any advice is appreciated, thanks. Mister IT Guru -- misteritguru@gmx.com Twittersphere @mritguru -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sat, Jan 7, 2012 at 9:34 AM, Mister IT Guru <misteritguru@gmx.com> wrote:> Good Evening > > I just wanted to ask a question here, is it possible to build a static > binary that I could sep to a client machine, and have it do it''s first run > to connect to a puppet master? > > My plan is to use a static binary as a sort of installer for particular > systems, as I don''t really want to have to install puppet client on 70 > systems by hand! These are all production servers already, so I''m not > getting the opportunity to build them from the ground up. >Is it that much more difficult to push a package to a machine than it is to copy a static binary to it? If you download the source tarball for Puppet, you can use ext/envpuppet to run Puppet directly out of the source tree, assuming that you''ve already got Ruby on the machines.> > Any advice is appreciated, thanks. > > Mister IT Guru -- misteritguru@gmx.com > Twittersphere @mritguru > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- Nigel Kersten Product Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I don''t see this as any different than pushing a script to the system to do the initial deployment or running a script that makes ssh connections to it. There''s no need for a static binary. In the early days, before it was part of our base config, we used to push puppet to machines that didn''t have it using a puppet-deploy script which would connect to a named host via ssh and use the package manager to install puppet, set a couple of initial things and fire it up. If you run your version of this type of tool from your puppet master, you can even make it automate the signing step for you. -z On Sat, Jan 7, 2012 at 12:34 PM, Mister IT Guru <misteritguru@gmx.com>wrote:> Good Evening > > I just wanted to ask a question here, is it possible to build a static > binary that I could sep to a client machine, and have it do it''s first run > to connect to a puppet master? > > My plan is to use a static binary as a sort of installer for particular > systems, as I don''t really want to have to install puppet client on 70 > systems by hand! These are all production servers already, so I''m not > getting the opportunity to build them from the ground up. > > Any advice is appreciated, thanks. > > Mister IT Guru -- misteritguru@gmx.com > Twittersphere @mritguru > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- Zac Sprackett, Director of Network Operations SugarCRM, Inc. w: http://sugarcrm.com e: zac@sugarcrm.com t: +1.613.265.0860 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I just wanted to ask a question here, is it possible to build a static > binary that I could sep to a client machine, and have it do it''s first run > to connect to a puppet master? > > My plan is to use a static binary as a sort of installer for particular > systems, as I don''t really want to have to install puppet client on 70 > systems by hand! These are all production servers already, so I''m not > getting the opportunity to build them from the ground up. >We have a script that preps a machine for puppet, it''s usually called like this, on the remote box: curl http://puppetmaster.example.com/install-puppet.sh | bash -x the script just sets up the yum repos, removes any crufty ruby installed, yum installs our puppet rpms, pulling in the right ruby rpm & runs the first puppet apply, with wait for cert & then sets up the service. We also do a few other steps that trip us up (clock drift being one for certs, so ntpd is configured & time pulled from a known good source etc). I can sanitize & post this if you want. Simon. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.