similar to: YUMREPO { productname => PowerEdge 2650}

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

Hello All, In all the examples that I see you configure one repo per file; i.e: yumrepo { "testing.com-repo": baseurl => "http://repos.testing.com/fedora/$lsbdistrelease/", descr => "Testing.com''s YUM repository", enabled => 1, gpgcheck => 0, } But how do I specify multiple entries to the same file?. For instance, I just one to have one

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Hello All, I''m trying to start using external nodes under foreman, and I''m running into some issues. I have the entries in puppet.conf: [main] external_nodes = /etc/puppet/external_node.rb node_terminus = exec The enternal_node.rb script is the one that came with foreman: #!/usr/bin/ruby # a simple script which fetches external nodes from Foreman # you

Hello All, I''m new to puppet, and I''d like to know: Is there a formal best practices guide for syncing { /etc/passwd, shadow, group, hosts} across clients from the master? For instance; is it a better practice to make a hard link to these files and share the link, as opposed to just sharing the files directly via a target in fileserver.conf? Inquiring minds want to know...

Hi, are there any good ways of scripting an inventory of managed resources on all nodes? I''ve found the inventory script by R.I.Pienaar ( http://www.devco.net/archives/2010/02/26/what_does_puppet_manage_on_a_node-2.php) which does what I want but only locally on each client. Is there any native way of syncing the client_yaml data centrally or any other way of doing this? I need a

My understanding was that at the beginning of each run the puppetmaster imports all modules so that any includes at the top level are applied directly. However, I am not so sure anymore. I''ve been tracing how this works and it seems like modules are included more lazily. In other words, when able_to_import is called seems like when the magic happens, rather than up front when the run

When attempting to execute the mcollective puppet plugin: # mco puppet runonce -v aixl : execution expired aixj : execution expired I get an error, ''execution expired'' on some hosts. However, these hosts respond via mco ping and, I have verified the date/time on the servers. The puppet agent is also

Every time a client checks in with the puppetmaster, I receive the following error in the client logs: Wed Aug 24 19:55:27 +0000 2011 Puppet (notice): Starting Puppet client version 0.25.5 Wed Aug 24 19:56:05 +0000 2011 Puppet (err): Could not prefetch package provider ''yum'': Execution of ''/usr/bin/python /usr/lib/ruby/

With 0.25 we can use the split function to parse a string in to an array. In puppet how can I reference a single element of that array? $temp = "1,2,3,4" Then i''d lilke to do : $val = split($temp,'','')[0] Thanks, Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

Hi, I am running puppet 2.6.12 on a SLES11SP1 server. I get the following error message as part of the puppet catalog run on a SLED11SP1 client. Augeas[sap_host_entries](provider=augeas): Opening augeas with root /, lens path , flags 0 err: /Stage[main]/Sap/Augeas[sap_host_entries]: Could not evaluate: unknown error - Failed to initialize Augeas Can somebody shed some light on the error

I was working with yumrepo, defining new entried and seeing them appear in /etc/yum.repos.d After considerable tinkering, and with the sad discovery that resource { ''yumrepo'': purge => true } does not work, I moved my working /etc/yum.repos.d to /etc/yum.repos.d-old and re-ran my catalog. To my surprise, the repo entried were appended to /etc/yum.conf Long story short: I

Hi list, Reading the thread "can a class require an other class?" it''s been mentioned that perhaps one way forward for the Puppet language is to phase out the include keyword in favour of parametrised classes. I''m thinking of my Puppet and the several levels of include chaining I use and I''m wondering how on earth that''d be possible. Maybe

hello, Till now hiera-puppet was the only way I know that allowed hiera data to be loaded from inside a module. The problem with this was that it was still subject to the site specific hierarchy which means a module author had a pretty hard time to store his data in a proper way in his module thus perpetuating the use of the params classes pattern. Now that Puppet 3 is out and it''s gem

Anyone able to explain why "$fqdn" works and "$environment" doesn''t in: $extlookup_precedence=["%{fqdn}","%{environment}","common"] How to reproduce it: ----------------------------- - In "/etc/puppet/manifests/site.pp" : $extlookup_datadir = "/etc/puppet/manifests/extdata"

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

How do folks feel about getting Puppet job listings on this list? I''ve rejected a few that we quite spammy, but when the subject matter really is a system admin with puppet experience, the decision becomes a bit different. I''m looking for general feelings. A simple +1 or -1 would be great. Mike -- You received this message because you are subscribed to the Google Groups

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

We are using Enterprise Ruby - I want to dig into Mcollective; however, there is no installation script in the *.tgz. Also, the rpms have various requirements from the stock distribution (RHEL5 in my case) that are already present under our Enterprise Ruby installation. Is there some clever way to weave this together. How to install the Mcollective without the typical setup.rb scripting.

I have a puppet server and various puppet agents. I want to do mcollective stuff. So please anyone tell me what should i install on puppet server and agent to run mcollective? Is there any need to install ActiveMQ also and where should i install it? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe