WebRick role

[bernard...@morpho.com]

Hy,

I am just starting with Puppet, and install a test bed with community
version, one master and 8 clients.

I wonder if WebRick is used only of master-agents communication or
does WebRick provides a web application usable by human with a web
browser ?

Thank's for any helps

Bernard

[Sam Kottler]

Hi and welcome!

The puppet master itself is a simple rack application so webrick is the default rack server. You can use any application server that is Rack-compatible; Apache w/ Passenger is also a very common configuration.

There is not a web interface by default, but there are a number of tools that provide a web UI for managing your Puppet infrastructure, like Foreman [1] and Puppet Enterprise [2].

Hope that helps!

1. http://theforeman.org

2. http://puppetlabs.com/puppet/puppet-enterprise/

Bernard

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

[GRANIER Bernard (MORPHO)]

Hi,

 

Thanks for your answer, in the same time, I installed puppet dashboard.

 

Now I will try my first deployment test and I will see J

 

Cordialement,

 

Bernard Granier

CE Plateforme Système

bernard...@morpho.com

01 58 11 32 51

#
" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#

[Garrett Honeycutt]

On 1/7/13 10:48 AM, GRANIER Bernard (MORPHO) wrote:
> Hi,
>
> Thanks for your answer, in the same time, I installed puppet dashboard.
>
>
> Now I will try my first deployment test and I will see J
>
>
> Cordialement,
>
> Bernard Granier
>

Webrick is useful for doing a demo and learning about Puppet with a
couple of nodes. It is not at all meant to scale and if you attempt to
run your eight agents, you are likely to have performance issues. If
this is a production level deployment, you should look at Apache with
Passenger.

Regards,
-g

--
Garrett Honeycutt

206.414.8658
http://puppetlabs.com

[jcbollinger]

On Monday, January 7, 2013 11:44:00 AM UTC-6, Garrett Honeycutt wrote:

Webrick is useful for doing a demo and learning about Puppet with a
couple of nodes. It is not at all meant to scale and if you attempt to
run your eight agents, you are likely to have performance issues. If
this is a production level deployment, you should look at Apache with
Passenger.

Only eight?  I have webrick reliably serving in excess of 50 clients, all updating at the default rate of twice per hour.

Webrick's biggest problem is not performance per se, it's lack of multiple threads.  Apache / passenger does not make Puppet faster; it just runs more instances and handles contemporaneous requests more gracefully.  Thus it improves throughput when there are enough system resources behind it, but that's not exactly the same thing as performance.

I think webrick works well for me because my manifests change infrequently and are fairly quick to compile (even though the master is not particularly well-provisioned).  In that context, the master can serve catalog requests quickly enough that clients rarely time out, despite webrick's single-threaded nature.

My recommendation for a new Puppeteer would certainly be to start out with webrick, since it works out of the box with no additional software or configuration.  Switch to Passenger or something more capable only when webrick becomes inadequate.  When that will be depends a lot on the manifests involved, the hardware underneath, the number of clients, and the request frequency.


John

[Nikola Petrov]

On Tue, Jan 08, 2013 at 06:47:55AM -0800, jcbollinger wrote:
>
>
> On Monday, January 7, 2013 11:44:00 AM UTC-6, Garrett Honeycutt wrote:
> >
> >
> > Webrick is useful for doing a demo and learning about Puppet with a
> > couple of nodes. It is not at all meant to scale and if you attempt to
> > run your eight agents, you are likely to have performance issues. If
> > this is a production level deployment, you should look at Apache with
> > Passenger.
> >
> >
> Only eight? I have webrick reliably serving in excess of 50 clients, all
> updating at the default rate of twice per hour.
>

> Webrick's biggest problem is not performance *per se*, it's lack of

> multiple threads. Apache / passenger does not make Puppet faster; it just
> runs more instances and handles contemporaneous requests more gracefully.

> Thus it improves *throughput* when there are enough system resources behind

> it, but that's not exactly the same thing as performance.
>
> I think webrick works well for me because my manifests change infrequently
> and are fairly quick to compile (even though the master is not particularly
> well-provisioned). In that context, the master can serve catalog requests
> quickly enough that clients rarely time out, despite webrick's
> single-threaded nature.

All true.

>
> My recommendation for a new Puppeteer would certainly be to start out with
> webrick, since it works out of the box with no additional software or
> configuration. Switch to Passenger or something more capable only when
> webrick becomes inadequate. When that will be depends a lot on the
> manifests involved, the hardware underneath, the number of clients, and the
> request frequency.
>

Passenger works out of the box too here. I just install it from the
provided packages. It is a no brainer

--
Nikola