similar to: Thoughts on job listings?

Since our move to github for pull requests and patches, the usefulness of puppet-dev has declined significantly. puppet-dev used to be a great list for development discussion of puppet and the ecosystem around it. With the information and pull request emails from github, unless everybody has finely-tuned their email clients, the puppet-dev list has turned into mostly noise. We have a goal to

Hi all, i planned for a startup to install one of this gui tools. But if i look in the documentation, or google it, i find no results which helps. If i would like to install the rpm package i get the following dependencies problems rpm -i puppet-dashboard-1.2.3-1.el6.noarch.rpm warning: puppet-dashboard-1.2.3-1.el6.noarch.rpm: Header V4 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 error: Failed

Hi, I am trying to install puppet-dashboard on my puppet server, which is running CentOS 5.4. However, I cannot find a RPM for REHL 5 on http://yum.puppetlabs.com/. So the question is how I can get the puppet-dashboard rpm for CentOS 5.4? Thanks. Hai Tao -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send

Got the following: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload package: Could not autoload /usr/local/lib/site_ruby/1.8/puppet/provider/package/windows.rb: no such file to load -- windows/error at /etc/puppet/modules/php/manifests/init.pp:28 on node This after I reverted back to puppet v2.7.11 on my master. Not running windows anywhere... why am I

Greetings, I''d like to remove the cruft (no longer maintained) areas of yum.puppetlabs.com. I fear they only cause confusion and offer less-than-desirable experience for our users. I''d like to remove /base /prosvc /porsvc.unsigned /SRMS /sources I''d like to do this some time next week. The stuff mostly found in base is available elsewhere and signed properly. The

Puppet Labs is really thrilled to announce, in conjunction with EMC, our new open source bare metal provisioning tool: Razor. Razor is next generation provisioning software that handles bare metal hardware and virtual server provisioning with inventory discovery and tagging, rule-based policy management, and extensible broker plugin integration. It integrates closely with Puppet and Facter. The

I want to use Puppet and Facter on a machine where I don''t have sudo or root access privileges. I won''t be using Puppet for anything that requires that level of access, so I should be OK if I can get it on the box. Any advice on how to proceed? Currently the Facter installer complains that it doesn''t have privileges for /usr/bin/facter. I assume Puppet will have the same

Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was being previewed in the 2.7.7rc series as well as some new content. Key highlight in this release (beyond items from 2.7.7rc series) are: * Allow providers to be selected in the run they become suitable * Showdiff is now not auto-enabled when running in noop mode * Provide default subjectAltNames while bootstrapping

This a feature release candidate (number 3) of Puppet Dashboard. If you''re wondering what happened to rc2, it was internal only. Our CI system found a few issues before we released it to the public. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download

I am currently using Puppet''s firewall module: http://forge.puppetlabs.com/puppetlabs/firewall I am trying to have Puppet flush iptables before it applies firewall rules. I tried the following: exec { ''clear-firewall'': command => ''/sbin/iptables -F'', refreshonly => true, } Firewall { subscribe =>

PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

Hi, I''m having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo''s to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR

Welcome to the first Puppet Dashboard maintenance release of the new year. This release includes a security update to address CVE-2012-0891, a XSS vulnerability discovered by David Dasz <david@dasz.at>. We have classified the risk from this exposure as moderate. All Puppet Dashboard users are encouraged to upgrade when possible. Puppet Enterprise users should visit

Hy I m new to puppet. I ''d like to install epel.repo on a my node and this is the module that I ve created class epel { package { ''epel'': provider => ''rpm'', ensure => installed, source => ''http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm'' } } Now my connection on node when I

We have discovered a security vulnerability (“AltNames Vulnerability”) whereby a malicious attacker can impersonate the Puppet master using credentials from a Puppet agent node. This vulnerability cannot cross Puppet deployments, but it can allow an attacker with elevated privileges on one Puppet-managed node to gain control of any other Puppet-managed node within the same infrastructure. All

Hello, I add a node Fedora 17. The reports are a aperture in puppet-server in /var/ lib/puppet/reports but not in Dashboard. While all other Fedra (16, 15, 14) are visible in Dashboard. Do you have an idea? Thank you. mauris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Hi, am trying this rule: firewall { ''100 allow ssh from GUNET'': proto => ''tcp'', dport => ''22'', source => [''10.0.0.0/8'',''192.168.0.0/16'',], action => accept, } and it only seems to add a rule for the first subnet. The second is silently

On Feb 1, 2012, at 8:06 PM, Nan Liu wrote: > Puppet uses REST, so you can run puppet master on 443 to work around firewalls. I would like to get a bit more information on this. Is it as simple as setting all the ports in puppet.conf to 443 on master and agent ? “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact

Hi, This follows on a bit from the previous thread ''trouble with hiera and puppet defines'' [1] Up to now I''ve had a large file of virtual resources and then enabled them on demand on various services. The very standard. @metric{''1234: one => 1 two => [1,2] } @metric{''abcd'': one => a, two => [b,c] } and