similar to: Provider suitability reports

Hi all, In looking at the current bug list for elmo[1], it''s pretty clear that this is a lot of work, and some of it is kind of segmented into related chunks. Additionally, a good bit of it has an impact on backward compatibility, although in nearly all cases I expect to be able to remain entirely or almost entirely backwards compatible. Given that, would people prefer that I

Hi I¹m not sure if I¹m misunderstanding, however, when I try the following: class thttpd { package { thttpd: version => "2.25b-4.2", source => "http://dag.wieers.com/packages/thttpd/thttpd-2.25b-4.2.el4.rf.i386.rpm" } [snip other code] } On fedora core 5, the ³source² is ignored: yum is used to pull the package from the upstream repos listed in

I''d like to be removed from the puppet-users email list... but I cant find my name on the webpage. Thanks, Jennifer Ford *********************************** Manager, Unix Administration Teach For America Phone: 212-279-2080 ext. 688 jennifer.ford at teachforamerica.org One day, all children in this nation will have the opportunity to attain an excellent education.

One of the *big* benefits of providers is that it is now easy to document the different backends available to you. Puppet will automatically collect all of the docs for your providers and stick them in the autogenerated docs page. For instance, check out the package docs: http://reductivelabs.com/projects/puppet/documentation/ typedocs.html#package I''m also adding what the

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

Hi, I wanted to configure reporting in puppet. I came across the below links which says what needs to be added in config file to enable reports. But I was wondering how I view the visual report/graphs do I need to create my own script. http://reductivelabs.com/trac/puppet/wiki/ReportReference#rrdgraph http://reductivelabs.com/trac/puppet/wiki/ReportsAndReporting -- Deepak

Hi all, I''m proud to announce that I seem to have pushed a new release of Puppet out in record time. This is a minor upgrade, mostly bugfixes and small features, but there are lots of each. See the changelog[1] for an idea of what this release provides, but keep in mind that this changelog is my first real attempt at keeping an up-to-date changelog. Enjoy! 1 -

In my neverending quest to generate documentation so I don''t have to write it myself, I am proud to announce a new form of documentation generation: Provider features. Each resource type can now declarate "features" (currently defined as a list of methods a provider must define). Providers can then be tested to see whether they provide a given feature; for instance:

Hi, I have this small problem with my servers managed by Puppet (i have a workaround so the problem is not so important): 1) These servers are installed with Red Hat Linux Enterprise and i use Puppet in client-server mode. 2) I''ve made a Puppet class called "yum" to install (by the RPM package provider) and configure YUM on my servers. I don''t use the YUM package

I''ve just committed Facter 1.3.8. All of the work for this release was done by James Turnbull, so everyone should thank him for getting it done. Here''s the changelog: Fixed Rdoc::usage bug on CentOS 5 - closed Puppet #753 and Facter #40 Added support to return multiple interfaces and their IP addresses and MAC addressess as facts. Returns

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

Hi all, I''ve now finished all of the functionality I plan to add in the next release, so all that remains is closing as many open bugs as possible. I''ve gone through and marked all of the bugs I specifically plan on fixing with the ''minor'' milestone. If you have a bug in the db[1] that you think needs to be fixed in the next release but is not

I maintain a few production gentoo machines. I do this by creating builtds for packages and centralizing these builds via nfs. when puppet tries to fulfill a requirement for say sudo it calls emerge, but i want to call emerge with -k which forces emerge to look for a binary before trying to built the package itself. is there any way to do this in the current release ?

Hi all, Peter Abrahamsen has duplicated all of the documentation and cookbook pages in Puppet''s Trac page: https://reductivelabs.com/trac/puppet/wiki/DocumentationStart Please let me or Peter know if there are any problems. -- A motion to adjourn is always in order. --Robert Heinlein --------------------------------------------------------------------- Luke

I''ve got a first version of a doc explaining how multiple environment support will work in the next release: http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments As always, comments are appreciated. Even if you just don''t understand what the doc says, please let me know. It''s clear that the community is generally unhappy with the documentation I

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

Hi all, It was brought to my attention that the front page lists 0.23.3 as the stable release, but that no such release exists. I could have sworn I released this a few weeks ago, but now I can find no evidence of that. I''m going to publish it from the latest commit in the 0.23.x branch as soon as possible (probably in about 12 hours), so if anyone wants to get that last-minute

Hi all, I''ve just rewritten the Puppet introduction from scratch: https://reductivelabs.com/trac/puppet/wiki/PuppetIntroduction I think it''s better, but I''m not convinced it''s a whole heckuva lot better. Comments are very much appreciated, especially if you can recommend a better approach to the document. I tried to organize it how I have been giving

Looks like there''s enough interest in runnels that it''s time to create a list: https://mail.madstop.com/mailman/listinfo/runnels-dev -- Risk! Risk anything! Care no more for the opinions of others, for those voices. Do the hardest thing on earth for you. Act for yourself. Face the truth. -- Katherine Mansfield

I think I''ve got every fix except one in that''s going to make it into grover, which I''ll hopefully be releasing tomorrow. I plan on adding Tim Stoop''s patches for home directory management (#432), but everything else is getting pushed to the next release at this point. I''ve fixed all of the major bugs, or at least I think I have. If