similar to: Commenting changes on the wiki

Hi all, When making changes to the wiki, please make sure to add a comment describing your change -- it makes it far easier to read the RSS feed or the timeline. Digant is being a diligent doc wrangler, but he needs your help managing the changes over time. Also, if you''re making many (or maybe even any) modifications to the wiki, please make sure your profile is configured

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.

Hi all, After discussions with Ben about development priorities, it looks like we''re going to make elmo be 1.0. Puppet is clearly no longer beta, and it''s time for our version number to reflect that fact. I''m about to go through the entire ticket database and classify everything appropriately, so it will be clear what we''re planning on doing for elmo.

Mr. Kanies, If you would not mind filing the bug, it would be appreciated. Puppet Version: 0.22.0 Platform: Fedora Core 6 Thank you, -- Rob -- ----- Original Message ---- From: Luke Kanies <luke@madstop.com> To: Puppet User Discussion <puppet-users@madstop.com> Sent: Friday, February 2, 2007 1:34:13 PM Subject: Re: [Puppet-users] Subscribe to multiple files - Modification On Feb

Hi all, Paul Anderson, a friend of mine who works at the University of Edinburgh, is looking for complicated problems that are currently difficult to handle with existing config mgmt tools. Please read his request below, and if you have any difficult problems that seem to meet his needs, I''d appreciate it if you would send descriptions of them to him. Thanks, Luke Begin

It seems like a very common expectation that the following code would work: class boo { $me = "/something" file { $me: ensure => present } } class yay inherits boo { $me = "/something/else" } Yet, as many have found to their chagrin, it does not work. Should it? I believe I know how I could make this work: Create a single variable namespace for class

OK, too bad. I could work around it of course by adding ''unless'' and ''creates'' clauses on all the individual parts of the define where appropriate, but I think I''ll just ignore the warnings and overhead for now. It would be cool, though, if something like the ''unless'', ''onlyif'', etc, logic was available for all

Hi all, Is everyone switched over to the Google lists? I''m basically ready for the switch, I think, and doing so would be one more closed loop for me. I notice we''ve only got a bit over 300 subscribers to the Puppet Users list, while my madstop list has nearly 600. This is a bit depressing, but it probably represents a better idea of who''s actually using the

Hi all, I''ve finally released 0.23.0 (only two days late!). You can get it from the usual locations (although the packagers will take a little while to package it up, I assume): https://reductivelabs.com/trac/puppet/wiki/InstallationGuide You can read the full changelog[1], which is pretty long, but here''s a summary of the things you either want or should look out for:

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

Hi all, again. It looks like my last attempt of sending this message got cut off, at least it looks like that in the archive[1], so I''m trying again: <rerun> Luke Kanies suggested that I take this up here since his memory on the subject was a bit poor. I am trying to cat various files together into one file. According to the documentation "sourceselect => all" might

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

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 -

Hi all, As most probably know by now, I''ll be in London and Brussels for the next week, starting Tuesday (well, I leave Tuesday but don''t arrive until Wednesday). That means I''ll hopefully get to meet more of you (I''m giving talks in London Thursday night and in Brussels, probably on Sunday morning), but it also means I''ll have limited access

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''m considering moving --parseonly to just puppet, rather than it and puppetmasterd. Considering that it''s really only useful for parsing a specific file, puppet has the benefit of requiring that you specify that file directly. Since Puppet now supports multiple environments, --parseonly becomes both more difficult and more ambiguous when used with

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

Hi, I''m experimenting with using Mongrel to serve XMLRPC, and I''m having trouble passing the XMLRPC errors on to the client. In my webrick implementation, I just raise the XMLRPC error and the client receives it and can handle it like a normal exception. With Mongrel, when I raise the error, Mongrel catches it and just closes the client connection, which means the

Hi all, Now that it looks like we have some kind of process to manage tickets, I need people to help me with that process. There are currently something like 117 open tickets, and there are about 6 different dimensions on which these tickets can be categorized (e.g., complexity, triage stage -- all the report times listed on the Reports page). My plan is to work my fingers raw going

Hi all, As requested by at least one person (and because I''d been thinking about it and figured it would be a good idea), I''ve just made it simple to use external node sources with Puppet. If you set ''external_nodes'' to a command (the default is ''none''), then Puppet will call that command and use it to configure nodes. The output of