[Puppet Users] Re: simple question.
Thanks a lot On May 18, 12:14 pm, "Matt Ackerman" wrote: > Hello, > > I am assuming you mean the file is not present on the client and you > want to transfer it from the masters file server. This is actually very > easy and one of the most basic things you can do. > > Take a look at the following and let us know if you have any questions: > > http://docs.puppetlabs.com/guides/types/file.html > > -Matt > > > > -Original Message- > From: puppet-users@googlegroups.com > > [mailto:puppet-us...@googlegroups.com] On Behalf Of Ray Liu > Sent: Monday, May 17, 2010 8:32 PM > To: Puppet Users > Subject: [Puppet Users] simple question. > > Hi Guys, > > I'm new to puppet, how can I write a recipe that puppet client will > retrieve a file from puppet master server if it's not present. any > ideas? Thanks > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: External Nodes
According to experience what's the pros/cons of those methods to store the nodes? Like ldap, DB, a library/framework like clusto/puppetdashboard/foreman etc. Thanks On Sat, May 15, 2010 at 5:22 PM, Silviu Paragina wrote: > On 15.05.2010 00:30, Baker, Luke Jefferson wrote: > >> Speaking of external nodes.. >> >> Any decent tutorials out there for someone that has no idea where to >> start? ;) >> >> > External nodes are a way of looking up classes and vars to be applied to a > node via an external application. > http://docs.puppetlabs.com/guides/external_nodes.html - you may try a do > it yourself script/application > > But you should try foreman, puppet dashboard or extlookup (I think there > are other, but I don't know them). Each has a different setup process to > long to explaing here. (do a few googles ;) ) > > Silviu > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Tony -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Negative requires
Ah. Thanks everyone. I new I'd misunderstood something.
On 18 May 2010 16:49, Ohad Levy wrote:
> package { "MySQL-client-community" : ensure => installed, require =>
> Package[ "mysql" ] }
>
> will just work, as you are requiring the the mysql package is already absent
> before you install the other package.
>
> Ohad
>
>
> On Tue, May 18, 2010 at 12:35 PM, Tim Nicholas wrote:
>>
>> Hello everyone,
>>
>>
>> I'm just getting to grips with Puppet so apologies if I've missed
>> something.
>>
>> I'm wondering if there is a way to require that something isn't the case.
>>
>> My current situation/example is that I'm trying to uninstall one
>> package ("mysql") and install another one that conflicts with it
>> ("MySQL-client-community") in one puppet run.
>>
>> I can do something like:
>>
>> package { [ "mysql" ] : ensure => absent, }
>> package { [ "MySQL-client-community", ] : ensure => installed, }
>>
>> Which is fine, unless "MySQL-client-community" is scheduled to be
>> installed before mysql is removed, in which case it errors and I'm
>> left with a system with no mysql.
>>
>> Obviously, I can just run puppet again and it'll be fine but I'd
>> really like to do something like:
>>
>> package { [ "MySQL-client-community", ] : ensure => installed,
>> require => ! Package[ "mysql" ] }
>>
>> with the ! negating the requirement.
>>
>> Is this possible or am I approaching this from the wrong angle and I
>> should be doing something quite different?
>>
>>
>> Thanks,
>> Tim
>>
>> --
>> Tim Nicholas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-us...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
Tim Nicholas
Cell/SMS: +64 21 337 204
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Negative requires
package { "MySQL-client-community" : ensure => installed, require =>
Package[ "mysql" ] }
will just work, as you are requiring the the mysql package is already absent
before you install the other package.
Ohad
On Tue, May 18, 2010 at 12:35 PM, Tim Nicholas wrote:
> Hello everyone,
>
>
> I'm just getting to grips with Puppet so apologies if I've missed
> something.
>
> I'm wondering if there is a way to require that something isn't the case.
>
> My current situation/example is that I'm trying to uninstall one
> package ("mysql") and install another one that conflicts with it
> ("MySQL-client-community") in one puppet run.
>
> I can do something like:
>
> package { [ "mysql" ] : ensure => absent, }
> package { [ "MySQL-client-community", ] : ensure => installed, }
>
> Which is fine, unless "MySQL-client-community" is scheduled to be
> installed before mysql is removed, in which case it errors and I'm
> left with a system with no mysql.
>
> Obviously, I can just run puppet again and it'll be fine but I'd
> really like to do something like:
>
> package { [ "MySQL-client-community", ] : ensure => installed,
> require => ! Package[ "mysql" ] }
>
> with the ! negating the requirement.
>
> Is this possible or am I approaching this from the wrong angle and I
> should be doing something quite different?
>
>
> Thanks,
> Tim
>
> --
> Tim Nicholas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Negative requires
On May 17, 2010, at 9:35 PM, Tim Nicholas wrote:
> I can do something like:
>
> package { [ "mysql" ] : ensure => absent, }
> package { [ "MySQL-client-community", ] : ensure => installed, }
>
> Which is fine, unless "MySQL-client-community" is scheduled to be
> installed before mysql is removed, in which case it errors and I'm
> left with a system with no mysql.
>
> Obviously, I can just run puppet again and it'll be fine but I'd
> really like to do something like:
>
> package { [ "MySQL-client-community", ] : ensure => installed,
> require => ! Package[ "mysql" ] }
>
> with the ! negating the requirement.
>
> Is this possible or am I approaching this from the wrong angle and I
> should be doing something quite different?
You've almost got it. I'll work find if you remove the "!". That will require
resource not the package itself and the resource says to remove the package.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Negative requires
Hi Tim,
What you want is this:
package { "mysql": ensure => absent, before =>
Package["MySQL-client-community"]; }
package { "MySQL-client-community": ensure => installed;}
On Mon, May 17, 2010 at 9:35 PM, Tim Nicholas wrote:
> Hello everyone,
>
>
> I'm just getting to grips with Puppet so apologies if I've missed something.
>
> I'm wondering if there is a way to require that something isn't the case.
>
> My current situation/example is that I'm trying to uninstall one
> package ("mysql") and install another one that conflicts with it
> ("MySQL-client-community") in one puppet run.
>
> I can do something like:
>
> package { [ "mysql" ] : ensure => absent, }
> package { [ "MySQL-client-community", ] : ensure => installed, }
>
> Which is fine, unless "MySQL-client-community" is scheduled to be
> installed before mysql is removed, in which case it errors and I'm
> left with a system with no mysql.
>
> Obviously, I can just run puppet again and it'll be fine but I'd
> really like to do something like:
>
> package { [ "MySQL-client-community", ] : ensure => installed,
> require => ! Package[ "mysql" ] }
>
> with the ! negating the requirement.
>
> Is this possible or am I approaching this from the wrong angle and I
> should be doing something quite different?
>
>
> Thanks,
> Tim
>
> --
> Tim Nicholas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Negative requires
Hello everyone,
I'm just getting to grips with Puppet so apologies if I've missed something.
I'm wondering if there is a way to require that something isn't the case.
My current situation/example is that I'm trying to uninstall one
package ("mysql") and install another one that conflicts with it
("MySQL-client-community") in one puppet run.
I can do something like:
package { [ "mysql" ] : ensure => absent, }
package { [ "MySQL-client-community", ] : ensure => installed, }
Which is fine, unless "MySQL-client-community" is scheduled to be
installed before mysql is removed, in which case it errors and I'm
left with a system with no mysql.
Obviously, I can just run puppet again and it'll be fine but I'd
really like to do something like:
package { [ "MySQL-client-community", ] : ensure => installed,
require => ! Package[ "mysql" ] }
with the ! negating the requirement.
Is this possible or am I approaching this from the wrong angle and I
should be doing something quite different?
Thanks,
Tim
--
Tim Nicholas
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
RE: [Puppet Users] simple question.
Hello, I am assuming you mean the file is not present on the client and you want to transfer it from the masters file server. This is actually very easy and one of the most basic things you can do. Take a look at the following and let us know if you have any questions: http://docs.puppetlabs.com/guides/types/file.html -Matt -Original Message- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of Ray Liu Sent: Monday, May 17, 2010 8:32 PM To: Puppet Users Subject: [Puppet Users] simple question. Hi Guys, I'm new to puppet, how can I write a recipe that puppet client will retrieve a file from puppet master server if it's not present. any ideas? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] simple question.
Hi Guys, I'm new to puppet, how can I write a recipe that puppet client will retrieve a file from puppet master server if it's not present. any ideas? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ANNOUNCE: Puppet 0.25.5 available!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Welcome back to the Puppet release cycle for the stable release of
0.25.5.
The 0.25.5 release is a maintenance release in the
0.25.x branch. It contains a number of bug fixes but also
performance enhancements including speed-ups to Puppet's graphing.
The release is available at:
http://puppetlabs.com/downloads/puppet/puppet-0.25.5.tar.gz
Please note that all releases of Puppet are signed with the
Reductive Labs key (we'll issue a new, improved Puppet Labs key
after the Rowlf release).
See the Verifying Puppet Download section at
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet
Please report feedback via the Puppet Labs Redmine site:
http://projects.puppetlabs.com
Please select an affected version of 0.25.5.
RELEASE NOTES
The default location for Puppet's dynamic files, the $vardir option,
has changed from /var/puppet to /var/lib/puppet. This is already the
default for the Fedora EPEL and Debian/Ubuntu packages and brings
Puppet into FHS compliance.
You can now specify checksum => none in the file type to disable
file check-summing.
The default factpath is now $vardir/lib/facter/.
The generate function now sets the working directory to the
directory containing the specified command.
The "warning: Value of 'preferred_serialization_format' ('pson') is
invalid, using default ('yaml')" is now a debug level message.
The "use_cached_catalog" option is available. This determines
whether to only use the cached catalog rather than compiling a new
catalog on every run. Puppet can be run with this enabled by
default and then selectively disabled when a recompile is desired.
The option defaults to false.
The certificate_revocation option is now available. Setting it to
false disables certification revocation (see #3640). The default
setting is true.
CHANGELOG
0.25.5
==
d88b357 Fixes incorrect line in partial CRL fix
dec84e5 Fixed documentation issues exposed in #3772
0.25.5rc3
=
9214400 WIP - trying to fix #3460
9d3e98b Minimal footprint fix for #3751 (serialization 0.25.5 <->
0.24.8)
d481340 Updated Template documentation link
5a1a45c Update Red Hat spec file for 0.25.5
0.25.5rc2
=
5258a0a Fixing #3533 - Removing all transaction cleanup
bcde541 Fix for #2910 -- Tidy/matches is too tricky to use
5abe571 Bug #3451: Don't leak the terminus class setting from
Puppet::Resource::Catalog's spec
ebd924c Fix to the fix for #3295
ce233aa Write ssh_authorized_keys as user
6739bab Fix for #3558 -- source file reading speedup
b0e3c61 Fix for #3556 Plussignment value melding
8a30495 Fixed #3655 - Puppet doesn't find installed packages with
portage provider
e4130af Fixed #3672 - Error message on duplicate fileserver mounts
incorrect
1275a47 conf/redhat: Add notifempty to logrotate config
134204d Fixed stored configuration documentation
1aa98a6 Fixes #3653 - Changed default factpath value to better
reflect plugins in modules
44f6d64 Partial fix to #2837 - changed warning message to debug
3a1b178 Fix #3555 - fix state of purged lists
f6046ab Fix for #3577 -- to_yaml parameter in 0.25.5rc1
f351e2d Renamed all references to Reductive Labs to Puppet Labs
cf7e696 Updated Rake tasks to no longer load puppet.rb
b93924e Fix #3540 - name methods correctly
9bc2f28 Fixes #3295 - generate() now sets the working directory to
the directory containing the specified command.
3ee6834 Added YARD task
99818ef Update man pages and partial doc fix to #3491
f988af3 Fixed #3532 - Typo in lib/puppet/ssl/host.rb
f0e12e5 Fix #3496 - suppress transaction debug message
0.25.5rc1
=
0eea2f5 Updated version and CHANGELOG to 0.25.5rc1
57ae381 Modify SuSE spec file for 0.25.x and correct shebang lines
for puppetd/puppetmasterd
d90ec79 Fixes #3460 - Makes Puppet FHS compliant by moving
/var/puppet to /var/lib/puppet
ae0b0bf Fix for #3101 (bug in MRI 1.8.7)
9db066b Fixes #3419. OS X 10.6 Ruby doesn't set supplementary groups
306d082 Revert the guts of #2890
4eea77a Fail gracefully on packages that don't have the HOMEPAGE
variable set (e.g. dev-lang/php).
f5b8494 Fixed #3443 - Typo in mount type
b0ef2c6 Fixes #3135 - darwin doesn't support 'mount -o remount'
7018cf5 Adding :catalog_terminus setting
978ab8a fixing obsolete comment in puppetd
6d13d0d Adding support for only using cached catalogs
bc28715 Refactoring Configurer to enable the next feature
ba43d7b Fix for #3366 - --tags '' treated as boolean 'true'
5ab5e8a Supressing warnings (not really failures) in test/unit
e4df0b0 Fix test using wrong Puppet util filesetting group
eeb3d74 Mock user in SUIDManager tests
9ea27db Removing resources generate tests
218e3e9 Removing old test for service/debian provider
1556938 Replace test/unit file write test with spec
2defc00 Fix for #3424 and tests to prove it.
44798b9 Fixed changelog Rake task
5d10f65 Fix #3155 - prevent error when using two matching regex in
cascade
fbedb99 Fixing #3148 Settings#wit
[Puppet Users] Re: Writing a properly-formed custom type (configxml)
This post enlightened me. http://groups.google.com/group/puppet-users/browse_thread/thread/449e106437c3f673/ca9ff7055797f18c?lnk=gst I've split configxml into a provider and a type and it appears to work properly now. In more detail, I rewrote "attributes" as a property. All logic is moved into an eponymous provider in 2 methods: "attributes" and "attributes=(value)". -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Issue with naginator and elusive nagios cfg file corruption (#3712)
On 05/03/2010 03:33 PM, Joe McDonagh wrote: > Hello, I have run into a data corruption problem with naginator that is > fairly difficult for me to track down. Hand-written configurations do > not suffer from this fate. This was present in .24.8, and still present > in .25.4. I'd love to complete this automatic nagios project, if anyone > has some ideas on narrowing down the source after reading the bug report > (http://projects.reductivelabs.com/issues/3712) please let me know. > If anyone was wondering, I traced this back to a custom-compiled nagios package. It must have been compiled against a buggy library or something; the official canonical nagios3 package for 10.04 LTS seems to have rectified the issue. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L'ennui est contre-révolutionnaire -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Have I found a bug with variables in nodes?
On Fri, May 14, 2010 at 8:12 PM, Dan Bode wrote: > > > On Fri, May 14, 2010 at 6:01 PM, Nigel Kersten wrote: > >> >> >> On Fri, May 14, 2010 at 1:42 PM, Paul Lathrop wrote: >> >>> >>> Assuming the client has puppeted at least once against that server. >>> This >>> >>> won't work for bootstrapping a client though will it? >>> >> >>> >> it does, the facts yaml file is created before the external node >>> >> classifier is called ;) >>> > >>> > Whoa. This should be called out in the external node docs, as I simply >>> > assumed this happened after the node classifier is called. >>> >>> +1000 >>> >>> >> I did some tests as I didn't quite trust this :) and it's absolutely true. >> >> So my plan is for my external node provider >> > > do you mean node classifier? Are you using provider in the traditional > Puppet sense? > no, classifier sorry. > > >> to redirect clients that haven't provided facts to a "bootstrap" >> environment that contains the bare minimum facts that are required to work >> out what environment they should be in, and then my puppetd wrapper scripts >> to detect that a bootstrap run has occurred (probably a file set to be >> present on the bootstrap run and absent on all other runs) and re-run. >> > > Nigel, I think this answers your question: > > write a fact that returns the current environment. > > during provisioning, set environment to 'bootstrap'. > > in your classifier, set a parameter called $puppet_environment that is > used in your puppet class to update environment in puppet.conf. > Not quite. This doesn't cope with a machine where someone say incorrectly wipes out the local fact cache, it wouldn't take effect until the next run. You need the external node classifier to make the decision as to whether the client should be redirected to a bootstrap/provisioning environment, but we have no real way of telling the client that it needs to perform a second run. Sometimes I wonder if we should be able to have a directive in puppet manifests to tell puppet "hey, you need to start your run all over again". > > >> How could we achieve the same functionality within puppetd itself? I can't >> think of a way this could be done right now with it running as a daemon. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] common module [was: puppet-module-apache]
> Since I'm almost convinced that people will keep on doing their own > apache modules and there will hardlly be a monstre module good for > every use [...] I've been thinking about this and about the various attempts to start a "common modules" project that we have seen in the past. I believe the reason it will probably be difficult to build one common apache module that everyone will be happy to use, is that apache is one of these tools that offers many different ways to do the same sort of thing. Then there is the personal/cultural preferences of every sysadmin on how thing should be done. Add this to the various constraints which are imposed to us by the clients/managers which we work for. So either this module will eventually be extremely simple and generic, but will probably not be very useful because all the job of configuring apache will be left to the module user. Or it will be full of cool ideas, will allow the user to skip past the complicated configuration stuff, but will be biased towards the authors habits and constraints. I think this will be the case for any "middleware" tool, not only for apache. By middleware, I mean the tools which the users have direct interaction with (databases, application servers, fileservers, etc). In contrast, ntp, syslog, mta, etc, are much less subject to this problem. Except the sysadmins, nobody usually cares how ntp works, or if it even exists. So what I'm suggesting is that it may be easier to start a set of common modules with this second sort of modules (which probably have at least as many variants as the apache module). Sorry if I sound pessimistic, but to quote Paul, "Let's get all the disparate apache modules out there merged together into One Awesome Module." seems to me like the 12 labors of Hercules. On the other hand, without ambitious people to start such projects, incredible tools like puppet or apache wouldn't exist :-) I'm looking forward to debate this around a belgian beer in Ghent ! Marc -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Namespace conflicts
Hmm..I didn't think about that. That does indeed appear to work. Most interesting. Thanks! Trevor On Mon, May 17, 2010 at 5:47 PM, R.I.Pienaar wrote: > > - "Trevor Vaughan" wrote: > >> Sorry if this has been covered before, but I couldn't find it in a >> cursory search. >> >> If you have a module: >> >> /etc/puppet/modules/foo >> >> And you have a module: >> >> /etc/puppet/modules/bar/manifests/foo.pp >> >> Then all references to 'foo' within that namespace seem to scope down >> to the local foo; is this correct? >> >> So, in /etc/puppet/modules/bar/manifests/baz.pp, if I have the line: >> >> include 'foo' >> >> Then it will always grab 'bar::foo', not 'foo' as I desire. >> >> Is this by design, or a defect? > > By design I'd say, you can do: > > include ::foo > > to get the top level one. though there's a few points where the language > blows up with this syntax so your milage might vary > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Namespace conflicts
- "Trevor Vaughan" wrote: > Sorry if this has been covered before, but I couldn't find it in a > cursory search. > > If you have a module: > > /etc/puppet/modules/foo > > And you have a module: > > /etc/puppet/modules/bar/manifests/foo.pp > > Then all references to 'foo' within that namespace seem to scope down > to the local foo; is this correct? > > So, in /etc/puppet/modules/bar/manifests/baz.pp, if I have the line: > > include 'foo' > > Then it will always grab 'bar::foo', not 'foo' as I desire. > > Is this by design, or a defect? By design I'd say, you can do: include ::foo to get the top level one. though there's a few points where the language blows up with this syntax so your milage might vary -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Time is running out to register for Puppet Camp Europe in Ghent, Belgium May 27-28th
> > Luke Kanies > > Jeff McCune > > Scott Campbell > > Markus Roberts Too bad that Dan (Bode) is not in the bunch... :-) For the people unsure if it's worth the case to partecipate I can say that the previous Puppet Camp has been a totally enjoyful, interesting, inspiring and enlightening experience. Really something that a Puppeteer, or anyone somehow involved in systems operations, can't miss. my2c Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Namespace conflicts
Sorry if this has been covered before, but I couldn't find it in a cursory search. If you have a module: /etc/puppet/modules/foo And you have a module: /etc/puppet/modules/bar/manifests/foo.pp Then all references to 'foo' within that namespace seem to scope down to the local foo; is this correct? So, in /etc/puppet/modules/bar/manifests/baz.pp, if I have the line: include 'foo' Then it will always grab 'bar::foo', not 'foo' as I desire. Is this by design, or a defect? Puppet 0.24.9 Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Time is running out to register for Puppet Camp Europe in Ghent, Belgium May 27-28th
- "Scott Olson" wrote: > Hi, > > The following Puppet Labs employees will be attending Puppet Camp > Europe next week: > > Luke Kanies > Jeff McCune > Scott Campbell > Markus Roberts thank you! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Time is running out to register for Puppet Camp Europe in Ghent, Belgium May 27-28th
Hi, The following Puppet Labs employees will be attending Puppet Camp Europe next week: Luke Kanies Jeff McCune Scott Campbell Markus Roberts Scott On May 17, 2010, at 8:34 AM, R.I.Pienaar wrote: > hello, > > - "Scott Olson" wrote: > >> Get details about the event and registration from our blog: >> >> http://www.puppetlabs.com/blog/time-is-running-out-to-register-for-puppet-camp-europe-may-27th-28th-in-ghent-belgium/ >> >> If you're going to be in Europe next week don't miss this opportunity >> to interact with the Puppet Labs team and the Puppet community face >> to face. > > It would be really useful if someone wanted to comment on the record who from > PL is actually going, thusfar its proving hard to find out! > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Time is running out to register for Puppet Camp Europe in Ghent, Belgium May 27-28th
hello, - "Scott Olson" wrote: > Get details about the event and registration from our blog: > > http://www.puppetlabs.com/blog/time-is-running-out-to-register-for-puppet-camp-europe-may-27th-28th-in-ghent-belgium/ > > If you're going to be in Europe next week don't miss this opportunity > to interact with the Puppet Labs team and the Puppet community face > to face. It would be really useful if someone wanted to comment on the record who from PL is actually going, thusfar its proving hard to find out! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Time is running out to register for Puppet Camp Europe in Ghent, Belgium May 27-28th
Get details about the event and registration from our blog: http://www.puppetlabs.com/blog/time-is-running-out-to-register-for-puppet-camp-europe-may-27th-28th-in-ghent-belgium/ If you're going to be in Europe next week don't miss this opportunity to interact with the Puppet Labs team and the Puppet community face to face. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Unable to retrieve files from puppet server (Errror 400)
On Mon, May 17, 2010 at 6:05 AM, Abhishek wrote: > > > On Apr 11, 4:57 pm, Mark Nelson wrote: > > Hello > > > > I am using the following software - > > > > *Operating System: > > > > *Scientific Linux SL release 5.3 (Boron), Scientific Linux is a rebuild > > of Redhat Enterprise > > > > *Ruby version:* > > > > ruby-shadow-1.4.1-7.el5.x86_64 > > ruby-irb-1.8.5-5.el5_3.7.x86_64 > > grub-0.97-13.2.x86_64 > > ruby-libs-1.8.5-5.el5_3.7.x86_64 > > ruby-rdoc-1.8.5-5.el5_3.7.x86_64 > > ruby-1.8.5-5.el5_3.7.x86_64 > > ruby-augeas-0.3.0-1.el5.x86_64 > > ruby-ldap-0.9.7-3.el5.x86_64 > > > > *Puppet Version: > > > > *puppet-0.25.4-1.el5.noarch > > puppet-server-0.25.4-1.el5.noarch > > > > I am getting an "Error 400 message" when I try to download a file from > > the puppet server I'm getting the following error when running puppet > > --test -dv > > > > err: //dns/File[/etc/resolv.conf]: Failed to retrieve current state of > > resource: Error 400 on SERVER: Not authorized to call find on > > /file_metadata/common/etc/resolv.conf Could not retrieve file metadata > > for puppet://puppet/common/etc/resolv.conf: Error 400 on SERVER: Not > > authorized to call find on /file_metadata/common/etc/resolv.conf at > > /etc/puppet/manifests/classes/dns.pp:8 > > > > Running the puppermasterd in debug mode produces the following error > > message > > > > info: mount[files]: allowing * access > > err: Not authorized to call find on /file_metadata/common/etc/resolv.conf > > > > Both the client and the server are running on the same machine. There > > are references to similar issues in puppet 0.25.1 I'm not sure if these > > issues are fixed in 0.25.4 > > > > My configuration files are as follows - > > > > *Auth.conf * > > > > # inconditionnally allow access to all files services > > # which means in practice that fileserver.conf will > > # still be used > > path /file > > allow * > > > > *Fileserver.conf > > > > *[files] > > path /etc/puppet/files > > #allow *.int.tardis.cx > > allow * > > #deny *.examp > > > > Thanks > > > > Mark. > > Hi Mark, > > "puppet://puppet/common/etc/resolv.conf: Error 400 on SERVER" > > you have to define following in /etc/puppet/fileserver.conf > > [puppet] > > allow * > No. Look at his URI more closely. It's a double slash, so it's referring to a server named 'puppet' with a fileserver mountpoint of 'common'. Assuming this is a proper module, there's no need to put anything in fileserver.conf (It really is better to get in the habit of replacing "puppet://$server" with "puppet:///" ) > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Documentation link error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Silviu Paragina wrote: > I have found some broken links on > http://docs.puppetlabs.com/guides/more_language.html#functions . Where > should I post and/or fix the error? > http://projects.puppetlabs.com/projects/puppet-docs/issues And you're welcome to fork: http://github.com/reductivelabs/puppet-docs And submit a patch. Thanks James Turnbull - -- Author of: * Pro Linux Systems Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJL8U+QAAoJECFa/lDkFHAyGCMH/3R2dt7CI/IBTIlIFaRSJj+R fulrTk5AhM0Sa7R8gD36AIP79Vheq4NPH09qqr1B1Jj4Aiwdeb1nsnYEyeUvBexZ gI8zkIzshh7b/XzY0TrHz6dhli6Cu5Riubtbc+K2+CCa8Ku2eNIqNlTG3QgDs+E1 VLLAUvzrAkexSZe1JiMNJdCvgSnfLTxHReaH9p+kZWTujuXkUbtqShzCktgN0rlJ ZwjXsm2OS7fh8grerdrKMUrox1IhbPEZQnhDgvTDoq2YDqzoIeg5bTOImq6k59Dk Y7vmw4E8yl3iP5yyqh6tauQ3foBut7ad8780TJGUWKeQGfz8zHrXm+rET10P+tE= =/3xQ -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: External Nodes
On 15.05.2010 00:30, Baker, Luke Jefferson wrote: Speaking of external nodes.. Any decent tutorials out there for someone that has no idea where to start? ;) External nodes are a way of looking up classes and vars to be applied to a node via an external application. http://docs.puppetlabs.com/guides/external_nodes.html - you may try a do it yourself script/application But you should try foreman, puppet dashboard or extlookup (I think there are other, but I don't know them). Each has a different setup process to long to explaing here. (do a few googles ;) ) Silviu -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: External Nodes
On 15.05.2010 00:30, Baker, Luke Jefferson wrote: Speaking of external nodes.. Any decent tutorials out there for someone that has no idea where to start? ;) To my last e-mail. Correction extlookup does not do external node lookup. :) It's a puppet function sorry about the confussion. Silviu -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ssh::auth unable to get working
On 15.05.2010 10:18, Michael Dodwell wrote:
Hey all,
Just trying to get
http://projects.reductivelabs.com/projects/puppet/wiki/Module_Ssh_Auth_Patterns
to work:
I've managed to get everything except ssh::auth::client happening. I
just don't understand why it isn't working. It is just a very simple
call:
include ssh::auth
ssh::auth::key { [ "us...@domain.com", "us...@domain.com" ]: ensure =>
present }
class base_system {
realize User["user1"]
ssh::auth::client { "us...@domain.com": ensure => present }
realize User["user2"]
ssh::auth::client { "us...@domain.com": ensure => present }
}
node app1 {
include base_system
}
When running puppetd --test i get the following:
err: Could not run Puppet configuration client: Could not find
dependency File[/home/user1] for File[/home/user1/.ssh/id_rsa] at /etc/
puppet/modules/ssh/manifests/auth.pp:262
I'm not sure about the usage of the recipe, but this requires you to
create the specified resource.
file { "/home/user1":
ensure => directory,
owner => user1,
group => user1,
}
Also reading a bit about the recipe note that:
* you *must *include ssh::auth::keymaster class on the puppetmaster
(that is where the keys are created)
* client means that the private key installed on that computer
* server means that the public key will be installed in authorized_keys
I've tried to realize File[/home/user1] then i get a error about being
unable to realize virtual resource. I'm not really sure why calling
realize on anything is required.
This http://docs.reductivelabs.com/guides/virtual_resources.html should
explain it.
Also read the Language guide and the advanced language guide if you
haven't read them already. ;)
Silviu
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Documentation link error
I have found some broken links on http://docs.puppetlabs.com/guides/more_language.html#functions . Where should I post and/or fix the error? Silviu -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Writing a properly-formed custom type (configxml)
Please hold my hand.
After studying the wiki, several unofficial pages, various mailing list
entries, and the operation of the "iptables" type as found on the net, I have
created a custom type, lovingly named ``configxml''.
It updates attributes on the first element matching a supplied XPath in a given
XML file. The first use case is configuring Atlassian JIRA to use Postgres ..
The custom type:
- Detects the need to update attribute values
- Updates attribute values
- Pretty prints to the log, ex. when run with ``puppetd -dtv''
- Solves today's immediate need, but I don't trust its ability to properly
integrate into the dependency tree, nor even its return value
Initially this was split into a type and a provider, which didn't work. I don't
clearly understand how provider functionality is invoked, nor its relationship
with a type.
How should this custom type be better structured and written?
I greatly appreciate feedback and pointers.
I've attached relevant code, sorry if its a little long ..
As you might sense from reading the code, today marks my 3rd day as a Ruby
newbie ..
8< manifest snippet 8<
node 'jira' inherits 'basenode' {
...
configxml { '/opt/jira/atlassian-jira/WEB-INF/classes/entityengine.xml':
xpath => "/entity-config/datasour...@name='defaultDS']",
attributes => 'field-type-name=postgres72,schema-name=public',
}
...
}
8< configxml.rb 8<
module Puppet
newtype(:configxml) do
@doc = "Modify attributes of the first element matching the
XPath expression in an XML file."
require 'rexml/document'
require 'set'
def test_it
doc = REXML::Document.new(File.open(value(:name)))
# Take the first element matching the provided XPath
expression
attrs = doc.elements[value(:xpath) + "[1]"].attributes
# Split up the comma-separated key-value pairs into an
array and then isolate the keys
keys = value(:attributes).split(/,/).map { |s|
s.split(/=/)[0] }
# Build up an array of attributes for the specified keys
keys.map { |k| "#{k}=#{attrs[k]}" }
end
def set_it
doc = REXML::Document.new(File.open(value(:name)))
# Take the first element matching the provided XPath
expression
attrs = doc.elements[value(:xpath) + "[1]"].attributes
# Split up the list comma-separated key-value pairs and
convert the array to hash
updates = Hash[*value(:attributes).split(/,/).map { |s|
s.split(/=/) }.flatten]
# Update this element's attributes
updates.each { |k, v| attrs[k] = v }
# Write the changes back
doc.write(File.open(value(:name), 'w'))
end
newparam(:name) do
desc "Full path of the XML document."
end
newparam(:xpath) do
desc "XPath expression selecting target elements; the
first of which whose attributes will be set."
end
newparam(:attributes) do
desc "An array of strings, each containing 'key=value'
expressions setting element attributes."
end
def evaluate
cur_attrs = test_it
if Set.new(value(:attributes).split(/,/)) ==
Set.new(cur_attrs)
debug("Attributes for element at
#{value(:xpath)} already #{value(:attributes)}. No changes necessary.")
return [] # TODO what goes here?
else
notice("Updating attributes for element at
#{value(:xpath)} to #{value(:attributes)}.")
set_it
return [] # TODO what goes here?
end
end
end
end
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] filebucket issue
Hi,
I am using puppet to deploy config files but i am facing issue while
implementing filebucket for backup. Issue is i am defining central
file bucket but still files are getting stored in local file client
bucket.
site.pp ( content)
include node.pp
filebucket { main: server => 'nmlimage01.edc.mihi.com' }
File { backup => main }
class test {
file { "/etc/resolv.conf":
source => "puppet:///globalconfig/resolv.conf",
backup => main
}
}
node.pp (content)
node pp01 {
include test
}
Client Log:
info: Caching catalog for nmlgamepp01.edc.mihi.com
debug: Creating default schedules
debug: Finishing transaction 23456272463300 with 0 changes
debug: Loaded state in 0.01 seconds
info: Applying configuration version '1274102055'
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: //test/File[/etc/resolv.conf]: Changing checksum,content
debug: //test/File[/etc/resolv.conf]: 2 change(s)
debug: //test/File[/etc/resolv.conf]/checksum: Replacing /etc/
resolv.conf checksum {md5}958836dd057fdbb33597d688cc6d28a2 with {md5}
d7fbc1695489ce896d30b7b04d72887c
notice: //test/File[/etc/resolv.conf]/checksum: checksum changed '{md5}
958836dd057fdbb33597d688cc6d28a2' to '{md5}
d7fbc1695489ce896d30b7b04d72887c'
info: Filebucket[/var/lib/puppet/clientbucket]: Adding /etc/
resolv.conf(d7fbc1695489ce896d30b7b04d72887c)
info: //test/File[/etc/resolv.conf]: Filebucketed /etc/resolv.conf to
main with sum d7fbc1695489ce896d30b7b04d72887c
debug: //test/File[/etc/resolv.conf]/checksum: Replacing /etc/
resolv.conf checksum {md5}d7fbc1695489ce896d30b7b04d72887c with {md5}
958836dd057fdbb33597d688cc6d28a2
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
notice: //test/File[/etc/resolv.conf]/content: content changed '{md5}
d7fbc1695489ce896d30b7b04d72887c' to '{md5}
958836dd057fdbb33597d688cc6d28a2'
debug: Finishing transaction 23456272349400 with 2 changes
debug: Storing state
debug: Stored state in 0.11 seconds
notice: Finished catalog run in 1.95 seconds
notice: Caught INT; calling stop
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Unable to retrieve files from puppet server (Errror 400)
On Apr 11, 4:57 pm, Mark Nelson wrote: > Hello > > I am using the following software - > > *Operating System: > > *Scientific Linux SL release 5.3 (Boron), Scientific Linux is a rebuild > of Redhat Enterprise > > *Ruby version:* > > ruby-shadow-1.4.1-7.el5.x86_64 > ruby-irb-1.8.5-5.el5_3.7.x86_64 > grub-0.97-13.2.x86_64 > ruby-libs-1.8.5-5.el5_3.7.x86_64 > ruby-rdoc-1.8.5-5.el5_3.7.x86_64 > ruby-1.8.5-5.el5_3.7.x86_64 > ruby-augeas-0.3.0-1.el5.x86_64 > ruby-ldap-0.9.7-3.el5.x86_64 > > *Puppet Version: > > *puppet-0.25.4-1.el5.noarch > puppet-server-0.25.4-1.el5.noarch > > I am getting an "Error 400 message" when I try to download a file from > the puppet server I'm getting the following error when running puppet > --test -dv > > err: //dns/File[/etc/resolv.conf]: Failed to retrieve current state of > resource: Error 400 on SERVER: Not authorized to call find on > /file_metadata/common/etc/resolv.conf Could not retrieve file metadata > for puppet://puppet/common/etc/resolv.conf: Error 400 on SERVER: Not > authorized to call find on /file_metadata/common/etc/resolv.conf at > /etc/puppet/manifests/classes/dns.pp:8 > > Running the puppermasterd in debug mode produces the following error > message > > info: mount[files]: allowing * access > err: Not authorized to call find on /file_metadata/common/etc/resolv.conf > > Both the client and the server are running on the same machine. There > are references to similar issues in puppet 0.25.1 I'm not sure if these > issues are fixed in 0.25.4 > > My configuration files are as follows - > > *Auth.conf * > > # inconditionnally allow access to all files services > # which means in practice that fileserver.conf will > # still be used > path /file > allow * > > *Fileserver.conf > > *[files] > path /etc/puppet/files > #allow *.int.tardis.cx > allow * > #deny *.examp > > Thanks > > Mark. Hi Mark, "puppet://puppet/common/etc/resolv.conf: Error 400 on SERVER" you have to define following in /etc/puppet/fileserver.conf [puppet] allow * -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: External Nodes
On 5/14/2010 10:38 PM, Paul Lathrop wrote: No, you cannot put resources directly into nodes when you are using external nodes. In practice, this hasn't mattered; you wrap your resources in a class, done. Exactly. The most straght-forward way to do this is to s/node/class/ and include $fqdn via external nodes. Best Regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppetcamp
About the PuppetCamp, it would be nice, as "consolidated tradition", to arrange a meetup at least the evening of 26th of May for who is already at Ghent. Any reccomendation from belgian natives about pubs or places good for the gathering? Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
