Re: [Puppet Users] Introducing our new Community Manager - Dawn Foster

[Kelsey Hightower]

On Tue, Oct 2, 2012 at 5:35 PM, James Turnbull  wrote:

> Hi all
>
> I am thrilled to announce our new Community Manager: Dawn Foster. Dawn
> joins us from Intel where she managed several open source communities
> (I'm going to let her introduce herself in more detail in a later email).
>
> Dawn will initially be lurking and getting to know you all. She's going
> to have a focus on helping us communicate better, making the
> relationship between the community and Puppet Labs work better,
> extending our developer community, helping getting traction on tickets
> and features the community wants, sharing lots of cool metrics and
> generally working to make Puppet and the community more awesome.
>
> Please make Dawn welcome!
>
> Regards
>
> James
>
> --
> James Turnbull
> Puppet Labs
> 1-503-734-8571
> To schedule a meeting with me: http://tungle.me/jamtur01
>
> --
> 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.
>
>
Welcome to Puppet Labs Dawn!


-- 
Kelsey Hightower
Operations Manager
Puppet Labs
(678) 4719501

-- 
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 3.0.0 and hiera

[Kelsey Hightower]

You'll need hiera-puppet, which contains the parser functions. Puppet 3.0.0 
should bring in both Hiera and hiera-puppet as deps.

On Jul 9, 2012, at 9:21 AM, Henrik Lindberg  
wrote:

> Hi,
> If I have understood it correctly, puppet 3.0.0 will include / require hiera. 
> In order to add support for hiera directly in Geppetto I downloaded the 
> puppet 3.0.0rc tarball expecting to find the puppet-hiera functions, but they 
> where not there.
> 
> What is the expected packaging going to be when 3.0.0 is released?
> Where should I expect the hiera "parser functions" to be located?
> 
> (For now I can compose the result manually, but I would like to know where 
> they are supposed to be so I do this correctly from the start).
> 
> If you want to, you can also comment on 
> https://github.com/cloudsmith/geppetto/issues/282
> 
> Regards
> - henrik
> 
> -- 
> 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: Hiera Tutorials

[Kelsey Hightower]

On Thu, Jun 28, 2012 at 1:01 PM, windowsrefund wrote:

> Are you sure Hiera defaults to /etc/hiera.yaml and not /etc/puppet/
> hiera.yaml?
>

Yep, the hiera parser functions default to /etc/puppet/hiera.yaml, but
Hiera defaults to /etc/hiera.yaml. Most people are not use to running Hiera
in stand-alone mode and is commonly the source of confusion.


>
> --
> 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.
>
>


-- 
Kelsey Hightower
Developer
Puppet Labs
(678) 4719501

-- 
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] Re: Hiera Tutorials

[Kelsey Hightower]

I need to add the following 'cookbook' style tutorials:

   - Hiera and custom Facter Facts
   - Using Hiera data in Puppet manifests - looping over hashes and arrays
   - Creating resources from Hiera data
   - Hiera CLI vs Parser Functions -- how do they match up
   - Hiera Ruby API


On Thursday, June 28, 2012 12:32:03 PM UTC-4, Kelsey Hightower wrote:
>
> I'm beginning the process of creating Hiera tutorials covering the 
> following topics:
>
> *Beginner*
>
>- Getting Started with Hiera 
> (draft<https://github.com/kelseyhightower/hiera/blob/maint/1.0rc/add_getting_started_tutorial/docs/tutorials/getting_started.md>
>)
>- Understanding hierarchies, sources, and scope
>- Understanding answer resolution (array, priority, hash, resolution 
>order, etc)
>- Hiera and Puppet - Using the parser functions and data bindings for 
>parameterized classes
>
> *Advanced*
>
>- Hiera backends -- Creating new backends
>- Hiera parser functions -- Creating new hiera parser functions
>
>
> If you can think of anything else that should be covered let me know.
>
> Thanks.
>

-- 
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/-/V8cLL0Fw_wsJ.
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] Hiera Tutorials

[Kelsey Hightower]

I'm beginning the process of creating Hiera tutorials covering the 
following topics:

*Beginner*

   - Getting Started with Hiera 
(draft
   )
   - Understanding hierarchies, sources, and scope
   - Understanding answer resolution (array, priority, hash, resolution 
   order, etc)
   - Hiera and Puppet - Using the parser functions and data bindings for 
   parameterized classes

*Advanced*

   - Hiera backends -- Creating new backends
   - Hiera parser functions -- Creating new hiera parser functions


If you can think of anything else that should be covered let me know.

Thanks.

-- 
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/-/LTMeZtgI5P8J.
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] Request for Feedback - What do you want in an ENC

[Kelsey Hightower]

Help me produce the best ENC service/api possible by giving me your user 
stories, feature requests, and anything that would make a *new* ENC 
awesome. Don't worry about justifying your feature or user story, I want 
all ideas, even crazy ones.

*What am I building?*
Right now my focus is on building the best ENC service/api possible. This 
will be a combination of a new data and classification services.

Details on the classification service can be found here: 
https://github.com/kelseyhightower/puppet-classifier (Ignore the bits about 
TorqueBox, it's only used for prototyping. Final version will be a simple 
Sinatra application targeted at Ruby 1.8.7+)

-- 
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/-/KVCiF3bafdQJ.
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

[Kelsey Hightower]

On Tuesday, June 26, 2012 9:41:00 AM UTC-4, jmslagle 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 
>

Yep, also see Eric's example of using something like gem2rpm to create 
those OS packages. If you like this idea, please up vote the ticket and add 
your comments there.

-- 
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/-/R3GfTzJw6CgJ.
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] Hiera - can't convert Array into String error

[Kelsey Hightower]

On Thursday, June 14, 2012 1:51:45 AM UTC-4, Mike wrote:
>
> Thanks, 
> It appears to be something internal to the hiera function, so I'll have to 
> go digging in there to find out what's going on. 
>
> Cheers 


Are you in position to **test** the 1.0rc branches of hiera and 
hiera-puppet?
 

>
> On 14/06/2012, at 1:06 AM, Wolf Noble wrote: 
>
> > I had some issues with using boolean logic with data being fed to me by 
> hiera. I went for a slightly hacky option of: 
> > 
> > might help you, might be a BadIdea(™) 
> > 
> > (untested) 
> > 
> > 
> > class foo::params{ 
> > bool_to_be_tempname = hiera('some_TorF_key_as_a_string') 
> >  case bool_to_be_tempname { 
> >[tT][rR][uU][eE]: { 
> >  bool_to_be = true 
> >} 
> >default: { 
> >  bool_to_be = false 
> >} 
> >  } 
> > } 
> > 
> > 
> > On Jun 13, 2012, at 7:40 AM, Michael Knox wrote: 
> > 
> >> Hi, 
> >> I've been moving from extlookup to hiera, and it's generally gone 
> fairly smoothly, but I've run into a problem with one of our defines ... 
> >> 
> >> I get this error: 
> >> err: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: can't convert Array into String at ... 
> >> 
> >> The define uses an exec to install Perl CPAN modules and sets log 
> output based on a hiera lookup. 
> >> exec{"cpan_load_${title}": 
> >>  < cut …> 
> >>   logoutput   => hiera('cpan_logoutput'), 
> >> } 
> >> 
> >> If I remove that line, everything runs through fine. 
> >> 
> >> The yaml for hiera: 
> >> --- 
> >> cpan_logoutput: true 
> >> 
> >> Any ideas on what could be triggering this error? 
> >> 
> >> 
> >> -- 
> >> 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. 
> >> 
> > 
> > 
> >  
> > 
> > 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. 
> > 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 view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/2GdyZeaN6DoJ.
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] Re: Using simulation capability against a specific node

[Kelsey Hightower]

On Monday, June 25, 2012 9:39:13 AM UTC-4, williamstw wrote:
>
> I've just learned of the 'noop' flag on apply and it is really nice. 
> Only, I can't figure out how to get it to do what I want and I wonder 
> if I misunderstand how it's supposed to be used. 
>
> I've got several different types of nodes in a cluster where each type 
> gets some combination of the modules on puppetmaster applied to them. 
>
> So, when I change a module, I was thinking 'puppet apply --noop' would 
> allow me to see what that change would look like on a node of that 
> type.  Currently, it seems to compare to the "current" system - the 
> puppetmaster in this case.  So is there a way to do this same sort of 
> simulation against a specific node?  Or elsewhere I should be looking? 
>  Any pointers are greatly appreciated. 
>
> Thanks, 
> --tim 
>

I think what you want here is to run the follow command on the specific 
node:

*puppet agent* --test --*noop* 

-- 
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/-/qYTU-X6vx4AJ.
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] Re: Installing hiera

[Kelsey Hightower]

On Friday, June 22, 2012 3:25:49 PM UTC-4, llo...@oreillyauto.com wrote:
>
> My puppet master is behind a proxy and unable to connect to a gem repo, so 
> I used a different machine to fetch hiera and hiera-puppet gems, and the 
> hiera-puppet source tarball.
>
> I then did a gem install on them, and I made sure that hiera was in the 
> path, and extracted the hiera-puppet sources into my modulepath.
>
> I ran puppet agent on the master (as suggested by a comment on 
> http://puppetlabs.com/blog/first-look-installing-and-using-hiera/ ) and I 
> also did a service puppetmaster restart.
>
> I set up a basic hierarchy, with just a common layer for right now, and I 
> added some variables to it.
>
> When I do a puppet run, I get the following error:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> no such file to load -- hiera
>
> Did I miss a step, or am I doing something wrong?
>
> I am using puppet 2.7.14 on Lucid for my puppet master, and the agent in 
> question is running 2.7.16 on Precise.
>
> My hiera.yaml is:
> ---
> :hierarchy:
>   - common
> :backends:
>   - yaml
> :yaml:
>   :datadir: '/etc/puppet/environments/%{environment}/hieradata'
>
>
Did you ever get this working? 

-- 
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/-/FbGipFztkZ0J.
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] Re: Is this possible with Hiera - Puppet Module Development and using Hiera

[Kelsey Hightower]

On Friday, June 22, 2012 7:02:33 PM UTC-4, Peter wrote:
>
> Hi Joh,
>
> On Wednesday, 20 June 2012 03:18:46 UTC+10, jcbollinger wrote:
>>
>>
>> I confess that I don't follow what you are suggesting.  Hiera already 
>> supports module developers providing data, and module users overlaying 
>> their own on top, in the order of their choice.  What more would your 
>> suggestion provide in that area?  And why do module developers need to 
>> configure specific locations for (the root of) their data on the 
>> filesystem?  That should be under the control of module users (== the 
>> administrators of the master).  What am I missing?
>>
>>
> Thanks for taking the time to reply.
>
> Yes hiera provides support for module developers ... however I would argue 
> that it is limited for example, the hiera-puppet plugin is *hard-coded* to 
> only look for values in the module manifest directory for a file called 
> data.pp.
>
> This does allow for a very low threshold for module developers to start 
> implementing hiera in their modules (rename their existing params.pp files).
>
> I believe by extending the hiera-puppet plugin for module developers to 
> follow a similar convention as hiera for module users would make certain 
> things easier for module developers.
>
> By providing the ability to signal the hiera-puppet plugin (using a 
> module-hiera.yaml file (for lack of a better name)) a module developer 
> could reduce complexity and use the DRY principle to setup sane defaults 
> (either in a defaults.pp or in a defaults.yaml file) and than use layer on 
> top specific settings for Operating systems or even Hardware Types (as 
> examples).
>
> Sorry I don't have time right now to provide something in depth but a 
> brief example would be setting up ISCSI, the module I currently have has a 
> complex params.pp file for detecting particular setups.
>
> As a module developer I am interested in setting up a hierarchy such that 
> from most specific to least specific:   
> * Hardware_platform
> * Operating System
> * Defaults
>
> By defining this in the module-hiera.yaml file it makes it very easy for 
> me to signal to the module user what settings override which.
>
> I am not suggesting taking any control from module users, and to be 
> explicit user settings (if set) would override the module variable.
>
> Hopefully I have done a better job of explaining what I am thinking.
>
> Thanks,
>
> Peter.
>

I like where this idea is going. You would like a backend, hiera-puppet for 
now, to be able to lookup "default" data from the current module directory 
during parse time. Let's open a ticket (feature request) for this and 
workout the details.

-- 
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/-/Ib1O42g43JYJ.
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] Re: Extending Puppet using Rubygems

[Kelsey Hightower]

On Monday, June 25, 2012 9:19:01 AM UTC-4, jcbollinger wrote:
>
>
>
> On Saturday, June 23, 2012 7:38:20 PM UTC-5, Kelsey Hightower wrote:
>>
>> There is a pending pull request that adds the ability for Puppet to load 
>> Faces, parser functions, and report processors installed via Rubygems.
>>
>> https://github.com/puppetlabs/puppet/pull/873
>>
>> This means in addition to extending Puppet via pluginsync you would be 
>> able to simply do something like this:
>>
>>gem install puppetlabs-cloud-provisioner
>>
>> That would bring in all the gem dependancies and be ready for use without 
>> restarting Puppet. For more examples take a look at this ticket: 
>> http://projects.puppetlabs.com/issues/7788
>>
>> I would really love to get some feedback around this, and if you like it, 
>> add your vote to the ticket.
>>
>
>
> I will never use it, at least for any system that has a decent native 
> package manager.  As I have written before, it is a bad idea to give 
> multiple agents (e.g. gem and yum) overlapping management 
> responsibilities.  If it doesn't interfere with anything else, though, nor 
> take substantial effort to maintain then I won't vote against it.
>
>
> John
>

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. 
 

>  
>

-- 
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/-/OS_O3XoInLYJ.
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] Extending Puppet using Rubygems

[Kelsey Hightower]

There is a pending pull request that adds the ability for Puppet to load 
Faces, parser functions, and report processors installed via Rubygems.

https://github.com/puppetlabs/puppet/pull/873

This means in addition to extending Puppet via pluginsync you would be able 
to simply do something like this:

   gem install puppetlabs-cloud-provisioner

That would bring in all the gem dependancies and be ready for use without 
restarting Puppet. For more examples take a look at this ticket: 
http://projects.puppetlabs.com/issues/7788

I would really love to get some feedback around this, and if you like it, 
add your vote to the ticket.

Thanks.

-- 
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/-/dfuw73cfR9AJ.
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] Announcing Windows registry module initial release

[Kelsey Hightower]

On Wed, May 16, 2012 at 7:53 PM, Josh Cooper  wrote:

> Hello,
>
> We're pleased to announce the first release of the Windows registry
> module, version 0.1.0.
>
> This release provides the ability to manage registry keys and values
> on Windows 2003, 2003R2, 7, 2008, and 2008R2 systems.  It supports the
> most commonly used registry value types (REG_SZ, REG_MULTI_SZ,
> REG_EXPAND_SZ, REG_DWORD, REG_QWORD, REG_BINARY), as well as purging
> unmanaged registry values from a specified key.  The module can manage
> redirected registry keys and values when running on a 64-bit version
> of Windows.
>
> For example:
>
>  registry_key { 'HKLM\System\CurrentControlSet\Services\Puppet':
>ensure => present,
>  }
>  registry_value {
> 'HKLM\System\CurrentControlSet\Services\Puppet\Description':
>ensure => present,
>type   => string,
>data   => "The Puppet Agent service periodically manages your
> configuration",
>  }
>
> The best way to install this module is with the puppet module subcommand
> or the puppet-module Gem.
>
>puppet module install puppetlabs-registry
>
> More information about the module is available here:
>
>http://forge.puppetlabs.com/puppetlabs/registry
>
> Josh
>
> --
> Josh Cooper
> Developer, Puppet Labs
>
>
You guys are on it, and double kudos for kicking ass on Windows.


> --
> 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.
>
>


-- 
Kelsey Hightower
Developer
Puppet Labs
(678) 4719501

-- 
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: Puppet Sites. Your thoughts?

[Kelsey Hightower]

et cert revoke
> (replaced by `puppet site remove`)
>
> puppet cert sign
> (replaced by `puppet site accept`)
>
> puppet cert clean
>
> This command doesn't map cleanly to sites. In Puppet as it exists today,
> removing
> a certificate from the CA doesn't revoke permission to talk to other
> Puppet services.
> In Puppet Sites, removing a node from the site revokes permission for that
> node
> to ask the site where other Puppet services live. Because of this, we're
> replacing this
> with two commands (one being the replacement for `puppet cert revoke`):
>
> puppet site reject (reject a node's request to join the site)
> puppet site remove (remove a node from the site)
>
> In Puppet Sites, nodes are still identified by their certname. With the
> exception of a
> slight behavior change to the CA--so it can serve as the authoritative
> source of information
> about which nodes are in your site--the deprecation of these CA actions is
> a deprecation of
> semantics, not functionality.
>
> I'm happy to elaborate on the mental model these replacement commands are
> designed
> to support.
>
> - Daniel
>

I guess what people really want to know is: Will they be able to use
auto-signing? Will auto-signing still work like it does today?

I see the advantages for people who never intend to use auto-signing, but
the people who have accepted the risk do want to lose the "functionality"
of auto-signing.



>  --
> 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/-/W9hQXvYw3v8J.
>
> 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.
>



-- 
Kelsey Hightower
Developer
Puppet Labs
(678) 4719501

-- 
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 Sites. Your thoughts?

[Kelsey Hightower]

On Thu, May 10, 2012 at 12:44 PM, Daniel Sauble wrote:

> Hey all,
>
> I've been designing a new feature for Puppet, and wanted to get some
> kick-back from the community to see if you think this is needed or not. The
> feature is called Puppet Sites, and meets some specific goals by means of a
> few tasks.
>
>- Securely add nodes to your deployment without manually signing
>certificates on the CA...
>   - ...so that you can have the advantages of autosigning without its
>   security problems.
>
>
>- Get a list of all the nodes in your deployment...
>   - ...so that a single command can give you what previously you had
>   to trawl multiple services (ENCs, CAs, etc...) on each Puppet master in
>   your deployment to retrieve.
>
>  How does this work with ENCs? Will the ENC need to talk to Puppet sites
for node information such as environment settings? When nodes are added and
removed from Puppet sites will they be updated in the ENC and vice-versa.

>
>- Store connection information for Puppet services in a central
>location (accessible from manifests, puppet.conf, and defaults.rb)...
>   - ...so that you don't have to manage puppet.conf files on each
>   node in your population
>   - ...so that agent/master/CA configuration stays consistent across
>   your deployment
>   - ...so that you can update your config and fetch a new catalog in
>   a single operation.
>
> So will each node then need to be configured with the location to Puppet
sites?



> Thanks in advance for the feedback!
> - Daniel
>
> --
> 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/-/cdG9GFFqvYEJ.
> 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.
>



-- 
Kelsey Hightower
Developer
Puppet Labs
(678) 4719501

-- 
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 module... remove?

[Kelsey Hightower]

On Thu, May 10, 2012 at 12:35 PM, Philip Brown  wrote:

> Is there really no way to have puppet module, aka puppet-module, remove a
> module? It doesnt seem to exist in the usage message.
> Nor do I see a "show installed" option?


Philip,

We just updated the module tool and integrated it into Puppet core starting
with Puppet 2.7.14. I have also written two blog posts covering some of the
features here:

http://puppetlabs.com/blog/module-of-the-week-puppet-module-tool-part-2
http://puppetlabs.com/blog/module-of-the-week-puppet-module-tool-part-1




>
>  --
> 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/-/-EjkkYgWMKEJ.
> 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.
>



-- 
Kelsey Hightower
Developer
Puppet Labs
(678) 4719501

-- 
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] hiera rpm

[Kelsey Hightower]

On Wed, Apr 25, 2012 at 10:22 AM, Nick  wrote:

> Hi,
>
> Just wondered if there are any plans to put a heira RPM in the puppetlabs
> yum
> repositories (for EL6)?
>
>  http://yum.puppetlabs.com/el/6/products/i386/
>
> So far there doesn't seem to be one.


Yep, we are working on that, should have one available in the next week or
two.



>
> N
>
> --
> 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.
>
>


-- 
Kelsey Hightower
Solutions Engineer
Puppet Labs
1-678-471-9501

-- 
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-dev] Re: [Puppet Users] Telly: Nagios types moving into Module

[Kelsey Hightower]

On Tue, Apr 17, 2012 at 2:28 PM, Walter Heck  wrote:

> Yeah, right after that email I saw the 2.7.14rc1 release notes and
> answered my own question, my apologies :)


No worries, we're here to help.

-- 
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-dev] Re: [Puppet Users] Telly: Nagios types moving into Module

[Kelsey Hightower]

On Tue, Apr 17, 2012 at 2:19 PM, Walter Heck  wrote:

>
> On Apr 18, 2012 1:39 AM, "Nigel Kersten"  wrote:
>
> > Absolutely. This is the functionality we'll have available in Puppet.
> >
> > # puppet module list
> > /etc/puppetlabs/puppet/production/modules
> > └── nigelkersten-testmac (v0.0.2)
> > /opt/puppet/share/puppet/modules
> > ├── puppetlabs-pe_accounts (v1.0.2)
> > ├── puppetlabs-pe_compliance (v0.0.6)
> > ├── puppetlabs-pe_mcollective (v0.0.43)
> > └── puppetlabs-stdlib (v2.3.1)
>
> Just checking since that example mentions puppet enterprise modules: this
> will be in the community edition as well, right?
>
Yep, the next release of Puppet open source will have it baked in.

-- 
Kelsey Hightower
Solutions Engineer
Puppet Labs
1-678-471-9501

-- 
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-dev] Re: [Puppet Users] Telly: Nagios types moving into Module

[Kelsey Hightower]

On Mon, Apr 16, 2012 at 4:07 PM, Ken Barber  wrote:

> A pm2rpm tool perhaps Todd? :-).


Something like pm2rpm would work, but we need to have a least one standard
path for Puppet modules. I guess we can count on /etc/puppet/modules or
/usr/share/puppet/modules being part of the default module path.

-- 
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 to modify a file content?

[Kelsey Hightower]

On Mon, Apr 16, 2012 at 1:30 PM, Marco Parra D. wrote:

>  Hi Josh,
> Where can I find the complete fact's list to use on windows?...
>
> thank you in advance!
>
> Regards..
>

You should be able to run Facter directly on the system in question.


>
> On 16-04-2012 12:55, Josh Cooper wrote:
>
> Hi Marco,
>
> On Mon, Apr 16, 2012 at 7:22 AM, Marco Parra D. 
> wrote:
>
>> Hi guys, I trying to modify a file on Windows using puppet,  I got a
>> template file like this:
>> [default]
>> host = SOmeNAme
>>
>> [WinEventLog:Security]
>> disabled = 1
>>
>> is copied using puppet to the windows machine as C:\Program
>> Files\Soft1\inputs.conf
>>
>> And I need to replace the host line with the real name of the windows
>> machine:
>>
>> i.e.: host = machine1
>>
>> Is this possible using puppet for windows?
>>
>> Regards.
>
>
>  Yes, definitely. You should be able to specify the file content
> parameter as a template:
>
>file { 'C:\Program Files\Soft1\inputs.conf':
>  ensure => present,
> content => template('module/template.erb')
>   }
>
>  and then in your template template.erb, you can have it resolve the
> value of the host property using the agent's hostname fact:
>
>host = <%= @hostname %>
>
>  This page provides more information about puppet templates:
> http://docs.puppetlabs.com/guides/templating.html
>
>  Josh
>
>  --
> Josh Cooper
> Developer, 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.
>



-- 
Kelsey Hightower
Solutions Engineer
Puppet Labs
1-678-471-9501

-- 
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] Telly: Nagios types moving into Module

[Kelsey Hightower]

On Friday, April 13, 2012 3:06:52 PM UTC-4, Ashley Penney wrote:
>
> I think that would be OK.  I'm actually fairly nervous about this new move 
> towards dragging
> more and more out of the core into modules.  It wouldn't be so bad if 
> Puppet had a proper
> "packaging system" that handled dependencies and so forth, but as it 
> stands I'm just worried
> about reaching a situation where we're constantly telling people in 
> #puppet "oh, well first
> you need to get stdlib, nagios, yum, this, that, etc, that's why you can't 
> do this".
>

Newer versions of Puppet include an updated module tool that handles 
dependencies and some other niceties: Check out The Puppet Module Tool 
Screencast 
 

>
> However assuming this is going ahead then I think the error message should 
> probably for
> now tell the user that they've been moved AND spit out an appropriate 
> commandline to
> immediately import the module to the right place.
>
> On Fri, Apr 13, 2012 at 1:55 PM, Michael Stahnke 
> wrote:
>
>> For the next major Puppet version, code-named Telly, we have some
>> changes coming.  This is the first in a series of emails around these
>> changes and may require some input from the community.
>>
>> For Telly, the nagios types will be moved into a module.  This allows
>> them to be iterated on in isolation from the rest of Puppet's core
>> release cycle and process. In the future we have plans to move several
>> other types into modules that can be individually maintained,
>> improved, tested and used.
>>
>> The module for Nagios will be available on the Forge.
>>
>> The upgrade path is the thing we need some feedback about.  The basic
>> steps to upgrade would be to setup a Telly master, and then install
>> the Nagios module via the Puppet Module Tool, which ships integrated
>> with 2.7.13+ and Telly.
>>
>> The only caveat with this is that if, in the past, you were relying on
>> the Nagios types and forget to install that module (or are unable to
>> for some reason), you would get a failure.  The best proposal we could
>> come up with was to have the platform team add some code that lets the
>> user know that the Nagios types have moved. This basically moves this
>> into a 'fail-well' state.  We'll try to provide the best information
>> possible to the end-user about what is going on.
>>
>> Is that an acceptable path moving forward?  Comments and discussion 
>> welcome.
>>
>>
>> Mike Stahnke
>> Community Manager
>>
>> --
>> 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 view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/87YHcX_tf9UJ.
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] Could not find node. cannot compile

[Kelsey Hightower]

On Mon, Feb 27, 2012 at 4:33 PM, Nan Liu  wrote:

> On Mon, Feb 27, 2012 at 1:17 PM, Mohamed Lrhazi  wrote:
> > From my ENC, I return something like, for a given node:
> >
> >  nfs_mounts:
> >  - [/data, fas3319-518.example.com:/vol/crddb_data/test]
> >
> > and in my manifests I added:
> >
> >   define mount_nfs_shares() {
> >$mount_point = $name[0]
> >$mount_device = $name[1]
>
> $name is not an array, but rather just the resource title, so you
> can't do this, you need to pass parameters to the define such as:
>
> define mount_nfs(
>  $mount_point = $name,
>  $mount_device
> ) {
> ...
> }
>
> This is now a resource which can be declared as:
>
> mount_nfs { '/data':
>  mount_device => 'fas3319-518.example.com:/vol/crddb_data/test',
> }
>
> >notice("mount_point: ",$mount_point)
> >notice("mount_device: ",$mount_device)
> >
> >file{ $mout_point: ensure => directory }
> >mount { $mount_point:
> >device => $mount_device,
> >name => $mount_point,
> >require => File[$mount_point],
> >}
> >}
> >mount_nfs_shares { $nfs_mounts: }
> >
> > This results in error:
> >
> >
> > Feb 27 16:10:07 pirates puppet-master[16073]: [daemon.err] Could not
> > find node 'nodename.example.com'; cannot compile
> >
> > The idea of course is for me to be able to specify for each node, in
> > my ENC, a list of NFS mount it needs, and have the corresponding
> > puppet resources created and compiled for each.
> >
> > Why is this not working? And what would be better way of achieve my goal?
>
> Defines are resources, you can not pass resources via ENC. You have
> two options, create a class that passes the options, or in your
> example, I think you are looking for something like create_resources
> function and pass the resources hash to create mount
>

+1

-- 
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: Could not find node. cannot compile

[Kelsey Hightower]

On Mon, Feb 27, 2012 at 4:32 PM, Mohamed Lrhazi  wrote:

> Chaging my ENC to output this, adding double quotes:
>
>  nfs_mounts:
>  - ["/data", "fas3319-518.uis.georgetown.edu:/vol/onecrddb_data/test"]
>
> and adding a  notice($nfs_mounts)  to the manifests, gives this log:
>
> [daemon.notice] (Scope(Class[Gu_misc])) nfs_mounts:
> /datafas3319-518.example.com:/vol/onecrddb_data/test
> [daemon.notice] (Scope(Class[Gu_misc])) nfs_mounts:  /data
> fas3319-518.example.com:/vol/onecrddb_data/test
>
> [daemon.err] name is not an hash or array when accessing it with 0 at
>
> /etc/puppet/environments/production_ml623/modules/gu_misc/manifests/init.pp:68
> on node nodename.example.com
> [daemon.err] name is not an hash or array when accessing it with 0 at
>
> /etc/puppet/environments/production_ml623/modules/gu_misc/manifests/init.pp:68
> on node nodename.example.com


Ok, so now your ENC is returning data for the node, good. Now you seem to
be reference some var $name, but based on your example it seems that you
should be using $nfs_mounts.

Also, looks like in you ENC it should be:

 nfs_mounts: ["/data", "fas3319-518.uis.georgetown.edu:
/vol/onecrddb_data/test"]

-- 
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] Could not find node. cannot compile

[Kelsey Hightower]

On Mon, Feb 27, 2012 at 4:17 PM, Mohamed Lrhazi  wrote:

> From my ENC, I return something like, for a given node:
>
>  nfs_mounts:
>  - [/data, fas3319-518.example.com:/vol/crddb_data/test]
>
> and in my manifests I added:
>
>   define mount_nfs_shares() {
>$mount_point = $name[0]
>$mount_device = $name[1]
>
>notice("mount_point: ",$mount_point)
>notice("mount_device: ",$mount_device)
>
>file{ $mout_point: ensure => directory }
>mount { $mount_point:
>device => $mount_device,
>name => $mount_point,
>require => File[$mount_point],
>}
>}
>mount_nfs_shares { $nfs_mounts: }
>
> This results in error:
>
>
> Feb 27 16:10:07 pirates puppet-master[16073]: [daemon.err] Could not
> find node 'nodename.example.com'; cannot compile
>

The first thing we need to do is resolve this error. What do you get when
you pass 'nodename.example.com' to your external node script? What exit
code do you get?

-- 
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: opensource VPN modules

[Kelsey Hightower]

On Fri, Feb 10, 2012 at 10:24 AM, Raffael Schmid  wrote:

>
> Hi Kelsey
>
> On Fri, 10 Feb 2012, Kelsey Hightower wrote:
>
> > > Check minehttps://github.com/luxflux/puppet-openvpn, I think it is
> > > complete. Or which options are you missing?
> >
> > Raffael, cool module, how can I help you get that on the Puppet Forge:
> > http://forge.puppetlabs.com. Looks like you are only missing a
> > metadata file and an account on the Forge.
>
> I've got an account on the Forge and wanted to put it there... I
> dunno why I failed :) Think it's because it misses some tests...?
> Are they needed? Whats the easiest way to generate a metadata file?
>

The tests are not required.

One way to generate the metadata file is to use the puppet module tool:
https://github.com/puppetlabs/puppet-module-tool

Once you have it installed run the generate command:

puppet-module generate username-modulename

You can grab the Modulefile from there and add it to your git repo. Once
you have a Modulefile you can use the puppet-module build command to
generate a release package.



-- 
Kelsey Hightower
Solutions Engineer
Puppet Labs
1-678-471-9501

-- 
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] Re: opensource VPN modules

[Kelsey Hightower]

On Feb 10, 10:12 am, Raffael Schmid  wrote:
> Hi Gabriel
>
> On Thu, 09 Feb 2012, Gabriel Filion wrote:
> > Do you guys know of opensourced puppet modules for managing VPN services?
>
> > I've only found a handful of modules for openvpn that seemed less than
> > complete.
>
> Check minehttps://github.com/luxflux/puppet-openvpn, I think it is
> complete. Or which options are you missing?

Raffael, cool module, how can I help you get that on the Puppet Forge:
http://forge.puppetlabs.com. Looks like you are only missing a
metadata file and an account on the Forge.

-- 
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] Re: puppet 2.6.13-2.el5 not writing logs

[Kelsey Hightower]

On Feb 10, 7:52 am, Sam F  wrote:
> Hi every one,
>
> I have a strange behavior with my puppet agent on CentOS 5.7.
>
> The agent does not write into the log file when it runs as a daemon.
> Nevertheless, It does when it is run manually by "puppet agent -t".
>
> And the behavior is the same even if I specify explicitly the log file
> on the command line like :
>
> /usr/bin/puppet agent --logdest=/var/log/syslog
>
> Here is my puppet.conf
> ---
> [main]
> vardir=/var/lib/puppet
> ssldir=/var/lib/puppet/ssl
> rundir=/var/run/puppet
> factpath=$vardir/lib/facter
> pluginsync=true
> server=puppetmaster01.back.adencf.local
> #server=puppetmaster02.int.adencf.local
>
> [agent]
> environment=development
> #listen = true # Issue on CentOS 5.7 confirmed by a bugreport on
> PuppetLabs
> report = true
>
> In /etc/sysconfig/puppet
> ---
> # Defaults for puppet - sourced by /etc/init.d/puppet
> # Start puppet on boot?
> START=yes
>
> # Pull puppetmaster periodicaly
> PUPPET_EXTRA_OPTS=""
> PUPPET_LOG="/var/log/syslog"
> PUPPETD="/usr/bin/puppet agent"
>
> PUPPET_LOG="/var/log/syslog"
>
> Have any one of you an idea about that ?

Can you try and set autoflush to true?

http://docs.puppetlabs.com/references/2.7.9/configuration.html#autoflush

-- 
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] Re: SSL certificates issues with some of the nodes

[Kelsey Hightower]

On Feb 10, 8:59 am, mukulm  wrote:
> Hi,
>
> I am using puppet open source & their are above 2000 nodes in my
> network & getting SSL certificates issues with some of the remote
> nodes & they are not in sync with puppet server where others are in
> sync with server & date of the nodes systems are in sync with ntp
> server, also tried the following as,
>
>    1. Deleted the nodes certificate on the puppet server
>    2. Deleted the SSL directory of the agent.
>    3. Run puppet agent --test on that agent to generate a new
> certificate request.
>
> but I have to regularly repeat the above process within a timeframe
> (weekly or monthly) so is there any other way other than this so that
> all of my agent should be in sync.
>
> Also how can I find the sync & unsync count    ?
>
> Thanks
> mukulm

To help clarify things, are all your nodes and masters in sync with
the same NTP server? This is a common source of the issues you are
describing.

If you are still running into issues can you post (pastbin) the errors
so
others can help you troubleshoot?

-- 
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] Re: How do I track updates to forge modules?

[Kelsey Hightower]

On Feb 2, 5:55 pm, John Warburton  wrote:
> Is there a way to "watch" modules and be notified if they are updated?
>
> I can't see anything obvious in the documentation
>
> Thanks
>
> John

Currently there is no easy way to "track" when modules are updated on
the Forge. One way I can think of to track updates to modules, but not
necessarlly releases to the Forge, would be to follow the project on
Github.

For example, if I wanted to track updates to the nginx module by
BenoitCattie

http://forge.puppetlabs.com/BenoitCattie/nginx

I could follow his Github repo here: http://github.com/BenoitCattie/puppet-nginx

I'm fully aware not everyone will have a corresponding github repo for
their module on the Forge, but so far this has been the convention.

This also sounds like a really good feature request which can be
opened here: https://projects.puppetlabs.com/projects/module-site

-- 
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-module-tool question

[Kelsey Hightower]

On Feb 10, 2012, at 8:41 AM, Darin Perusich wrote:

> The puppet-module-tool GIT pages says it's been converted into a
> puppet face and merged into puppet core. Does this make puppet-module
> obsolete or does it still need to be installed?

The puppet module tool still needs to be installed, sorry for the confusion. If 
you would like to use it right now, please following the installation 
instructions on the github page (gem install puppet-module). Once the new 
version of the module tool is ready for release, we will deprecate the current 
stand-alone version, but it will stay around to support users running older 
versions of Puppet.


> I'm running puppet
> 2.7.9 but this "face" is not included so obviously it's not available.
> 
> Can someone provide a little clarification please.

+1 one making this more clear.

> 
> --
> Later,
> Darin
> 
> -- 
> 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] Using LDAP with puppet

[Kelsey Hightower]

External Node Classifier:
http://docs.puppetlabs.com/guides/external_nodes.html

On Thu, Feb 9, 2012 at 2:15 PM, Daniel Bahena  wrote:

> Sorry to ask but, what's ECN?
>
> Best regards,
> --
> Kwame
> On Jan 26, 2012 11:45 AM, "Matt Ackerman"  wrote:
>
>> Does anyone have experience using LDAP as the ENC at medium to large
>> scale? We have around 600 nodes but will quickly grow that to 2000 or so in
>> short order.
>>
>> If so, is it working well? Would you do it again? If it didn't work what
>> did you replace it with?
>>
>> We are thinking of using it and was looking for a little feedback from
>> the group if anyone has done this. On the surface it sounds very nice to
>> have the flexibility of a standards based system like LDAP and I know LDAP
>> can scale very well for read intensive operations.
>>
>> Cheers!
>>
>> -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-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<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.
>



-- 
Kelsey Hightower
Solutions Engineer
Puppet Labs
1-678-471-9501

-- 
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] Re: Compiled catalog arount 70s

[Kelsey Hightower]

70s sounds does sound a bit high for managing only three resources,
but more info is required before I can really answer your question.

How did you install Puppet? (OS packages, gem?)
What OS are you running, and can you provide some info about the
Hardware?

Also, if you have a sample of the manifest that you are using that
would be great as well.

On Jan 27, 5:02 am, Antidot SAS  wrote:
> Hi everyone,
>
> I am using puppet 2.7.9 and ruby 1.8.7 on debian box. I don't a lot of
> modules right now: just one module that create user + dotfile + ssh key and
> compiled catalog takes around 70s do I have to worry is that big.
>
> Does the compiled time scale with the module number? Do I have to make sure
> I don't cross a certain limit?
>
> Regards,
> JM

-- 
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] Announce: puppet-dashboard-face alpha

[Kelsey Hightower]

I would like to present the alpha release of puppet-dashboard-face: A
Puppet Face for interacting with Puppet Dashboard.

This release is available for download at:
https://github.com/khightower/puppet-dashboard-face

Making Puppet Dashboard accessible from the cli:

$ puppet dashboard search nodes --class class-name
$ puppet dashboard list classes
$ puppet dashboard list groups
$ puppet dashboard list nodes
$ puppet dashboard report failed


Documentation is available at:
https://github.com/khightower/puppet-dashboard-face/blob/master/README.md

Please report feedback or issues via github at:
https://github.com/khightower/puppet-dashboard-face/issues

-- 
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] Re: exec inside a function bombs and kills the puppetmaster

[Kelsey Hightower]

I like the idea of having puppet manage a directory by mirroring it
using rsync. The function you have seems pretty good, one thing
missing is some logging. I have run in to times where you only want to
sync on puppetruns and not during a predetermined time period using
cron. I normally write scripts that issue a puppetrun for a specific
host as part of it's execution.

Also did you every git the mirror function to work?

On Jul 13, 2:28 pm, Scott Smith  wrote:
> Jeff wrote:
> >   newfunction(:mirror) do |args|
> >     user  = args[0]
> >     host  = args[1]
> >     src   = args[2]
> >     dest  = args[3]
> >     cmd   = "/usr/bin/rsync-vaz --delete --delete-during --rsh=\"ssh -
> > i /var/puppet/.ssh/" +
> >             user +" -l " + user +"\" " + src + " " + host + ":" + dest
> >     exec(cmd)
>
> You might want to sanitize those parameters before blindly passing them
> to a shell.
>
> -scott
>
> --
> sc...@ohlol.net
>
> http://github.com/ohlol
--~--~-~--~~~---~--~~
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] Re: Regular Expressions

[Kelsey Hightower]

Based on a snippet from the group provider, it looks like the answer
to your question is yes.

Taken from: puppet/lib/puppet/type/group.rb

munge do |gid|
case gid
when String
if gid =~ /^[-0-9]+$/
gid = Integer(gid)
else
self.fail "Invalid GID %s" % gid
end
when Symbol
unless gid == :absent
self.devfail "Invalid GID %s" % gid
end
end

return gid
end




On Apr 29, 2:31 pm, jekhokie  wrote:
> Is there any way to use regular expressions within a custom type's
> provider, or are they not yet implemented within Puppet?  If they are,
> do you simply execute them as usual according to regular Ruby syntax?
--~--~-~--~~~---~--~~
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] Re: Update RPM through Puppet

[Kelsey Hightower]

Not sure if it would be worth it for you, but I have setup up a local
"puppet" YUM repo to solve this very problem. I add updated RPM's from
EPEL and then run "yum update" on the puppetmaster, and then the
clients.

On Apr 29, 7:19 am, Grezly  wrote:
> I'm using currently puppet 0.24.6 and I'm a new user to it.
> Now i would update all the clients to 0.24.8, i've allready got the
> rpm's.
>
> Is here a nice and clean way for to do this, because i couldn't find
> such a thing.
--~--~-~--~~~---~--~~
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] Re: Puppet and yum repositories

[Kelsey Hightower]

The first thing I would do; split the repositories up. In your case I
would have only the CentOS specific repositories available under "/etc/
yum.repos.d/" for CentOS. servers.

There are several ways to achieve this.

- During the Kickstart process add a repository specifically for
CentOS or Fedora in the "%post" section.
- Create separate base classes, one for Fedora and one for CentOS. In
each base class use the "yumrepo" type to define the different YUM
repositories.



On Apr 29, 11:14 am, "t.kend...@kew.org" 
wrote:
> I'm running puppet 0.24.6 on CentOS 5.2 from a puppetmaster on a
> virtual server to a variety
> of client servers both virtual and metal running either CentOS 5.2 or
> Fedora Core 10. I want to
> extend this to servers running RHEL 5 (and 6) in the near future.
>
> My problem is I have puppet set up with all repositories (mirrored
> locally using cobbler)
> included in one file in /etc/yum.repos.d/kewrepos.repo on the
> puppermaster. This file contains
> both Centos and Fedora repos and when I run a yum update I just --
> disablerepo=whichever I don't want,
> which can be done as a cron job.
>
> The difficulty is sometimes puppet runs yum automatically, which loops
> on a CentOS webserver
> trying to reinstall httpd, getting confused by the presence of Fedora
> repositories.
>
> My question is how can I set up puppet so that I can tell, once and
> for all, The Fedora boxes to
> look at the Fedora repos and the CentOS boxes to CentOS repos only? I
> want to be able to
> configure unlimited repos in the future for workstations (Fedora) and
> servers (CentOS or RHEL).
>
> Thanks in advance
>
> Tim Kendall
>
> I just added Kew Gardens where I work to your Wiki list of users
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---