[Puppet Users] Announce: puppet-agent 1.9.1 released

[Geoff Nichols]

Hi All,

Puppet Agent 1.9.1 is now available. This release includes Puppet 4.9.2,
which fixes several bugs in Hiera 5.

Please try this new release and let us know what you think!

For a complete list of fixes in Puppet 4.9.2, please see the release notes
at https://docs.puppet.com/puppet/4.9/release_notes.html.

To install or upgrade Puppet Agent, follow the getting started directions:
http://docs.puppetlabs.com/puppet/latest/reference/index.html

For information on upcoming platform end-of-life (EOL) for Puppet Agent,
please see our Platform Support Lifecycle page:
https://puppet.com/content/platform-support-lifecycle
-- 
Geoff Nichols
Puppet Agent and Platform Team

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADjnYBw4ZWd3kseuqUZ7V1UzX4p9tHByByCUwGc3AzybyY8-Tg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera 5 calling_class

[Henrik Lindberg]

On 10/02/17 14:10, Ben Hines wrote:

Okay, thanks! From reading changelogs in git it looked like it was
intended to be supported.


It is supported when using hiera.yaml version 3 as we must keep that 
backwards compatible.



It might be worth mentioning in the release notes.


yes, will make sure this gets to the docs folks.


Anyway in my case i can work around with module data.



Excellent!

- henrik


thanks!

-Ben

On Fri, Feb 10, 2017 at 1:39 PM, Henrik Lindberg
> wrote:

On 08/02/17 17:55, Ben Hines wrote:

Perhaps this is just a bug, but does %{calling_class} function with
Hiera 5? I haven't been able to get it to function.  Perhaps it
has a
new syntax?


It is deliberately not supported in the hiera 5 format.

- henrik

Notice it's blank:

==> test:   Hierarchy entry "calling_class"
==> test: Path
"/tmp/vagrant-puppet/environments/myenv/data/classes/.yaml"
==> test:   Original path: "classes/%{calling_class}.yaml"
==> test:   Path not found


hiera.yaml looks like: (per the 'prerelease documention' :)


version: 5
hierarchy:
  - name: "calling_class"
path: classes/%{calling_class}.yaml

defaults:
  datadir: data
  data_hash: yaml_data


-Ben

--
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+unsubscr...@googlegroups.com

>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/2083ae8f-5437-43c3-8c40-075c3b7abf57%40googlegroups.com



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



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/


--
You received this message because you are subscribed to a topic in
the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/puppet-users/UYvmlCaOqLc/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/8616db10-6e15-f71d-a999-c663d8d2bfe3%40puppet.com

.

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


--
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+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CABGPr5m-s3MvwgrY-4yih4VSpMqnNq%3DcWnvW6EzJc2SRF%2BkGqw%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/73ce8f7e-173d-dbeb-3b22-9c88ad810736%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] hiera_hash, lookup, Hiera 5

[Henrik Lindberg]

On 10/02/17 13:32, Daniel Urist wrote:

I have been using ":merge_behavior: deeper" in my hiera.yaml file to
turn on deep hash merges with hiera_hash, but now this appears to be broken.



Puppet 4.9.0/4.9.1 went out with a number of issues related to hiera.
All reported problems (including breaking deeper merges) have now been 
fixed and there is a 4.9.2 release any minute now...


Please retry on Puppet 4.9.2

- henrik


The latest docs
(at https://docs.puppet.com/puppet/4.9/lookup_quick.html) suggest using
the lookup() function, but then state this:

IMPORTANT: These docs are outdated, and replacement pages are coming
soon. Puppet lookup is now called Hiera 5, and it works differently
from what’s described on this page.


So, how do I get hiera hash merges right now? I'm on debian jessie with
the following versions:

puppetserver  2.7.2-1puppetlabs1
puppet-agent 1.9.1-1jessie

I also have clients running the puppet agent from jessie backports,
version 3.8.5-2~bpo8+1, but I'm assuming this problem is on the server side.


--
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+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEo6%3DKb8SRWC0217ZSb2J2jbpmj8VrJ1sa4As5WBRv3wDQUcPQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/761f998b-6910-61d8-6dac-0c7e6dbc3119%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: No nodes reported in Dashboard 2.0.0

[James Pryor]

Hello Dimitri,
Hopefully someone on this list can help you with Puppet Dashboard,
unfortunately I am not that person.

That said, today if I were to choose a Web UI for reporting or as ENC, I
personally would not use puppet dashboard.  I would like to be proven
wrong, but based on a quick search of this list's archives, it appears that
many people that  have moved away from it and on to other Web UIs. Looking
at it's github repo's [1] activity, it looks like there are long standing
pull requests and open issues with it. In fact the book's author has two
open PRs from about 18 months ago. It makes me sad, and I wish that Puppet
Dashboard had a lively & responsive community of users/contributors because
I was at PuppetConf 2013 and sat in on the presentation from @sodabrew
where he expressed his intent to keep it going.

You might be better served by using the alternatives as explained in the
book, perhaps PuppetDB together with puppetboard[2].

[1] https://github.com/sodabrew/puppet-dashboard
[2] https://github.com/voxpupuli/puppetboard

As an aside, I like many parts of the book. The author has done good job of
the difficult task of distilling the vibrant puppet ecosystem and tooling
into a comprehensive book. However, I find it a bit odd in that a book
about learning puppet 4 that says: "PuppetDB is a full-featured product
worthy of its own book. At this time, the best available documentation can
be found at 'PuppetDB Overview' on the Puppet docs site." - p109; basically
glosses over PuppetDB when PuppetDB brings a whole lot to the table.

Regards,
James





On Fri, Feb 10, 2017 at 5:21 PM, Dimitri Yioulos  wrote:

> A bit more information:
>
> - I used instructions from O'Reilly *Learning Puppet 4*
> -  I see the reports from nodes in /opt/puppetlabs/server/
> data/puppetserver/reports.
> -  If I click on the "Nodes" tab in Dashboard, I get "Forbidden You don't
> have permission to access /nodes on this server."
> -  I used dashboard.conf (as provided with *Learning Puppet 4*) for
> Apache.  Of course, I did some tweaking.  But, here's the part that may be
> the bug-a-boo:
>
>   Listen 3000
> 
>   ServerName   dashboard.example.com
>   DocumentRoot /opt/puppet-dashboard/public/  <--- there is no nodes
> subdirectory here
>   RailsBaseURI /
>
>
> On Friday, February 10, 2017 at 3:06:23 PM UTC-5, Dimitri Yioulos wrote:
>>
>> Hi, All.
>>
>> Previously, I had a Puppet server running version 3.x, and Puppet
>> Dashboard 1.2.  Worked a treat.  Now, I created a new Puppet server version
>> 4.  I got that all working fine.  I also installed Dashboard 2.0.0.  While
>> I can see the Dashboard, there are no nodes reported.  Has anyone else
>> installed Puppet Dashboard 2.0.0 to work with Puppet 4 that might give me
>> some help?
>>
>> Thanks.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/b975e1bf-a063-4055-b021-236ed8511857%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAOsPUcigGRvGQfSiPpexMaoQsJVjrJaOzevBnH8AO8tCK7LPaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: No nodes reported in Dashboard 2.0.0

[Dimitri Yioulos]

A bit more information:

- I used instructions from O'Reilly *Learning Puppet 4*
-  I see the reports from nodes 
in /opt/puppetlabs/server/data/puppetserver/reports.
-  If I click on the "Nodes" tab in Dashboard, I get "Forbidden You don't 
have permission to access /nodes on this server."
-  I used dashboard.conf (as provided with *Learning Puppet 4*) for Apache. 
 Of course, I did some tweaking.  But, here's the part that may be the 
bug-a-boo:

  Listen 3000

  ServerName   dashboard.example.com
  DocumentRoot /opt/puppet-dashboard/public/  <--- there is no nodes 
subdirectory here
  RailsBaseURI /


On Friday, February 10, 2017 at 3:06:23 PM UTC-5, Dimitri Yioulos wrote:
>
> Hi, All.
>
> Previously, I had a Puppet server running version 3.x, and Puppet 
> Dashboard 1.2.  Worked a treat.  Now, I created a new Puppet server version 
> 4.  I got that all working fine.  I also installed Dashboard 2.0.0.  While 
> I can see the Dashboard, there are no nodes reported.  Has anyone else 
> installed Puppet Dashboard 2.0.0 to work with Puppet 4 that might give me 
> some help?
>
> Thanks.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b975e1bf-a063-4055-b021-236ed8511857%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera 5 calling_class

[Ben Hines]

Okay, thanks! From reading changelogs in git it looked like it was intended
to be supported. It might be worth mentioning in the release notes.

Anyway in my case i can work around with module data.

thanks!

-Ben

On Fri, Feb 10, 2017 at 1:39 PM, Henrik Lindberg  wrote:

> On 08/02/17 17:55, Ben Hines wrote:
>
>> Perhaps this is just a bug, but does %{calling_class} function with
>> Hiera 5? I haven't been able to get it to function.  Perhaps it has a
>> new syntax?
>>
>>
> It is deliberately not supported in the hiera 5 format.
>
> - henrik
>
> Notice it's blank:
>>
>> ==> test:   Hierarchy entry "calling_class"
>> ==> test: Path
>> "/tmp/vagrant-puppet/environments/myenv/data/classes/.yaml"
>> ==> test:   Original path: "classes/%{calling_class}.yaml"
>> ==> test:   Path not found
>>
>>
>> hiera.yaml looks like: (per the 'prerelease documention' :)
>>
>>
>> version: 5
>> hierarchy:
>>   - name: "calling_class"
>> path: classes/%{calling_class}.yaml
>>
>> defaults:
>>   datadir: data
>>   data_hash: yaml_data
>>
>>
>> -Ben
>>
>> --
>> 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+unsubscr...@googlegroups.com
>> .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/2083ae8f-5437
>> -43c3-8c40-075c3b7abf57%40googlegroups.com
>> > 7-43c3-8c40-075c3b7abf57%40googlegroups.com?utm_medium=email
>> _source=footer>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/puppet-users/UYvmlCaOqLc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/puppet-users/8616db10-6e15-f71d-a999-c663d8d2bfe3%40puppet.com.
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CABGPr5m-s3MvwgrY-4yih4VSpMqnNq%3DcWnvW6EzJc2SRF%2BkGqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera 5 calling_class

[Henrik Lindberg]

On 08/02/17 17:55, Ben Hines wrote:

Perhaps this is just a bug, but does %{calling_class} function with
Hiera 5? I haven't been able to get it to function.  Perhaps it has a
new syntax?



It is deliberately not supported in the hiera 5 format.

- henrik


Notice it's blank:

==> test:   Hierarchy entry "calling_class"
==> test: Path
"/tmp/vagrant-puppet/environments/myenv/data/classes/.yaml"
==> test:   Original path: "classes/%{calling_class}.yaml"
==> test:   Path not found


hiera.yaml looks like: (per the 'prerelease documention' :)


version: 5
hierarchy:
  - name: "calling_class"
path: classes/%{calling_class}.yaml

defaults:
  datadir: data
  data_hash: yaml_data


-Ben

--
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+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2083ae8f-5437-43c3-8c40-075c3b7abf57%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.



--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8616db10-6e15-f71d-a999-c663d8d2bfe3%40puppet.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] hiera_hash, lookup, Hiera 5

[Daniel Urist]

I have been using ":merge_behavior: deeper" in my hiera.yaml file to turn
on deep hash merges with hiera_hash, but now this appears to be broken.

The latest docs (at https://docs.puppet.com/puppet/4.9/lookup_quick.html)
suggest using the lookup() function, but then state this:

IMPORTANT: These docs are outdated, and replacement pages are coming soon.
> Puppet lookup is now called Hiera 5, and it works differently from what’s
> described on this page.


So, how do I get hiera hash merges right now? I'm on debian jessie with the
following versions:

puppetserver  2.7.2-1puppetlabs1
puppet-agent 1.9.1-1jessie

I also have clients running the puppet agent from jessie backports, version
3.8.5-2~bpo8+1, but I'm assuming this problem is on the server side.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAEo6%3DKb8SRWC0217ZSb2J2jbpmj8VrJ1sa4As5WBRv3wDQUcPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] No nodes reported in Dashboard 2.0.0

[Dimitri Yioulos]

Hi, All.

Previously, I had a Puppet server running version 3.x, and Puppet Dashboard 
1.2.  Worked a treat.  Now, I created a new Puppet server version 4.  I got 
that all working fine.  I also installed Dashboard 2.0.0.  While I can see 
the Dashboard, there are no nodes reported.  Has anyone else installed 
Puppet Dashboard 2.0.0 to work with Puppet 4 that might give me some help?

Thanks.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1cb9b73f-880a-466a-b247-862bce933ad8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Can PE ENC variables be used in hiera hierarchy definition?

[J.T. Conklin]

I'm one of the admins of a site running PE 2016.4.2.  Over the last
year, we've migrated from our own puppet module organization to the
roles and profiles pattern.

Currently, we're setting the parameters for modules that are shared
by more than one role/profile on a per-node basis. This has a draw-
back that we have many node *.yaml files for roles with many hosts;
and we must remember to add addiitonal node *.yaml files whenever
new hosts are assigned to the role.

It would be convienent if we could have role-based *.yaml files. If
we create a 'role' variable in the PE ENC for each classification
group, can that be used in the hierarchy definition in hiera.yaml?
If so, what would happen for unclassified nodes where the new 'role'
variable is not defined?

Thanks,

--jtc

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/87d1ep7vam.fsf%40wopr.acorntoolworks.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] rabbitMQ puppet module - deploy ssl certificate

[Andrew Grimberg]

On 02/10/2017 03:26 AM, Romgo wrote:
> Hello,
> 
> I am using the rabbitmq puppet module from
> https://forge.puppet.com/puppetlabs/rabbitmq/readme
> 
> I want to enable the ssl configuration for the management port.
> So the declaration is like this :
> 
>   ssl_key=> '/etc/rabbitmq/ssl/key.pem',
>   ssl_cert=> '/etc/rabbitmq/ssl/cert.pem',
>   ssl_ca   => '/etc/rabbitmq/ssl/ca.pem',
> 
> But I want this module to deploy those file ca.pem cert.pem and key.pem
> The code doesn't seems to be able to do this.
> 
> I though that modifying the code of puppet modules wasn't a good idea
> (for upgrade).
> How do you deal with that kind of issues ?

Greetings Romgo,

You're correct that modifying the code of the module isn't the proper
way to get the certificates to the systems. This is something that
should be part of your profile definition, which is part of _your_
business logic, that is in turn what is then calling the rabbitmq module.

-Andy-

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8ee72be2-2c2a-89d8-a5b7-81d147750002%40bardicgrove.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[Puppet Users] rabbitMQ puppet module - deploy ssl certificate

[Romgo]

Hello,

I am using the rabbitmq puppet module from 
https://forge.puppet.com/puppetlabs/rabbitmq/readme

I want to enable the ssl configuration for the management port. 
So the declaration is like this :

  ssl_key=> '/etc/rabbitmq/ssl/key.pem',
  ssl_cert=> '/etc/rabbitmq/ssl/cert.pem', 
  ssl_ca   => '/etc/rabbitmq/ssl/ca.pem',

But I want this module to deploy those file ca.pem cert.pem and key.pem
The code doesn't seems to be able to do this.

I though that modifying the code of puppet modules wasn't a good idea (for 
upgrade).
How do you deal with that kind of issues ?

Regards

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/2b0db0c0-6e47-4a71-b64e-dbd86ae8663d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.