search for: explanatorygap

...atest Facter and Puppet, as well as a combined mpkg for them both. Jeff McCune and I are doing a fair bit of testing on them this week in preparation for MacWorld, so I wasn''t going to upload them to the official site for another few days, but they''re looking pretty good. http://explanatorygap.net/puppet/Facter_1.3.8.pkg.zip http://explanatorygap.net/puppet/Puppet_0.24.1.pkg.zip http://explanatorygap.net/puppet/Puppet_0.24.1_Facter_1.3.8.mpkg.zip I was running into issues with older versions lying around, so I''ve made preflight scripts as follows: Facter: /bin/rm -Rf /usr/lib...

Hey all, I have recorded my steps towards getting puppet functional through one of the four different methods that I can think of, which are: 1.Source(copying and insatlling to the recommended unix FSH directory, /usr/local/src) 2.pkg hosted at explanatorygap 3.MacPorts 4.RubyGems I haven''t cleanly tested the last two, but here''s where I am with the first two: 1. I can''t seem to install either facter or puppet properly, this is with the most recent ruby, 1.9.1. Here''s where I left off with facter: sudo ruby ./install...

...current state of resource: Did not get id; Failed to retrieve current state of resource: Did not get id; Failed to retrieve current state of resource: Did not get id". This is running on a G4 Xserv with OS X Server 10.5. Ruby is up to date. I installed Puppet from the packages here: http://explanatorygap.net/puppetfacter/. I''ve also tried it from a Power Mac running OS X 10.4, and I get this error: /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:166:in `handle'': Certificate names must be lower case; see #1168 (ArgumentError) from /usr/lib/ruby/site_ruby/1.8/puppet/default...

> Adam, you should be able to either grab the unstable deb from here: > > http://packages.debian.org/sid/puppet > > or build from source using git-buildpackage, this post describes how: > > http://explanatorygap.net/2009/10/29/puppet-0-25-1-debs-done-but-dela... Thank you very much!! I have already tried the debian-experimental packages on both Ubuntus, but I finally gave up because of broken stored configs (see http://groups.google.com/group/puppet-users/browse_thread/thread/2ca509fef3f7feb/05306edfee070...

Has anyone got/seen Python code to read puppet reports? I added a bunch of these: class PuppetReport(yaml.YAMLObject): yaml_tag = u''!ruby/object:Puppet::Transaction::Report'' def __init__(self, host, logs, metrics, records, time): self.host = host self.logs = logs self.metrics = metrics self.records = records self.time = time However, the Python YAML

Can anyone have detailed list of dependencies? I am under impression, that all my all problems with getting puppet to work come from the fact, that I have no idea what are puppet dependencies. On puppet Wiki one can read, that what is required is "ruby", and for storedconfigs "sqlite3" and "libsqlite3-ruby". Well, it is true, that they are required, but by far it

I''m trying to manipulate the following facter variable: ipaddress => 10.85.207.2 What I need is the second group of digits. If it''s 84 then location is A, but if it''s 85 then location is B. In puppet I couldn''t grab this second set of digits, but maybe there is a way? I''ve already tried to make a custom fact, but my ruby knowledge is *ahem* pretty

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.24.8 is now available! This is a maintenance release for the 0.24.x branch but contains a small number of new features including some significant performance enhancements for large installations and stored configurations. The tarball is available at: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz MD5 hash:

Hi all, We''re writing a few scripts at the moment that could really make use of Facter, however the vast majority of them team (including my self!) are not proficient in Ruby, however they are highly proficient in other languages such as (dare I say it!) Python. Is there (or are there any plans to!) release bindings for other languages to enable facts to be used in scripts other

Hello all, This is not a puppet proper issue of course.. but I was wondering if any of you could share some thoughts... When you deploy a system like Puppet at a large park of systems, you instantly increase the efficacy of mistakes and bugs in destroying the environment.... How do you deal with that? I would be interested in any experience or input, especially puppet proper best practices...

Hi all Here is the 0.24.7 release - the last of the 0.24.x branch and codenamed Gonzo. You can download it here: http://reductivelabs.com/downloads/puppet/puppet-0.24.7.tgz Big tickets items in the release are: * Manifest documentation http://reductivelabs.com/trac/puppet/wiki/PuppetManifestDocumentation This new functionality creates documentation from marked up manifests and modules and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

Hi! I''m testing Puppet 2.6 and got all the basic stuff working with the default webricks. I read that it doesn''t scale very well and is not suited for production environments and the recommended setup is Apache/ Passenger. Is there a step-by-step-guide on how to set it up? Any help is very appreciated. Regards, Freddie -- You received this message because you are subscribed