Puppet users - Jun 2011 - Any good documentation NGINX + Passenger + Puppet?

Hello,

I been browsing around and can not find any good documentation how to setup
Puppet with Nginx and passenger

I have a working Nginx with passenger support working but then what ?
Kinda confuse and wondering if maybe Passenger is not the way to go ?
Mongrel ? or something different?
any pointer appreciated .



btw I have read :

http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel_Nginx
and
http://projects/puppetlabs.com/projects/1/wiki/Using_Passenger



and still I do not get it ...


Nginx 1.0.0, Passenger 3.0.7 and puppet 2.6.2


thanks

-- 
-ls

-- 
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.

Passenger setup is annoyingly complicated since you''re having to set up
Apache, configure Ruby as an application server on top of that and then
install the Puppetmaster on top of that.  To add to the fun, Apache configs
are different between distributions, it''s different between releases of
Puppet and most of the instructions out there are a bit out of date.  And
it''s very very picky about versions.  I had to cobble mine together
from
about three different sources to make it work.  Are you using a Red Hat
derivative?  I''ve never done this on the Debians.

On Tue, May 31, 2011 at 6:15 PM, Luc Suryo <lsuryo@gmail.com> wrote:
> Hello,
>
> I been browsing around and can not find any good documentation how to setup
> Puppet with Nginx and passenger
>
> I have a working Nginx with passenger support working but then what ?
> Kinda confuse and wondering if maybe Passenger is not the way to go ?
> Mongrel ? or something different?
> any pointer appreciated .
>
>
>
> btw I have read :
>
> http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel_Nginx
> and
> http://projects/puppetlabs.com/projects/1/wiki/Using_Passenger
>
>
>
> and still I do not get it ...
>
>
> Nginx 1.0.0, Passenger 3.0.7 and puppet 2.6.2
>
>
> thanks
>
> --
> -ls
>
> --
> 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.
>
>
-- 
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.

Well I got it working! The mistake I made was mixing mongrel and
passenger

So I have now a ''working'' nginx + passenger + puppet

Still doing some test BUT the one things I did found out is that the
file /etc/puppet/auth.conf
need to be adjusted...



Still some weird issue :

1. files get changed to a different user/group...
since I was struggling with permission I tried to change everything to
puppet:puppet
and it end-up changing file that were suppose to be root:root to
nagios:nagios !
reverse back and this problem is gone.



2. Things seems (not all) to be re-evaluated every time puppetd is
run
(im looking to into this : 
http://www.masterzen.fr/2010/03/21/more-puppet-offloading/


3. SO my next issue is a function I wrote (random minute for cron),
this stopped working,
So instead of executing the function is takes is a value... Anyone ???



Here is my nginx setup


in nginx.conf:

The following lines added in the http section
        # Passenger needed for puppet
        passenger_root          /var/lib/gems/1.8/gems/
passenger-3.0.7;
        passenger_ruby          /usr/bin/ruby1.8;


in puppetmaster.conf (virtual host)

server {
        # Default Puppet master port and SSL
        listen 8140 default ssl;

        # Musy match certificate
        server_name puppet.ec2 puppet;

        # Rack-app root direcory
        root                            /data/lib/puppet/rack/public;

        # Log files
        error_log                       /data/lib/puppet/rack/log/
puppet_error_log error;
        access_log                      /data/lib/puppet/rack/log/
puppet_access_log;

        # Enable passenger
        passenger_enabled               on;

        # Make sure we serve everything as raw
        types { }
        default_type application/x-raw;

        # SSL certs and options
        ssl                             on;

        ssl_certificate                 /data/lib/puppet/ssl/certs/
puppet.pem;
        ssl_certificate_key             /data/lib/puppet/ssl/
private_keys/puppet.pem;
        ssl_client_certificate          /data/lib/puppet/ssl/ca/
ca_crt.pem;
        ssl_crl                         /data/lib/puppet/ssl/ca/
ca_crl.pem;
        ssl_verify_client               optional;

        ssl_protocols                   SSLv3 TLSv1;
        ssl_ciphers                     HIGH:+MEDIUM;
        ssl_prefer_server_ciphers       on;

        ssl_verify_depth                1;
        ssl_session_cache               shared:SSL:8m;
        ssl_session_timeout             5m;
}


NOTE : I moved puppet into /data/lib/puppet and have a symlink :  /var/
lib/puppet -> /data/lib/puppet


My track directory structure

/data/lib/puppet/rack
                  |_ public/
                           |_puppet   <-- symlink to /usr/lib/ruby/1.8/
puppet
                  |_ tmp
                  |_ config.ru
                  |_ log



So every entry has in /etc/puppet/auth.conf

allow *
auth no



Hope this help other!


On Jun 1, 8:59 am, Aaron Grewell <aaron.grew...@gmail.com>
wrote:
> Passenger setup is annoyingly complicated since you''re having to
set up
> Apache, configure Ruby as an application server on top of that and then
> install the Puppetmaster on top of that.  To add to the fun, Apache configs
> are different between distributions, it''s different between
releases of
> Puppet and most of the instructions out there are a bit out of date.  And
> it''s very very picky about versions.  I had to cobble mine
together from
> about three different sources to make it work.  Are you using a Red Hat
> derivative?  I''ve never done this on the Debians.
>
>
>
>
>
>
>
> On Tue, May 31, 2011 at 6:15 PM, Luc Suryo <lsu...@gmail.com> wrote:
> > Hello,
>
> > I been browsing around and can not find any good documentation how to
setup
> > Puppet with Nginx and passenger
>
> > I have a working Nginx with passenger support working but then what ?
> > Kinda confuse and wondering if maybe Passenger is not the way to go ?
> > Mongrel ? or something different?
> > any pointer appreciated .
>
> > btw I have read :
>
> >http://projects.puppetlabs.com/projects/1/wiki/Using_Mongrel_Nginx
> > and
> >http://projects/puppetlabs.com/projects/1/wiki/Using_Passenger
>
> > and still I do not get it ...
>
> > Nginx 1.0.0, Passenger 3.0.7 and puppet 2.6.2
>
> > thanks
>
> > --
> > -ls
>
> > --
> > 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.
-- 
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.

> 3. SO my next issue is a function I wrote (random minute for 
> cron), this stopped working, So instead of executing the 
> function is takes is a value... Anyone ???
I can''t help with the problem you''re having, but would this do
for your
random minute?

	# Random minute between 10 past and 10 to the hour
	$random_minute = fqdn_rand(40) + 10
	cron { "foo":
		command => "bar",
		minute  => $random_minute,
		ensure  => present,
	}

fqdn_rand is described here:
http://docs.puppetlabs.com/references/stable/function.html#fqdnrand

-- 
Russell Howe
rhowe@moonfruit.com

-- 
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.

Thanks

It end up a restart of nginx and everything is working! So pretty
happy
my next thing would be document what I did and make that available to
whoever needs it


On Jun 2, 4:28 am, Russell Howe <rh...@moonfruit.com>
wrote:
> > 3. SO my next issue is a function I wrote (random minute for
> > cron), this stopped working, So instead of executing the
> > function is takes is a value... Anyone ???
>
> I can''t help with the problem you''re having, but would
this do for your
> random minute?
>
>         # Random minute between 10 past and 10 to the hour
>         $random_minute = fqdn_rand(40) + 10
>         cron { "foo":
>                 command => "bar",
>                 minute  => $random_minute,
>                 ensure  => present,
>         }
>
> fqdn_rand is described
here:http://docs.puppetlabs.com/references/stable/function.html#fqdnrand
>
> --
> Russell Howe
> rh...@moonfruit.com
-- 
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.