Re: [Puppet Users] Mcollective plugin packages in the PC1 repository

[Francois Lafont]

Hi,

On 24/09/2015 04:39, Michael Stahnke wrote:

> Short answer, yes there are plans, but we haven't scheduled the work yet.

Ok. Cool.

> We know it's painful right now, and I'm sorry for that. I'll see we can get
> that slotted in soon.

Absolutely no problem. I just wanted to know what it expected in a long-term
about these plugins in PC1 collection, that's all. In any case my message was
a complaint (plugins are not complicated to install "by hand"). ;)

Thanks for the answer and for all this work.
Bye.

François Lafont

-- 
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/5603CEE0.9050705%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Forge ACL Module 1.1.1 on Windows 7 x64 SP1

[jmp242]

So per my previous post, I'm now trying to replace the file POSIX 
permissions with ACLs. I'm apparently missing something though. I want to 
replicate what I had before in the new supported method, i.e.:

owner   => 'SYSTEM',
group   => 'Administrators',
mode=> '0775',


So I tried doing:
acl { 'chocolatey.config':
target  => 'C:/ProgramData/chocolatey/config/chocolatey.config',
purge   => false,
permissions => [
  {
identity=> 'SYSTEM',
rights  => [
  'full'],
perm_type   => 'allow',
child_types => 'all',
affects => 'all'
  }
  ,
  {
identity=> 'Administrators',
rights  => [
  'full'],
perm_type   => 'allow',
child_types => 'all',
affects => 'all'
  }
  ,
  {
identity=> 'Users',
rights  => [
  'read',
  'execute'],
perm_type   => 'allow',
child_types => 'all',
affects => 'all'
  }
  ],
owner   => 'SYSTEM', # Creator_Owner specific, doesn't manage 
unless specified
group   => 'Administrators', # Creator_Group specific, doesn't 
manage unless specified
inherit_parent_permissions => true,
require => File['chocolatey.config'],
  }


As I understand the documentation, this seems to map, mind you - being far 
more verbose and complicated - to the original permissions. However, I get 
errors:
Could not evaluate: The parameter is incorrect. - ReportEvent

This doesn't really help me figure out what I did wrong here...

-- 
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/a49f14bc-6804-4ba8-a033-752a6da2a9cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] puppet-4-able agent for RHEL7 on ppc64?

[Marc Haber]

Hi,

I am looking for a puppet agent rpm that can run against a puppet 4
server (and can use its features) for RHEL 7 on ppc 64. On
yum.puppetlabs.com, I can only find binaries for agent 1.2.4 (latest
version) for x86_64 and i386, and the corresponding SRPM directories
do only have puppetdb and puppetserver src.rpms.

What can I do to be able to use puppet 4 with my ppc64 LPAR systems?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

-- 
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/20150924125447.GI23456%40torres.zugschlus.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Status of activemq

[Michael Stahnke]

On Tue, Sep 22, 2015 at 12:40 PM, Kenton Brede  wrote:

> I'm wondering the same thing here.
>
> Sorry, missed this thread the first time.

> Kent
>
> On Wed, Jul 22, 2015 at 6:28 PM, Ellison Marks  wrote:
>
>> So, I'm going through the dance of upgrading to puppet 4.2 from 3.8 on
>> CentOS 6, and I've run into a few things that brought up some questions.
>> During the install, I ran into a number of collisions and incompatibilities
>> between pc1 and the existing packages, but pertinent to this issue, I had
>> to uninstall the old puppetlabs-release package in favor of the pc1 release
>> package, as they were both claiming ownership of the signing key. It's
>> mostly worked out, however, now I'm at the point where I'm working on
>> migrating mcollective. Aside from some hiccups with involving
>> incompatibilities with the new facter, I've got things talking to each
>> other. Now though, I'm wondering about activemq. I've still got the version
>> I had installed from the puppetlabs-deps repo, and it's working, I'm just
>> not sure where I'm supposed to
>>
>
> We haven't done much with activemq or moved it into PC1. Let me look into
to posting it there.

-- 
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/CAMto7L%2Bgt_tLLsiaTASXDK_7%2Bqx9JFEUr88qK9oxmxkotyCbmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Puppet Enterprise 2015.2.1 is available

[Rob Braden]

Dear Puppet Enterprise Users,

Puppet Enterprise 2015.2.1 is now available.

Puppet Enterprise 2015.2.1 is a bug-fix and security release of Puppet
Enterprise. All users of Puppet Enterprise are encouraged to upgrade when
possible to Puppet Enterprise 2015.2.1.

For information on the fixes in this release, please see
https://puppetlabs.com/security and https://docs.puppetlabs.com/pe/2015.2
/release_notes.html.

As a current Puppet Enterprise user, you can upgrade to this new version as
part of your annual subscription. If upgrading, it is recommended to
upgrade your master and console servers first.

As always, we want to hear about your experiences with Puppet Enterprise.
If you have any questions about upgrading, be sure to get in touch with
Puppet Labs Support.

-- 
Rob Braden
Puppet Labs Release Team

*PuppetConf 2015 ** is right around the
corner! Join us October 5-9 in Portland, OR. **Register now
**.*

-- 
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/CANrW%3D%3D3s-SyT1gSibnO3avn4a-aoV4n5AhEXzt_cdv2MX9q7UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Can we lookup hiera data object providing the file name

[Henrik Lindberg]

On 2015-24-09 7:13, Malintha Adikari wrote:

Hi Corey,

Thank you very much for your answer. May be this is what I am looking
for. I have few doubts about the way using this solution.

hiera('nodes', 'default_value', 'nodes/host1234')

*'nodes/host1234' - *Is this a yaml file name ? I know the yaml file
name in which hiera should search data. I want to provide that file name
in the looking up function.



That will not work. If you are using hiera, the configuration of which 
yaml files that it loads is controlled by the configuration in hiera.yaml.


- henrik




On Wednesday, September 23, 2015 at 9:29:27 PM UTC+5:30, Corey Osman wrote:

You should be able to just use the normal hiera syntax.  example:
hiera('nodes', 'default_value', 'nodes/host1234')

Documented here:

https://github.com/puppetlabs/puppet/blob/master/lib/puppet/functions/hiera.rb



Also, its bad practice to lookup hiera from within a template. Put
the value in a puppet variable and then just use the variable in the
template.
This way the next person will not have to troubleshoot your template.

Corey
On Tuesday, September 22, 2015 at 11:48:33 PM UTC-7, Malintha
Adikari wrote:

I am using hiera lookup as follows in my puppet template

|
<%-nodeinfo =scope.function_hiera(['nodes'])-%>
|

I have provided the .yaml file which includes above 'nodes'
object in my hiera.yaml file ( that is inside nodesfile.yaml
file which is dynamically loaded as follows)

|
---
:backends:
   - yaml
:yaml:
   :datadir: /etc/puppet/hieradata
:hierarchy:
   - "%{::nodes_file}
|

I have want to load another data object into my puppet template
but the problem is that data object is in a .yaml file which is
not registered in my hiera.yaml file. I cannot register that
file in my hiera.yaml.

Is there anyway to load data object providing the file along
with the lookup method. I do know the .yaml file name that
object is in ?

--
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/79f39a77-cc92-45b9-86c2-68c79b4fec34%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/mu1tpc%24act%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 4, rspec, and stages

[Sean McKinley]

We recently upgraded to PE2015, and as such have upgraded our local puppet 
gems to match (4.2.2). Unfortunately a few of our specs that were 
previously passing are now failing, mostly in regards to stages:

"Evaluation Error: Error while evaluating a Function Call, Could not find 
stage first specified by Class[Ipa::client]"

The class is fairly simple:

class ipa::client(
  $principal = 'host_manager',
  $password = 'obscured_because_security'
  $stage = first,
 ){

Has anyone run into this yet by chance?

-- 
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/02ebfaec-04b8-4f5c-89f8-6f81a9827f2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet 4, rspec, and stages

[Russell Cecala]

You might need a comma after 'obscured_because_security' :)

On Thu, Sep 24, 2015 at 3:40 PM, Sean McKinley 
wrote:

> We recently upgraded to PE2015, and as such have upgraded our local puppet
> gems to match (4.2.2). Unfortunately a few of our specs that were
> previously passing are now failing, mostly in regards to stages:
>
> "Evaluation Error: Error while evaluating a Function Call, Could not find
> stage first specified by Class[Ipa::client]"
>
> The class is fairly simple:
>
> class ipa::client(
>   $principal = 'host_manager',
>   $password = 'obscured_because_security'
>   $stage = first,
>  ){
>
> Has anyone run into this yet by chance?
>
> --
> 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/02ebfaec-04b8-4f5c-89f8-6f81a9827f2b%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/CAHu%2B3OyYfe%2BJnfEC2Cne6__caPCpuxv-kSYGuA7QFKfAGyb_CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.