Displaying 20 results from an estimated 6000 matches similar to: "Provider features"
2006 Aug 28
0
Provider documentation
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
2007 Mar 29
0
Intended behavior of sourceselect => all
Hi all
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 do this.
From the language reference [1]:
"Whether to copy all valid sources, or just the first one. Valid values
are first, all."""
Giventhe
2007 Mar 30
4
Intended behavior of sourceselect => all [Proper]
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
2007 Jan 05
3
ANNOUNCE: 0.22.0
Hi all,
I''ve just published the long-awaited new release of Puppet. Yes, I
accidentally skipped 0.21.0; oops.
Important features in this new release are:
- Graphing
Puppet now uses the GRATR[1] library to do all of the internals of
managing relationships between resources. This gives Puppet a lot of
functionality internally, but it also makes it possible to produce
simple
2006 Sep 04
7
package: ignores "source"; "provider" doesn''t work as advertised?
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
2007 Jan 24
3
Another ''found a bug'' problem - This time with user purging.
Ok, given the statement on the web page about unlesssystemuser under
Resources (
http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources),
I assume that users can be purged.
However, when I attempt to do this with resources { user: purge => true,
noop => true } and what I get is:
err: Found a bug: private method ''split'' called for nil:NilClass.
2007 Oct 22
1
unsubscribe
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.
2007 Mar 21
3
Slight 0.22.2 backward compatibility reporting problem
Hi all,
Turns out there''s a small backward compatibility problem in 0.22.2.
If you''ve got clients in older versions sending reports to a daemon
running the newer version, you''ll run into a problem because I
renamed the Puppet::Metric class to Puppet::Util::Metric.
I''ve committed a fix to svn, but it''s not a big enough problem to
require a new
2007 Mar 19
3
ANNOUNCE: Puppet 0.22.2 (grover)
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 -
2007 May 08
3
Provider suitability reports
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,
2007 Feb 02
1
Re: Subscribe to multiple files - Modification
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
2007 Jun 20
0
ANNOUNCE: 0.23.0 release
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:
2007 Jan 15
1
Re: How to conditionally run defines? (and a question about updating... )
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
2007 Feb 16
0
Looking for descriptions of difficult problems
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
2007 May 09
3
RFC: Multiple small releases, or one big roll-up?
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
2008 Feb 25
2
Switching to Google Groups tomorrow night
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
2007 Aug 07
0
ANNOUNCE: 0.23.2 is available
Hi all,
I released 0.23.2 last night; you can get it from the usual places
[1]. Apparently Matt has already uploaded debs.
This is a bug-fix release, and I''m hoping it will be stable enough to
supplant 0.22.4.
It looks pretty likely that I''ll be putting out another release very
soon, though, because a coworker of Matt''s has figured out a way to
use HTTP
2007 Jan 05
0
Last chance to test before the next release
Hi all,
I''ve now got all but one bugs closed or bumped to the next release,
and I am planning on releasing today. People have been testing the
SVN code all week and have helped to find many bugs that we would not
have wanted in a released project, and you can help more by testing
right now.
The major change in this release is that the transactions now use a
graph library to
2007 May 02
1
UPDATE automated installation of puppet into solaris 10 zones
On Apr 30, 2007, at 4:44 AM, Frank.Munsche@izb.de wrote:
> I''ve built a puppet solaris - package which is distributed via
> jumpstart at installation time of a solaris 10 machine.
> It''s postinstallation registers the puppetd into smf and starts
> puppetd afterwards. Puppetd connects to puppetmasterd, gets ist
> certificate signed (autosig on) and the
2007 Feb 18
1
Passing XMLRPC errors on to clients
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