[Puppet Users] cannot using LDAP nodes with site.pp together?

2013-06-10 Thread yorks
*FROM:*
http://projects.puppetlabs.com/projects/puppet/wiki/LDAP_Nodes
"""*
NOTE: You can use node entries in your manifests together with LDAP nodes.
External or LDAP nodes will be used before node entries. You cannot however
use LDAP nodes and external nodes together. You must use one of these two
types.*
"""

But,
in *PRO PUPPET* page 127:
"""
*Note The use of LDAP nodes overrides node definitions in your manifest
files and your ENC. If you use LDAP
node definitions, you cannot define nodes in your manifest files or in an
ENC.*
"""

this means the ldap nodes does not like ENC can merge the classes ?*
*

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Recommend a good tutorial on using Hiera as an ENC?

2013-06-10 Thread Paul Tötterman
Hi,
 

> Can anyone recommend a good tutorial on using Hiera as an ENC?


There's not that much to it. Maybe have a look at: 
http://blog.yo61.com/assigning-resources-to-nodes-with-hiera-in-puppet.html

Cheers,
Paul 

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: Recommend a good tutorial on using Hiera as an ENC?

2013-06-10 Thread Lab Yizhar
Hi,

Not much into this but did you this link ?

http://docs.puppetlabs.com/hiera/1/puppet.html

Regards,

Yizhar


On Mon, Jun 10, 2013 at 3:07 PM, Paul Tötterman wrote:

> Hi,
>
>
>> Can anyone recommend a good tutorial on using Hiera as an ENC?
>
>
> There's not that much to it. Maybe have a look at:
> http://blog.yo61.com/assigning-resources-to-nodes-with-hiera-in-puppet.html
>
> Cheers,
> Paul
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] ruby issue

2013-06-10 Thread Yizhar A.
Hi,
 
Finish my things on this issue for now as the last one in this chain 
talented enough to be asking for pay for answering this
 
I'll update when I'll figure it out else.  
 
Stay tuned,
 
Yizhar 
 
"Don't ask what the community can contribute to you ? ask what I can 
contribute the community"
On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:

> Dear Stuart,
>  
> Kind of my first steps into puppet on RHEL 6 and I wonder how you manage 
> to solve the rubygems issue.
>  
> Since I'm using RHEL 6.4 (.x86_64) in my test env. *with only puppetlabs 
> repo* I can't see from where I can get the rubygems missing package.
>  
> As you after wiki'd it :) can you give me a piece of advise in here or 
> attached your docs to help me through ?
>  
> Thanks,
>  
> --Yizhar
>  
>
> On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
>
>> Hey, good news. 
>>
>> All is well. 
>>
>> Ruby & related are good. Puppet too. And Red Hat. 
>>
>> Also, I've documented/wiki'd the Puppet Master + Client install with 
>> respect 
>> to bare metal to delivered system for all related aspects and 
>> transmitted, fully, 
>> disclosed entirely, to staff. 
>>
>> Next week, I will be tuning the configuration file on master and agents 
>> and 
>> writing many more puppet patterns plus training staff. 
>>
>> As it is their only hope! 
>>
>> --Stuart 
>>
>> P.S. The firm's personnel have had heart attacks, strokes and other major 
>> maladies amongst 
>> staff in the past year due to the LACK OF AUTOMATION!!! 
>>
>> Puppet is the Cure 
>>
>> Kick Chef and CF Engine's non-collective butts! 
>>
>>
>>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] White Paper: Migrating from Redhat satellite server to Puppet + Foreman

2013-06-10 Thread Keiran Sweet
Hi Everyone,
I've written a paper that captures the approach that we took when moving 
from Redhat Satellite for configuration and software management to Puppet 
and Foreman (alongside some other assorted technologies).

The paper contains a number of lessons learnt in the Ruby, Puppet, Foreman 
and Software deployment spaces that are likely to be useful for other 
administrators looking to move from Satellite or similar technologies.

It is important to note that whilst this approach to migrating from 
Satellite server was ideal for this particular business and environment, it 
is not suitable for everyone. It is also worth mentioning that a number of 
the Puppet techniques used in this document may no longer be considered 
best practice as the product evolves rapidly and features that are now 
available such as hiera did not exist at the time the environment was being 
designed and deployed. 

The document can be found here: 
- De-Orbiting Satellite (PDF) - http://goo.gl/0CAcy


I hope some of you find this of some use and if you have any questions, 
feedback, etc feel free to drop me a line.

Cheers,

K

Keiran (at) gmail.com || @keiran_s

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Puppetd with --noop and operation with puppetrun

2013-06-10 Thread jcbollinger


On Friday, June 7, 2013 11:54:24 AM UTC-5, Giovanni wrote:
>
>
> Instead of --noop, I think you want --no-client.  That will prevent the 
>> agent from automatically retrieving and applying catalogs, but when 
>> triggered via puppetrun it will apply whatever catalog it retrieves 
>> normally.
>>
>>  
> Thank you John for your suggestion. 
> With --no-client puppet stop to send reports to puppermaster. 
>


Do you mean it does not send reports when you manually trigger the client 
to perform a run, or that it does not send reports on a regular schedule?  
The latter is to be expected, since the whole point of --no-client is that 
the agent does not perform any automated runs in the first place (so 
there's nothing to report on).

On the other hand, if the agent is configured to send reports but does not 
do so when it actually performs a run, then I would account that a bug.  If 
that's the case then I recommend you file a ticket.

 

> Do I need to use a crontab for reports or I have to change some parameters 
> in puppet.conf?
>
>

If you want agent reports on a regular schedule then you need to perform 
runs on a regular schedule.  If you do not want these regularly-scheduled 
runs to change anything, then the agent processes performing them should 
use --noop.

If you want to be able to trigger runs via the 'puppetrun' mechanism (which 
is what I think foreman does) then you must have an agent running in daemon 
mode and listening for network requests to perform runs.  For those 
triggered runs to actually apply any changes, the agent processes 
performing them must *not* use --noop.

To the best of my knowledge and expectation, you cannot get both --noop and 
standard behavior from the same agent process, therefore you need separate 
processes if you want both types of behavior on the same node.  Your best 
bet in that case would be to perform the --noop runs via an external 
scheduler, such as cron (though there are other alternatives).  (So that's 
a long-winded "yes".)

Do note that if you try to trigger a manual run while an automated --noop 
run is in progress then the manual run will be blocked (but the agent 
should recover gracefully).


John

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] ruby issue

2013-06-10 Thread Stuart Cracraft
It's not that hard!

You can do it!!!

Also, you could buy some books on the subject!

On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:

> Hi,
>  
> Finish my things on this issue for now as the last one in this chain talented 
> enough to be asking for pay for answering this
>  
> I'll update when I'll figure it out else. 
>  
> Stay tuned,
>  
> Yizhar 
>  
> "Don't ask what the community can contribute to you ? ask what I can 
> contribute the community"
> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
> Dear Stuart,
>  
> Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to 
> solve the rubygems issue.
>  
> Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs repo 
> I can't see from where I can get the rubygems missing package.
>  
> As you after wiki'd it :) can you give me a piece of advise in here or 
> attached your docs to help me through ?
>  
> Thanks,
>  
> --Yizhar
>  
> 
> On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
> Hey, good news. 
> 
> All is well. 
> 
> Ruby & related are good. Puppet too. And Red Hat. 
> 
> Also, I've documented/wiki'd the Puppet Master + Client install with respect 
> to bare metal to delivered system for all related aspects and transmitted, 
> fully, 
> disclosed entirely, to staff. 
> 
> Next week, I will be tuning the configuration file on master and agents and 
> writing many more puppet patterns plus training staff. 
> 
> As it is their only hope! 
> 
> --Stuart 
> 
> P.S. The firm's personnel have had heart attacks, strokes and other major 
> maladies amongst 
> staff in the past year due to the LACK OF AUTOMATION!!! 
> 
> Puppet is the Cure 
> 
> Kick Chef and CF Engine's non-collective butts! 
> 
> 
> 
> -- 
> 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/ghDZsdkC3C0/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to 
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Does stdlib break the regsubst function?

2013-06-10 Thread c!w
Hi all,
We are currently using the regsubst function of Puppet to generate some 
information out of our hostnames (customer, environment, and so.). The 
manifest is running fine since months.

7:   $customer = regsubst($::fqdn, '(^[^-]*)-[^-]*.*', "\\1")
8:   $environment = regsubst($::fqdn, '^[^-]*-([^-]*).*', "\\1")
9:   $product = regsubst($::fqdn, '^[^-]*-[^-]*-([^\.1-9]*).*', "\\1")

Last week I discovered the stdlib module and added the module to my Puppet 
environment. After rolling out some changes to a test machine, I 
encountered some problems.

err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Function 'regsubst' does not return a value at 
/etc/puppet/environments/dev_foo/modules/auth/manifests/hosting.pp:7 on 
node unic-dev-bei.p.unic24.net
 
The regsubst function does not work like before. We did not upgrade our 
Puppet installation (version 2.7.18) or anything like that. What confuses 
me most, is that even running Puppet against our production environment 
produces the same error.
So the only change I did is adding the stdlib module. Could it be that this 
may broke the regsubst function?

Cheers,
Christian

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Puppet error reporting

2013-06-10 Thread jcbollinger


On Saturday, June 8, 2013 3:23:33 PM UTC-5, Francisco Reyes wrote:
>
> Trying to understand how puppet reports errors
> Example of why I am asking the question (on a test setup environment)
>
> Created a base-1 node
> Created 2 slave nodes that inherit from base-1
> Let's call those slave1 and slave2
>
> No errors. It all works.
>
> Created a base-2 node
> created a third slave that inherits from base-2. Let's call that slave3
>
> Get an error
> Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Duplicate declaration: Adduser[USERNAME] is already declared in file 
> /etc/puppet/manifests/nodes/base-1.pp at line 15; cannot redeclare on node 
> slave1
>
> What I am trying to figure out is why the error is reported in 
> base-1/slave-1... even though those 2 alone work until I introduce 
> base-2/slave3.
>


First guess: slave3.pp contains an adduser { : } declaration at 
top level (that is, not in a class, definition, or node block), or possibly 
a global variable declaration that influences the behavior of node 
'base1'.  Top-level declarations apply to all nodes, the file in which they 
appear notwithstanding.

Second guess: you accidentally made some change to the base1 or slave1 node 
declaration when you added base2 and slave3.

There are other possibilities.  If you post your init.pp and all manifests 
'import'ed into it, directly or indirectly, then I suspect we will be able 
to identify the problem pretty quickly.

 

>
> I would have expected the error to report say in slave-3.. that  the 
> adduser was already defined in base1-/slave-1.. but don't understand why it 
> refers to base1/slave1
>
>

Your error message indicates that the master has selected the 'slave1' node 
declaration, or possibly one inheriting from it, as the one best matching 
the client.  The master therefore attempts evaluate that node declaration, 
and the error occurs in the context of that evaluation.  If that node 
declaration was working before then you have somehow broken it.

 

> If I had come to this error without knowing I just added base-2 and slave3 
> I would be looking, possibly, at the wrong files.
>
> Is: puppet catalog find 
> the best way to "lint" after making changes?
>


Compiling catalogs is a reasonable way to test changes, but not an 
exhaustive one.  It cannot be exhaustive, because catalog compilation 
depends on node facts, and it is impossible to exhaustively enumerate all 
the possible values of all facts of even one node, let alone of all your 
nodes.  However, although I think you could use "puppet catalog" to do test 
compiles, my first inclination would be to use "puppet master --compile 
" instead.

Folks around here also tend to point to rspec for testing puppet 
manifests.  I guess you could go pretty much as far as you want with 
setting up rspec tests for your manifest set.  Again, however, you will 
only end up testing the scenarios you think to test.


John

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Using yum provider to install local RPM

2013-06-10 Thread jcbollinger


On Saturday, June 8, 2013 12:56:22 PM UTC-5, Ygor wrote:
>
> If the local install is not working, then just do it from your custom, 
> local repo
>
>

+1 for setting up a local repository.  This is FAR better than slinging 
around RPM files (semi-)manually or serving them directly from some shared 
filesystem.


John

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] ruby issue

2013-06-10 Thread Lab Yizhar
Thanks m8 for the mental support :)

As you already know, as an open source believer ,I'm kind of into it
and the solution is there, But I want to do it without RHN subscription
that will used on our production env.

Couple of humps and I'll be there this way or the offical other...

On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft  wrote:

> It's not that hard!
>
> You can do it!!!
>
> Also, you could buy some books on the subject!
>
> On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:
>
> Hi,
>
> Finish my things on this issue for now as the last one in this chain
> talented enough to be asking for pay for answering this
>
> I'll update when I'll figure it out else.
>
> Stay tuned,
>
> Yizhar
>
> "Don't ask what the community can contribute to you ? ask what I can
> contribute the community"
> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
>
>> Dear Stuart,
>>
>> Kind of my first steps into puppet on RHEL 6 and I wonder how you manage
>> to solve the rubygems issue.
>>
>> Since I'm using RHEL 6.4 (.x86_64) in my test env. *with only puppetlabs
>> repo* I can't see from where I can get the rubygems missing package.
>>
>> As you after wiki'd it :) can you give me a piece of advise in here or
>> attached your docs to help me through ?
>>
>> Thanks,
>>
>> --Yizhar
>>
>>
>> On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
>>
>>> Hey, good news.
>>>
>>> All is well.
>>>
>>> Ruby & related are good. Puppet too. And Red Hat.
>>>
>>> Also, I've documented/wiki'd the Puppet Master + Client install with
>>> respect
>>> to bare metal to delivered system for all related aspects and
>>> transmitted, fully,
>>> disclosed entirely, to staff.
>>>
>>> Next week, I will be tuning the configuration file on master and agents
>>> and
>>> writing many more puppet patterns plus training staff.
>>>
>>> As it is their only hope!
>>>
>>> --Stuart
>>>
>>> P.S. The firm's personnel have had heart attacks, strokes and other
>>> major maladies amongst
>>> staff in the past year due to the LACK OF AUTOMATION!!!
>>>
>>> Puppet is the Cure
>>>
>>> Kick Chef and CF Engine's non-collective butts!
>>>
>>>
>>>
> --
> 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/ghDZsdkC3C0/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Puppet Windows package not seeing DisplayName in Registry?

2013-06-10 Thread Kevin D
Reginal,

Does it work if you put the contents of the parameter 'name' into the title 
of the type:

package {'SQL Server 2008 R2 SP2 Common Files':
ensure  => installed,
provider=> windows,
source  => "C:\\puppet_temp\\${mssql_filename}",
install_options => ['/quiet', '/IAcceptSQLServerLicenseTerms', 
'/allinstances'],
require => Exec['run_mssql2008r2sp2_artifact_extract_ps1'],
}

>From http://docs.puppetlabs.com/windows/writing.html: 

> Identifying Packages 
>
> The title or name of the package must match the value of the 
> DisplayNameproperty in the registry, which is also the value displayed in 
> Add/Remove 
> Programs. Alternately, when a package name is not unique across versions 
> (e.g. VMWare Tools, or where there are 32- and 64-bit versions with the 
> same name), we provide the ability to specify the package’s PackageCode as 
> the package name. This is a GUID that’s unique across all MSI builds. For 
> instance:
>
Also, what are the results from this PowerShell command:

Get-WmiObject -class win32_product | Where-Object {$_.name.contains("SQL 
Server 2008")}

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] ruby issue

2013-06-10 Thread Stuart Cracraft
You are most welcome. 

On Jun 10, 2013, at 7:40 AM, Lab Yizhar  wrote:

> Thanks m8 for the mental support :)
>  
> As you already know, as an open source believer ,I'm kind of into it and the 
> solution is there, But I want to do it without RHN subscription that will 
> used on our production env.
>  
> Couple of humps and I'll be there this way or the offical other...
>  
> On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft  wrote:
>> It's not that hard!
>> 
>> You can do it!!!
>> 
>> Also, you could buy some books on the subject!
>> 
>> On Jun 10, 2013, at 5:51 AM, Yizhar A.  wrote:
>> 
>>> Hi,
>>>  
>>> Finish my things on this issue for now as the last one in this chain 
>>> talented enough to be asking for pay for answering this
>>>  
>>> I'll update when I'll figure it out else. 
>>>  
>>> Stay tuned,
>>>  
>>> Yizhar 
>>>  
>>> "Don't ask what the community can contribute to you ? ask what I can 
>>> contribute the community"
>>> On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
 Dear Stuart,
  
 Kind of my first steps into puppet on RHEL 6 and I wonder how you manage 
 to solve the rubygems issue.
  
 Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs 
 repo I can't see from where I can get the rubygems missing package.
  
 As you after wiki'd it :) can you give me a piece of advise in here or 
 attached your docs to help me through ?
  
 Thanks,
  
 --Yizhar
  
 
 On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
> Hey, good news. 
> 
> All is well. 
> 
> Ruby & related are good. Puppet too. And Red Hat. 
> 
> Also, I've documented/wiki'd the Puppet Master + Client install with 
> respect 
> to bare metal to delivered system for all related aspects and 
> transmitted, fully, 
> disclosed entirely, to staff. 
> 
> Next week, I will be tuning the configuration file on master and agents 
> and 
> writing many more puppet patterns plus training staff. 
> 
> As it is their only hope! 
> 
> --Stuart 
> 
> P.S. The firm's personnel have had heart attacks, strokes and other major 
> maladies amongst 
> staff in the past year due to the LACK OF AUTOMATION!!! 
> 
> Puppet is the Cure 
> 
> Kick Chef and CF Engine's non-collective butts!
>>> 
>>> -- 
>>> 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/ghDZsdkC3C0/unsubscribe?hl=en.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> puppet-users+unsubscr...@googlegroups.com.
>>> 
>>> To post to this group, send email to puppet-users@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> -- 
>> 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 post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> 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/ghDZsdkC3C0/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to 
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Packages for Ubuntu 13.04 (raring)

2013-06-10 Thread Andreas Ntaflos
It seems there are no packages available for Ubuntu 13.04. There is a 
puppetlabs-release package for raring, but except for that the directory 
http://apt.puppetlabs.com/pool/raring/main/p/ is empty.


I see no packages anywhere else for 13.04, only the ones in the official 
Ubuntu repos. This doesn't seem right, does it?


Andreas

--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Puppet Windows package not seeing DisplayName in Registry?

2013-06-10 Thread Josh Cooper
Hi Reginald,


On Fri, Jun 7, 2013 at 7:54 AM, Reginald Choudari <
adnanchowdhur...@gmail.com> wrote:

> Hello,
>
> I've got Package resource on my Windows machine that keeps creating itself
> even though the package has been properly installed.
>
> I've got the name attribute set to the DisplayName found in the Registry
> for the package.
>
> Every time the agent polls, I see in the Event Logs:
>
> /Stage[main]/Mssql_rtwo_sptwo/Package[mssql2008r2sp2_exec]/ensure: created
>
> This is what's in my manifest:
>
> package { 'mssql2008r2sp2_exec':
> ensure  => installed,
> name=> 'SQL Server 2008 R2 SP2 Common Files',
> provider=> windows,
> source  => "C:\\puppet_temp\\${mssql_filename}",
> install_options => ['/quiet', '/IAcceptSQLServerLicenseTerms',
> '/allinstances'],
> require => Exec['run_mssql2008r2sp2_artifact_extract_ps1'],
>   }
>
> I'm thinking there has got to be some weird bug/error with this ... Can
> anyone help?
>
> Thanks in advance
>
> --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

Try running `puppet resource package` and see if the package you tried to
installed is in the output, and that it's name matches exactly with the
`name` parameter above.

Josh

-- 
Josh Cooper
Developer, Puppet Labs

*Join us at PuppetConf 2013, August 22-23 in San Francisco - *
http://bit.ly/pupconf13*
**Register now and take advantage of the Early Bird discount - save 25%!*

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Force osfamily value

2013-06-10 Thread Stefan Schulte
On Fri, 7 Jun 2013 07:03:21 -0700 (PDT)
Charly Mathieu  wrote:

> Actually, it doesn't get better. Nice try ^^
> 

What version of facter are you using now? Can you please post the output
of

% facter facterversion operatingsystem osfamily
facterversion => 1.7.0
operatingsystem => Gentoo
osfamily => Gentoo

-Stefan

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Best way to add APC and change size of apc.shm_size

2013-06-10 Thread Josh sutton
Hello!! 
I am a new user to puppet and I need to use puppet to install apc and 
change the size of  apc.shm_size to 64.

I have found a module here: https://github.com/ridonkulous/puppet-apc
However, when I add the module in, it does not work. I get errors on the 
puppet code. 

Is there a way to just install the apc package normally and just use puppet 
code to change apc.shm_size?

Thanks in advance for your help




Josh

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Using yum provider to install local RPM

2013-06-10 Thread Paul Pham
Totally agree with both of you, and we had planned on setting up our custom 
repo in the near future. This was really just going to be an interim 
solution for us, and more generally an optional solution for 
adhoc/masterless puppet deployments. While I think having a custom repo is 
the elegant and scalable solution, I still think there are scenarios where 
it doesn't make sense to spin up a yum server (or deploy one on the 
localhost) just so I can install an rpm that's sitting in my home 
directory. Given that yum supports the ability to install from local, I'd 
still call this a puppet bug :)

Anyway, thanks for the input, sounds like the yum repo just became a higher 
priority.

P

On Monday, June 10, 2013 7:18:05 AM UTC-7, jcbollinger wrote:
>
>
>
> On Saturday, June 8, 2013 12:56:22 PM UTC-5, Ygor wrote:
>>
>> If the local install is not working, then just do it from your custom, 
>> local repo
>>
>>
>
> +1 for setting up a local repository.  This is FAR better than slinging 
> around RPM files (semi-)manually or serving them directly from some shared 
> filesystem.
>
>
> John
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Best way to add APC and change size of apc.shm_size

2013-06-10 Thread llowder


On Monday, June 10, 2013 12:43:12 PM UTC-5, Josh sutton wrote:
>
> Hello!! 
> I am a new user to puppet and I need to use puppet to install apc and 
> change the size of  apc.shm_size to 64.
>
> I have found a module here: https://github.com/ridonkulous/puppet-apc
> However, when I add the module in, it does not work. I get errors on the 
> puppet code. 
>
>
Can you show your code and the actual error?

 

> Is there a way to just install the apc package normally and just use 
> puppet code to change apc.shm_size?
>
>

Several, such as using a package resource and then using one of: file, 
file_line or augeas to edit the config file and change the value(s).
 

> Thanks in advance for your help
>
>
>
>
> Josh
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] any elegant way to iterate/map over data types?

2013-06-10 Thread Martin Langhoff
Sysadmins have the (reasonable?) expectation of installing more than
one ssh key.

Relevant bits from my current config follows:

class rl_users {
define ssh_user($uid, $gid, $password, $akey, $ensure=present) {
user{ $name :
ensure   => $ensure, managehome => true,
uid  => $uid,gid=> $gid,
password => $password,
groups   => ['wheel'],
require  => Group[$name],
}
group { $name :
ensure => $ensure,
gid=> $gid,
}
ssh_authorized_key { "${name}-akey":
ensure  => $ensure,
key => $akey,
type=> 'ssh-rsa',
user=> $name,
require => User[$name],
}
}

@ssh_user { 'foo':
uid=> 2004 , gid => 2004,
password => '$6$foo',
akey => 'B3xyz/VFwxhtYhw==',
}

# how can we support user bar?
@ssh_user { 'bar':
uid=> 2005 , gid => 2005,
password => '$6$bar',
akey => [ 'B3xyz/VFwxhtYhw==',
   ''Bz==' ]
}

Right now I have a fugly kludge in place to support a second "akey0" slot.



m
--
 martin.langh...@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] any elegant way to iterate/map over data types?

2013-06-10 Thread Rilindo Foster
Starting in Pupet 3.2, there is experimental support for iteration:

http://docs.puppetlabs.com/puppet/3/reference/lang_experimental_3_2.html#collection-manipulation-and-iteration


On Jun 10, 2013, at 3:41 PM, Martin Langhoff  wrote:

> Sysadmins have the (reasonable?) expectation of installing more than
> one ssh key.
> 
> Relevant bits from my current config follows:
> 
> class rl_users {
>define ssh_user($uid, $gid, $password, $akey, $ensure=present) {
>user{ $name :
>ensure   => $ensure, managehome => true,
>uid  => $uid,gid=> $gid,
>password => $password,
>groups   => ['wheel'],
>require  => Group[$name],
>}
>group { $name :
>ensure => $ensure,
>gid=> $gid,
>}
>ssh_authorized_key { "${name}-akey":
>ensure  => $ensure,
>key => $akey,
>type=> 'ssh-rsa',
>user=> $name,
>require => User[$name],
>}
> }
> 
> @ssh_user { 'foo':
>uid=> 2004 , gid => 2004,
>password => '$6$foo',
>akey => 'B3xyz/VFwxhtYhw==',
>}
> 
> # how can we support user bar?
> @ssh_user { 'bar':
>uid=> 2005 , gid => 2005,
>password => '$6$bar',
>akey => [ 'B3xyz/VFwxhtYhw==',
>   ''Bz==' ]
>}
> 
> Right now I have a fugly kludge in place to support a second "akey0" slot.
> 
> 
> 
> m
> --
> martin.langh...@gmail.com
> -  ask interesting questions
> - don't get distracted with shiny stuff  - working code first
> ~ http://docs.moodle.org/en/User:Martin_Langhoff
> 
> -- 
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Using yum provider to install local RPM

2013-06-10 Thread Brian Mathis
I've been playing with this a little (currently a work in progress).  The
idea is to create a package repository on the node itself, like in
/var/lib/local_packages, then create a yum repo config that points to the
local filesystem.  I'm using a defined type to add files to the local
repository, then kick off createrepo to update the repo metadata.

This is sort of a half-way solution between a total hack and "doing it
perfectly correct" with a central yum repo server.


❧ Brian Mathis


On Mon, Jun 10, 2013 at 3:09 PM, Paul Pham  wrote:

> Totally agree with both of you, and we had planned on setting up our
> custom repo in the near future. This was really just going to be an interim
> solution for us, and more generally an optional solution for
> adhoc/masterless puppet deployments. While I think having a custom repo is
> the elegant and scalable solution, I still think there are scenarios where
> it doesn't make sense to spin up a yum server (or deploy one on the
> localhost) just so I can install an rpm that's sitting in my home
> directory. Given that yum supports the ability to install from local, I'd
> still call this a puppet bug :)
>
> Anyway, thanks for the input, sounds like the yum repo just became a
> higher priority.
>
> P
>
>
> On Monday, June 10, 2013 7:18:05 AM UTC-7, jcbollinger wrote:
>>
>>
>>
>> On Saturday, June 8, 2013 12:56:22 PM UTC-5, Ygor wrote:
>>>
>>> If the local install is not working, then just do it from your custom,
>>> local repo
>>>
>>>
>>
>> +1 for setting up a local repository.  This is FAR better than slinging
>> around RPM files (semi-)manually or serving them directly from some shared
>> filesystem.
>>
>>
>> John
>>
>>  --
> 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 post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Validation failed: Host already has a report for time and kind

2013-06-10 Thread Luke Vidler


On Thursday, December 1, 2011 7:55:42 PM UTC+11, Chris Phillips wrote:
>
> Howdy,
>
> I've been getting this issue for about a month in dashboard. All our
> nodes poll on a cronjob between 00:00 and 01:00 daily, but one node
> has been getting this as a failed task for a while, with the yaml
> files building up on the server. Outside of this one cronjob, other
> puppet runs on the same node are running just fine. The backtrace on
> dashboard is:
>
> Importing report report-1009-84.yaml at 2011-11-22 00:33 GMTValidation
> failed: Host already has a report for time and kind
> Backtrace
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/validations.rb:1102:in
> `save_without_dirty!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in
> `save_without_transactions!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in
> `transaction'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in
> `transaction'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in
> `rollback_active_record_state!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
> /usr/share/puppet-dashboard/app/models/report.rb:113:in `create_from_yaml'
> /usr/share/puppet-dashboard/app/models/report.rb:86:in 
> `create_from_yaml_file'
>
>
> Any pointers appreciated.
>
> Thanks
>
> Chris
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Validation failed: Host already has a report for time and kind

2013-06-10 Thread Luke Vidler
Me Three, same versions and errors - Did you guys work out how to fix it 
yet?

On Thursday, December 1, 2011 7:55:42 PM UTC+11, Chris Phillips wrote:
>
> Howdy,
>
> I've been getting this issue for about a month in dashboard. All our
> nodes poll on a cronjob between 00:00 and 01:00 daily, but one node
> has been getting this as a failed task for a while, with the yaml
> files building up on the server. Outside of this one cronjob, other
> puppet runs on the same node are running just fine. The backtrace on
> dashboard is:
>
> Importing report report-1009-84.yaml at 2011-11-22 00:33 GMTValidation
> failed: Host already has a report for time and kind
> Backtrace
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/validations.rb:1102:in
> `save_without_dirty!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/dirty.rb:87:in
> `save_without_transactions!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in
> `transaction'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:182:in
> `transaction'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:208:in
> `rollback_active_record_state!'
>
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/transactions.rb:200:in
> `save!'
> /usr/share/puppet-dashboard/app/models/report.rb:113:in `create_from_yaml'
> /usr/share/puppet-dashboard/app/models/report.rb:86:in 
> `create_from_yaml_file'
>
>
> Any pointers appreciated.
>
> Thanks
>
> Chris
>
>

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.