similar to: Re: [Puppet-dev] Re: Distributed Puppet Architecture and Management

G''day. We are proud to announce that Puppet 2.7.0RC2 is now available. Notable Features and Bug Fixes: pkgutil provider We have improved pkgutil provider support, resolving #4258 Faces We have made substantial usability improvements to the faces, including documentation accessible through the puppet help subcommand: puppet help <face> [action] There have also been a

Hello All, Unable to install Puppet Enterprise v2.0.0 for RHEL 5-x86_64. [root@1801 puppet-enterprise-2.0.0-el-5-x86_64]# ./puppet-enterprise- installer -a answers/full_suite.answer.sample ============================================================================================================================ Puppet Enterprise v2.0.0 installer for el-5-x86_64

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hello all, To experiment with Puppet Enterprise (we already use open source) and to create a case for our management to buy it, I''m trying to set up a Puppet Enterprise environment on some virtuals. While the puppet part works fine, and the client I''ve set up is doing fine as well, it seems the Live Management part is not. When I click on the Live Management tab it only

There has been a vulnerability discovered in Puppet (CVE-2011-3848). # Recommended Action # Puppet Labs has an updated version of Puppet available at the following locations: * http://puppetlabs.com/security/hotfixes * http://puppetlabs.com/downloads/puppet The fixed versions are 2.6.10 in the 2.6.x branch and 2.7.4 in the 2.7.x branch. The hotfixes page also contains updated Puppet

I have a test setup like this: host ======= *puppet-idc*: Ubuntu 12.04 running ActiveMQ, Mcollective, puppet agent and server *puppet-node1*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node2*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node3*: CentOS 6.3 running MCollective and puppet agent I installed the *mcollective-plugins-puppetd plugin* on all *3 Ubuntu

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

Hi All, I have a working installation of a Puppet Master (CA) with Puppet agents, this using The Foreman. I really see the usage of Puppet this way but because The Foreman supports pushing your classes/templates to you nodes (agents) and uses the depricated Run/Kick for it I''m looking into Mcollective. Mcollective is supported by The Foreman since 1.2, the version I''m

Puppet 2.7.15rc1 is a maintenance release candidate for Puppet in the 2.7.x series. Downloads are available at: * Source http://downloads.puppetlabs.com/puppet/puppet-2.7.15rc1.tar.gz RPMs are available at http://yum.puppetlabs.com/el or /fedora Debs are available at http://apt.puppetlabs.com Mac packages are available at http://downloads.puppetlabs.com/mac/puppet-2.7.15rc1.dmg See the

We are looking to hire a full time (or possibly a consultant) in Boston with experience in AWS and Puppet (or Chef :) http://www.fiksu.com/company/careers/cloud-operations-manager Any good leads on other places to look for someone like that? Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

All, There are now development package repos located at yum.puppetlabs.com and apt.puppetlabs.com. Moving forward, these repos will contain Release Candidate packages of Puppet, Facter, Puppet Dashboard, MCollective and Hiera, including the soon to be released RCs of Puppet 3.0 and its dependencies, Facter 2.0 and Hiera 1.0. Packages are available to easily add these repos to yum and apt

Hi everyone, I''m going to try announcing new versions of Modules I''m working on as I release them to the Forge. puppet-users and mcollective-users seems like the best place, but please let me know if you have other preferences. I''ve added a small change to the mcollective module we''ve recently released [1]. This change ensures all of the resources managed by

I''m installing puppet from git per instructions in another thread. The instructions given at http://docs.puppetlabs.com/guides/installation.html for installing puppet from source lead to it dumping things all over my Ruby, which I really wasn''t expecting and doesn''t work well with our environment. (1) How do I uninstall it? (2) How do I turn the git source into a gem?

Hi, My platform is Ubuntu 12.04. The hostname is puppet and this is a Virtual Machine in Vmware 5.0. This is a lab server and it is behind a proxy. I am having a problem with the installer. Any ideas what is going on? root@puppet:/home/rbgonza/puppet/puppet-enterprise-2.8.0-all# ./puppet-enterprise-installer

On Tue, Jan 22, 2013 at 12:30 AM, yarlagadda ramya <rams.15891@gmail.com> wrote: You really want the `puppet-users@googlegroups.com` list for this sort of question; the dev list is about modifying Puppet itself, not about manifest level questions. > I have created two manifests one for moving and other for renaming the moved > file. > > these are the two manifests i wrote. >

Now, I am getting this .... Thanks for the help! puppet5 : Cannot validate input: Unknown validator: ''puppet_server_address''. Cannot validate input: Unknown validator: ''puppet_server_address''.puppetdev04 : Puppet command ''puppet agent --test --onetime --daemonize --color=false --no-splay

I''ve just posted a feature request <http://projects.puppetlabs.com/issues/8120> relating to FIPS 140-2 compliance. I''m pointing to it here on the mailing list because I listed there five places where Puppet (nay, Ruby!) crashed while I was testing a deployment using FIPS mode on all hosts. It crashed because it tried to use MD5, and OpenSSL in FIPS mode doesn''t let

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up

I have a couple of applications (backup, Cacti, Asset Tracking) where I want a node to have some package and config installed, and once that is done, some config to be done on another system to register the client with a central server. Is there a standard way to do this, short of having some kind of web service accessible from all the client systems? From my limited Puppet knowledge, anything I

This is a maintenance release of Puppet Dashboard. It includes contributions from Adrien Thebo, Chad Metcalf, Chris W, Daniel Pittman, Daniel Sauble, Devon Harless, Michael Stahnke, Moses Mendoza, Randall Hansen, Josh Lifton, and Nick Fagerlund. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball