Interesting information. Thanks Mohamed and Dominic for this info. Our setup is all local. In the case of an NFS mount - I don't know how easy it would be to tell puppet to look at the NFS mount, instead of /etc/sysconfig, etc., for it's info. In any event, you will still need to have a local /etc/init.d/puppet script. So why bother trying to store the localized items on NFS... ?
On Apr 29, 12:14 pm, Dominic Maraglia <domi...@puppetlabs.com> wrote: > On 4/28/11 11:57 AM, Forrie wrote: > > > Thanks for the feedback. > > > It will make life a lot easier if I can deploy/maintain puppet via a > > RO NFS mount point. I presume you have the local stuff like /etc/ > > init.d/puppetmaster /etc/sysconfig/puppet /etc/puppet/puppet.conf > > managed separately and located on each system? > Correct. > > I thought it might be interesting to have the configs on NFS, but I > > don't know if that would scale very well. > > I think this is possible, depending on the installation. Some Puppet > customers have deploy Puppet world wide, cross continents, where the > stateless nature of NFS would not provide a suitable solution. For > smaller/geographically confined environments, a single source > deployment/management method might be worth researching. > > Regards, > > Dominic > > > > > > > > > > > Thanks! > > > On Apr 26, 8:13 pm, Dominic Maraglia<domi...@puppetlabs.com> wrote: > >> Hello, > > >> On 4/25/11 2:13 PM, Forrie wrote: > > >>> How do you handle the *.rpm prerequisites of puppet itself. If one > >>> installs (deploys) puppet on an NFS mount, presumably you would also > >>> include enterprise-ruby (or standard) with those dependencies there. > >>> Enterprise Ruby seems to have rolled their own rpms, prefixed with > >>> "pe-". > >> Actually, we (Puppet) do not package Enterprise Ruby; however, we do > >> package Ruby 1.8.7 and do indeed name the rpm "pe-ruby". This is done > >> to differentiate the Puppet "stack" Ruby from a possible pre-installed > >> vendor Ruby. Puppet Enterprise's (pe) Ruby binary can be found here > >> "/opt/puppet/bin/ruby" > > >> On 4/26/11 12:55 PM, Forrie wrote: > > >>> I was referring to the RPMs that ship with Enterprise Puppet -- I > >>> haven't poked through the code, but if they get installed into the > >>> system, then that would pretty much negate (or make more difficult) > >>> creating an NFS-deployed Puppet for use. > >> We have not specifically tested a single shared deployment as described > >> by Mohamed (below). We do support and test installation, on all our > >> supported operating systems, from a RO NFS mount point. > > >> Cheers, > >> Dominic Maraglia > >> Puppet Labs > > >>> On Apr 25, 9:43 pm, Mohamed Lrhazi<lrh...@gmail.com> wrote: > >>>> Sorry ignore my last statement... I did not use REE on Solaris, but > >>>> used OpenCSW which packages all the software to go under /opt/csw, > >>>> including ruby and puppet, and makes it straightforward to share the > >>>> whole /opt/csw readonly over NFS > >>>> I still think REE with facter and puppet in one directory should be > >>>> work fine too. > >>>> Thanks, > >>>> Mohamed, -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
