<div dir="ltr"><div><div>The version in OpenCSW is quite old.  If you're starting fresh with Puppet start with the newest version possible.   Upgrades can be very painful.<br><br>I run Puppet 4.3.2 installed from a gem.   I use Ruby from OpenCSW to make this possible.  <br><br></div>It's still in early development, but is working very well.   I've been running Puppet for 5 years on Linux, just recently on OmniOS.<br><br>Soon the provision script will be on our public repo.  If any would like to look at it now, email me and I'll send you a copy.   <br><br></div>I have to update ruby gems before installing puppet.  The important snippets from my provision script:<br><pre><span class="">RUBYGEMS_VERSION</span><span class="">=</span><span class="">"2.0.15"</span>
<a name="provision_agentomnios.sh-19"></a><span class="">RUBYGEMS_UPDATE</span><span class="">=</span><span class="">"rubygems-update-</span><span class="">${</span><span class="">RUBYGEMS_VERSION</span><span class="">}</span><span class="">.gem"</span>
<a name="provision_agentomnios.sh-20"></a><span class="">RUBYGEMS_UPDATE_SOURCE</span><span class="">=</span><span class="">"<a href="https://github.com/rubygems/rubygems/releases/download/v">https://github.com/rubygems/rubygems/releases/download/v</a></span><span class="">${</span><span class="">RUBYGEMS_VERSION</span><span class="">}</span><span class="">"<br></span><span class="">current_gems_version</span><span class="">=</span><span class="">`</span>/opt/csw/bin/gem --version<span class="">`</span>
<span class="">if</span> <span class="">[</span> <span class="">"</span><span class="">$current_gems_version</span><span class="">"</span> !<span class="">=</span> <span class="">"</span><span class="">${</span><span class="">RUBYGEMS_VERSION</span><span class="">}</span><span class="">"</span> <span class="">]</span><span class="">;</span> <span class="">then</span>
<a name="provision_agentomnios.sh-78"></a>    wget <span class="">${</span><span class="">RUBYGEMS_UPDATE_SOURCE</span><span class="">}</span>/<span class="">${</span><span class="">RUBYGEMS_UPDATE</span><span class="">}</span>
<a name="provision_agentomnios.sh-79"></a>    /opt/csw/bin/gem install --local <span class="">${</span><span class="">RUBYGEMS_UPDATE</span><span class="">}</span> <span class="">&&</span> rm <span class="">${</span><span class="">RUBYGEMS_UPDATE</span><span class="">}</span>
<a name="provision_agentomnios.sh-80"></a><span class="">fi<br></span><span class="">/opt/csw/bin/gem install --no-rdoc --no-ri puppet<br></span></pre>-Chip<br><div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 17, 2016 at 6:01 PM, Trey Palmer <span dir="ltr"><<a href="mailto:trey@mailchimp.com" target="_blank">trey@mailchimp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra">I should add, I'd use the niksula package over CSW if you can.   I really appreciate their repo (and OmniOS).</div><div class="gmail_extra"><br></div><div class="gmail_extra">We only use the CSW package because at the time the available version happened to line up with what we were running everywhere else.   As a general rule, the agents shouldn't be an earlier version than your masters.   </div><div class="gmail_extra"><br></div><div class="gmail_extra">Now niksula has 3.8.5 which I might actually be able to change to.   Using CSW packages intended for a diverging closed source Solaris is obviously gonna bite me sooner or later.</div><div class="gmail_extra"><br></div><div class="gmail_extra">As far as the manifest/method, if you run the daemon you can have puppet install them on the first run, and puppet's standard service resource has a "manifest" parameter that will "svccfg import" for you.</div><div class="gmail_extra"><br></div><div class="gmail_extra">But Lauri is right that there's no real reason to run the daemon vice from cron except to standardize with the rest of your org.</div><span class=""><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">   -- Trey</div></font></span><div><div class="h5"><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">On Wed, Feb 17, 2016 at 4:59 PM, Lauri Tirkkonen <span dir="ltr"><<a href="mailto:lotheac@iki.fi" target="_blank">lotheac@iki.fi</a>></span> wrote:<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Wed, Feb 17 2016 15:52:00 -0600, Paul Jochum wrote:<br>
>     Thanks for responding.  I am new to puppet, and curious, why do you run<br>
> it from cron, instead of in daemon mode?  Is it more secure, or is there<br>
> something else I am missing?<br>
<br>
</span>It used to be that the agent was leaking memory in version 2.something<br>
when we first started using it. 'puppet kick' also existed then, to<br>
trigger an agent run from the master, but it doesn't anymore; we don't<br>
think there's any reason to run the agent as a daemon.<br>
<span><br>
--<br>
Lauri Tirkkonen | lotheac @ IRCnet<br>
</span><div><div>_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com" target="_blank">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
</div></div></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" rel="noreferrer" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
<br></blockquote></div><br></div></div></div></div></div>