similar to: puppetlabs-stdlib

I have been working on adding some predicate functions to puppetlabs-stdlib that test things based on ''interfaces'' and related facts. The functions themselves seem to work fine in my manifest-based smoketests, but I am running into trouble that may or may not be due to my ignorance about rspec or Facter. Something needs to be done to initialize Facter because

Hmmm.... So I was just trying the extlookup function that comes with puppet 2.6.1. It now lets you do this: $version = extlookup("rsyslog_version", "present", "packages") which, according to the documentation: # This will look for a version configured in packages.csv and then in the rest as configured # by $extlookup_precedence if it''s not found anywhere

I''ve been struggling with puppet variable scope all day, well, for several months actually. I think I have pretty simple requirements. For any given node, I want to be able to set a series of variables and include a set of classes, based on three different aspects of a node, being physical location, operating system, and function. If I try and do this with classes, I find that variables

How can I pass an array to a define? It''s not documented in the puppet language guide. I''ve got: define lvm::create_vg ( $pvdisks ) { exec { ''pvcreate'': command => "/sbin/pvcreate -yf $pvdisks", unless => "/sbin/pvdisplay $pvdisks", ... } } class someclass { lvm::create_vg {

I''ve got this: file { ''/opt/sugarsync/tomcat/tomcat-home/current'': ensure => "tomcat-$config[''tomcat_version_server'']"; where $config[''tomcat_version_server''] was set with extlookup (the yaml one), by loading: --- tomcat_config: tomcat_version_server: 6.0.20-1 tomcat_version_libs: 1.0-1

I have an array: $nodes = [''gfs01'' ,''gfs02'', ''gfs03'', ''gfs04] and a string variable: $brick_store = "/var/bricks" How can I append "/var/bricks" to each item in the array? Lack of a looping construct makes this challenging in puppet. Such that: brick_array = [''gfs01:/var/bricks'',

Hi, I''m gettinng a dependency cycle when using PE 2.7, puppetlabs::mrepo, "role classes" and hiera : I''m trying to mirror RHN repos : # ROLE CLASS > class site::yum_repository{ > > $repos = hiera(''site::yum_repository::repos'') > create_resources(mrepo::repo::rhn, $repos) > } > # HIERA DEFAULTS >

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

Hi all, We are currently using the regsubst function of Puppet to generate some information out of our hostnames (customer, environment, and so.). The manifest is running fine since months. 7: $customer = regsubst($::fqdn, ''(^[^-]*)-[^-]*.*'', "\\1") 8: $environment = regsubst($::fqdn, ''^[^-]*-([^-]*).*'', "\\1") 9: $product =

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

In puppet stdlib doc here at https://github.com/puppetlabs/puppetlabs-stdlib, it only mentions its support for puppet 2.6 and puppet 2.7. Puppet 3.0.1 is not listed there. Why puppet 3.x is not listed in the above doc as supported? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

So, this has always puzzled me a bit. By convention, init.pp contains one class, named the same as the module. However, what is the convention when the module may have multiple external access points? Say you have a module called ''syslog'' which provides both a client and a server class. I typically have used syslog::server and syslog::client. I''ve ended up using this

Anyone know where I can find a good chrooted named module for centos? Named as chroot is ugly... soft and hard links everywhere... 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

Does anyone have some examples of using this create_resources function, https://github.com/puppetlabs/puppetlabs-create_resources, ? Based on the README example I can''t figure out exactly how to change from using defines to using this function. Maybe I misunderstand the purpose of create_resources...is it to replace defines, or is it to allow ENCs (for example) to use a define? Below

I''m trying to upgrade from 2.6.7 to to 2.7.6 and I''m running into an issue in my extlookup() calls. A lot of the variables which should be defined aren''t defined within extlookup.rb. I''ve tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slightly to provide some debug output.

Anyone, I''ve read this doc several times: http://docs.puppetlabs.com/guides/plugins_in_modules.html As a whole, it really doesn''t make sense. It seems pretty obvious it was written by someone with deep knowledge of the subject, but there is little context for someone like me. Is there better documentation somewhere? Doug -- You received this message because you are

We are happy to announce the first public release candidate of our Puppet Cloud Provisioner. This release is available for download at our Module Forge: http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/> Extensive documentation can be found at: http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html Please report feedback via the

Hi, I have been trying to improve the coding of some of my puppet recipes and had some trouble so wrote this: http://blog.wl0.org/2011/05/thoughts-about-extlookup-in-puppet/ Comments on the web seem to indicate that extlookup() solves "all problems" but I don''t really see that and hence have proposed a possible way to keep the data closer together and make the extlookup()

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

I''m new to Puppet, and I''m a software developer, not a sysadmin, so be gentle. I have puppet managing some files via templates, and one of the template variables that needs to be plugged in is a password of sorts that shouldn''t be generally available. In particular, it can''t be stored in the manifest, as that''s stored in version control, and the