Announce: Puppet Server 1.0.2 available!

[Jeff McCune]

We're pleased to announce that Puppet Server 1.0.2 is now available.

This release is the first bug fix version of Puppet Server 1.0. In accordance

with the [Semantic Versioning](http://semver.org) specification, this release

contains fixes for bugs reported against the 1.0 release.

Puppet Server 1.0.1 was not released, hence the move from 1.0.0 to 1.0.2.

In addition, the following issues have been resolved:

 * (SERVER-269) Puppet Server aggressively coerces request data to UTF-8.

 * (SERVER-262) `puppetserver gem env` does not work, useful for

   troubleshooting.

 * (SERVER-166) Set START_TIMEOUT to 120 seconds for sysv init scripts and

   systemd.

 * (SERVER-275) Fixed an issue where logback levels weren't changed unless you

   restarted Puppet Server.

 * (TK-130) Create a dynamic default for Jetty's max-threads setting.  Without

   this change puppet server may fail to start on a machine with a large number

   of CPU's.

See the complete release notes for details about these changes:

https://docs.puppetlabs.com/puppetserver/1.0/release_notes.html

For a list of all changes in this release, check out the JIRA page:

https://tickets.puppetlabs.com/browse/SERVER/fixforversion/12423/

[Oliver Schad]

Hi everybody,

does somebody already use the puppet server at all? Can you share your
experiences?

Best Regards
Oli

[Trevor Vaughan]

Hi Oli,

I've been using Puppet Server for a while now and it works a champ.

The only real issue is getting used to the amount of time that it takes to start.

Trevor

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150119154355.181e2b73%40dickeberta.automatic-server.com.

For more options, visit https://groups.google.com/d/optout.

--

Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvau...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

[Mike Hendon]

Triggering a refresh when you've changed manifests is also a pain.

[Tony Thayer]

I've been using it in testing and so far so good. It is pretty heavy on resources and it takes somewhere around five minutes to start on the VM I'm using, but it has been picking up changes to my manifests almost instantly. Previously I would have to manually restart the puppetmaster service almost half the time when I wanted a change to take effect.

[Cristian Falcas]

Is there any speed difference in compiling a catalog?

Best regards,
Cristian

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/puppet-users/2c192d8f-0270-48d5-b8eb-4da004485926%40googlegroups.com.

[Oliver Schad]

On Wed, 21 Jan 2015 05:40:27 -0800 (PST)
Mike Hendon <mi...@samknows.com> wrote:

> Triggering a refresh when you've changed manifests is also a pain.

Is a refresh on every change needed?

Best Regards
Oli

[Nick Howes]

It varies for me - some changes are noticed quite quickly, but others seem to need a refresh (or maybe I get impatient). Other times it notices them after a good few minutes. It would be nice if it could hook into libnotify and other similar OS systems, or at least if I could find some documentation on what the rules are on manifest caching, so that I can add something to my update hook. I've read hints elsewhere that touching manifests/site.pp is enough. It starts up 5 JRuby instances so I wonder if it depends which instance handles the request.

Other than that it's working well and does seem better at noticing changes than puppetmaster on Passenger. 

[Eric Sorenson]

On Wednesday, January 21, 2015 at 5:40:27 AM UTC-8, Mike Hendon wrote:

Triggering a refresh when you've changed manifests is also a pain.

Mike do you mean using the environment refresh API is a pain? 

https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#new-feature-admin-api-for-refreshing-environments

Or are you having to do a full restart?

We're looking at adding more CLI convenience around these APIs so if it's the former, this is good info to have. 

[Trevor Vaughan]

I've been able to do everything from the APIs thus far and, yes, having a 'puppet master reload' and 'puppet master environment-flush' (or something) would be nice.

Also, why not allow the local PM to run the API commands by default? It would save a few steps of munging config files.

Thanks,

Trevor

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a3f6d2bd-fe83-4c7c-928c-4c7e3b0fa7a0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Kevin Corcoran]

On Sun, Jan 25, 2015 at 5:07 PM, Trevor Vaughan <tvau...@onyxpoint.com> wrote:

I've been able to do everything from the APIs thus far and, yes, having a 'puppet master reload' and 'puppet master environment-flush' (or something) would be nice.

Trevor - I just created https://tickets.puppetlabs.com/browse/SERVER-349.  On the issue of config reloading, we've got that on our radar as well (I know it's one of Eric's "favorite" issues).

[Trevor Vaughan]

Nice! Thanks.

Trevor

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF-bMBeX_v8xF-HuB0i0gNSUdJjp4ekr6TZTyOeCXPCjftj7EQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.