search for: puppetdoc

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'' /us...

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/manifes...

...exposed all that well, especially on the command- line. Just a few examples: - Which providers for which types are functional on the current machine - Whether a given parameter is valid for a given provider - What transaction reports exist - What functions exist I''ve written ''puppetdoc'' to turn some of this information into monolothic documents, but it''s difficult to add new reference documents to `puppetdoc`, and it has a lot of text stored in-line. I''m thinking that I''ll create a new type of autoloading file, ''reference'...

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) - puppetmasterd(8) At this point I am still working out the technical details of converting some of the existing reference documentation to valid man pages. However, I felt it prudent to have...

...://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 errors in the translation, or in the documents in general. I''ve modified puppetdoc so it can write directly to trac as long as it runs on my server (it uses trac- admin), so it''s very easy to update. I''m 99% of the way to being able to generate all four of these in a single PDF (apparently, it''s around 58 pages), but I''m getting a failu...

...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 re...

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

...Results logged to >> /opt/csw/lib/ruby/gems/1.8/gems/json-1.7.5/ext/json/ext/generator/gem_make.out > > Nothing to update > > So I decided to uninstall the old version and try again: # gem uninstall puppet > > Remove executables: > > filebucket, pi, puppet, puppetdoc, ralsh, puppetca, puppetd, >> puppetmasterd, puppetqd, puppetrun > > >> in addition to the gem? [Yn] y > > Removing filebucket > > Removing pi > > Removing puppet > > Removing puppetdoc > > Removing ralsh > > Removing puppetca > > Removi...

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 ======== ========= ============ ========== ====...

...get lost (unless, as happened here, someone notices them). If any of the references are wrong, please file a bug or send a note to me or to the list. I''ve reverted the Type reference so it''s again correct, and I''ve incorporated the Function reference changes into puppetdoc. Thanks, Luke -- One of the Ten Commandments for Technicians (7) Work thou not on energized equipment, for if thou dost, thy fellow workers will surely buy beers for thy widow and console her in other ways. --------------------------------------------...

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

...falures when testing redhat service providers on debian varients * Bug #2619: Fresh 0.25.0 client cannot ''authenticate'' to 0.25.0 puppetmaster. * Bug #2620: Regex problem in puppetmaster auth.conf * Bug #2621: possible JSon serialization issue (on debian/lenny/amd64) * Bug #2622: puppetdoc returns undefined method ''[]'' * Bug #2626: Unhelpful error message * Bug #2627: Node regular expressions only work in some cases * Bug #2632: require doesnt seem to work * Bug #2634: nagios type serviceescalation should support servicegroup_name * Bug #2637: SSL socket race condit...

...functions to better fit an overall model. List of binary changes puppetmasterd –> puppet master puppetd –> puppet agent puppet –> puppet apply puppetca –> puppet cert ralsh –> puppet resource puppetrun –> puppet kick puppetqd –> puppet queue filebucket –> puppet filebucket puppetdoc –> puppet doc pi –> puppet describe This also results in a change in the puppet.conf configuration file. The sections, previously things like [puppetd], now should be renamed to match the new binary names. So [puppetd] becomes [agent]. You will be prompted to do this when you start Puppet...

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