I really hate poor documentation.
I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack & passenger modules from rubygems.
I ran the passenger build script and it compiled and installed into my local apache httpd server successfully.
Now where do I find an working example of puppetmaster.conf ?
Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ?
Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster?
I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever
Puppet seems way too clumber some with the amount of dependencies required so far.
I almost feel like going back to hacking on my system based on Python & Fabric L
--RB
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
(Or pkg_add -r puppet or yum install puppet etc. etc.)
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
On 05.04.2012 22:42, Brown, Rodrick wrote:
> I really hate poor documentation.
>
> I’m following along in PDF documentation I downloaded from the official
> site and I’m stuck after I installed rack & passenger modules from
> rubygems.
There is a PDF?! OK...
However, Maybe helpful:
<http://blog.andreas-haerter.com/2012/02/05/how-to-start-puppet-system-config-links-resources-tutorials>
-> "How to start" listing
> I ran the passenger build script and it compiled and installed into my
> local apache httpd server successfully.
I personally started by using Puppet without master but "puppet apply"
instead. I created modules and then ran something like
> su -
> puppet apply --verbose --modulepath /your/modules-directory/ -e "class { 'example': } foobar { [...] }"
to learn the stuff before creating master infrastructure and stuff.
BTW: There are masterless users out there (cf. "Masterless" listing at
my blog posting linked above).
> Puppet seems way too clumber some with the amount of dependencies
> required so far.
Seriously: use the packages of your distribution or the YUM/APT repos by
Puppetlabs if you want to start with all the 2.7 features right now (I
would recommend that - why learning and maintain old stuff if you just
start to use Puppet?). Or are you running Puppet on windows (=no
repositories available)?
--
Andreas <http://blog.andreas-haerter.com>
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
> But an MSI is available for windows: http://downloads.puppetlabs.com/windows
Cool, even better. Since when does a Puppet MSI exist?
However: One more reason why I can't understand the "Puppet seems way
too clumber some with the amount of dependencies required so
far"-statement. :-)
I’m running 64Bit CentOS 6.2 I’m using the Puppet software from scratch I couldn’t find any RPM’s is there a yum repo for puppet RPM binaries and dependencies? I didn’t see one so I built from source.
I need to support roughly ~3000 Linux host, I have a 3 VM’s in my lab right now I’m using to familiarize myself with the software so ill rather start learning to configure Puppet for a large production deployment instead of just running it in adhoc or simple configuration modes.
Thanks.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
----- Rodrick Brown <rbr...@knight.com> wrote:
> I'm running 64Bit CentOS 6.2 I'm using the Puppet software from scratch I couldn't find any RPM's is there a yum repo for puppet RPM binaries and dependencies? I didn't see one so I built from source.
>
> I need to support roughly ~3000 Linux host, I have a 3 VM's in my lab right now I'm using to familiarize myself with the software so ill rather start learning to configure Puppet for a large production deployment instead of just running it in adhoc or simple configuration modes.
>
> Thanks.
>
>
> From: puppet...@googlegroups.com [mailto:puppet...@googlegroups.com] On Behalf Of Russell Van Tassell
> Sent: Thursday, April 05, 2012 5:26 PM
> To: puppet...@googlegroups.com
> Subject: Re: [Puppet Users] Getting started
>
> It might also be helpful to include your O/S, here ... as there are many linuxes where installing puppet can largely be reduced to installing the right RPMs out of one repository or another (so you worry less about compiling and manufacturing basic configs than just learning how to make puppet go).
>
>
> On Thu, Apr 5, 2012 at 1:42 PM, Brown, Rodrick <rbr...@knight.com<mailto:rbr...@knight.com>> wrote:
> I really hate poor documentation.
>
> I'm following along in PDF documentation I downloaded from the official site and I'm stuck after I installed rack & passenger modules from rubygems.
> I ran the passenger build script and it compiled and installed into my local apache httpd server successfully.
>
> Now where do I find an working example of puppetmaster.conf ?
> Which config.ru<http://config.ru> should I be coping into /usr/share/puppet/rack/puppetmasterd ?
>
> Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster?
>
> I'm almost fed-up already and I've not even gotten 1 agent configured to talk to my sever
>
> Puppet seems way too clumber some with the amount of dependencies required so far.
>
> I almost feel like going back to hacking on my system based on Python & Fabric :(
>
> --RB
>
> Please visit our website for important disclaimers/disclosures regarding Knight's products and services:
>
> http://knight.com/KnightEmailDisclaimer.html
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com<mailto:puppet...@googlegroups.com>.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com<mailto:puppet-users%2Bunsu...@googlegroups.com>.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com<mailto:puppet...@googlegroups.com>.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com<mailto:puppet-users...@googlegroups.com>.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
> Please visit our website for important disclaimers/disclosures regarding Knight's products and services:
>
> http://knight.com/KnightEmailDisclaimer.html
>
On 08.04.2012 00:46, Michael Stahnke wrote:Cool, even better. Since when does a Puppet MSI exist?
>>> Puppet seems way too clumber some with the amount of dependencies
>>> required so far.
>>
>> Seriously: use the packages of your distribution or the YUM/APT repos by
>> Puppetlabs if you want to start with all the 2.7 features right now (I
>> would recommend that - why learning and maintain old stuff if you just
>> start to use Puppet?). Or are you running Puppet on windows (=no
>> repositories available)?
> But an MSI is available for windows: http://downloads.puppetlabs.com/windows