Re: [Puppet Users] Beaker + RHEL 6

[Eric Shamow]

Tim,

Not based on experience specifically with beaker but have you tried using SCLs 
to install ruby 1.9.3?

-Eric

-- 
Eric Shamow
Sent with Airmail

On October 3, 2014 at 7:53:09 AM, Tim Skirvin (tskir...@fnal.gov) wrote:

If using the Beaker framework is going to be a core part of  
determining that a puppet module has been "tested", I figure I'd better be  
able to use Beaker. And so far, this seems tricky, at least on my RHEL 6  
systems.  

Perhaps Puppet Labs should provide RPMs?  

Failing that, does anybody have any advice as to getting Beaker  
working on a RHEL 6 system? I can't even get it installed, due to  
nokogiri requiring a more recent ruby than is provided by RedHat. A  
puppet module would be nice, but I don't see anything on the Forge.  

- Tim Skirvin (tskir...@fnal.gov)  
--  
HPC Systems Administrator / Developer http://www.linkedin.com/in/tskirvin  
USCMS-T1 Collaboration Fermilab Scientific Computing  

-- 
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/etPan.542ef267.140e0f76.160a6%40rassilon.local.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Git Repo Strategy

[Eric Shamow]

I highly recommend going with Gary Larizza’s functional puppet workflow unless 
you’ve got lots of prior experience. You can find part 1 here:

http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/

It’s a 3 part series, and there are good follow-ups on r10k and environments 
(http://garylarizza.com/blog/2014/03/26/random-r10k-workflow-ideas/) and an 
update to that post to cover directory environments 
(http://garylarizza.com/blog/2014/08/31/r10k-plus-directory-environments/)

Start there - there are criticisms to be had but it’s a good, tested functional 
workflow at use at a lot of orgs.

-Eric

-- 
Eric Shamow
Sent with Airmail

On September 30, 2014 at 4:17:45 PM, Tom Tucker (tktuc...@gmail.com) wrote:


I just got back from PuppetConf last week and several presenters mentioned 
using more than one Git repo with Puppet.  Some even recommend having a repo 
per module.  For our initial Puppet deployment this seems a bit excessive.  My 
plan was to have three repos for each of our environments (Dev, QA and 
Production).  The contents of these repos would contain Puppet Enterprise 
directory of /etc/puppetlabs/puppet.

 

Deployment strategy

-   Upload changes to Dev repo

-   Deploy Dev changes to Dev master

-   Test

-   Merge Dev changes to QA repo

-   Rinse and repeat

 

 

Thoughts? Any tips for a Puppet and Git newbie in regards to file hierarchy, 
Git repo strategies, etc.

 

Thank you in advance,

 

Tom







 

Sample tree and repo of /etc/puppetlabs/puppet

# tree *

auth.conf

autosign.conf

console.conf   # File excluded this is site specific.  We will have a unique 
Puppet master for each env.

environments

├── development

│   ├── hieradata

│   │   └── environmentX.yaml

│   ├── manifests

│   │   └── site.pp

│   └── modules

└── production

fileserver.conf

hieradata

├── defaults.yaml

├── master.mydomain.com.yaml

└── production.yaml

hiera.yaml [error opening dir]

manifests

├── hieradata

│   └── hostgroups.yaml

└── site.pp

modules

├── custom

puppet.conf   # File excluded this is site specific.  We will have a unique 
Puppet master for each env.

puppetdb.conf   # File excluded this is site specific.  We will have a unique 
Puppet master for each env.

routes.yaml

ssl # Directory excluded this is site specific

< extra lines removed>

 

 

# cat hiera.yaml

---

:hierarchy:

    - "hieradata/fqdn/%{::fqdn}"

    - "%{environment}/%{::osfamily}"

    - "%{environment}/hieradata/%{::network_location}"

    - "%{environment}/hieradata/%{::systemrole}"

    - "hieradata/common"

 

:backends:

    - yaml

 

:yaml:

    :datadir: /etc/puppetlabs/puppet/environments

--
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/CAGymF1DKrTsh%2BNO%3DQLMpP1pM80ac3MMxvbo2p0aN9q9USXLj5Q%40mail.gmail.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/etPan.542b464a.238e1f29.160a6%40rassilon.local.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Announce: nightly repos available

[Eric Shamow]

+1 great news Eric, thanks.

-Eric

On Aug 27, 2014, at 8:27 AM, Martijn  wrote:

> That's very nice. Should make testing a pre-release easier for many users 
> than building from Git.
> 
> Thanks,
> Martijn
> 
> Op dinsdag 26 augustus 2014 19:23:54 UTC+2 schreef Eric Sorenson:
> After the Puppet 3.5.0 release problems, we had a retrospective and tried to 
> figure out some process improvements which would have surfaced the problems 
> earlier. Despite a lengthy 4-week release candidate cycle, that release still 
> had a fatal flaw that nobody had caught until it went into final release. As 
> we talked it over, our thoughts turned to continuous delivery. Puppet (along 
> with most of the other open-source projects) already produces packaged 
> artifacts as moves through our Jenkins pipeline, so it seemed like a natural 
> step to make those packages publicly available. 
> 
> In lieu of release candidates, we are moving toward a more automated system 
> which will have the latest green builds (passed spec and Beaker acceptance 
> tests) cut off the 'master' branch for most of our projects. What this means 
> is that as we near feature complete on a release, like the coming Puppet 
> 3.7.0 release, users like yourself can begin trying out the packages to 
> ensure that the new features haven't broken anything you depend on, and that 
> the new features work the way you expect/want them to. 
> 
> The repos are live now and you can try them out by following these 
> directions: 
> https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#using-the-nightly-repos
>  
> 
> Hopefully this will help get faster turnaround AND better coverage. Please 
> let us know if you find it useful! 
> 
> 
> Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0 
> puppet platform // coffee // techno // bicycles 
> 
> 
> -- 
> 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/ca60c8f6-6c8c-4338-9855-ddd8c81fb6d7%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/7D8B4729-AA9A-432E-8470-9CE77907CD90%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to unzip archive to a master's location

[Eric Shamow]

Generate is probably useful here:

http://docs.puppetlabs.com/references/latest/function.html#generate


On Thu, Jul 10, 2014 at 4:21 PM, Cristian Falcas 
wrote:

> Exec resources are executed on the agent. Functions are executed on
> master. So you first need a function that does the processing of the
> original zip and copies the new file to some module, from where you can
> retrieve it with the file resource.
>
> cristi
>
>
> On Tue, Jun 24, 2014 at 12:16 PM, Malintha Adikari 
> wrote:
>
>> Hi,
>>
>> I keep archive files in my puppet master side. I want to unzip the
>> archive to master's location and do some file replacements and again zip it
>> and then copy it to the agent side. I use following code snippet to unzip
>> it. How can I give an own location (master side location) here ?
>>
>> exec { "unzip":
>> command => 'unzip wso2esb-4.8.1.zip',
>> cwd => "/home/malintha/",
>>  path  => $command_path,
>> logoutput => true,
>> timeout => 3600,
>> require => File['/home/agent2/adikari11/wso2esb-4.8.1.zip'],
>> }
>>
>>
>> here "*cwd*" means the destination. But this is the agent side
>> destination.I want to set it to master side location
>>
>> Regards,
>> Malintha Adikari
>>
>> --
>> 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/fa17081c-1b25-4a0d-8b3d-236208caba9f%40googlegroups.com
>> <https://groups.google.com/d/msgid/puppet-users/fa17081c-1b25-4a0d-8b3d-236208caba9f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/CAMo7R_cxbvg%3D6i%3DV23nCGNUz1WGoumaGyxz6h4Fi9Eodh_s65w%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAMo7R_cxbvg%3D6i%3DV23nCGNUz1WGoumaGyxz6h4Fi9Eodh_s65w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric Shamow
Methodologies Lead
Puppet Labs

-- 
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/CAOkEyqz%2BvyWvaw0453_mcjZrPtvTB%3D19ZUTyRcpMgq1rymz5tQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Server acceptance unit testing

[Eric Shamow]

There is Beaker, which is an internal (but open) PL testing framework:

https://github.com/puppetlabs/beaker/wiki

Beaker has an rspec variant, but it also has its own DSL which is much,
much simpler.

-Eric



On Mon, Jun 16, 2014 at 11:13 PM, Nan Liu  wrote:

> On Mon, Jun 16, 2014 at 10:52 PM, John Warburton 
> wrote:
>
>> Hi Everyone
>>
>> We want to unit test our servers with something like serverspec, but we
>> do not have the coding skills in the team to write ruby/rspec, and we want
>> a low barrier to entry for writing tests
>>
>>
>>
>> Our site isn't small with 3.5K servers, 200 modules, 400 manifests
>> covering 3K resources. Each server averages about 650 resources
>>
>>
>>
>> I was wondering what others do for server acceptance testing given a
>> similar set of requirements. Based on my quick reviews on what is out
>> there, Jenkins with perl's Test::Harness looks a good fit, which is a
>> little scary
>>
>>
>>
>> Am I missing something?
>>
>
> If you are looking for something that's low barrier of entry and shell is
> your target, have you considered something like bats?
> https://github.com/sstephenson/bats
>
> Nan
>
> --
> 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/CACqVBqB_kX8VUYwb2BHwaTpfCi%2B%2BFqxH3J4ono67tdU_3ve5Aw%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CACqVBqB_kX8VUYwb2BHwaTpfCi%2B%2BFqxH3J4ono67tdU_3ve5Aw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric Shamow
Methodologies Lead
Puppet Labs

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

Re: [Puppet Users] Possible to copy ssh key from node A to node B?

[Eric Shamow]

Sandra,

On the run so no time to write up a quick example - but take a look at exported 
resources.  There's a design patterns page --

http://docs.puppetlabs.com/guides/exported_resources.html

These are designed to do what you're looking for.

-Eric 

--

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12


On Thursday, August 30, 2012 at 9:41 AM, Sandra Schlichting wrote:

> Hi,
> 
> I would like to write a class that can copy /root/.ssh/id_dsa from node A to 
> node B.
> 
> > class sshkeycopy {
> >exec {"ssh-keygen -q -t dsa -f /root/.ssh/id_dsa -P ''":
> >   creates => "/root/.ssh/id_dsa.pub"
> >}
> >file {"/root/.ssh/id_dsa":
> >   mode   => "644",
> >   owner  => root,
> >   group  => root,
> >}
> >exec {"???":
> >   subscribe => Exec["ssh-keygen -q -t dsa -f /root/.ssh/id_dsa -P ''"],
> >   refreshonly => true
> >}
> > }
> 
> The puppet master can login to node B without passphrase and append a key
> 
> cat .ssh/id_rsa.pub | ssh b@B 'cat >> .ssh/authorized_keys'
> 
> So the question is how to copy /root/.ssh/id_dsa.pub from node A to the 
> puppet master and then push it to node B?
> 
> Hugs,
> Sandra
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/UZoM9krZK74J.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] How can MCollective replace "puppet kick"?

[Eric Shamow]

You get a good bit more than that - PE sets up the ActiveMQ stuff for you and 
handles key setup/exchange, which is fairly difficult to do by hand the first 
time if you aren't familiar with the stuff.  As it is, any PE node you add to 
your PE master automatically gets added to your mcollective environment, which 
is quite nice.

--

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12


On Sunday, August 26, 2012 at 3:30 PM, Walter Heck wrote:

> mcollective is stand-alone software, it doesn't actually require
> puppet. It's also free and open source. The only thing you get with PE
> is the live management fature in the dashboard, which is essentially a
> GUI for mcollective if I'm not mistaken.
>  
> cheers,
>  
> Walter
>  
> On Mon, Aug 27, 2012 at 12:54 AM, Dan White  (mailto:y...@comcast.net)> wrote:
> > Spoke too soon !
> >  
> > Found it !
> >  
> > http://docs.puppetlabs.com/pe/2.5/orchestration_overview.html
> > "PE’s orchestration features are built on the MCollective framework"
> >  
> > On Aug 26, 2012, at 12:52 PM, Dan White wrote:
> >  
> > Is MCollective part of Puppet Enterprise ?
> >  
> > I cannot find documentation that says yea or nay.
> >  
> > On Aug 25, 2012, at 3:11 PM, Johan Kamb wrote:
> >  
> > On Sat, Aug 25, 2012 at 8:44 PM, Sandra Schlichting
> > mailto:littlesandr...@gmail.com)> wrote:
> > > >  
> > > > > How can MCollective replace "puppet kick"?
> > > >  
> > > >  
> > > > http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/AgentPuppetd
> > >  
> > >  
> > > I don't know what MCollective is, and that link doesn't say anything that
> > > will explain it or how I can push configs to nodes =(
> > >  
> >  
> >  
> >  
> > http://projects.puppetlabs.com/projects/mcollective gives a bit more
> > information on mcollective itself. You don't actually push configs to nodes
> > with it; you have a client which "tells" all machines that matches a fact to
> > trigger a puppet run. The puppetd agent plugin is required for this to work.
> >  
> >  
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >  
>  
>  
>  
>  
> --  
> Walter Heck
>  
> --
> Check out my startup: Puppet training and consulting @ http://www.olindata.com
> Follow @olindata on Twitter and/or 'Like' our Facebook page at
> http://www.facebook.com/olindata
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>  
>  


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] How can MCollective replace "puppet kick"?

[Eric Shamow]

Sandra,

The mcollective agent is written in Ruby, but it's really tiny.  You can use 
the mco controller plugin to view resource utilization over time, and it's 
generally infinitesimal.

-Eric 

--

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12


On Saturday, August 25, 2012 at 3:33 PM, Sandra Schlichting wrote:

> > MCollective is a service that runs on every node. It constantly polls a 
> > message queue server for real-time messages and sometimes responds to them 
> > by performing actions. 
> > 
> > You use a command-line client app to send messages, and you can set filters 
> > on each message so only certain nodes or groups of nodes will respond to 
> > them. Every node that matches a message will react simultaneously when the 
> > message goes out. 
> > 
> > Each node has a set of actions it can run, provided by plugins. The 
> > "puppetd" plugin lets you control puppet agent, but it's better than puppet 
> > kick: It can trigger runs even if puppet agent usually runs via cron 
> > instead of as a service, it can enable and disable puppet runs, and it can 
> > fetch last run summaries. MCollective also lets you be smarter about 
> > triggering runs because it doesn't limit you to hostnames; you can filter 
> > by puppet class, facts, etc. 
> > 
> > Does that help? 
> 
> Absolutely =)
> 
> Wow! That is impressive.
> 
> I have seen the puppet agent taking ~100MB of ram.
> 
> Is MCollective also written in Ruby, and therefore take a lot of ram?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/VK67c2UfgG4J.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Dynamic Lookup of facter variable.

[Eric Shamow]

Facts exist at top scope, as indicated in the scoping doc several people have 
referred you to on this list.  Use $::ec2_instance_type

Sent from my iPad

On Aug 19, 2012, at 10:44 PM, Douglas Garstang  wrote:

> I don't get it...
> 
>if ! ( $ec2_instance_type in [$ec2_inst_type_allow]) {
>notice("NOT ALLOWED")
>} else {
>notice("ALLOWED")
>}
> 
> 2012-08-20T02:39:10.537134+00:00 truth puppet-master[24080]: Dynamic
> lookup of $ec2_instance_type at /truth/sauce/env/prod/modules/rol
> e/manifests/validate_server.pp:12 is deprecated.  Support will be
> removed in Puppet 2.8.  Use a fully-qualified variable name (e.g., $
> classname::variable) or parameterized classes.
> 
> Line 12 is the if statement. However, on the same client system...
> 
> [us1:i-16c5c050] root@testweb11:~# facter | grep ec2_instance_type
> ec2_instance_type => m1.large
> 
> It's a facter variable. What's it complaining about?
> 
> Doug.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppetlabs lvm module

[Eric Shamow]

On Wednesday, August 15, 2012 at 2:58 PM, Douglas Garstang wrote:
> Seriously can you run it through a syntax checker before posting it?


Douglas,

Ryan has worked to support you and has posted a fix for the problem.  He's also 
acknowledged our error and apologized.  Is there something specific we can do 
to further assist you?

-Eric

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Custom Providers and Environmemts.

[Eric Shamow]

Specifically the types need to be in the server's $libdir. You can place them 
there manually, but the way they generally get there is via pluginsync. So the 
easiest way to ensure the master can process them is to place them in the 
module path used by the server *when the server is acting as a puppet agent* 
and run puppet agent on the server.

This will sync the types to the correct directory on the master and enable it 
to parse them when they are used elsewhere.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  


On Tuesday, August 14, 2012 at 5:47 PM, Douglas Garstang wrote:

> On Tue, Aug 14, 2012 at 2:40 PM, Eric Shamow  (mailto:e...@puppetlabs.com)> wrote:
> > Douglas,
> > 
> > Do you intend to use different versions of the type in different 
> > environments, or are you just concerned with trying to get the same code 
> > out everywhere?
> > 
> > According to
> > 
> > http://projects.puppetlabs.com/issues/13858
> > 
> > this is fixed for Telly, and there is a patch available if you want to give 
> > it a try.
> > 
> > If you don't mind the type being available on the master as well, making it 
> > available in the modulepath the master uses as a client should resolve the 
> > issue. The problem is that the master loads new types locally for 
> > validation, and so needs access to them itself.
> 
> Eric,
> 
> Not sure I follow. Your saying that puppetlabs-lvm-0.1.0/* needs to be
> placed in the location set by modulepath on the server?
> 
> Doug.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Custom Providers and Environmemts.

[Eric Shamow]

Douglas,

Do you intend to use different versions of the type in different environments, 
or are you just concerned with trying to get the same code out everywhere?

According to

http://projects.puppetlabs.com/issues/13858

this is fixed for Telly, and there is a patch available if you want to give it 
a try.

If you don't mind the type being available on the master as well, making it 
available in the modulepath the master uses as a client should resolve the 
issue. The problem is that the master loads new types locally for validation, 
and so needs access to them itself.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  


On Tuesday, August 14, 2012 at 5:25 PM, Douglas Garstang wrote:

> I've installed the puppet labs lvm module. After fixing the missing
> "}" at line 20 in init.pp (really?!?!), I'm getting this:'
> 
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError:
> Invalid resource type physical_volume at
> /truth/sauce/env/prod/modules/role/manifests/common.pp:43 on node
> testweb10.us1.xxx.com (http://testweb10.us1.xxx.com)
> 
> Seems related to:
> http://projects.puppetlabs.com/issues/4409
> 
> I'm using environments. Is this fixed?
> 
> Doug
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppetlabs lvm module

[Eric Shamow]

Oh right - for the code compression syntax…I don't use it and so I tend to 
forget it exists. Sorry about that.

Is line 29 specifically this?

absent: {

It would be helpful to see in context with line numbers, such as in a gist.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Tuesday, August 14, 2012 at 4:43 PM, Douglas Garstang wrote:

> I've always used semicolons at the end of resources never caused a
> problem before, and puppet-lint doesn't complain about them.
>  
> On Tue, Aug 14, 2012 at 1:42 PM, Eric Shamow  (mailto:e...@puppetlabs.com)> wrote:
> > Everything else aside, you have a semicolon after ensure => present instead 
> > of a comma in your physical_volume resource. I'm not certain that it's 
> > causing the problem but it might be confusing the parser.
> >  
> > -Eric
> >  
> > --
> >  
> > Eric Shamow
> > Professional Services
> > http://puppetlabs.com/
> > (c)631.871.6441
> >  
> > Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
> > Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12
> >  
> >  
> > On Tuesday, August 14, 2012 at 4:39 PM, Douglas Garstang wrote:
> >  
> > > I just grabbed the puppet labs lvm module from Puppet forge.
> > >  
> > > Attempting to use...
> > >  
> > > physical_volume {
> > > ['/dev/xvdb1', '/dev/xvdc1']:
> > > ensure => present;
> > > }
> > >  
> > > results in:
> > >  
> > > err: Could not retrieve catalog from remote server: Error 400 on
> > > SERVER: Syntax error at ':'; expected '}' at
> > > /truth/sauce/env/prod/modules/lvm/manifests/init.pp:29 on node
> > > testweb10.us1.xxx.com (http://testweb10.us1.xxx.com)
> > >  
> > > Line 29 of init.pp is:
> > >  
> > > #
> > > # Just clean up the logical volume
> > > #
> > > absent: {
> > > logical_volume { $name: ensure => absent, volume_group => $vg,
> > > size => $size }
> > > }
> > >  
> > > I don't get it what am I missing
> > >  
> > > Doug.
> > >  
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Puppet Users" group.
> > > To post to this group, send email to puppet-users@googlegroups.com 
> > > (mailto:puppet-users@googlegroups.com).
> > > To unsubscribe from this group, send email to 
> > > puppet-users+unsubscr...@googlegroups.com 
> > > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > > For more options, visit this group at 
> > > http://groups.google.com/group/puppet-users?hl=en.
> >  
> >  
> >  
> >  
> >  
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
>  
>  
>  
>  
>  
> --  
> Regards,
>  
> Douglas Garstang
> http://www.linkedin.com/in/garstang
> Email: doug.garst...@gmail.com (mailto:doug.garst...@gmail.com)
> Cell: +1-805-340-5627
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppetlabs lvm module

[Eric Shamow]

Everything else aside, you have a semicolon after ensure => present instead of 
a comma in your physical_volume resource. I'm not certain that it's causing the 
problem but it might be confusing the parser.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  


On Tuesday, August 14, 2012 at 4:39 PM, Douglas Garstang wrote:

> I just grabbed the puppet labs lvm module from Puppet forge.
> 
> Attempting to use...
> 
> physical_volume {
> ['/dev/xvdb1', '/dev/xvdc1']:
> ensure => present;
> }
> 
> results in:
> 
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Syntax error at ':'; expected '}' at
> /truth/sauce/env/prod/modules/lvm/manifests/init.pp:29 on node
> testweb10.us1.xxx.com (http://testweb10.us1.xxx.com)
> 
> Line 29 of init.pp is:
> 
> #
> # Just clean up the logical volume
> #
> absent: {
> logical_volume { $name: ensure => absent, volume_group => $vg,
> size => $size }
> }
> 
> I don't get it what am I missing
> 
> Doug.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] variable scoping?

[Eric Shamow]

First off, it's important to distinguish import from include. They "feel" like 
similar concepts but they're not - import goes and physically loads a file. 
Include says "ensure that this class is part of this host's resource graph."

It's important not to think of Puppet in procedural, top-down terms. We haven't 
just said, "give me all the stuff in this class, and now do these things." 
Rather we are building a model of a server, and manifest code simply informs 
pieces of that model. So by saying "include " you are really saying, 
"Puppet, if you haven't already, make sure this class is part of the overall 
resource graph."

The better model for this example is, rather than a box inside of a box, you 
are looking at two sealed boxes sitting side by side. When you include the 
first group, it is added to the list of boxes used. Within the first box, when 
you then say "give me the second box," that second box is placed *alongside* 
the first. Thus in order to grab anything from it, you have to specify "I need 
the stuff from box 2."

Does that analogy help a bit more?

The reason for this is that, as your number of classes grows, so too will your 
variables. If they share a single global namespace, the likelihood of a global 
variable name being used more than once increases. This can lead to really 
unexpected changes and ambiguity in building the graph.

An example: suppose is this module you say $puppetmaster = "myserver.local" and 
in another module, you want to only run on a puppet master and so say 
$puppetmaster = true. When Puppet assembles the model of your system, which of 
the two is to be applied where? Dynamic scoping tried to guess at this. The 
idea here is to say, eliminate ambiguity - tell us exactly which one you want.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Sunday, August 12, 2012 at 2:35 AM, Zachary Alex Stern wrote:

> So, your explanation makes sense to me - but that doesn't exactly explain to 
> me why the "include" statement isn't enough.
>  
> E.g. when I'm "including the puppet::params class in the puppet::config 
> class, what affect is it having at all, if not setting things like the 
> variables included in the original puppet::params class?
>  
> How can I change variables on the fly effectively, if I can't just do the 
> import and then have the variable $puppetserver equal the one from the 
> imported class? I'm having a hard time grasping what import does, if not this.
>  
> On Saturday, August 11, 2012 10:36:48 PM UTC-4, Eric Shamow wrote:
> > The best reference to explain how variable scoping works in Puppet is this 
> > one -  
> >  
> > http://docs.puppetlabs.com/guides/scope_and_puppet.html  
> >  
> > Scoping has changed with 2.7, so you may find some confusing references 
> > online that follow the pre-2.7 rules. In general the 2.7 changes are 
> > designed to introduce some sanity to variable scopes and eliminate dynamic 
> > scoping, which causes all kinds of pain.  
> >  
> > The easiest way to think about scoping in general is that a scope is 
> > defined by its container. If I put something physical in a box, I have 
> > access to it the moment I open the box, and other objects inside the box 
> > can interact with it. If, however, I now put that box inside a second box, 
> > the objects in the second box cannot interact directly with the objects in 
> > the first - the first object is protected by its container.  
> >  
> > Scoping mostly works the same way. The right way to get at the variable is 
> > to always explicitly scope, as you began to get at below with your 
> > scope.lookupvar example. As that can be a bit of a pain to repeat, you can 
> > always copy the value into a local variable:  
> >  
> > class puppet::config {  
> > include puppet::params  
> > $puppetserver = puppet::params::puppetserver  
> > …  
> > }  
> >  
> > -Eric  
> >  
> > --  
> >  
> > Eric Shamow  
> > Professional Services  
> > http://puppetlabs.com/  
> > ©631.871.6441  
> >  
> > Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
> > Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  
> >  
> >  
> > On Saturday, August 11, 2012 at 8:45 PM, Zachary Stern wrote:  
> >  
> > > I'm having a really hard time grasping how var

Re: [Puppet Users] Re: Installing Modules.

[Eric Shamow]

I should add, the default path is

/etc/puppet/modules

for FOSS, and

/etc/puppetlabs/puppet/modules

for PE.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Sunday, August 12, 2012 at 1:47 AM, Eric Shamow wrote:

> Douglas,
>  
> I recommend reading the parent page of the "Installing" document you pulled 
> up before:
>  
> http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html
>  
> This covers some basic information about modules that will help answer your 
> question.
>  
> Presuming you are in client/server mode, modules are installed in the module 
> path of your puppetmaster. You can find this by looking in your puppet.conf, 
> or by running
>  
> puppet master --configprint modulepath
>  
> On the master.
>  
> -Eric  
>  
> --  
>  
> Eric Shamow
> Professional Services
> http://puppetlabs.com/
> ©631.871.6441
>  
> Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
> Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  
>  
>  
> On Sunday, August 12, 2012 at 1:44 AM, Douglas Garstang wrote:
>  
> > On Sat, Aug 11, 2012 at 10:33 PM, Douglas Garstang
> > mailto:doug.garst...@gmail.com)> wrote:
> > > Someone directed me to this...
> > >  
> > > http://forge.puppetlabs.com/puppetlabs/lvm
> > >  
> > > How do you install these...? The documentation at
> > > http://docs.puppetlabs.com/puppet/2.7/reference/modules_installing.html
> > > says to use the puppet module command... where? On the server? The
> > > docs also say this isn't available until puppet 2.7.14, and we're
> > > using 2.7.1. How do I install?
> > >  
> > > Doug
> >  
> >  
> > Main page 
> > http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
> >  
> > Seriously... is it that hard to document _how_ to install these
> > things? It HAS to be there but where...?
> >  
> > Doug
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
>  



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Installing Modules.

[Eric Shamow]

Douglas,

I recommend reading the parent page of the "Installing" document you pulled up 
before:

http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html

This covers some basic information about modules that will help answer your 
question.

Presuming you are in client/server mode, modules are installed in the module 
path of your puppetmaster. You can find this by looking in your puppet.conf, or 
by running

puppet master --configprint modulepath

On the master.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Sunday, August 12, 2012 at 1:44 AM, Douglas Garstang wrote:

> On Sat, Aug 11, 2012 at 10:33 PM, Douglas Garstang
> mailto:doug.garst...@gmail.com)> wrote:
> > Someone directed me to this...
> >  
> > http://forge.puppetlabs.com/puppetlabs/lvm
> >  
> > How do you install these...? The documentation at
> > http://docs.puppetlabs.com/puppet/2.7/reference/modules_installing.html
> > says to use the puppet module command... where? On the server? The
> > docs also say this isn't available until puppet 2.7.14, and we're
> > using 2.7.1. How do I install?
> >  
> > Doug
>  
> Main page 
> http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
>  
> Seriously... is it that hard to document _how_ to install these
> things? It HAS to be there but where...?
>  
> Doug
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] variable scoping?

[Eric Shamow]

Zachary,

Is there a particular section of the scoping doc I can help you understand?

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Sunday, August 12, 2012 at 1:24 AM, Zachary Alex Stern wrote:

> Also, fwiw, I've read that document on scoping beginning to end several 
> times. Doesn't mean much to me I'm afraid - pretty new to all this.
>  
> On Saturday, August 11, 2012 10:36:48 PM UTC-4, Eric Shamow wrote:
> > The best reference to explain how variable scoping works in Puppet is this 
> > one -  
> >  
> > http://docs.puppetlabs.com/guides/scope_and_puppet.html  
> >  
> > Scoping has changed with 2.7, so you may find some confusing references 
> > online that follow the pre-2.7 rules. In general the 2.7 changes are 
> > designed to introduce some sanity to variable scopes and eliminate dynamic 
> > scoping, which causes all kinds of pain.  
> >  
> > The easiest way to think about scoping in general is that a scope is 
> > defined by its container. If I put something physical in a box, I have 
> > access to it the moment I open the box, and other objects inside the box 
> > can interact with it. If, however, I now put that box inside a second box, 
> > the objects in the second box cannot interact directly with the objects in 
> > the first - the first object is protected by its container.  
> >  
> > Scoping mostly works the same way. The right way to get at the variable is 
> > to always explicitly scope, as you began to get at below with your 
> > scope.lookupvar example. As that can be a bit of a pain to repeat, you can 
> > always copy the value into a local variable:  
> >  
> > class puppet::config {  
> > include puppet::params  
> > $puppetserver = puppet::params::puppetserver  
> > …  
> > }  
> >  
> > -Eric  
> >  
> > --  
> >  
> > Eric Shamow  
> > Professional Services  
> > http://puppetlabs.com/  
> > ©631.871.6441  
> >  
> > Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
> > Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  
> >  
> >  
> > On Saturday, August 11, 2012 at 8:45 PM, Zachary Stern wrote:  
> >  
> > > I'm having a really hard time grasping how variables are scoped in  
> > > puppet (not really much of a programmer).  
> > >  
> > > I've got a manifest that looks like this:  
> > > ###  
> > > class puppet::config {  
> > > include puppet::params  
> > > file { '/etc/puppet/puppet.conf':  
> > > ensure => present,  
> > > content => template('puppet/puppet.conf.erb'),  
> > > owner => 'root',  
> > > group => 'admins',  
> > > require => Class['puppet::install'],  
> > > notify => Class['puppet::service'],  
> > > }  
> > > }  
> > > ###  
> > >  
> > >  
> > > I've then got a manifest like this, which has a class being included 
> > > above:  
> > > ###  
> > > class puppet::params {  
> > > $puppetserver = 'command.enterawesome.com 
> > > (http://command.enterawesome.com) (http://command.enterawesome.com)'  
> > > }  
> > > ###  
> > >  
> > > The template being used in the first class includes the variable  
> > > $puppetserver, but somehow, the include statement isn't enough for the  
> > > variable to be defined within the scope of the manifest/template  
> > > above.  
> > > What gives?  
> > > It works just fine if I include a statement like this in the erb file:  
> > > <%= scope.lookupvar('puppet::params::puppetserver') %>  
> > >  
> > > But I'd really like to understand scoping better. What is it I need to  
> > > do to just refer to the variable by name? Why isn't the include  
> > > statement enough? Isn't in including the puppet::params class inside  
> > > the puppet::config class, and therefore having the variable defined in  
> > > that context? Apparently not. But I don't understand why. I wan't to  
> > > end up at a point where the variable is in the proper scope, such that  
> > > I can just have a statement like <%= puppetserver %> inside of the  
> > > template I'm usin

Re: [Puppet Users] variable scoping?

[Eric Shamow]

Sorry, that should be

$puppetserver = $puppet::params::puppetserver

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Saturday, August 11, 2012 at 10:36 PM, Eric Shamow wrote:

> The best reference to explain how variable scoping works in Puppet is this 
> one -
>  
> http://docs.puppetlabs.com/guides/scope_and_puppet.html
>  
> Scoping has changed with 2.7, so you may find some confusing references 
> online that follow the pre-2.7 rules. In general the 2.7 changes are designed 
> to introduce some sanity to variable scopes and eliminate dynamic scoping, 
> which causes all kinds of pain.
>  
> The easiest way to think about scoping in general is that a scope is defined 
> by its container. If I put something physical in a box, I have access to it 
> the moment I open the box, and other objects inside the box can interact with 
> it. If, however, I now put that box inside a second box, the objects in the 
> second box cannot interact directly with the objects in the first - the first 
> object is protected by its container.
>  
> Scoping mostly works the same way. The right way to get at the variable is to 
> always explicitly scope, as you began to get at below with your 
> scope.lookupvar example. As that can be a bit of a pain to repeat, you can 
> always copy the value into a local variable:
>  
> class puppet::config {
> include puppet::params
> $puppetserver = puppet::params::puppetserver
> …
> }
>  
> -Eric  
>  
> --  
>  
> Eric Shamow
> Professional Services
> http://puppetlabs.com/
> ©631.871.6441
>  
> Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
> Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12  
>  
>  
> On Saturday, August 11, 2012 at 8:45 PM, Zachary Stern wrote:
>  
> > I'm having a really hard time grasping how variables are scoped in
> > puppet (not really much of a programmer).
> >  
> > I've got a manifest that looks like this:
> > ###
> > class puppet::config {
> > include puppet::params
> > file { '/etc/puppet/puppet.conf':
> > ensure => present,
> > content => template('puppet/puppet.conf.erb'),
> > owner => 'root',
> > group => 'admins',
> > require => Class['puppet::install'],
> > notify => Class['puppet::service'],
> > }
> > }
> > ###
> >  
> >  
> > I've then got a manifest like this, which has a class being included above:
> > ###
> > class puppet::params {
> > $puppetserver = 'command.enterawesome.com (http://command.enterawesome.com)'
> > }
> > ###
> >  
> > The template being used in the first class includes the variable
> > $puppetserver, but somehow, the include statement isn't enough for the
> > variable to be defined within the scope of the manifest/template
> > above.
> > What gives?
> > It works just fine if I include a statement like this in the erb file:
> > <%= scope.lookupvar('puppet::params::puppetserver') %>
> >  
> > But I'd really like to understand scoping better. What is it I need to
> > do to just refer to the variable by name? Why isn't the include
> > statement enough? Isn't in including the puppet::params class inside
> > the puppet::config class, and therefore having the variable defined in
> > that context? Apparently not. But I don't understand why. I wan't to
> > end up at a point where the variable is in the proper scope, such that
> > I can just have a statement like <%= puppetserver %> inside of the
> > template I'm using.
> >  
> > Thanks in advance!
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
>  



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] variable scoping?

[Eric Shamow]

The best reference to explain how variable scoping works in Puppet is this one -

http://docs.puppetlabs.com/guides/scope_and_puppet.html

Scoping has changed with 2.7, so you may find some confusing references online 
that follow the pre-2.7 rules. In general the 2.7 changes are designed to 
introduce some sanity to variable scopes and eliminate dynamic scoping, which 
causes all kinds of pain.

The easiest way to think about scoping in general is that a scope is defined by 
its container. If I put something physical in a box, I have access to it the 
moment I open the box, and other objects inside the box can interact with it. 
If, however, I now put that box inside a second box, the objects in the second 
box cannot interact directly with the objects in the first - the first object 
is protected by its container.

Scoping mostly works the same way. The right way to get at the variable is to 
always explicitly scope, as you began to get at below with your scope.lookupvar 
example. As that can be a bit of a pain to repeat, you can always copy the 
value into a local variable:

class puppet::config {
include puppet::params
$puppetserver = puppet::params::puppetserver
…
}

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
©631.871.6441

Join us for PuppetConf 2012 at the Mission Bay Convention Center in San 
Francisco, California on September 27th and 28th --> http://bit.ly/pcsig12   


On Saturday, August 11, 2012 at 8:45 PM, Zachary Stern wrote:

> I'm having a really hard time grasping how variables are scoped in
> puppet (not really much of a programmer).
>  
> I've got a manifest that looks like this:
> ###
> class puppet::config {
> include puppet::params
> file { '/etc/puppet/puppet.conf':
> ensure => present,
> content => template('puppet/puppet.conf.erb'),
> owner => 'root',
> group => 'admins',
> require => Class['puppet::install'],
> notify => Class['puppet::service'],
> }
> }
> ###
>  
>  
> I've then got a manifest like this, which has a class being included above:
> ###
> class puppet::params {
> $puppetserver = 'command.enterawesome.com (http://command.enterawesome.com)'
> }
> ###
>  
> The template being used in the first class includes the variable
> $puppetserver, but somehow, the include statement isn't enough for the
> variable to be defined within the scope of the manifest/template
> above.
> What gives?
> It works just fine if I include a statement like this in the erb file:
> <%= scope.lookupvar('puppet::params::puppetserver') %>
>  
> But I'd really like to understand scoping better. What is it I need to
> do to just refer to the variable by name? Why isn't the include
> statement enough? Isn't in including the puppet::params class inside
> the puppet::config class, and therefore having the variable defined in
> that context? Apparently not. But I don't understand why. I wan't to
> end up at a point where the variable is in the proper scope, such that
> I can just have a statement like <%= puppetserver %> inside of the
> template I'm using.
>  
> Thanks in advance!
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] rand losing its randomness after using fqdn_rand

[Eric Shamow]

Not sure that this should be considered a bug in fqdn_rand - the idea with 
fqdn_rand is that it should generate the same random number each time it is run 
in order to maintain idempotency.

The salt will be different on *different* hosts, but it will be the same on the 
same host.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Wednesday, August 1, 2012 at 1:13 PM, R.I.Pienaar wrote:

> 
> 
> - Original Message -
> > From: "Felipe Ortega" mailto:orteg...@gmail.com)>
> > To: puppet-users@googlegroups.com (mailto:puppet-users@googlegroups.com)
> > Sent: Wednesday, August 1, 2012 5:28:23 AM
> > Subject: [Puppet Users] rand losing its randomness after using fqdn_rand
> > 
> > 
> > Hi,
> > 
> > 
> > I'm a newbie puppet user, and I'm facing some weird behaviour in my
> > testing environment.
> > I'm using Debian packages from testing/Wheezy (version 2.7.18) via
> > apache+passenger installation. Also:
> > 
> > 
> > $ ruby -v
> > ruby 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux]
> > 
> > 
> > I developed the following custom function (with some help from
> > Google) to generate the shadow password of any new user:
> > 
> > 
> > module Puppet::Parser::Functions
> > newfunction(:shadow_pwd, :type => :rvalue) do |args|
> > passwd = args[0]
> > case args[1]
> > when 'md5'
> > algo = '$1$'
> > when 'blowfish'
> > algo = '$2$'
> > when 'sha256'
> > algo = '$5$'
> > when 'sha512'
> > algo = '$6$'
> > end
> > o = [('a'..'z'),('A'..'Z'),('0'..'9')].map{|i| i.to_a}.flatten
> > salt = (0..8).map{ o[rand(o.length)] }.join
> > hash = passwd.crypt(algo + salt)
> > end
> > end
> > 
> > 
> > it takes two arguments, the cleartext password and the algorithm to
> > encrypt it.
> > 
> > 
> > So, with this setup, on every run of the puppet agent, a new shadow
> > password was assigned to the user. Well, in fact it was always the
> > same cleartext password, but as the salt was different on every run,
> > the shadow password of the user was different too, and puppet
> > updated the user password accordingly.
> > 
> > 
> > Here comes a new class, puppet, to manage the agent configuration on
> > every node. I chose to run puppet agent via cron task, and in order
> > to prevent every agent try to get the catalog at the same time, I
> > use the following code snippet (picket up online):
> > 
> > 
> > $first = fqdn_rand(30)
> > $second = $first + 30
> > cron {'puppet':
> > command => '/usr/bin/puppet agent --no-daemon --onetime',
> > user => 'root',
> > minute => [$first,$second],
> > ensure => present,
> > require => Class['puppet::install'],
> > }
> > 
> > 
> > This works OK too, it creates a new task in the crontab file of user
> > root, executing the command twice an hour, always on the same two
> > minutes.
> > 
> > 
> > But then I realized the shadow password of the users were not being
> > updated anymore (only when I change the cleartext password). After
> > some debugging, I found out that the salt was always the same!
> > Further debugging led me to the definition of the fqdn_rand
> > function, and the culprit seems to be this line:
> > 
> > 
> > srand(Digest::MD5.hexdigest([lookupvar('::fqdn'),args].join(':')).hex)
> > 
> > 
> > which sets the seed used for the rand function.
> > 
> > 
> > After all this stuff, what should I do? Is it a bug in fqdn_rand?
> > Because after using it, rand loses its randomness. Or, is it my
> > fault for not setting the seed in my custom function? If so, how and
> > where should a set the seed so it works as before using fqdn_rand?
> 
> 
> 
> I'd say this is a bug in fqdn_rand, but if you wish to work around it
> in your function you can also just call srand() when your function get
> called
> 
> Would be great if you could file a bug about fqdn_rand
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] activeMQ client on the puppet server?

[Eric Shamow]

On Jul 26, 2012, at 6:50 PM, Hai Tao  wrote:

> OK.
> 
> when I issue a "mco ping" command, it will discover its own subnet
> only, or it can across subnets?

Hai,

I would recommend reading up on how MCollective/ActiveMQ works.  There is 
documentation here:

http://docs.puppetlabs.com/mcollective/

In particular pay attention to the stuff on the broadcast paradigm and the 
publish/subscribe model. 


--

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: proper usage of global variables / node variables / +=

[Eric Shamow]

Nan is a Puppet Labs guy. One of our best :)

His warning about dynamic scoping is something to take seriously. That's not a 
gratuitous error message - dynamic scoping causes all kinds of problems and has 
been scheduled for deprecation for a while now, and that's coming in the next 
major release.

Details:

http://docs.puppetlabs.com/guides/scope_and_puppet.html

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, July 12, 2012 at 1:27 AM, fp wrote:

> > At this point, however, I'm hoping that one of the PuppetLabs guys will
> > jump in to either explain why I'm wrong or confirm that it's a bug.
> 
> 
> 
> Any PuppetLabs guys reading? I realize they are all busy people, and it 
> may take a while. It's all good.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] create multiple resources from an array of things.

[Eric Shamow]

Wolf,

Are you calling that parameterized class multiple places?

This sounds like a situation where what you want may be a defined type but in 
fact you are using a parameterized class. You can include paramaterized classes 
multiple times using "include" but not using parameters.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Sunday, July 8, 2012 at 2:00 PM, Wolf Noble wrote:

> Hi gang,
>  
> I feel like I'm missing something fundamental here…
> I've got the following:
>  
> class snmp::rhel::rh5enable {
> $collector = ['10.0.0.1', '10.0.0.2']
> define add_snmp_hosts_allow ($ip) {
> exec { "hosts_allow_$ip":
> command => "/bin/echo \"snmpd : $ip : ALLOW\" >>/etc/hosts.allow",
> unless => "/bin/grep -c \"snmpd : $ip : ALLOW\" /etc/hosts.allow",
> }
> }
> notify { "COLLECTOR IS SET TO ${collector}": }
> add_snmp_hosts_allow{$collector: ip=> $collector,}
> }
>  
> yet I get borked, as :
>  
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Duplicate declaration: Exec[hosts_allow_10..0.0.110.0.0.2] is already 
> declared in file 
> /etc/puppetlabs/puppet/modules/core/snmp/manifests/rhel/rh5enable.pp at line 
> 4; cannot redeclare at 
> /etc/puppetlabs/puppet/modules/core/snmp/manifests/rhel/rh5enable.pp:4 on 
> node centos
>  
>  
> how do I go about doing this "correctly" ?
>  
>  
>  
>  
>  
> 
>  
> This message may contain confidential or privileged information. If you are 
> not the intended recipient, please advise us immediately and delete this 
> message. See http://www.datapipe.com/legal/email_disclaimer/ for further 
> information on confidentiality and the risks of non-secure electronic 
> communication. If you cannot access these links, please notify us by reply 
> message and we will send the contents to you.
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] puppet-server-3.0.0-0.1rc3.2 with foreman-1.0.0-0.4

[Eric Shamow]

Ohad,

Without poking too deeply, the "Could not find value for $confdir" raises an 
eyebrow - possible that you are referencing a global, which will be deprecated 
in the next major release. You'll need to fully qualify scope:

http://docs.puppetlabs.com/guides/scope_and_puppet.html

This should be producing warnings in 2.7 and failing when the next major 
release hits.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Friday, July 6, 2012 at 3:16 PM, Ohad Levy wrote:

> 
> 
> On Wed, Jul 4, 2012 at 6:49 PM, pdpinfo  (mailto:pdp...@tiscali.it)> wrote:
> > Hi all,
> > 
> > just trying a lab with newest versions:
> > 
> > - puppet-server: 3.0.0-0.1rc3.2
> > - passenger: 3.0.12-1
> > - foreman: 1.0.0-0.4 
> > 
> > I hit problems with foreman 1.0 not able to work with Puppet 3.0.
> > 
> > Foreman 1.0 worked correctly with puppet-server 2.7.17-1 (fresh-installed).
> > 
> > Upgrading the package (from foreman-devel repo) to latest version,
> > Foreman service fails with error:
> > "...
> > /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:278:in `convert': Error 
> > converting value for param 'hostcert': Error converting value for param 
> > 'certdir': Error converting value for param 'ssldir': Could not find value 
> > for $confdir (Puppet::Settings::InterpolationError)
> > "
> > 
> > Any hints ?
> 
> I'm guessing puppet internals changed a bit, mind opening an issue on foreman 
> tracker ? 
> as a work around, you could probably change 
> lib/foreman/default_settings/loader.rb not to use Puppet settings..
> 
> Ohad
> > 
> > Thank you
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/puppet-users/-/qQ6yvf73SvUJ.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users%2bunsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Style guide question..

[Eric Shamow]

On Tuesday, July 3, 2012 at 8:39 AM, jcbollinger wrote:
> You mean "less objectionable" I presume?  I agree that classes generally 
> should not define other classes, but the guide already says that elsewhere.  
> I guess there's no harm in repeating it, if you think it worth the emphasis.

Sorry, yes - I meant that the practice was more objectionable rather than the 
phrasing.

However if it's defined elsewhere no need to repeat.

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] UX/UI of puppet help when face actions have unmet dependencies

[Eric Shamow]

On Friday, June 29, 2012 at 1:22 PM, Daniel Pittman wrote:
> Pieter is absolutely right that reporting errors on the output channel
> is a bad habit in Puppet - it makes us wildly different to the Unix
> standard. Every normal application behaves the way we do now - errors
> to stderr - and if the user isn't looking, they have that same problem
> with every other application too.
> 
> 


+1 to keeping errors on STDERR.  It would be my expectation as a sysadmin that 
I could filter one from the other on output and I'd be fairly frustrated if I 
couldn't.

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Style guide question..

[Eric Shamow]

On Friday, June 29, 2012 at 9:55 AM, jcbollinger wrote:
> Note, however, that elsewhere the style guide (version 1.1.2) says "Classes 
> should generally not declare other classes," which is a bunch of bologna.  A 
> Puppetlabs employee told me recently that he would have that removed, but 
> evidently it hasn't happened yet.

I'm wondering if it would be better to say "classes should generally not 
*define* other classes," which I find a lot more objectionable.

-Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Conditionals within a class based of something else than facter variable

[Eric Shamow]

On Tuesday, July 3, 2012 at 5:31 AM, Itamar Landsman wrote:
> Hi All,
>  
> First I want to apologize, I never completely dove into the fine details of 
> puppet. I just use it on my network of +-100 VMs for odd jobs.
>  
> my question is: I know how to set up a class that would, for example, install 
> a package on a machine based on a facter variable (e.g. operating system 
> version).  
> within the curly braces I can even put a list of operation that would all not 
> be run if the machine in question does not conform to the specific variable.
>  
> I am looking for a way to do something similar using something like if a file 
> on the host exists (similar to the 'onlyif' that is available in the exec 
> type).
>  
> my dream is:
>  
> class foo{
>onlyif "test[ condition ]" {
>  file{.}
>  exec{...}
>}
> }

Itamar,

You should take a look at the Puppet Language Guide 
(http://docs.puppetlabs.com/guides/language_guide.html) - and in general the 
rest of the docs site, in particular Learning Puppet, which might help you with 
some of the fundamentals.

There are a number of ways to express what you are attempting to do, but you 
nearly have it.  If you have a fact "myfile_present" for which the value is 
true, for instance, you can do the following:

class foo {
  if $::myfile_present == true {
file { … }
exec { … }
  }
}

In the above mentioned Language Guide, check out the section on Conditionals.

-Eric

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Clarification Request: The need for ruby 1.8.7 on a RHEL/CentOS 5 Puppet Master

[Eric Shamow]

Dan,

Understood re running into problems and playing nice.  Haus' comment
stands, 1.8.5 works.

-Eric

On Tue, Jun 26, 2012 at 10:44 AM, Dan White  wrote:

> Thanks for the pointer, Eric, but I was able to build my own ruby 1.8.7
> from the rbel.frameos.org source RPM
>
> The problem is that it won't play nice with the other pieces I want to use.
> Maybe I could build passenger from source as well, but I'd rather work
> from binary RPM's as much as possible.
>
> If puppet won't break when I back down to ruby 1.8.5, that is my main
> concern.
>
> “Sometimes I think the surest sign that intelligent life exists elsewhere
> in the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
>
> - Eric Shamow  wrote:
> > Also as a note, there are (unofficial, but maintained by the CentOS
> > maintainer, Karanbir Singh) packages for RHEL 5 at:
> >
> > http://centos.karan.org/el5/ruby187/
> >
> > I've used these in production with much success.
> >
> > -Eric
> >
> >
> > On Tue, Jun 26, 2012 at 10:06 AM, Matthaus Litteken <
> matth...@puppetlabs.com
> > > wrote:
> >
> > > Yes, 1.8.5 will work with puppet 2.7.x. Here is a quick link to a
> > > supported ruby versions chart
> > > (http://docs.puppetlabs.com/guides/platforms.html#ruby-versions).
> > > 1.8.7 is better for various reasons, but 1.8.5 will work.
> > >
> > > HTH.
> > >
> > > On Tue, Jun 26, 2012 at 8:47 AM, Dan White  wrote:
> > > > I am stuck on RHEL 5 for the moment, and I am trying to set up a
> Puppet
> > > 2.7.x Master.
> > > > From this post (
> > >
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg27199.html ),
> > > > I got the impression that I needed ruby 1.8.7.  I tried to install
> > > passenger using the stealthymonkeys.com repo and it complained that it
> > > wants ruby 1.8.5 exactly (Processing Dependency: ruby = 1.8.5 for
> package:
> > > rubygem-passenger-native-libs).
> > > >
> > > > Looking back at the referenced mailing list item, it says that ruby
> > > 1.8.7 is needed for Dashboard and Foreman.
> > > > I am not using either of those.  Just plain old puppet with a dash of
> > > hiera.
> > > >
> > > > The Question: Is ruby 1.8.5 OK to use with puppet 2.7.x ?
> > > >
> > > > Thanks.
> > > >
> > > > “Sometimes I think the surest sign that intelligent life exists
> > > elsewhere in the universe is that none of it has tried to contact us.”
> > > > Bill Waterson (Calvin & Hobbes)
> > > >
> > > > --
> > > --
> > > Matthaus Litteken
> > > Release Manager, Puppet Labs
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Clarification Request: The need for ruby 1.8.7 on a RHEL/CentOS 5 Puppet Master

[Eric Shamow]

Also as a note, there are (unofficial, but maintained by the CentOS
maintainer, Karanbir Singh) packages for RHEL 5 at:

http://centos.karan.org/el5/ruby187/

I've used these in production with much success.

-Eric


On Tue, Jun 26, 2012 at 10:06 AM, Matthaus Litteken  wrote:

> Yes, 1.8.5 will work with puppet 2.7.x. Here is a quick link to a
> supported ruby versions chart
> (http://docs.puppetlabs.com/guides/platforms.html#ruby-versions).
> 1.8.7 is better for various reasons, but 1.8.5 will work.
>
> HTH.
>
> On Tue, Jun 26, 2012 at 8:47 AM, Dan White  wrote:
> > I am stuck on RHEL 5 for the moment, and I am trying to set up a Puppet
> 2.7.x Master.
> > From this post (
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg27199.html ),
> > I got the impression that I needed ruby 1.8.7.  I tried to install
> passenger using the stealthymonkeys.com repo and it complained that it
> wants ruby 1.8.5 exactly (Processing Dependency: ruby = 1.8.5 for package:
> rubygem-passenger-native-libs).
> >
> > Looking back at the referenced mailing list item, it says that ruby
> 1.8.7 is needed for Dashboard and Foreman.
> > I am not using either of those.  Just plain old puppet with a dash of
> hiera.
> >
> > The Question: Is ruby 1.8.5 OK to use with puppet 2.7.x ?
> >
> > Thanks.
> >
> > “Sometimes I think the surest sign that intelligent life exists
> elsewhere in the universe is that none of it has tried to contact us.”
> > Bill Waterson (Calvin & Hobbes)
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
>
> --
> Matthaus Litteken
> Release Manager, Puppet Labs
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Extending Puppet using Rubygems

[Eric Shamow]

Jason,

Packaging gems as OS packages is pretty easy to do. You can use gem2rpm on
RHEL systems or fpm (https://github.com/jordansissel/fpm) in the more
general case.

-Eric

On Tue, Jun 26, 2012 at 7:41 AM, Jason Slagle  wrote:

>
> On 06/25/2012 09:25 AM, Kelsey Hightower wrote:
>
>>
>> John you make a really good point. Rubygems support would be totally
>> optional. One of my hopes is that once people are able to use rubygems for
>> things like parser functions and report processors we start seeing more OS
>> packages built from those gems.
>>
>>
>>
> More useful might be a good and easy way to create OS packages to do
> plugins like this.
>
> That would solve some amount of the chicken and egg problem you see
> bootstrapping puppet clients that need certain plugins.
>
> I suspect this change will allow that since it will suck plugin stuff from
> a system location, so we don't have to go trying to create packages to
> throw stuff in $libdir?
>
> Thanks!
>
> Jason
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users+unsubscribe@**
> googlegroups.com .
> For more options, visit this group at http://groups.google.com/**
> group/puppet-users?hl=en
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] can we avoid notify/subscribe firing on a mode change?

[Eric Shamow]

Jo,

Let's not make this personal.  You don't know how old I am or what 
infrastructures I've managed.

You don't need to use Hiera.  You can use any data lookup tool you like to do 
the same thing.

What you are seeing is not an official stance of any kind, it's a spontaneous 
community reaction.  People aren't agreeing with you, which means you aren't 
arguing effectively.

Instead of making the case that someone else should do this, I recommend that 
you code up a solution and issue a pull request.  If the code looks valuable it 
can then be managed like any other feature or code request in Puppet.  

Clearly the community is not crying out for the solution as you've enunciated 
it.  Maybe you've enunciated it poorly.  In that case, write something to fix 
it and some demo usage.  Code wins arguments.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Monday, June 18, 2012 at 5:07 PM, Jo Rhett wrote:

> Right, sure.  Instead of 18 lines of puppet policy that do exactly what I 
> need, I should instead go create an infrastructure based around a barely 
> documentation and SLOW part of puppet.  Because who wants finer granularity 
> for your controls, when you could implement a huge infrastructure instead?
> 
> I take it you are a bit too young to have watched companies go out and 
> implement Active Directory to solve a minor technical problem, aren't you?  
> There is no value in implementing an infrastructure with its own requirements 
> for redundancy and its own dependancies to solve something you can code in an 
> hour.
> 
> On Jun 18, 2012, at 4:27 PM, Eric Shamow wrote:
> > No - if it's that small and simple, the data bout which host is in which 
> > should be in your source of truth, CMDB, etc - and Puppet should read that 
> > data and determine which attribute or set of attributes (or resources) is 
> > applied based on that.
> > 
> > You can do this today with hiera and conditionals.
> > 
> > -- 
> > 
> > Eric Shamow
> > Professional Services
> > http://puppetlabs.com/
> > (c)631.871.6441
> >  
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> 
> -- 
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] can we avoid notify/subscribe firing on a mode change?

[Eric Shamow]

On Monday, June 18, 2012 at 4:04 PM, Jo Rhett wrote:
> Same software, same management functions, same configs… just a different 
> permissions change on new installations. Should I really duplicate the entire 
> module, and manage all changes in both places?  And forever try to manage 
> which host should be in which generation?

No - if it's that small and simple, the data bout which host is in which should 
be in your source of truth, CMDB, etc - and Puppet should read that data and 
determine which attribute or set of attributes (or resources) is applied based 
on that.

You can do this today with hiera and conditionals.

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441
  

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] can we avoid notify/subscribe firing on a mode change?

[Eric Shamow]

On Monday, June 18, 2012 at 1:07 PM, Jo Rhett wrote:
> *boggle* Um, so your configuration management system is not part of your 
> change management implementation? That's what you just said, and it makes no 
> sense.

Jo,

Not to speak for David but in general - the point is that they are different 
components of an interlocking whole.

In the cases you are discussing (conflict between multiple groups working on 
related systems) you need to implement better change control or CI.  While 
Puppet works quite well with those technologies, we don't yet provide tooling 
around git/svn/choose your tool VCS, nor do we provide the workflow itself.

In terms of conflicting changes, you really need code review, CI, or preferably 
both.  That's how large organizations handle scale.  Trying to force the tool 
to solve development problems isn't going to work.

Look at how development teams solve the same problems.  They don't do it by 
refusing to build a new daily snapshot of parts of the software.

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet / scalability

[Eric Shamow]

Nigel,

Don't we have one or two an order of magnitude larger than that?

http://indico.cern.ch/getFile.py/access?contribId=29&sessionId=3&resId=3&materialId=slides&confId=160737
 (warning: large PDF)

I think they're looking at 300K or so.  And I believe we have a few more at 
that size as well.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Monday, May 14, 2012 at 12:35 PM, Nigel Kersten wrote:

> 
> 
> On Sun, May 13, 2012 at 11:53 PM, Alex Harvey  (mailto:alexharv...@gmail.com)> wrote:
> > Hi list,
> > 
> > I am looking at configuration management tool options.
> > 
> > I have a large fleet (> 3,000 hosts) and highly heterogeneous
> > (RHEL3-5, CentOS, 5RH7, Solaris 10 LDOMs/zones, Solaris 8-9, AIX 5.3 &
> > 6.1 LPARs, HP-UX & Tru64 + Windows).  We care mainly about RHEL and
> > new versions of Solaris & AIX but ability to compile on older versions
> > is an advantage.  Probably, the Windows will be managed by SCCM.
> > 
> > I have read that Puppet could have scalability problems to a site as
> > large as ours.  To keep this simple, I'd like feedback on whether that
> > is likely to be true for us.
> > 
> > A rep from CFengine has told me that ours would be the largest Puppet
> > site in the world (I think that's not true).  Could someone confirm?
> 
> There are at least a couple of deployments that are more like 30k hosts than 
> 3k 
> 
> It's absolutely not true. 
> 
>  
> > 
> > General feedback also welcome.
> > 
> > Kind regards,
> > Alex Harvey
> > 
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users%2bunsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> > 
> 
> 
> 
> -- 
> Nigel Kersten | http://puppetlabs.com | @nigelkersten
> Schedule Meetings at: http://tungle.me/nigelkersten
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Managing system yum repositories with yumrepo cache issues

[Eric Shamow]

Just a note - it's better to do yum clean metadata than all in most cases.  

There's no reason to drop all that cached package stuff - you just want to get 
rid of the repo index.  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Friday, May 4, 2012 at 5:11 PM, Jo Rhett wrote:

> I just have it run a "yum clean all" exec command every time a repo is 
> updated.  Since they all refer to the same exec, it only happens once after 
> the repos are updated.
>  
> The tricky part is ensuring that anything trying to update software in the 
> same run has a require=> set that ensures all the yum repos and the yum clean 
> all are completed before they run, or you get:
>  
> update yum repo
> update package
> yum clean all
> ….
>  
> I just require the entire yumrepo class, but there may be better ways.
>  
> On May 4, 2012, at 6:54 AM, Andy Taylor wrote:
> > I'm trying to get my yum module to manage system repositories like
> > CentOS-Base. My yum module is part of a pre run stage so it puts the
> > necessary repositories in place before other modules try to install
> > anything.
> >  
> > I've just run into a problem though; when Puppet installs a repo via
> > yumrepo, it doesn't clear the yum cache. This means that when the
> > modules in the main stage start trying to install packages, many will
> > error as yum doesn't see the new respositories.
> >  
> > Running yum clean metadata fixes this, but I'm not sure how best to
> > automate it in the module. I don't want to turn metadata caching off,
> > or have a regular cron flushing it as I've seeen suggested before - an
> > exec subscribed to /etc/yum.repos.d would be perfect, but that doesn't
> > work.
> >  
> > I'm posting this here prior to putting something in the Puppet Labs
> > bug tracker, as either a feature request or a bug (I think it's fairly
> > essential that adding repositories leads to a refresh of yum cache...
> > shouldn't really have to work around it in my opinion)
> >  
> > Thanks!
> >  
> > Andy
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> >  
>  
> --  
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
>  
>  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Determining if hiera (or any function) is installed on a node

[Eric Shamow]

As a +1 on this (and as the guy who wrote safe_hiera) --

It shouldn't be a function, the safety should be wrapped into hiera.  But yes, 
this will get you the right syntax so you can just search/replace safe_hiera 
for hiera once it's fixed.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Tuesday, April 17, 2012 at 12:29 PM, Gary Larizza wrote:

> Hey Geoff,
> 
> We actually had a talk about this.  There is this code that will help catch 
> that scenario FOR NOW -->  https://github.com/puppetlabs/hiera-puppet/pull/23 
> 
> I believe this is a bug and should DEFINITELY be fixed in source.  Until 
> then, the 'safe_hiera()' function allows you to make this check.   
> 
> 
> 
> On Tue, Apr 17, 2012 at 12:21 PM, Geoff Davis  (mailto:gada...@ucsd.edu)> wrote:
> > Alas that doesn't work as the manifest fails to compile properly without 
> > the /etc/puppet/hiera.yaml file being there.
> > 
> > Nan's code does provide defaults for the hiera lookups similar to what you 
> > are doing below, but the compiler balks before they are even evaluated.
> > 
> > Here's the version of staging/init.pp that generated the error below: 
> > https://github.com/nanliu/puppet-staging/blob/5e1a8763ae36c2ea21c0a5b6a1f0e586e077f0fd/manifests/init.pp
> >  
> > 
> > Note that all of the hiera calls have defaults.
> > 
> > Geoff Davis
> > Scripps Institution of Oceanography
> > gada...@ucsd.edu (mailto:gada...@ucsd.edu), (858) 822-5756 
> > (tel:%28858%29%20822-5756)
> > 
> > 
> > 
> > On Apr 17, 2012, at 12:14 PM, Gary Larizza wrote:
> > > Hey Geoff,
> > > 
> > > I see that as two separate steps (Is Hiera enabled and is Hiera 
> > > configured).  I think the function satisfies the former, but you might 
> > > want to write your own check for the latter (as each person probably 
> > > interprets 'configured' differently).  You could do a check like: 
> > > 
> > > if function_available('hiera') and hiera('hiera_enabled', false) {
> > >   
> > > } else {
> > >   
> > > }
> > > 
> > > This would do a hiera lookup for a parameter 'hiera_enabled' that could 
> > > be set in your common/global.yaml file (while defaulting to false if it's 
> > > not found).
> > > 
> > > 
> > > 
> > > On Tue, Apr 17, 2012 at 12:09 PM, Geoff Davis  > > (mailto:gada...@ucsd.edu)> wrote:
> > > > I've found a potential issue, but I'm not sure if this is within the 
> > > > scope of function_available or not.
> > > > 
> > > > The vagrant basebox I'm using actually does ship with puppet-hiera, but 
> > > > there's no /etc/puppet/hiera.yaml 
> > > > 
> > > > Thus, even though function_available('hiera') returns true, the 
> > > > function isn't actually usable:
> > > > 
> > > > Hiera config file /etc/puppet/hiera.yaml not readable at 
> > > > /tmp/vagrant-puppet/modules-0/staging/manifests/init.pp:31 on node 
> > > > centos-6-vagrant.vagrantup.com (http://centos-6-vagrant.vagrantup.com/) 
> > > > 
> > > > Is there a way to check whether the function is actually usable as well?
> > > > 
> > > > Geoff Davis
> > > > Scripps Institution of Oceanography
> > > > gada...@ucsd.edu (mailto:gada...@ucsd.edu), (858) 822-5756 
> > > > (tel:%28858%29%20822-5756)
> > > > 
> > > > 
> > > > 
> > > > On Apr 17, 2012, at 11:56 AM, Ken Barber wrote:
> > > > > I'm going to review this now. Its destined for master, so someone from
> > > > > the release team can probably comment on the next major release
> > > > > schedule for stdlib.
> > > > > 
> > > > > On Tue, Apr 17, 2012 at 7:35 PM, Geoff Davis  > > > > (mailto:gada...@ucsd.edu)> wrote:
> > > > > > That's what I'm looking for. I'll fold in that branch into my 
> > > > > > testing until
> > > > > > it goes mainline.
> > > > > > 
> > > > > > Any ETA on it going mainline?
> > > > > > 
> > > > > > 
> > > > > > On Apr 17, 2012, at 11:14 AM, Nigel Kersten wrote:
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > On Tue, Apr 17, 2012 at 1

Re: [Puppet Users] Getting started

[Eric Shamow]

Jo,

Very good advice - Rodrick, I'd try the Learning Puppet VM to start and get 
used to the tool first.  There's an excellent Learning Puppet doc as well -

http://docs.puppetlabs.com/learning/

That should get you started.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, April 5, 2012 at 5:14 PM, Jo Rhett wrote:

> You've probably gone about this the hard way.  It would be best to just get 
> the server running without passenger and learn Puppet itself.  You only need 
> passenger when you exceed 50-100 systems.  
>  
> Anyway, to answer your questions the config.ru (http://config.ru) is 
> available in share/puppet (exactly where depending on your OS), and 
> puppetmaster.conf should have been installed when the gem/rpm was installed. 
> But you should probably be using the docs on www.puppetlabs.com 
> (http://www.puppetlabs.com) rather than the PDF, I suspect they are kept more 
> up to date.
>  
> On Apr 5, 2012, at 1:42 PM, Brown, Rodrick wrote:
> > I really hate poor documentation.
> >   
> > I’m following along in PDF documentation I downloaded from the official 
> > site and I’m stuck after I installed rack & passenger modules from rubygems.
> > I ran the passenger build script and it compiled and installed into my 
> > local apache httpd server successfully.
> >   
> > Now where do I find an working example of puppetmaster.conf ?
> > Which config.ru (http://config.ru) should I be coping into 
> > /usr/share/puppet/rack/puppetmasterd ?
> >   
> > Is there a guide on generate the pem files required for use when defining 
> > the virtual host settings in puppetmaster?
> >   
> > I’m almost fed-up already and I’ve not even gotten 1 agent configured to 
> > talk to my sever   
> >   
> > Puppet seems way too clumber some with the amount of dependencies required 
> > so far.   
> >   
> > I almost feel like going back to hacking on my system based on Python & 
> > Fabric L
> >   
> > --RB
> >  
> >  
> > Please visit our website for important disclaimers/disclosures regarding 
> > Knight’s products and services:
> >  
> > http://knight.com/KnightEmailDisclaimer.html
> >  
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
>  
> --  
> Jo Rhett
> Net Consonance : consonant endings by net philanthropy, open source and other 
> randomness
>  
>  
>  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] stdlib module not working

[Eric Shamow]

Stefan,

Looks related to https://projects.puppetlabs.com/issues/13530, which I just 
opened.

Make sure you ensure => present in the file_line resource.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, March 29, 2012 at 6:17 PM, Dan White wrote:

> Why not use host instead of file_line ?
>  
> http://docs.puppetlabs.com/references/latest/type.html#host
>  
> host { 'puppet master host entry':
> ip => '172.16.240.200',
> name => 'master.dev.puppetlabs.com (http://master.dev.puppetlabs.com)',
> host_aliases => ['master'],
> }
>  
> On Mar 29, 2012, at 11:08 AM, Stefan Wiederoder wrote:
>  
> > I´m trying to utilize the new stdlib module, but got stuck after 
> > installation on my puppet server.
> >  
> > I´ve tried to use the included test file file_line.pp on the server, but 
> > it´s only creating the file - but not managing the content.
> >  
> > the same problem on my clients (the new provider file_line has been 
> > synced), it´s just not working:
> >  
> > file_line { 'puppet master host entry':
> > line => '172.16.240.200 master.dev.puppetlabs.com 
> > (http://master.dev.puppetlabs.com) master',
> > path => '/etc/hosts',
> > }
> >  
> > do you have any Ideas what´s wrong?
> >  
> > thanks
> > ,
> > Stefan
> >  
>  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>  
>  


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: vmware provisioning

[Eric Shamow]

Indeed, at $(job - 1) we implemented something to do this pretty quickly, 
although not with the flexibility of cloud provisioner.

In theory it should be easy to write something through the cloud provisioning 
framework that takes even less time and is more flexible than our tools, but 
it's a fairly straightforward task.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Wednesday, February 15, 2012 at 5:36 PM, Brian Gupta wrote:

> Foreman has support for this. (Tied into Foreman provisioning workflow). I am 
> unaware of any other support for VMware provisioning in the open source 
> Puppet world, but in theory it shouldn't be too hard to write.
> 
> -Brian
> 
> On Wed, Feb 15, 2012 at 3:55 PM, Luke  (mailto:lutay...@gmail.com)> wrote:
> > Just to clarify,
> > 
> > We currently have centos templates in ESX that we manually clone to VM
> > and configure (add HD network etc) then kick off puppet. We would like
> > to automate these initial steps.
> > 
> > On Feb 15, 4:30 pm, Luke mailto:lutay...@gmail.com)> 
> > wrote:
> > > Does anyone know of a module that will spin up and configure a centos
> > > vmware template? I see options with PE any with the open source
> > > version?
> > 
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users%2bunsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> > 
> 
> 
> 
> -- 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Question about reusing classes/modules

[Eric Shamow]

I would avoid this approach - global variables aren't a good idea.

Hiera would be a better approach:

http://www.devco.net/archives/2011/06/05/hiera_a_pluggable_hierarchical_data_store.php
http://www.devco.net/archives/2011/06/06/puppet_backend_for_hiera.php

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Saturday, February 11, 2012 at 7:08 PM, krish wrote:

> > My scenario is this: I have 4 environments, Dev, Test, QA, Prod. Each
> > of these environments lives in 2 sites, LA and NY. I have 5
> > applications that are site and env specific.
> > 
> > I want to use puppet to template-ize the config files that is required
> > for each env, per site, per app, so 40 files.
> > 
> > The config file is basically key=value pairs. Here's a simple example
> > of what each file may look like:
> > 
> > site=LA
> > env=Dev
> > app=App1
> > masterServer=host1
> > clientServer1=host2
> > clientServer2=host3
> > 
> 
> 
> 
> How about having these key value pairs in site.pp with a case environment
> Then they become global to all modules.
> 
> 
> 
> -- 
> Krish
> olindata.com (http://olindata.com)
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Odd behavior with hiera 0.3.0

[Eric Shamow]

To add: there's a reason for this - you are likely running the command line 
tool on the master, where facter output does not match what it would be when 
evaluating a client.

So you are essentially saying "for a client that looks like X, what would hiera 
tell me?"

One thought would be to write a quick script to grab the cached facts for a 
node and turn the relevant ones into hiera parameters, then use this to run 
hiera against an individual host.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, February 9, 2012 at 10:52 AM, Eric Shamow wrote:

> Hiera as a command line tool is unaware of the $::operatingsystem variable 
> available to Puppet as a fact.  So when running through puppet, 
> operatingsystem would be a known value, but when running through the command 
> line, you need to specify whatever information hiera needs to parse.
> 
> -Eric 
> 
> -- 
> 
> Eric Shamow
> Professional Services
> http://puppetlabs.com/
> (c)631.871.6441
> 
> 
> On Thursday, February 9, 2012 at 10:49 AM, windowsrefund wrote:
> 
> > $ cat /etc/hiera.yaml
> > ---
> > :hierarchy:
> > - %{operatingsystem}
> > - common
> > :backends:
> > - yaml
> > :yaml:
> > :datadir: /tmp/hieradata
> > 
> > $ cat /tmp/hieradata/Debian.yaml
> > ---
> > kitty : 'Handsome'
> > 
> > $ cat /tmp/hieradata/common.yaml
> > ---
> > kitty : 'Evil'
> > 
> > $ facter operatingsystem
> > Debian
> > 
> > $ hiera -d kitty
> > DEBUG: Thu Feb 09 10:09:01 -0500 2012: Hiera YAML backend starting
> > DEBUG: Thu Feb 09 10:09:01 -0500 2012: Looking up cat in YAML backend
> > DEBUG: Thu Feb 09 10:09:01 -0500 2012: Looking for data source common
> > Evil
> > 
> > $ hiera -d kitty operatingsystem=Debian
> > DEBUG: Thu Feb 09 10:46:20 -0500 2012: Hiera YAML backend starting
> > DEBUG: Thu Feb 09 10:46:20 -0500 2012: Looking up cat in YAML backend
> > DEBUG: Thu Feb 09 10:46:20 -0500 2012: Looking for data source Debian
> > Handsome
> > 
> > Shouldn't Debian.yaml take priority over common.yaml though? Not sure
> > why I need to pass operatingsystem=Debian in as an argument to hiera
> > 
> > Best,
> > Adam
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> > 
> > 
> > 
> 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Odd behavior with hiera 0.3.0

[Eric Shamow]

Hiera as a command line tool is unaware of the $::operatingsystem variable 
available to Puppet as a fact.  So when running through puppet, operatingsystem 
would be a known value, but when running through the command line, you need to 
specify whatever information hiera needs to parse.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, February 9, 2012 at 10:49 AM, windowsrefund wrote:

> $ cat /etc/hiera.yaml
> ---
> :hierarchy:
> - %{operatingsystem}
> - common
> :backends:
> - yaml
> :yaml:
> :datadir: /tmp/hieradata
> 
> $ cat /tmp/hieradata/Debian.yaml
> ---
> kitty : 'Handsome'
> 
> $ cat /tmp/hieradata/common.yaml
> ---
> kitty : 'Evil'
> 
> $ facter operatingsystem
> Debian
> 
> $ hiera -d kitty
> DEBUG: Thu Feb 09 10:09:01 -0500 2012: Hiera YAML backend starting
> DEBUG: Thu Feb 09 10:09:01 -0500 2012: Looking up cat in YAML backend
> DEBUG: Thu Feb 09 10:09:01 -0500 2012: Looking for data source common
> Evil
> 
> $ hiera -d kitty operatingsystem=Debian
> DEBUG: Thu Feb 09 10:46:20 -0500 2012: Hiera YAML backend starting
> DEBUG: Thu Feb 09 10:46:20 -0500 2012: Looking up cat in YAML backend
> DEBUG: Thu Feb 09 10:46:20 -0500 2012: Looking for data source Debian
> Handsome
> 
> Shouldn't Debian.yaml take priority over common.yaml though? Not sure
> why I need to pass operatingsystem=Debian in as an argument to hiera
> 
> Best,
> Adam
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Looping in Ruby DSL

[Eric Shamow]

Sateesh,

It is better if you don't look at it as a "loop."  A loop is a very procedural 
concept.  You are working with a machine that you are trying to get into a 
fixed state.

So better to think "I want to have a bunch of similar-looking resources that 
are identified and enumerated in an array."

This leads you to defined types: 
http://docs.puppetlabs.com/learning/definedtypes.html

Which is probably the way you should do this.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Wednesday, February 8, 2012 at 11:46 PM, sateesh wrote:

> Hi John,
> 
> Thank you for your response.
> 
> I am using the Ruby DSL, as I need to loop some exec commands for
> which there will be some IP adress array that will be passed. Please
> find below my actual code:
> 
> hostclass :swift::proxy-ring do
> require "swift::common"
> 
> $storage_local_net_ip = ['IP1','IP2'] #this may contain n number of
> IPs.
> 
> $zone = 0
> $storage_local_net_ip.each do |sip|
> $zone = $zone + 1
> # adding entries to each ring
> create_resource :exec, "ring_account_entry",
> :command => "swift-ring-builder account.builder add z#{$zone}-
> #{sip}:6002/sdb1 100",
> :cwd => "/etc/swift",
> :require => Class['swift::proxy-install'],
> :returns => [0,1],
> :path => ["/bin", "/sbin", "/usr/bin", "/usr/sbin"]
> 
> create_resource :exec, "ring_container_entry",
> :command => "swift-ring-builder container.builder add z#{$zone}-
> #{sip}:6001/sdb1 100",
> :cwd => "/etc/swift",
> :require => Class['swift::proxy-install'],
> :returns => [0,1],
> :path => ["/bin", "/sbin", "/usr/bin", "/usr/sbin"]
> 
> create_resource :exec, "ring_object_entry",
> :command => "swift-ring-builder object.builder add z#{$zone}-
> #{sip}:6000/sdb1 100",
> :cwd => "/etc/swift",
> :require => Class['swift::proxy-install'],
> :returns => [0,1],
> :path => ["/bin", "/sbin", "/usr/bin", "/usr/sbin"]
> end
> 
> end
> 
> so, How can we write this in Puppet DSL. Please give me a sample for
> this. I am newbie to Puppet. So I am unable to understand how to loop
> this.
> 
> Thanks,
> Sateesh B.
> 
> On Feb 8, 9:50 pm, jcbollinger  (http://stJude.org)> wrote:
> > On Feb 8, 4:11 am, sateesh http://gmail.com)> 
> > wrote:
> > 
> > 
> > 
> > > Hi,
> > 
> > > I have written a sample manifest in puppet using Ruby DSL. I want to
> > > build a looping functionality. But I am getting problem as shown
> > > below:
> > > 
> > 
> > 
> > > root@puppet-swproxy:/tmp# cat test.rb
> > > hostclass :test do
> > > $abc = ["a","b"]
> > > $abc.each do |sip|
> > >   create_resource :exec, "echoabc", :command => "echo #{sip}"
> > > end
> > > 
> > 
> > 
> > > file "/tmp/testecho.txt", :content => "This is test file", :require =>
> > > Exec['echoabc']
> > > end
> > > 
> > 
> > 
> > > node "default" do
> > > include "test"
> > > end
> > > root@puppet-swproxy:/tmp# puppet apply --verbose test.rb
> > > Duplicate definition: Exec[echoabc] is already defined on node puppet-
> > > swproxy.persistent.co.in (http://swproxy.persistent.co.in)
> > > 
> > 
> > 
> > This is not a problem with looping per se.  In fact, it shows that
> > your looping construct is itself working exactly the way it should.
> > 
> > > I can make the echoabc as dynamic,
> > 
> > And you need to do that, because every resource in the compiled
> > catalog needs a distinct title.
> > 
> > >   but how can specify that in require
> > > in next statement (file). I need to execute the file only after
> > > executing the exec.
> > > 
> > 
> > 
> > You need to manage the file only after executing *which* Exec?  You
> > declare two distinct ones, even if you try to give them the same
> > title.
> > 
> > > So what I need to do. Generall the puppet will not
> > > run in the synchronized way. I observed that the statements are
> > > executed asynchronously.
> > > 
> > 
> > 
> > Puppet runs completely synchronously, but the order in which it
> > applies r

Re: [Puppet Users] Re: define hostclass with special characters

[Eric Shamow]

Sateesh,

Still not following why you need to use the Ruby DSL.

There are many great reasons to ultimately use the Ruby DSL, but right now you 
are seemingly struggling to learn/understand Puppet fundamentals.  I would 
strongly suggest that the Puppet DSL is there for a reason - it will help you 
structure your thinking to match the infrastructure you're working with.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Wednesday, February 8, 2012 at 11:37 PM, sateesh wrote:

> Hi John,
> 
> I have solve that class issue. I have specified that as
> hostclass :'swift::proxy-ring' and it worked. My problem is I have to
> run the exec command in the script for which the Class "swift::proxy-
> install" is required. So, in general puppet DSL we will write that as
> follows:
> 
> exec {"somelabel":
> command => "command here",
> require => Class['swift::proxy-install']
> }
> 
> I need the equivalent Ruby DSL code. I have written the following:
> 
> create_resource :exec, "some label", :command => "command
> here", :require => Class['swift::proxy-install'].
> 
> Here I got error because I place Class['swift::proxy-install'] in
> require attribute. As Class is pre-defined in Ruby, we need to write
> it another way in Puppet DSL. I want that statement in Ruby DSL.
> 
> Thanks in advance,
> Sateesh B.
> 
> On Feb 8, 10:19 pm, jcbollinger  (http://stJude.org)> wrote:
> > On Feb 8, 7:31 am, Walter Heck http://gmail.com)> 
> > wrote:
> > 
> > > Also no idea what you are trying to do, but your manifest should have
> > > .pp as it's extension.
> > > 
> > 
> > 
> > > On Wed, Feb 8, 2012 at 15:27, Felix Frank
> > 
> > > http://felix.fr)...@alumni.tu-berlin.de 
> > > (http://alumni.tu-berlin.de)> wrote:
> > > > On 02/08/2012 02:19 PM, sateesh wrote:
> > > > > Please give me any example for implementing this. Also when I am
> > > > > writing Puppet DSL, it is allowing me the dashes.
> > > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > > > Sorry, I have no idea what you're trying to do. I never heard of
> > > > "hostclass".
> > > > 
> > > 
> > 
> > 
> > He is writing in Ruby DSL, not Puppet DSL, which is why the file has
> > extension .rb.  "hostclass" in Ruby DSL is analogous to "class" in
> > Puppet DSL.
> > 
> > I am by no means well-versed in Ruby DSL, but it seems suspicious to
> > me that he is passing a String object to the hostclass() function when
> > that function's usual first argument is a symbol.  It is possible that
> > manually converting the string to a symbol would solve the issue:
> > 
> > hostclass "swift::proxy_ring".to_sym do
> > # ...
> > end
> > 
> > Of course, that begs the question of why he wouldn't just write
> > 
> > hostclass :'swift::proxy_ring' do
> > # ...
> > end
> > 
> > My Ruby-fu is mediocre at best, but I think the quotes are required
> > because the symbol's string value contains colons.  The initial colon
> > is definitely required as part of the syntax for a symbol literal.
> > 
> > John
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] copying file(s) from agent to master??

[Eric Shamow]

Filebucket is the right answer.  Good docs on it here:

http://docs.puppetlabs.com/references/stable/type.html#file

And also the command-line utility to query or manage the bucket:

http://docs.puppetlabs.com/man/filebucket.html

-Erc 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Monday, January 9, 2012 at 11:14 AM, Christopher Johnston wrote:

> I think you want to use the filebucket setup for this, I am not 100% familiar 
> with it though.
> 
> On Mon, Jan 9, 2012 at 10:50 AM, Sans  (mailto:r.santanu@gmail.com)> wrote:
> > Is there a way to copy file(s) from the Puppet agent back to the
> > master? I know it sounds silly but that's what I need to do. This is
> > one of the s/w-tag files, gets created/modified automatically by the
> > software installation job and then I want to overwrite the tag files
> > on two other agents with this one. Is there a why for doing this?
> > 
> > Cheers,
> > San
> > 
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users%2bunsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> > 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] ETA for 2.7.10 ?

[Eric Shamow]

Jo,

You can find the description of Puppet's release process here:

http://groups.google.com/group/puppet-users/browse_thread/thread/3d703849246bd43f/c98d096d51ed221e

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, January 5, 2012 at 3:54 PM, Jo Rhett wrote:

> I've seen quite a few bug reports fly by and comments from puppet labs saying 
> "will be fixed in next version".  Do we have an eta just yet for 2.7.10?
> 
> Obviously, "when it's ready applies" -- I'm just curious if you are in 
> shake-down for 2.7.10 already or if you know right now that it's more than a 
> week away.
> 
> -- 
> Jo Rhett
> Net Consonance : consonant endings by net philanthropy, open source and other 
> randomness
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Issue with RPM dependency issue

[Eric Shamow]

I've run into this before.

The trick is to ensure that the Percona client is available and installed first 
and let *it* pull in perl-DBD-MySQL.  If you install perl-DBD-MySQL first, it 
will often attempt to directly grab the RPM that best meets its requirements, 
which is the standard MySQL package.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Wednesday, November 23, 2011 at 9:25 AM, jcbollinger wrote:

> 
> 
> On Nov 22, 8:43 am, TisMe http://gmail.com)> wrote:
> > I am running into an issue with perl-DBD-MySQL dependency with mysql
> > in CentOS 5.7.
> > 
> > I am trying to remove the mysql client and replace it with with
> > percona version of the mysql client.
> > 
> > It will not let me remove the mysql client because of that
> > dependency.  I have already defined perl-DBD-MySQL in a different
> > class...  I would rather not create an Exec[""].  I would rather do
> > that as a last resort.
> > 
> > Anyone have any suggestions with this?
> 
> 
> It would be easier if I didn't have to guess at what the actual issue
> is, but I think I can at least talk in the right general direction:
> 
> 1) CentOS 5 package perl-DBD-MySQL depends on at least one feature
> provided by package mysql, the distro's standard mysql client.
> Therefore,
> 
> 2) your options depend on (a) whether you want to keep perl-DBD-MySQL
> and (b) whether the percona client provides all the features perl-DBD-
> MySQL normally gets from package mysql.
> 
> Case 1: You don't need perl-DBD-MySQL or anything that depends on it
> In this case, you can cause puppet to remove the package, preferrably
> by declaring that resource with "ensure => absent". You must then
> also set up Puppet relationships so that Package['perl-DBD-MySQL'] is
> applied *before* Package['mysql'].
> 
> Case 2: You need to keep perl-DBD-MySQL, and
> 
> Case 2a: the percona client provides all the resources perl-DBD-MySQL
> needs.
> In this case, set up relationships so that the percona package is
> installed before Package['mysql'] is removed. Alternatively, consider
> whether you need to remove Package['mysql'] at all -- perhaps you can
> have both clients installed side by side. If you need to remove the
> standard client and install the percona one in the same yum
> transaction, however, then you are probably stuck with using the yum
> shell via an Exec.
> 
> Case 2b: the percona client does not provide all the resources perl-
> DBD-MySQL needs.
> In this case, your only possible option is to leave Package['mysql']
> installed and install the percona client alongside it. If that
> doesn't work then you're hosed (and Puppet has nothing to do with it).
> 
> 
> John
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 
> 


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Installing Oracle

[Eric Shamow]

Douglas,

https://github.com/jordansissel/fpm

It's pretty good at quick and dirty package building.

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Saturday, November 19, 2011 at 1:44 PM, Douglas Garstang wrote:

> Ashely,
> 
> Not familiar with fpm. What is it? Are you saying you installed
> Oracle, and then use fpm (rpm?) to create a package from the installed
> files? I thought about that... this approach would work if installing
> Oracle meant just installing files, but what if the installer executes
> scripts etc that are machine dependent?
> 
> Doug.
> 
> On Sat, Nov 19, 2011 at 11:43 AM, Ashley Penney  (mailto:apen...@gmail.com)> wrote:
> > This is not what you want to hear but I ended up installing oracle with the
> > installer and then using "fpm" to bundle the entire thing into (two, because
> > it's too goddamn big) rpms.  I had no luck doing the installer via Puppet so
> > I just cheated.
> > 
> > On Sat, Nov 19, 2011 at 1:11 PM, Douglas Garstang  > (mailto:doug.garst...@gmail.com)>
> > wrote:
> > > 
> > > That's what I am already using.
> > > 
> > > On Fri, Nov 18, 2011 at 6:33 PM, Mohamed Lrhazi  > > (mailto:lrh...@gmail.com)> wrote:
> > > > Maybe you need something like this:
> > > > http://www.oracle-base.com/articles/misc/OuiSilentInstallations.php
> > > > 
> > > > 
> > > > On Fri, Nov 18, 2011 at 9:23 PM, Douglas Garstang
> > > > mailto:doug.garst...@gmail.com)> wrote:
> > > > > This is pretty ugly.
> > > > > 
> > > > > I'm using puppet to install Oracle, ie an exec{} wrapped around:
> > > > > 
> > > > > /u01/oracle_extract/linux.x64_11gR2_database/database/runInstaller
> > > > > -silent -responseFile /etc/oracle_response.rsp
> > > > > 
> > > > > The problem is that the damn installer backgrounds itself and returns
> > > > > control to the shell. I tried putting the above command in a script,
> > > > > followed by a wait command, but that didn't help. Has anyone got any
> > > > > ideas how I can automate the installation of Oracle with puppet?
> > > > > 
> > > > > I need to know when the install is finished, because there's
> > > > > additional commands that need to be run by root, as advised by the
> > > > > installer, when it's complete.
> > > > > 
> > > > > Doug.
> > > > > 
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > > > Groups "Puppet Users" group.
> > > > > To post to this group, send email to puppet-users@googlegroups.com 
> > > > > (mailto:puppet-users@googlegroups.com).
> > > > > To unsubscribe from this group, send email to
> > > > > puppet-users+unsubscr...@googlegroups.com 
> > > > > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > > > > For more options, visit this group at
> > > > > http://groups.google.com/group/puppet-users?hl=en.
> > > > > 
> > > > 
> > > > 
> > > > --
> > > > You received this message because you are subscribed to the Google
> > > > Groups "Puppet Users" group.
> > > > To post to this group, send email to puppet-users@googlegroups.com 
> > > > (mailto:puppet-users@googlegroups.com).
> > > > To unsubscribe from this group, send email to
> > > > puppet-users+unsubscr...@googlegroups.com 
> > > > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > > > For more options, visit this group at
> > > > http://groups.google.com/group/puppet-users?hl=en.
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > --
> > > Regards,
> > > 
> > > Douglas Garstang
> > > http://www.linkedin.com/in/garstang
> > > Email: doug.garst...@gmail.com (mailto:doug.garst...@gmail.com)
> > > Cell: +1-805-340-5627
> > > 
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Puppet Users" group.
> > > To post to this group, send email to puppet-users@googlegroups.com 
> > > (mailto:puppet-users@googlegroups.com).
> > > To unsubscribe from this group, send email to
> > > puppet-users+unsubscr...@googlegroups.com 
> > > 

Re: [Puppet Users] [foreman-users] dropping support for ruby 1.85?

[Eric Shamow]

To Mike's point, I backported from f13 or 14 SRPMs - can't remember which - 
with great regularity and very little problem to RHEL 5.

Haven't done it in ages but it's not too bad.  And where that fails, gem2rpm…

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Thursday, November 17, 2011 at 2:49 PM, Aaron Grewell wrote:

> I'm not sure about the Ruby packages specifically, but Fedora has
> diverged so much from RHEL5 that building recent packages is a major
> undertaking. You'd probably be better off with tarballs and FPM.
>  
> On Thu, Nov 17, 2011 at 2:42 PM, Michael Stahnke  (mailto:stah...@puppetlabs.com)> wrote:
> > On Thu, Nov 17, 2011 at 11:34 AM, Jo Rhett  > (mailto:jrh...@netconsonance.com)> wrote:
> > > On Nov 17, 2011, at 11:02 AM, Ohad Levy wrote:
> > >  
> > > On Thu, Nov 17, 2011 at 8:55 PM, Jo Rhett  > > (mailto:jrh...@netconsonance.com)> wrote:
> > >  
> > > On Nov 17, 2011, at 10:30 AM, Ohad Levy wrote:
> > >  
> > > if its not clear, what it means, is that if you want to run it on
> > >  
> > > RHEL5, you can either keep running the current 0.4.x  versions or
> > >  
> > > upgrade your ruby stack. otherwise use a more recent distribution.
> > >  
> > > Given that "upgrading the ruby stack" means either "build your own RPMs 
> > > from
> > >  
> > > scratch" or "download from a random internet site" this is going to limit
> > >  
> > > the number of sites which can do this.
> > >  
> > > Since we understand its a pain upgrading to a newer distribution,
> > > we've built a puppet module which helps with foreman installation...
> > > if you have any better ideas of how we can try helping our ruby
> > > community…
> > >  
> > > Um… as I suggested, provide el5 rpms of ruby 1.8.7 and the various gems?
> > > Myself, I'm looking at this right now -- but open to better options:
> > >  https://github.com/largon/centos-ruby-spec_files
> > > --
> > > Jo Rhett
> > > Net Consonance : consonant endings by net philanthropy, open source and
> > > other randomness
> > >  
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Puppet Users" group.
> > > To post to this group, send email to puppet-users@googlegroups.com 
> > > (mailto:puppet-users@googlegroups.com).
> > > To unsubscribe from this group, send email to
> > > puppet-users+unsubscr...@googlegroups.com 
> > > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > > For more options, visit this group at
> > > http://groups.google.com/group/puppet-users?hl=en.
> > >  
> >  
> >  
> > A while back you could just take the srpms from Fedora's 1.8.7 and
> > they would build pretty easily on EL5.  I haven't tried that for a
> > while, but you can at least get the RPMs from a known source that way.
> >  
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> >  
>  
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>  
>  


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] dropping support for ruby 1.85?

[Eric Shamow]

Not supported, but Karanbir Singh has made available 1.8.7 RPMs:

http://centos.karan.org/el5/ruby187/

-Eric 

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Tuesday, November 15, 2011 at 8:30 PM, Jo Rhett wrote:

> On Nov 9, 2011, at 5:47 AM, Ohad Levy wrote:
> > Ruby 1.87 support
> > Foreman 0.4 would be the last major version supporting Ruby older then 1.87.
> > This has to be done since the upstream rails community no longer
> > supports older versions, which means that critical security patches
> > are no longer available if we keep supporting that.
> > 
> > if required, we would release 0.4.x maintenance releases, but since
> > ruby 1.87+ is available on most distribution these days, you are
> > encouraged to upgrade.
> 
> No distribution based on RHEL5 has a supported version of ruby other than 
> 1.85 AFAIK.  It's pretty much a roll-your-own-RPM for 1.87, and that's not 
> possible for most sites.
> 
> -- 
> Jo Rhett
> Net Consonance : consonant endings by net philanthropy, open source and other 
> randomness
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Moving a puppet client is not as simple as I had hoped

[Eric Shamow]

I should add - this behavior is configurable:

http://docs.puppetlabs.com/references/stable/configuration.html#nodename

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Friday, October 28, 2011 at 4:03 PM, Eric Shamow wrote:

> The certname is only used for authentication - it is not part of the node 
> lookup process.
>  
> You can still use the mac-address-certname model, if you match with regexes 
> in your node configuration.
>  
> -Eric  
>  
> --  
>  
> Eric Shamow
> Professional Services
> http://puppetlabs.com/
> (c)631.871.6441
>  
>  
> On Friday, October 28, 2011 at 4:01 PM, Dan White wrote:
>  
> > Yes, but that is part of the frustration.
> >  
> > The certname is unchanged because it derives from the primary MAC address 
> > of the machine.
> > My twisted little brain says that i should be able to change the machine's 
> > IP and/or hostname and still connect to the PuppetMaster.
> >  
> > I am, sadly, mistaken in this.
> >  
> > I guess I am hoping that I do not have to abandon my mac-address-certname 
> > idea, but it is sorta/kinda looking that way.
> >  
> > “Sometimes I think the surest sign that intelligent life exists elsewhere 
> > in the universe is that none of it has tried to contact us.”
> > Bill Waterson (Calvin & Hobbes)
> >  
> > - Christopher Wood  > (mailto:christopher_w...@pobox.com)> wrote:
> > > I'm assuming that you have a puppet manifest describing a machine's 
> > > function and you want the same function under a new name. Why not set up 
> > > a new host with the new name and the same function, and remove the old 
> > > machine from service?
> > >  
> > > Obviously I have a certain bias, but when puppet can set up my server in 
> > > seconds/minutes I don't feel like I should take ten minutes moving a host.
> > >  
> > > On Fri, Oct 28, 2011 at 07:50:19PM +, Dan White wrote:
> > > > I started with this as my foundation:
> > > > <http://fedoraproject.org/wiki/Infrastructure_Host_Rename_SOP#Telling_Puppet_about_the_new_host>
> > > >  
> > > > and then decided to use a string formed by the primary MAC address as 
> > > > my certname like this:
> > > >  
> > > > MACADDR=`facter macaddress | tr "[:upper:]" "[:lower:]" | sed 's/://g' `
> > > > MY_NEW_CERTNAME="macaddr${MACADDR}"
> > > >  
> > > > I thought I would save myself from the trouble in the referenced 
> > > > web-page by using a machine-unique certname rather than something as 
> > > > non-unique as the FQDN or IP address.
> > > >  
> > > > How wrong I was !!
> > > >  
> > > > I had my first occasion to test drive this (faulty) idea.
> > > >  
> > > > Set up a machine as described, then it was moved to another sub-net, 
> > > > new IP, new hostname, and so I thought it would fly when I ran puppetd 
> > > > from the new location.
> > > >  
> > > > What I got was a message saying:  
> > > > err: Could not retrieve catalog from remote server: Error 400 on 
> > > > SERVER: Could not find default node or by name with 
> > > > 'macaddr1234567890a, example.foo.bar, example.foo, example' on node 
> > > > macaddr1234567890a
> > > >  
> > > > example.foo.bar is the new FQDN of the machine.
> > > >  
> > > > Now ain't that a kick in the Planters ?
> > > >  
> > > > So now I have to ask, how is it looking for the FQDN and the 
> > > > not-so-FQDN and just the hostname ? I was under the impression that 
> > > > everything keyed from the certname.
> > > >  
> > > > Now, to add insult to injury, the above referenced process no longer 
> > > > works !
> > > >  
> > > > I went as far as doung rm -frv /var/lib/puppet on the client and after 
> > > > doing puppetca --revoke --clean on the master, I found two more 
> > > > references to "macaddr1234567890a" -- one in /var/lib/puppet/yaml/node 
> > > > and one in /var/lib/puppet/yaml/facts -- which I removed. And I even 
> > > > restarted the puppetmaster daemon a few times.
> > > >  
> > > > The only thing I have NOT yet done is to wipe /var/lib/puppet on the 
> > > > Master and re-certify everything. This setup is still in its infancy, 
> > >

Re: [Puppet Users] Moving a puppet client is not as simple as I had hoped

[Eric Shamow]

The certname is only used for authentication - it is not part of the node 
lookup process.

You can still use the mac-address-certname model, if you match with regexes in 
your node configuration.

-Eric  

--  

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441


On Friday, October 28, 2011 at 4:01 PM, Dan White wrote:

> Yes, but that is part of the frustration.
>  
> The certname is unchanged because it derives from the primary MAC address of 
> the machine.
> My twisted little brain says that i should be able to change the machine's IP 
> and/or hostname and still connect to the PuppetMaster.
>  
> I am, sadly, mistaken in this.
>  
> I guess I am hoping that I do not have to abandon my mac-address-certname 
> idea, but it is sorta/kinda looking that way.
>  
> “Sometimes I think the surest sign that intelligent life exists elsewhere in 
> the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
>  
> - Christopher Wood  (mailto:christopher_w...@pobox.com)> wrote:
> > I'm assuming that you have a puppet manifest describing a machine's 
> > function and you want the same function under a new name. Why not set up a 
> > new host with the new name and the same function, and remove the old 
> > machine from service?
> >  
> > Obviously I have a certain bias, but when puppet can set up my server in 
> > seconds/minutes I don't feel like I should take ten minutes moving a host.
> >  
> > On Fri, Oct 28, 2011 at 07:50:19PM +, Dan White wrote:
> > > I started with this as my foundation:
> > > <http://fedoraproject.org/wiki/Infrastructure_Host_Rename_SOP#Telling_Puppet_about_the_new_host>
> > >  
> > > and then decided to use a string formed by the primary MAC address as my 
> > > certname like this:
> > >  
> > > MACADDR=`facter macaddress | tr "[:upper:]" "[:lower:]" | sed 's/://g' `
> > > MY_NEW_CERTNAME="macaddr${MACADDR}"
> > >  
> > > I thought I would save myself from the trouble in the referenced web-page 
> > > by using a machine-unique certname rather than something as non-unique as 
> > > the FQDN or IP address.
> > >  
> > > How wrong I was !!
> > >  
> > > I had my first occasion to test drive this (faulty) idea.
> > >  
> > > Set up a machine as described, then it was moved to another sub-net, new 
> > > IP, new hostname, and so I thought it would fly when I ran puppetd from 
> > > the new location.
> > >  
> > > What I got was a message saying:  
> > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> > > Could not find default node or by name with 'macaddr1234567890a, 
> > > example.foo.bar, example.foo, example' on node macaddr1234567890a
> > >  
> > > example.foo.bar is the new FQDN of the machine.
> > >  
> > > Now ain't that a kick in the Planters ?
> > >  
> > > So now I have to ask, how is it looking for the FQDN and the not-so-FQDN 
> > > and just the hostname ? I was under the impression that everything keyed 
> > > from the certname.
> > >  
> > > Now, to add insult to injury, the above referenced process no longer 
> > > works !
> > >  
> > > I went as far as doung rm -frv /var/lib/puppet on the client and after 
> > > doing puppetca --revoke --clean on the master, I found two more 
> > > references to "macaddr1234567890a" -- one in /var/lib/puppet/yaml/node 
> > > and one in /var/lib/puppet/yaml/facts -- which I removed. And I even 
> > > restarted the puppetmaster daemon a few times.
> > >  
> > > The only thing I have NOT yet done is to wipe /var/lib/puppet on the 
> > > Master and re-certify everything. This setup is still in its infancy, so 
> > > doing that is not a big deal, but once things snowball a bit, I will not 
> > > have the luxury of rebuilding the PuppetMaster every time a machine moves.
> > >  
> > > Suggestions, please !
> > >  
> > > “Sometimes I think the surest sign that intelligent life exists elsewhere 
> > > in the universe is that none of it has tried to contact us.”
> > > Bill Waterson (Calvin & Hobbes)
> > >  
> > > --  
> > > You received this message because you are subscribed to the Google Groups 
> > > "Puppet Users" group.
> > > To post to this group, send email to puppet-users@googlegroups.com 
> > > (mailto:puppet-users@google

Re: [Puppet Users] Re: Puppet on Centos 6.0

[Eric Shamow]

My worry is often that a poorly-crafted will overwrite something that the gem 
db expects to be there.

It shouldn't happen but it does - so for me I stick to all-RPMs, because at 
least then expectations are managed by the rpm database, and I can fix things 
by repairing a broken package. If gem and/or RPM break each other, there's 
little I can do to fix it in any automated or predictable way.

-Eric

-- 

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Tuesday, October 18, 2011 at 12:43 PM, Michael Stahnke wrote:

> On Tue, Oct 18, 2011 at 6:19 AM, jcbollinger  (mailto:john.bollin...@stjude.org)> wrote:
> > 
> > 
> > On Oct 17, 3:03 pm, Russell Van Tassell  > (http://gmail.com)> wrote:
> > > Personally, I've had better luck letting gem managed its own gems, rather
> > > than depending on Yum repositories (specifically on CentOS).
> > > 
> > > I'd take a list of the Ruby gems you've installed via rpm (rpm -q -a | 
> > > grep
> > > ruby) and then consider installing them directly, as so:
> > > 
> > > % sudo gem install mysql
> > > % sudo gem list
> > 
> > 
> > I, on the other hand, would recommend avoiding gems altogether if
> > you're using the system's Ruby (i.e. one you installed from an RPM,
> > whether via yum or otherwise). Ruby modules installed via RPM are not
> > (should not be) gems. Using both gem and rpm to manage the same Ruby
> > installation is begging for trouble.
> 
> Why? The packages of many ruby libraries are basically gems wrapped
> in RPM. Basically it allows the library/tool to be registered with
> the RPM and gem database. I admit it's not my favorite thing to have
> gems (and not RPMs), but technically there is almost nothing wrong
> with it, other than future RPMs can't depend on something from a gem
> install only.
> 
> There are plenty of other debates about rubygems, and whether or not
> they are useful or helpful or anything. But as far as having a system
> with ruby and using to gem to install things, it will work and is
> always all that bad.
> > 
> > 
> > John
> > 
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com 
> > (mailto:puppet-users@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > puppet-users+unsubscr...@googlegroups.com 
> > (mailto:puppet-users+unsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] issues with puppet service and mco puppetd

[Eric Shamow]

You don't actually need the ensure => stopped. If you are set to enable => 
false, that's good enough - ensure => stopped will kill the daemon every time 
it starts.

-Eric

-- 
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Monday, September 26, 2011 at 5:13 PM, mbargar wrote:

> Ok so we are running puppet agent via cron jobs and have the puppet
> agent set to the following:
>  service { "pe-puppet-agent":
>  enable => false,
>  ensure => stopped,
>  hasstatus => true,
>  hasrestart => true,
>  }
> so i need to get something out to all of out servers urgently and used
> MCO to run "mco puppetd runonce -I mycomputer" and that works and all,
> but on the client side that runs "/opt/puppet/bin/ruby1.8 /opt/puppet/
> sbin/puppetd --onetime --splaylimit 120 --splay" which in turns starts
> the puppet agent service and then it reads my manifest and says that
> agent should be stopped. So how can i get MCO to work like i need it
> to, but also not interfere with the "ensure => stopped" of my
> manifest?
> 
> FYI, everytime that i run the MCO command, i get "Caught TERM; calling
> stop", which i am assuming is due to thge fact that it is stopping the
> service.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] run puppet as cron job

[Eric Shamow]

Hi Marshall, welcome!

I'm pretty sure the service is pe-puppet and not pe-puppet-agent…

Check in /etc/init.d.  

--  
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Thursday, September 22, 2011 at 11:37 AM, mbargar wrote:

> I have written the manifest that creates the cron jobs and those
> actully are created ok, but my issue is that i have the following
>  service { "pe-puppet-agent":
>  enable => false,
>  ensure => stopped,
>  }
> and for some reason it will set the enable to false but it does not
> stop the puppet service. Any ideas?
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

Douglas,

This is a long shot, but if you have your locate database being updated 
nightly, as is the default for RH-based OSes, can you run "locate puppet | 
pbcopy" and paste the results into a pastebin/pastie/your paste of choice?

I'd like to see where this shows up on your system. I think there really are 
remnants of an earlier install hanging around.

-Eric

-- 
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Monday, September 12, 2011 at 6:07 PM, Douglas Garstang wrote:

> On Mon, Sep 12, 2011 at 1:41 PM, Douglas Garstang
> mailto:doug.garst...@gmail.com)> wrote:
> > On Mon, Sep 12, 2011 at 1:28 PM, Eric Shamow  > (mailto:e...@puppetlabs.com)> wrote:
> > > You haven't imported the public key for that repository. Ken was probably 
> > > assuming that you'd add the repo to your list of repositories and use yum 
> > > to install. If you aren't going to do that, you need the GPG key:
> > > 
> > > RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs)
> > > 
> > > -Eric
> > 
> > Weird, I installed the key in /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs,
> > did an rpm --import, and I'm still getting the error.
> 
> So, I managed to install those RPM's (puppet and facter) on the
> client, and got the same results.
> 
> Doug
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

You haven't imported the public key for that repository. Ken was probably 
assuming that you'd add the repo to your list of repositories and use yum to 
install. If you aren't going to do that, you need the GPG key:

RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs)

-Eric

-- 
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Monday, September 12, 2011 at 4:25 PM, Douglas Garstang wrote:

> On Mon, Sep 12, 2011 at 1:17 PM, Douglas Garstang
> mailto:doug.garst...@gmail.com)> wrote:
> > On Mon, Sep 12, 2011 at 1:08 PM, Ken Barber  > (mailto:k...@puppetlabs.com)> wrote:
> > > > The RPM for the puppet client came from the Puppet Labs website. I
> > > > downloaded the source for 2.7.3, and had to make a few changes to the
> > > > SPEC file
> > > 
> > > (I keep asking this but ...) What OS are you running and version?
> > > Where did you get the RPM's for 0.25?
> > 
> > O/S on server is CentOS 5.4. O/S on client(s) is CentOS 5.5
> > 
> > I answered this one in the previous message, but I got the source from
> > Puppet Labs, modified the RPM spec file to make it work, and built the
> > RPM's from that,.
> > 
> > > 
> > > Also ... why don't you try these RPM's for 2.7.x:
> > > 
> > > http://yum.puppetlabs.com/el/5/products
> > 
> > Well, didn't know that existed. Maybe due to lack of documentation.
> > Every time I've complained about the spec files not being maintained
> > in the source code, Puppet labs people have said it wasn't their job
> > to maintain the spec file. Given that there are pre-build RPM's on the
> > puppet labs web site, I guess it's someone's job to maintain the spec
> > file.
> > 
> > > 
> > > I think Mike just updated these.
> > 
> > I'll give the client a try first. Little more worried about updating the 
> > server.
> 
> Uhm... what am I missing here?
> 
> [root@hproxy11 tmp]# rpm -i facter-1.6.0-1.x86_64.rpm
> error: facter-1.6.0-1.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD,
> key ID 4bd6ec30
> error: facter-1.6.0-1.x86_64.rpm cannot be installed
> 
> [root@hproxy11 tmp]# rpm -i puppet-2.7.3-1.el5.noarch.rpm
> error: puppet-2.7.3-1.el5.noarch.rpm: Header V4 RSA/SHA1 signature:
> BAD, key ID 4bd6ec30
> error: puppet-2.7.3-1.el5.noarch.rpm cannot be installed
> 
> Doug
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

> I know that notice() is a function, and notify{} is a resource. The
> documentation says that much. However, it doesn't really go beyond
> that. The documentation
> provides examples of how to use notify{} to notify another resource
> when it changes, but I don't believe it gives you any indication
> whatsoever that you can use it in a stand alone fashion like this.
> Where is that use documented? How would anyone except the core puppet
> developers know that you could even do this?
You are confusing the notify attribute with the notify{} type.

http://docs.puppetlabs.com/references/stable/type.html#notify 

This is different from

file { "foo":
notify => bar,
}
> I'm launching puppet with 'service puppet restart'. What libraries? If
> you know their names I can search for them.
So you are running it as a service, then. Please paste the results of the 
following two commands:

which puppet
pgrep puppet

-Eric


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

Notify is a resource, notice() is a function. So notice() is evaluated on the 
server, whereas notify{} is evaluated on the client.

My suspicion is that you somehow have two versions of the client binary hanging 
around. Perhaps one that is running when you execute "puppet" at the shell, and 
another running in the background.

Per Ken's question - how are you launching Puppet? Is it as a service? Or are 
you running it from a cron job?

-Eric


On Friday, September 9, 2011 at 8:16 PM, Douglas Garstang wrote:

> On Fri, Sep 9, 2011 at 4:55 PM, R.I.Pienaar  (mailto:r...@devco.net)> wrote:
> > 
> > 
> > - Original Message -
> > > On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar  > > (mailto:r...@devco.net)> wrote:
> > > > 
> > > > 
> > > > - Original Message -
> > > > > On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber  > > > > (mailto:k...@puppetlabs.com)>
> > > > > wrote:
> > > > > > What does:
> > > > > > 
> > > > > > puppet -e 'notice("$puppetversion")'
> > > > > > 
> > > > > > Show on the _client_? I know its probably obvious but you never
> > > > > > know.
> > > > > 
> > > > > Actually, it's not obvious. I didn't know you could do that. Never
> > > > > seen it documented anywhere...
> > > > 
> > > > > notice: Scope(Class[main]): 2.7.3
> > > > > notice: Finished catalog run in 0.21 seconds
> > > > 
> > > > if you change the notice() in your manifests to
> > > > notify{"${puppetversion} on ${fqdn}":}
> > > > and run puppet agent --test on the node, does it still give the
> > > > wrong version?
> > > 
> > > Changing the notice line to:
> > > notice ("fqdn = ${fqdn}, puppetversion = ${puppetversion}")
> > > 
> > > still gives (on the master):
> > > Sep 9 16:52:09 sv2admin1 puppet-master[14087]:
> > > (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com 
> > > (http://hproxy10.h.foo.com),
> > > puppetversion
> > > = 0.25.5
> > > 
> > > I assume you mean't to use notify(), not notify{}  ?
> > 
> > no, i did mean use notify :)
> 
> Ok, using notify{}, the client now says:
> 
> Sep 9 17:13:38 hproxy10 puppet-agent[30537]: 0.25.5 on hproxy10.h.foo.com 
> (http://hproxy10.h.foo.com)
> Sep 9 17:13:38 hproxy10 puppet-agent[30537]:
> (/Stage[main]/Puppet::Setup/Notify[0.25.5 on
> hproxy10.h.foo.com (http://hproxy10.h.foo.com)]/message) defined 'message' as 
> '0.25.5 on
> hproxy10.h.foo.com (http://hproxy10.h.foo.com)'
> 
> I know I'll get slammed for asking, but where is the use of notify{}
> in this manner documented? I didn't know you could do that. WHat does
> notify do? As far as the docs are concerned, it's a resource type.
> 
> Interestingly, it returns 0.25.5...
> 
> Doug.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

 Right, so your client is running 2.7.3, not 0.25. That's why faster is 
returning 2.7.3.

On the master try running the same. If it doesn't work try

puppetd --version

-Eric


On Friday, September 9, 2011 at 7:50 PM, Douglas Garstang wrote:

> On Fri, Sep 9, 2011 at 4:48 PM, Eric Shamow  (mailto:e...@puppetlabs.com)> wrote:
> > On the same box, what does
> > 
> > puppet agent --version
> > 
> > give you?
> 
> That gives me:
> 
> [root@hproxy10 ~]# puppet agent --version
> 2.7.3
> 
> Doug
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Facter variable $puppetversion

[Eric Shamow]

On the same box, what does 

puppet agent --version

give you? 

-Eric


On Friday, September 9, 2011 at 7:47 PM, Douglas Garstang wrote:

> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber  (mailto:k...@puppetlabs.com)> wrote:
> > What does:
> > 
> > puppet -e 'notice("$puppetversion")'
> > 
> > Show on the _client_? I know its probably obvious but you never know.
> 
> Actually, it's not obvious. I didn't know you could do that. Never
> seen it documented anywhere...
> 
> But,
> 
> 
> [root@hproxy10 ~]# puppet -e 'notice("$puppetversion")'
> warning: Implicit invocation of 'puppet apply' by passing files (or
> flags) directly
> to 'puppet' is deprecated, and will be removed in the 2.8 series. Please
> invoke 'puppet apply' directly in the future.
> 
> warning: You have configuration parameter $localconfig specified in
> [puppetd], which is a deprecated section. I'm assuming you meant
> [agent]
> warning: You have configuration parameter $classfile specified in
> [puppetd], which is a deprecated section. I'm assuming you meant
> [agent]
> warning: You have configuration parameter $report specified in
> [puppetd], which is a deprecated section. I'm assuming you meant
> [agent]
> notice: Scope(Class[main]): 2.7.3
> notice: Finished catalog run in 0.21 seconds
> 
> Doug
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Creating manifests automatically from an existing configuration?

[Eric Shamow]

John,

I suspect you're right. User requirements FTW.

-Eric

-- 
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Thursday, August 11, 2011 at 2:45 PM, jcbollinger wrote:

> 
> 
> On Aug 11, 11:52 am, Eric Shamow  (http://puppetlabs.com)> wrote:
> > This could also be a place for the use of exported resources. End result is 
> > similar to puppet resource but can change dynamically, which is nice. 
> 
> If the OP already had Puppet manifests for the machine he wanted to
> clone, then he would not need to go through this exercise in the first
> place. He could more or less just assign all the same classes to the
> new node that are assigned to the existing one. That would be a lot
> easier than exporting all of one node's resources and collecting them
> on the other, or using 'puppet resource' to analyze the original
> machine.
> 
> I interpreted the OP's use of "configuration" differently: I think he
> means what we more typically might describe as "state" (indeed, he
> later uses that term himself). He's looking for tools with which to
> create Puppet manifests describing the existing machine, which he will
> then apply to the new one. Exported resources are clearly no help
> there, because there are no existing resource declaration to export.
> 
> 
> John
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Creating manifests automatically from an existing configuration?

[Eric Shamow]

 This could also be a place for the use of exported resources. End result is 
similar to puppet resource but can change dynamically, which is nice.  

--  
Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 
23rd in Portland, OR.

Eric Shamow
Professional Services
http://puppetlabs.com/
(c)631.871.6441

On Thursday, August 11, 2011 at 9:27 AM, Daniel Pittman wrote:

> On Thu, Aug 11, 2011 at 16:05, Spiral Syzygy  (mailto:spiralena...@gmail.com)> wrote:
>  
> > I'm new to puppet and I would like to use it to clone the
> > configuration of an existing base machine. Are there any tools that
> > would allow puppet to scan the existing machine's state and generate
> > manifests I can then use to manage this other machine?
>  
> `puppet resource` can generate the raw material. It doesn't produce
> dependencies, and you would need to make sensible decisions about
> structuring file resources, but it can sure be a help.
>  
> Daniel
> --  
> ⎋ Puppet Labs Developer – http://puppetlabs.com
> ♲ Made with 100 percent post-consumer electrons
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com 
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com 
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Step by step guide to setting user passwords

[Eric Shamow]

Just a note - ralsh is also available from the puppet command line as "puppet 
resource."

-Eric

On Aug 6, 2011, at 2:22 AM, John Martin wrote:

> You can also use the ralsh command where the user is created as long
> as puppet is installed.  The command will spit out the complete user
> dsl.
> 
> ralsh user student
> 
> Also, make sure the password is in single quotes so $ doesn't get
> interpreted.
> 
> -John
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Validating a puppet configuration

[Eric Shamow]

Have you considered bootstrapping a test suite like cucumber-puppet?
https://github.com/nistude/cucumber-puppet

-Eric


>  Topic: Validating a puppet configuration
> Lars Kellogg-Stedman  Jul 29 06:33AM -0700 ^
>  
> If anyone out there follows Serverfault, this is a duplicate of 
> http://goo.gl/CTS2u. I'm hoping there are some subject matter experts here 
> :).
>  
> I am trying to place some sanity checks (currently as git pre-commit hooks) 
> in our configuration repository to avoid committing invalid Puppet 
> configurations. I'm having a surprising amount of trouble coming up with a 
> way to effectively validate the configuration. My obvious first choice was 
> "puppet parser validate ...", which does some gross syntax checks (unmatched 
> quotes and brackets and so forth) but doesn't throw errors on things like 
> this:
>  
> file { 'somefile':
> requires => Service['someservice']
> }
>  
> (where 'requires' should be 'require'), nor does it notice problems like 
> this:
>  
> sdlflsjlksdf { 'myname': }
>  
> (where 'sdlflsjlksdf' isn't defined anywhere).
>  
> Some folks have suggested "puppet master --compile ...", but this really, 
> reallly wants to fix permissions all over the place on directories that are 
> used by Puppet. I have also tried "puppet apply --noop", but this still 
> tries to stat() any files referenced in the manifests, which means it will 
> fail with permission errors if it tries to stat() a file or directory that 
> is not accessible to a non-root user. Does anyone here have suggestions for 
> effectively performing more aggressive syntax checks than those offered by 
> "puppet parser validate"?
>  
> -- Lars
>  
> 
> Greg Hellings  Jul 29 09:49AM -0700 ^
>  
> Have you looked at using these?
> projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
>  
> --
> Greg
>  
>  
>  
> 
> Scott Smith  Jul 29 10:19AM -0700 ^
>  
> Those hooks are the gross syntax checks to which he initially referred.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Recurse broken in File type?

[Eric Shamow]

Was going to open a new ticket but saw this --
http://projects.puppetlabs.com/issues/5414

The user reports the issue in 2.6.3, i see it in 2.6.4 as well, on
CentOS 5.5.  If I modify a file in a folder that is being deployed
recursively, that update is not happening on the clients.

Setting filetimeout to 0, waiting for it to expire, etc seems to make
no difference.

This has led us to have to do a ton of manual distributions.  Is this
a widely-known issue?  Any ideas for how I can begin to troubleshoot?

-Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Recurse broken in File type?

[Eric Shamow]

Was going to open a new ticket but saw this --
http://projects.puppetlabs.com/issues/5414

The user reports the issue in 2.6.3, i see it in 2.6.4 as well, on
CentOS 5.5.  If I modify a file in a folder that is being deployed
recursively, that update is not happening on the clients.

This has led us to have to do a ton of manual distributions.  Is this
a widely-known issue?  Any ideas for how I can begin to troubleshoot?

-Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: Redefine package type

[Eric Shamow]

Well as a starter --

This is a provider called rpm_plus.rb -- I found most of it floating
around on the web and I seem to recall tweaking some small part of it,
although I don't recall now what it was... in any event this works and
is in use in our environment.  Provider looks like:

Puppet::Type.type(:package).provide :rpm_plus, :parent => :rpm, :source =>
:rpm do

has_feature :versionable

desc "Support via ``rpm``."
commands :rpm_plus => "rpm"
def rpm(*args)
  rpm_plus(*args + @resource[:vendor].split(" "))
end
 end

You'd throw this in a file called rpm_plus.rb and stash it in
/lib/puppet/provider/package/.  What this basically does is
wrap the existing RPM provider with another one that lets you pass
arguments in a "vendor" attribute.

You would then install your RPM package in your manifest the following way:

   package{ 'My_package':
  ensure => 'version_number',
  provider => rpm_plus,
  source = "",
  vendor => "--prefix=/home/ads",
   }

The key bits are the provider => rpm_plus attribute, which tells
Puppet to override its default yum provider, and the vendor attribute,
into which you pass your additional arguments.

-Eric


On Thu, Sep 9, 2010 at 4:27 AM, SiD  wrote:
> Thanks for your quick answer.
> I've already analysed the code, but it does not really help me. Do I
> need to write a new provider in Ruby, or can I override the original
> one ?
>
> Thanks again !
>
> On Sep 8, 10:45 am, mohit chawla 
> wrote:
>> You can probably start by looking at the code for the various
>> types/providers under puppet's code directory. On Debian, for eg., the code
>> for rpm package provider is under
>> /usr/lib/ruby/1.8/puppet/provider/package/rpm.rb .
>>
>> On Wed, Sep 8, 2010 at 1:40 PM, SiD  wrote:
>> > Hello,
>>
>> > I would like to go in depth with Puppet, but I haven't found any good
>> > documentation about my issue (I've just ordered the official Puppet
>> > book, hope it helps).
>> > I need to install RPM packages with specified install-options, like --
>> > prefix. But the package type does not support this kind of option.
>> > Does anyone have an idea how to redefine a type ?
>>
>> > Thanks !
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups
>> > "Puppet Users" group.
>> > To post to this group, send email to puppet-us...@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > puppet-users+unsubscr...@googlegroups.com
>> > .
>> > For more options, visit this group at
>> >http://groups.google.com/group/puppet-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet system deployment hanging ..

[Eric Shamow]

Yep, this was our solution -- I raised the issue more to point out
that finding out that yum-updater was the problem was difficult as a
result of quiet execution and yum's hang.  Once we figured out the
problem the solution was fairly easy, but that's almost always the
case...

-Eric


On Tue, Aug 17, 2010 at 10:31 AM, Daniel Maher  wrote:
> On 08/17/2010 04:04 PM, Adrian Snyman wrote:
>>
>> Well, I wonder if there is a way to make puppet turn off the updater
>> before starting it's run ?
>
> Instead of trying to disable it, why bother installing it at all ?  Just
> remove the package in your kickstart config and be done with it.
>
> %packages
> # don't install the yum-updatesd package
> -yum-updatesd
>
> Or the equivalent in whatever your deployment system is...
>
> --
> Daniel Maher 
> "The Internet is completely over." -- Prince
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Puppet system deployment hanging ..

[Eric Shamow]

I have seen this behavior before as well. I've also seen it where
yum-updater (which is evil and shouldn't be running, but in some cases
hasn't been turned off yet by kickstart or puppet) will switch on and
demolish a bootstrap Puppet run.

It would help if the yum handler was a little more verbose or had some
kind of watchdog that could reap stale processes after a while.  The
hardest thing about this kind of problem is actually figuring out what
causes the issue, since Puppet/Yum only log the action after it's
completed.

-Eric


On Tue, Aug 17, 2010 at 2:04 AM, Adrian Snyman  wrote:
> On Fri, Aug 13, 2010 at 8:46 AM, Adrian Snyman  wrote:
>> On Fri, Aug 13, 2010 at 8:02 AM, Adrian Snyman  wrote:
>>> On Thu, Aug 12, 2010 at 1:38 PM, Trevor Hemsley
>>>  wrote:
 You're not exec'ing some install program that is stopping and waiting for
 input? When we deploy Platform Symphony, we have to do something like an
 exec that runs "echo Y | symphony-installer" or we get a similar problem.

>>>
>>> Hmm, I am not aware of any installers running ... I will take a look
>>> and see if there are
>>> any background processes waiting for input .. thanks !
>>>
>>
>> Well, I have run through the installation, and it appears to be
>> hanging on the installation of our grid software.
>> The commandline is executing, but the rpm's aren't downloading - so I
>> will keep looking ...
>>
 Adrian Snyman wrote:
>
> On Thu, Aug 12, 2010 at 12:49 PM, Ohad Levy  wrote:
>
>>
>> Does the puppet run starts at all?
>> I've seen similar case when the clock were out of sync, ntp started and
>> aligned it, but puppet got hanged because of it (or sleeping for a really
>> long time).
>> does debug mode provide more info?
>> Ohad
>>
>> On Thu, Aug 12, 2010 at 9:11 AM, MadX  wrote:
>>
>>>
>>> We have successfully installed puppet on a CentOS Server, but I am
>>> battling with a deployment.
>>>
>>> It has to do with grid software. The repository gets created, then
>>> begins installation.
>>> The problem is that it just hangs - no errors, no network activity. I
>>> can see puppet is running, but nothing it being updated.
>>>
>>> Any pointers ?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups
>>> "Puppet Users" group.
>>> To post to this group, send email to puppet-us...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> puppet-users+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/puppet-users?hl=en.
>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
> Well, This is happening at about 50% of the installation - so it is
> definitely deploying ..
> I am running :
>
> puppetd --test --verbose
>
> And, as listed above - that's the last message I am seeing .. :S Any
> other logs etc. I could give ?
>

>
> Okay, just a heads up here ...
> I found the issue to be a faulty rpm. The user/group did not exist on
> the target system, and so after about 300 warnings, yum simply
> freezes. Installing the rpm manually showed the error. After creating
> the user and group - the deployment was successful.
>
> Unfortunately, puppet simply hangs while waiting for the rpm
> transaction to finish, and there is no indication as to what is
> holding up the
> install ...
>
> --
> Regards,
>
>
> Adrian
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Dashboard or Foreman

[Eric Shamow]

Having tried both I settled on Foreman, although I haven't checked out
Puppet-Dashboard after the 1.0 release.

Foreman just provides more information, I find, although
Puppet-Dashboard looks slightly slicker.  Foreman also seems easily
hackable/extensible and comes with a nice query tool.

-Eric


On Tue, Jun 15, 2010 at 12:00 PM, Walter Heck  wrote:
> Hi Guys,
>
> I'm reading about dashboard and foreman, and I'm wondering if there is
> anyone who made a comparison of the two? Can anyone help me decide
> which one to use? It feels like foreman is 'ahead' for now?
>
> cheers,
>
> Walter Heck
> Engineer @ OlinData (http://olindata.com)
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

[Puppet Users] Job Posting: Hiring UNIX/Linux SA/SE in NYC area

[Eric Shamow]

Hey folks,

Normally on this list as a Puppet user, but I'm hiring two fairly
senior UNIX/Linux admins in my group, and as we are moving all of our
systems to Puppet, this list seemed the ideal target for job trolling.

The position is with a top 15 media company based out of Jersey City.
You'd be joining the Operations group, which is responsible for 800+
servers, about 50% virtualized, in a CentOS/VSphere environment.
We're a team of 7 SEs plus 2 DBAs, and are part of a larger technology
group.

We touch all sorts of technologies, but a major thrust is moving our
systems to configuration management using Puppet.  I've already rolled
out both the proof of concept and the first round of production
deploys, but it's early days yet, and there is still a significant
opportunity to contribute to the design and best practices for this
environment.

You should be a fairly experienced SA/SE -- environment size doesn't
matter so much but heavy experience with Linux, particularly
CentOS/RHEL, Apache, MySQL, etc are required.  Familiarity with
app-level debugging using strace or gdb is a big plus, as is
experience with Nagios and VMware.

If you are interested and would like more details, please drop me a line.

Thanks,

-Eric Shamow

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Re: mcollective scalability

[Eric Shamow]

Matt,

Really great posts -- you've inspired me to take a crack at MCollective.

-Eric


On Thu, May 6, 2010 at 4:11 AM, Matt Wallace
 wrote:
> On Wed, 2010-05-05 at 23:31 -0700, donavan wrote:
>> > 2000 nodes certainly is within my goals with the design, that said there 
>> > has not been such a big deploy.
>>
>> We've got 500+ nodes on mcollective currently. Nothing special as far
>> as setup, a few of the contrib agents and few more in house agents.
>> Nodes are primarily split between two buildings connected by gigE. 95%
>> response from mc-ping is 300ms, average 200ms.
>>
>> I'm expecting at least 1000 nodes in three geo areas by the end of the
>> year. My todo list for this summer has federating some more activemqs
>> into the setup.
>>
>> > You'd probably want a few activemq instances in a cluster in such a setup, 
>> > though I've heard of much larger client counts on activemq.
>>
>> The above all runs off of a single activemq server currently. Quad
>> core xeon w/ 3gb ram sitting at 99% idle.
>>
>
> For those of you that are interested, I've put up a few blogposts about
> configuring ActiveMQ and Mcollective on both Centos and Ubuntu at
> http://www.threedrunkensysadsonthe.net/
>
> Kind regards,
>
> Matt
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Re: [Puppet Users] Specifying Yum Options

[Eric Shamow]

A not-so-elegant solution is to write your own yum provider that
allows you to do this.  In my case I found one online -- if you google
yum_plus.rb you should be able to find it.  If not let me know and
I'll post the work here.

On Thu, Apr 1, 2010 at 10:19 PM, Isaac Christoffersen
 wrote:
> We're using RHN Satellite server to manage our packages and we have a custom
> package channel for third-party packages.  Unfortunately, some of the
> packages in the channel are unsigned.
>
> Is there a way to get the Package Provider for yum to use the nogpgcheck
> option?  Right now, I'm using an exec declaration instead of a package, but
> it seems kludgy to do this.
>
> Of course, from a larger perspective, I'd like to be able to pass any valid
> yum option via the package syntax in Puppet.  (i.e. Download Only, Enable
> Repo, Group Install, etc.)
>
> thanks,
>
> Isaac
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.