search for: puppetdocs

Is there a list somewhere? How do I know what $operatingsystem, for example, is going to be set to? Using ''solaris'' seems to work, but I haven''t tested ''ubuntu'' and ''redhat'' yet (haven''t gotten that far). It''d be nice to have a list of available vars, along with "how they are set." -Charlie

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, at the moment I fight with puppetdoc and end in a ruby confusion. To the problem: > puppetdoc --debug --trace --mode rdoc --all manifests/site.pp info: scanning: ["manifests/site.pp"] /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `output_resource_doc'' /usr/lib/ruby/1.8/puppet/util/rdoc.rb:82:in `sort''

I''m being a good boy and using the puppetdoc tool to document my classes, however I''m hitting a minor annoyance. The top level documentation for a module (let''s call it "example) is pulled from example/README (not example/manifests/init.pp), okay I can cope with that. The documentation for the class in example/manifests/init.pp ends up as example::example (hmm,

Hi all, I''ve been thinking about this for a while, and I think I''ve finally come up with the "right" way to do this. There''s a lot of data in Puppet that''d be useful as documentation but is not currently exposed all that well, especially on the command- line. Just a few examples: - Which providers for which types are functional on the current

Folks, I''ve been looking at creating a set of man pages for puppet and I''m trying to come up with a reasonable hierarchy. I''d appreciate any suggestions. So far, here''s what I''ve come up with: - puppet(1) - puppetca(1) - puppetdoc(1) - puppetrun(1) - puppetca.conf(5) - puppetd.conf(5) - puppetmasterd.conf(5) - puppetd(8) -

I''ve converted all of the inline docs over to restructured text, and I''ve got them all up on trac: http://reductivelabs.com/trac/puppet/wiki/TypeReference http://reductivelabs.com/trac/puppet/wiki/FunctionReference http://reductivelabs.com/trac/puppet/wiki/ReportReference http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference Please let me know if you find any

...efinition ''mongodb::addmongouser'' is already defined at /etc/puppet/environments/test/modules/mongodb/spec/fixtures/modules/mongodb/manifests/addmongouser.pp:36; cannot be redefined at /etc/puppet/environments/test/modules/mongodb/manifests/addmongouser.pp:36 Failed to process puppetdocs for /var/www/test while executing puppetdoc --output /var/www/test --modulepath /etc/puppet/environments/test/modules:/etc/puppet/modules -m rdoc What''s the best way to handle this, w/o having to constantly have to delete and recreate the symlinks created by rspec-puppet ? -- You rec...

I have this config: # BL00070 - Disable NFS service {["nfs","nfslock","netfs","portmap"]: ensure => stopped, enable => false, } user {"rpc": ensure => absent, provider => "useradd" } user {"rpcuser": ensure => absent, provider => "useradd" } file

There''s a problem installing puppet on Solaris 10 -- in this situation, we aren''t really doing anything with puppet there. The version we''re using is: ruby 1.8.7 (2011-02-18 patchlevel 334) [i386-solaris2.9] Here''s the first error: # gem update puppet > > Updating installed gems > > Updating puppet > > Building native extensions. This

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

Hi all, Now that (I hope) I''ve fixed the problems in 0.22.2 with 0.22.3, I''m prioritizing on documentation, since that''s the biggest complaint from people right now, from what I can tell. I''m starting with the introduction, since, of course, that''s where everyone else starts, and it has not kept pace with how I talk about Puppet in

Hi, using puppetdoc -r providers ... :Ruby version: 1.8.6 :Puppet version: 0.24.4 :Operating system: Solaris :Operating system release: 5.8 ... service_ -------- .. _service: http://reductivelabs.com/trac/puppet/wiki/TypeReference#service :Default provider: freebsd ======== ========= ============ ========== =========== Provider Suitable? controllable enableable refreshable ========

Hi all, I''ve just noticed that two wiki users edited the wiki reference documents. One of these edits (to the function reference) was a good edit but would have been overwritten if I did not find it. The other edit (s/darwinports/macports/g) made the documentation incorrect, since the provider actually is called darwinports (even if that itself is a bug). I haven''t

Does anyone know where I can get the latest puppet, 2.7.1 as RPM''s? The spec file that comes with the puppet 2.7.1 source is broken again, and only version 0.25.5 seems to be available via EPEL, which means that the website''s assertion that you can get puppet as an RPM from there is somewhat untrue. Douglas. -- You received this message because you are subscribed to the

As promised, I''m trying to extra more data out of Puppet''s internals, and this is one I''ve been wanting to do ever since I developed the idea of provider suitability. I''ve created new type of ''reference'' (although it''s more of a report than a reference) that can tell you which providers are functional on the current platform,

Do explicit class dependencies work? This simple example fails with: Could not find resource ''Class[Config]'' for relationship on ''Class[Uses_config]'' class config { } class uses_config { Class[''config''] -> Class[''uses_config''] } include uses_config Am I doing something? Thanks, Christian -- You received this

-----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:

Welcome back again to the Puppet release cycle with the long-awaited eleventy times better RC2 release. The 2.6.0 release is a major feature release and includes a huge variety of new features, fixes, updates and enhancements. These include the complete cut-over from XMLRPC to the REST API, numerous language enhancements, a complete rewrite of the events and reporting system, an internal Ruby

Just one more email and I''ll let you go for a few hours :) One of the things I like to see in apps is that they are immediately intuitive and easy to use for new users. I think Puppet is really good here, but there''s opportunity to make everything better. We want everyone to love Puppet from their first few minutes using it, all the way through to datacenter nirvana.

hi I''ve read about PuppetReporting at the Trac website. Apparently you are working on integrating the benchmark tests for every type in ruby. Do you have any idea when this will all get implemented? This is a crucial part (and actually a necessary feature) in the configuration management system we have set up using Puppet. grtz Koen Vereeken