Re: [Puppet Users] Bootstrap
If you need to save some time, have a look at theforeman.org - which should takes care for most of the work for you. Ohad On Fri, Jul 30, 2010 at 12:19 PM, Daniel Pittman dan...@rimspace.netwrote: parag(PK) myselfpk...@gmail.com writes: Can it be possible to boot up a bare metal client ,by downloding the whole OS from server .when the client is powered on . Yes. Feel free to research PXE booting, debootstrap, debconf preseeding, kickstart, satellite, jumpstart, FAI, and the other related technologies yourself. Regards, Daniel -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- 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.compuppet-users%2bunsubscr...@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] Re: 0.25.4 caching problem with custom function
I don't have much in the way of suggestions, but I ran into a lot of problems recently when I tried to have a docroot sitting on NFS. No matter what I did I always ran into weird problems just like this. It sort of worked but definitely not something I could use in production... We've been using NFS for 2 years and it works great. I worked very hard to eliminate NFS write issues when setting it up - as long as it's used as a read datastore it seems to work fine. The specific problem to which I'm referring didn't appear until we moved to 0.25 a few weeks ago. At 0.24.8 this never happened. I suppose it's possible that there's some sort of write issue with NFS under 0.25, but why would that manifest as an inability to read this one specific function and not in any other part of my massive module stack? Even when I've seen Puppet clients fail because of Stale NFS filehandle when the master is reloading something I've changed, they still do the run from cache and load that file fine the next time through. This function error is a critical error that kills the puppet run completely, and it never goes away until I change the .rb file for the function in some way (newline, space, whatever). That's not NFS - that's code. I'm not seeing any response from those who could speak to caching, and now that 2.6 is out, we'll probably have to wait to troubleshoot it with the developers until after we upgrade again. Thanks, everyone, for your response and for taking the time to think about what it might be. Adrian -- 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] Reconciling resource defaults, dynamic scope, and the singleton nature of classes
On 7/29/2010 8:07 PM, R.I.Pienaar wrote: - Jeff McCunej...@puppetlabs.com wrote: Perhaps it might be useful to set resource defaults only for the local scope, and not for any classes which get included into this scope. How do you feel about this change to the language? I've thought about this problem before and thought the fact that puppet did not behave in this way was a bug, so my vote is with this :) +1. I was not aware of the current behaviour and it's definitely not the way I'd expect a sensible language to work. 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.
Re: [Puppet Users] exec not finding shell builtins/functions?
+1
On 7/30/2010 6:18 AM, Daniel Pittman wrote:
James Turnbullja...@puppetlabs.com writes:
Richard Crowley wrote:
On Thu, Jul 29, 2010 at 3:23 PM, Greg Grafgreg.g...@rackspace.com wrote:
[...]
I saw the same thing happen with a few for-loops and had to wrap them
up in /bin/sh -c '...' for 2.6. Now that I look for it, I can't find
anything about this behavior change in the release notes for 2.6. Was
it coincidental that it ever worked?
See:
http://projects.puppetlabs.com/issues/4288
http://projects.puppetlabs.com/issues/4299
For some history and comments on this. We'd welcome some input into
what you think should be safe and expected behaviour here.
If this is a voting matter, let me put in a vote for passing a simple string
to the shell, and passing an array direct to exec, which is consistent with
the use of 'system' style commands in a whole bunch of sysadmin scripting
languages.
Eg, this:
exec { foo: command = ['/bin/ls', '|' 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
Daniel
--
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: Multiple repositories under one file
So it looks like it's a bug... Apparently, you can only specify one
repo per file via Yumrepo definition...
http://projects.puppetlabs.com/issues/2062
It looks like it was so long ago.. I'm surprised that no one has come
up with a work around yet.
On Jul 29, 3:15 pm, CraftyTech hmmed...@gmail.com wrote:
Hello All,
In all the examples that I see you configure one repo per file;
i.e:
yumrepo { testing.com-repo:
baseurl = http://repos.testing.com/fedora/$lsbdistrelease/;,
descr = Testing.com's YUM repository,
enabled = 1,
gpgcheck = 0,
}
But how do I specify multiple entries to the same file?. For
instance, I just one to have one file base.repo to contains all the
entries for the repos for my environment. i.e:
/etc/yum.repo.d/base.repo:
[base]
baseurl value
Desc value
[3rdParty]
baseurl value
Desc value
I'm running puppet 0.25.5.
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] Re: Multiple repositories under one file
On 2010-07-30 13:59, CraftyTech wrote: So it looks like it's a bug... Apparently, you can only specify one repo per file via Yumrepo definition... http://projects.puppetlabs.com/issues/2062 It looks like it was so long ago.. I'm surprised that no one has come up with a work around yet. That bug is about modifying existing repo definitions, where there already are multiple sections within a single file. Like the six repos in /etc/yum.repos.d/CentOS-Base.repo. And the reason no-one has bothered with working around that is probably that it actually works. At least I have had no problems with doing that with at least 0.24.4, 0.24.8, 0.25.0 and 0.25.4. As for creating new repo definitions using the yumrepo type, I personally don't mind it putting each repo in its own file. /Bellman -- 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: Struggling with syntax
Thanks for the responses! I'll try some of these out and post what I end up with. devzero, have you looked at how completely different the requirements are for 32bit and 64bit in audit.rules? Using an erb would be a nightmare! -- 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] exec not finding shell builtins/functions?
On Fri, 30 Jul 2010, Daniel Pittman wrote:
Eg, this:
exec { foo: command = ['/bin/ls', '|', 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
+1 [I added a missing comma above.]
--apb (Alan Barrett)
--
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: Struggling with syntax
After a brief deliberation, it was actually a toss up between Andrew Forgue and Erinn Loony-Trigss's suggestions. I opted for Andrew's solution as in this case it seemed the neatest, although it was a very close thing. I'm sure that using an architecture directory would be the more elegant solution in some cases though. To everyone else, thank you for shedding some light on how puppet deals with case statements as I'm sure I'll be needing those in the future. Thanks again for your help. -- 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] exec not finding shell builtins/functions?
On 2010-07-30 06:18, Daniel Pittman wrote:
If this is a voting matter, let me put in a vote for passing a simple string
to the shell, and passing an array direct to exec, which is consistent with
the use of 'system' style commands in a whole bunch of sysadmin scripting
languages.
Eg, this:
exec { foo: command = ['/bin/ls', '|' 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
I think this is a very reasonable suggestion, so +1 from me as well.
But I'd like to point out the shellquote() function, which can give you
the semantics of the first version already today:
exec { foo: command = shellquote(/bin/ls, |, foo); }
(There's actually a slight difference. Using shellquote() today will
give you an intermediate shell process, making it somewhat less efficient.)
/Bellman
--
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] exec not finding shell builtins/functions?
On 07/30/2010 12:18 AM, Daniel Pittman wrote:
James Turnbullja...@puppetlabs.com writes:
Richard Crowley wrote:
On Thu, Jul 29, 2010 at 3:23 PM, Greg Grafgreg.g...@rackspace.com wrote:
[...]
I saw the same thing happen with a few for-loops and had to wrap them
up in /bin/sh -c '...' for 2.6. Now that I look for it, I can't find
anything about this behavior change in the release notes for 2.6. Was
it coincidental that it ever worked?
See:
http://projects.puppetlabs.com/issues/4288
http://projects.puppetlabs.com/issues/4299
For some history and comments on this. We'd welcome some input into
what you think should be safe and expected behaviour here.
If this is a voting matter, let me put in a vote for passing a simple string
to the shell, and passing an array direct to exec, which is consistent with
the use of 'system' style commands in a whole bunch of sysadmin scripting
languages.
Eg, this:
exec { foo: command = ['/bin/ls', '|' 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
Daniel
That seems like the implementation would be tricky and error-prone,
compared to having people add sh/bash/ksh -c to the beginning of the
command in the exec. I mean, is that really such a big deal?
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
When the going gets weird, the weird turn pro.
--
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] Cannot save facts to the code store
Hey All, I've got a puppetmaster running .25.4 and tried to update it to .25.5 today. When I do that, I get a message whenever a client tries to make a puppet run: err: Could not retrieve catalog from remote server: Error 400 on SERVER: You cannot save facts to the code store; it is only used for getting facts from Facter err: Could not retrieve catalog; skipping run The message comes in right after custom facts are loaded. It appears to come from the following code in lib/puppet/indirector/facts/facter.rb -- def save(facts) raise Puppet::DevError, You cannot save facts to the code store; it is only used for getting facts from Facter end What exactly is it trying to say? Is the code store the /etc/puppet directory on the Server or someplace like /usr/lib/ruby/site_ruby/1.8/puppet? I can delete everything out of the /usr/lib/ruby/site_ruby/1.8/puppet directory (along with puppet.rb and the binaries in /usr/bin and /usr/sbin), then reinstall .25.4, and everything works properly. I don't know if this is a BUG or something I've done incorrectly with my puppet setup. The puppet.conf on my server looks like this: [main] external_nodes = /usr/bin/rubyexternalnode.rb node_terminus = exec pluginsync = true libdir = $vardir/lib [puppetmasterd] ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY reports = puppet_dashboard autosign = true I'm running Passenger (but I get the same message if I flip back to Webrick) and it's on an OS X 10.5.8 Server box. All my custom facts are in /etc/puppet/modules/custom/lib/facter. Thanks for any pointers anyone can send my way! -- Gary Larizza Director of Technology Huron City Schools http://www.huronhs.com 悟 -- 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: Multiple repositories under one file
Gotcha... and I may also not mind creating multiple files under the repo directory, but how do I disable the default repos that come with CentOS? Thanks, On Jul 30, 8:14 am, Thomas Bellman bell...@nsc.liu.se wrote: On 2010-07-30 13:59, CraftyTech wrote: So it looks like it's a bug... Apparently, you can only specify one repo per file via Yumrepo definition... http://projects.puppetlabs.com/issues/2062 It looks like it was so long ago.. I'm surprised that no one has come up with a work around yet. That bug is about modifying existing repo definitions, where there already are multiple sections within a single file. Like the six repos in /etc/yum.repos.d/CentOS-Base.repo. And the reason no-one has bothered with working around that is probably that it actually works. At least I have had no problems with doing that with at least 0.24.4, 0.24.8, 0.25.0 and 0.25.4. As for creating new repo definitions using the yumrepo type, I personally don't mind it putting each repo in its own file. /Bellman -- 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] Puppet dashboard and environments
Hi puppet users,
We've got a puppet (0.24.8) implementation with two environments, called
production and testing. We've also got a Puppet Dashboard (1.0) instance
up and running, which is receiving and displaying reports from hosts in
both of the environments.
We would like to start using the dashboard as an external node
classification tool, so I've taken the example from the puppet-dashboard
source tree and it's working up to a point.
My query is this:
Why doesn't the dashboard understand which environment applies to the
host, and return that in the yaml output?
Here's the sample external node definition from the puppet docs.
http://docs.puppetlabs.com/guides/external_nodes.html#external_node_scripts_for_version_023_and_later
#!/bin/sh
# Super-simple external_node script for versions 0.23 and later
cat END
---
classes:
- common
- puppet
- dns
- ntp
environment: production
parameters:
puppet_server: puppet.example.com
dns_server: ns.example.com
mail_server: mail.example.com
END
exit 0
And here's the default output from the external node tool.
- name: server.example.com
parameters: {}
classes: []
...without the environment defined.
At the moment, all of our testing environment clients are defined as
such in their own puppet.conf files, but we wanted to remove this
requirement by making it part of the external node definition.
I know that I could use a parameter for it, because I'm already managing
the puppet.conf file on the clients, but that seems a little convoluted.
Is this something that is better handled another way, or is it on the
roadmap for the puppet dashboard?
many thanks,
Ben
--
--
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: Newbie question - package installation
I'm using 0.25.5 and I do it in pretty much the same way:
file { oratoolkit_rpm:
require = [ Group[oinstall],
Group[dba],
User[oracle],
],
path = /home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm,
source = puppet:///oracle/oratoolkit-1.0.2.1.4-1.noarch.rpm,
owner = admin,
group = admin,
ensure = present,
}
# installs the oratoolkit package
package { oratoolkit:
require = File[oratoolkit_rpm],
source = /home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm,
provider = rpm,
ensure = installed,
}
Try adding an ensure = present to your File resource and see if it
avoids downloading the RPM file over and over again.
On Jul 29, 10:40 pm, Rustler coltsixshoo...@gmail.com wrote:
I am using version 2.6 and it would be nice if you could use a puppet
url for the package source, but that does not appear to work (docs say
it has to be a local file).
My other choices seem to be an nfs mount, or a local repo server.
Thanks
On Jul 29, 11:23 am, Patrick Mohr kc7...@gmail.com wrote:
On Jul 29, 2010, at 9:45 AM, Rustler wrote:
This code is working - but due to the file declaration it keeps
downloading the rpm even after the package gets installed.
1. How do I stop the rpm from downloading after the package is
installed?
Best method:
*) If at all possible you should just replace this with a real package
repository.
Should also work:
*) Put the rpm files on a webserver and download them as needed. I think
rpm can take URLs instead of local paths.
or
*)Install from a network drive like nfs
Not recommended:
*) Just put the rpms into a folder you create. It will keep growing
forever, but it probably won't ever get very big unless you release a lot
of packages. Trust me on this, pushing out big files with puppet is
probably a mistake. It will put a large load on the puppetmaster, and if
you are using a version of puppet less than 2.6.0, the RAM requirements on
the client and serve will be horrendous.
--
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] Dashboard external node tool - defaults
Hello,
I have a query about the use of the Puppet Dashboard as an external
node classification tool.
How do I set a default classes for all nodes?
Previously, we had the following in nodes.pp
node default {
include ourbaseclass
}
Now we are trying to move towards having the class membership all
defined within the dashboard, but we still need to have ourbaseclass
applied to all of the nodes, especially new ones.
Ought we simply to leave that definition in nodes.pp and merge it with
the results of the external node tool?
Many thanks,
Ben
--
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] exec not finding shell builtins/functions?
+1
On Fri, Jul 30, 2010 at 10:07 AM, Joe McDonagh
joseph.e.mcdon...@gmail.comwrote:
On 07/30/2010 12:18 AM, Daniel Pittman wrote:
James Turnbullja...@puppetlabs.com writes:
Richard Crowley wrote:
On Thu, Jul 29, 2010 at 3:23 PM, Greg Grafgreg.g...@rackspace.com
wrote:
[...]
I saw the same thing happen with a few for-loops and had to wrap them
up in /bin/sh -c '...' for 2.6. Now that I look for it, I can't find
anything about this behavior change in the release notes for 2.6. Was
it coincidental that it ever worked?
See:
http://projects.puppetlabs.com/issues/4288
http://projects.puppetlabs.com/issues/4299
For some history and comments on this. We'd welcome some input into
what you think should be safe and expected behaviour here.
If this is a voting matter, let me put in a vote for passing a simple
string
to the shell, and passing an array direct to exec, which is consistent
with
the use of 'system' style commands in a whole bunch of sysadmin scripting
languages.
Eg, this:
exec { foo: command = ['/bin/ls', '|' 'foo'] }
will pass '|' 'foo' to the ls command, compared to:
exec { foo: command = /bin/ls | foo }
...which passes it to the default system shell.
Daniel
That seems like the implementation would be tricky and error-prone,
compared to having people add sh/bash/ksh -c to the beginning of the command
in the exec. I mean, is that really such a big deal?
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
When the going gets weird, the weird turn pro.
--
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.compuppet-users%2bunsubscr...@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] Puppet dashboard and environments
Excerpts from Ben Tullis's message of Fri Jul 30 04:29:46 -0700 2010: Why doesn't the dashboard understand which environment applies to the host, and return that in the yaml output? Is this something that is better handled another way, or is it on the roadmap for the puppet dashboard? Hi Ben, Dashboard doesn't currently handle environments but it is on the roadmap. Rein Henrichs http://puppetlabs.com -- 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] exec not finding shell builtins/functions?
Daniel Any chance you could throw your solution on the ticket and I'll start a discussion about it internally. Thanks James -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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: Dashboard external node tool - defaults
Thanks Rein. I'll keep an eye on the progress. Kind regards, Ben On Jul 30, 4:28 pm, Rein Henrichs r...@reductivelabs.com wrote: Excerpts from Ben Tullis's message of Fri Jul 30 06:49:22 -0700 2010: How do I set a default classes for all nodes? Hi Ben, Dashboard doesn't currently have something like a default node but this seems like a useful feature so I've added a ticket: http://projects.reductivelabs.com/issues/4412 Thanks! -- Rein Henrichshttp://puppetlabs.com -- 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] Wrong version in SPEC file
I just downloaded puppet 2.6.0 from the web site, and the redhat spec file has the version number as 0.25.5 So, what version of puppet have I really got here? Doug -- 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: Wrong version in SPEC file
On Fri, Jul 30, 2010 at 9:28 AM, Douglas Garstang doug.garst...@gmail.com wrote: I just downloaded puppet 2.6.0 from the web site, and the redhat spec file has the version number as 0.25.5 So, what version of puppet have I really got here? Doug Actually, I'm also confused as to what version I was _supposed_ to have downloaded, because all the web site says is '2.6.0'. is this the final release of 2.6.0 or is it one of the release candidates? Which one, and how do I tell? Why doesn't the download at least have 2.6.0-rc1 or something in the file name? If this IS NOT one of the release candidates, I don't see the old release candidates on the web page. Where did they go? Doug -- 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: Wrong version in SPEC file
On Fri, Jul 30, 2010 at 9:30 AM, Douglas Garstang doug.garst...@gmail.com wrote: On Fri, Jul 30, 2010 at 9:28 AM, Douglas Garstang doug.garst...@gmail.com wrote: I just downloaded puppet 2.6.0 from the web site, and the redhat spec file has the version number as 0.25.5 So, what version of puppet have I really got here? Doug Actually, I'm also confused as to what version I was _supposed_ to have downloaded, because all the web site says is '2.6.0'. is this the final release of 2.6.0 or is it one of the release candidates? Which one, and how do I tell? Why doesn't the download at least have 2.6.0-rc1 or something in the file name? If this IS NOT one of the release candidates, I don't see the old release candidates on the web page. Where did they go? Doug The spec file for for (whatever version this actually is), doesn't cleanly build an RPM either. + /usr/lib/rpm/find-debuginfo.sh /usr/src/redhat/BUILD/puppet-2.6.0 find: debug: No such file or directory + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile + /usr/lib/rpm/redhat/brp-java-repack-jars error: Bad file: /usr/src/redhat/SOURCES/rundir-perms.patch: No such file or directory error: Bad file: /usr/src/redhat/SOURCES/puppet-2.6.0.tar.gz.sign: No such file or directory There's nothing on the download page about those two files. Where do I get them? I don't know what the earlier find error is about. Doug. -- 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: Wrong version in SPEC file
Douglas Garstang wrote: On Fri, Jul 30, 2010 at 9:28 AM, Douglas Garstang doug.garst...@gmail.com wrote: I just downloaded puppet 2.6.0 from the web site, and the redhat spec file has the version number as 0.25.5 So, what version of puppet have I really got here? Doug Actually, I'm also confused as to what version I was _supposed_ to have downloaded, because all the web site says is '2.6.0'. is this the final release of 2.6.0 or is it one of the release candidates? Which one, and how do I tell? Why doesn't the download at least have So a release candidate is tagged blah-2.6.0rc1.tar.gz a release is 2.6.0.tar.gz. By dowloading a tarball that is called 2.6.0 - you are getting 2.6.0. 2.6.0-rc1 or something in the file name? If this IS NOT one of the release candidates, I don't see the old release candidates on the web page. Where did they go? We update the page with the release - we don't want people to download RCs AFTER the release goes out. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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: Newbie question - package installation
I wasn't clear enough in describing the problem -
What I'm trying to achieve is that if the package is installed, don't
execute the file statement and download the rpm.
If I leave the file in /tmp, it does not download again, if I delete
the file and the package is installed, it still downloads the rpm. I
don't want to have to keep the rpm on the system after the package
install.
Seems an NFS mount for the rpm's might be the solution?
Thanks
On Jul 30, 2:53 am, quicksilver03 sebasti...@mailworks.org wrote:
I'm using 0.25.5 and I do it in pretty much the same way:
file { oratoolkit_rpm:
require = [ Group[oinstall],
Group[dba],
User[oracle],
],
path = /home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm,
source = puppet:///oracle/oratoolkit-1.0.2.1.4-1.noarch.rpm,
owner = admin,
group = admin,
ensure = present,
}
# installs the oratoolkit package
package { oratoolkit:
require = File[oratoolkit_rpm],
source = /home/admin/install/oratoolkit-1.0.2.1.4-1.noarch.rpm,
provider = rpm,
ensure = installed,
}
Try adding an ensure = present to your File resource and see if it
avoids downloading the RPM file over and over again.
On Jul 29, 10:40 pm, Rustler coltsixshoo...@gmail.com wrote:
I am using version 2.6 and it would be nice if you could use a puppet
url for the package source, but that does not appear to work (docs say
it has to be a local file).
My other choices seem to be an nfs mount, or a local repo server.
Thanks
On Jul 29, 11:23 am, Patrick Mohr kc7...@gmail.com wrote:
On Jul 29, 2010, at 9:45 AM, Rustler wrote:
This code is working - but due to the file declaration it keeps
downloading the rpm even after the package gets installed.
1. How do I stop the rpm from downloading after the package is
installed?
Best method:
*) If at all possible you should just replace this with a real package
repository.
Should also work:
*) Put the rpm files on a webserver and download them as needed. I think
rpm can take URLs instead of local paths.
or
*)Install from a network drive like nfs
Not recommended:
*) Just put the rpms into a folder you create. It will keep growing
forever, but it probably won't ever get very big unless you release a lot
of packages. Trust me on this, pushing out big files with puppet is
probably a mistake. It will put a large load on the puppetmaster, and if
you are using a version of puppet less than 2.6.0, the RAM requirements
on the client and serve will be horrendous.
--
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: Wrong version in SPEC file
Douglas Garstang wrote: The spec file for for (whatever version this actually is), doesn't cleanly build an RPM either. + /usr/lib/rpm/find-debuginfo.sh /usr/src/redhat/BUILD/puppet-2.6.0 find: debug: No such file or directory + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile + /usr/lib/rpm/redhat/brp-java-repack-jars error: Bad file: /usr/src/redhat/SOURCES/rundir-perms.patch: No such file or directory error: Bad file: /usr/src/redhat/SOURCES/puppet-2.6.0.tar.gz.sign: No such file or directory As I said before - spec file may not be up to date. But you can find the signature on that webpage where it says: Puppet tarball signature. http://puppetlabs.com/downloads/puppet/puppet-2.6.0.tar.gz.sign Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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] IP based node sections instead of hostname based?
Hi experts, Is there a way to specify in the nodes.pp sections with the ip address of the client? Currently I only saw instructions to use wildcarded hostnames. Thanks a lot -Yushu +-+ | Yushu Yao | Ph:1-510-486-4690 | | Lawrence Berkeley National Lab | Mailstop 50B-6222 | 1 Cyclotron Road | Berkeley CA 94720-8147 - USA +-+ -- 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] Bizarre Stuff in Puppet 2.6.0
Is it just me, or are others having all sorts of weird experiences with puppet 2.6.0? Specifically with parameterized classes I just had a situation where I restarted the client, got an error, restarted the client again, and the error went away. Then, I intentionally put an error in the config, restarted the client again, and the client didn't report any problems. After restarting the server and client a few more times, this error is still not being reported by the client. Doug. -- 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] Bizarre Stuff in Puppet 2.6.0
On 07/30/2010 02:43 PM, Douglas Garstang wrote: Is it just me, or are others having all sorts of weird experiences with puppet 2.6.0? Specifically with parameterized classes I just had a situation where I restarted the client, got an error, restarted the client again, and the error went away. Then, I intentionally put an error in the config, restarted the client again, and the client didn't report any problems. After restarting the server and client a few more times, this error is still not being reported by the client. Doug. Yes, see the 'empty catalogs' bug. I'm guessing it's near the same. -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode When the going gets weird, the weird turn pro. -- 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] Status of Docs: Style Guide
Hi, Is Docs: Style Guide[1] officially recommended? Styles are inconsistent across the documentation site, so either the guide or other docs have to be fixed. [1] http://docs.puppetlabs.com/guides/style.html -- 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] Setting Augeas values using an array
On 07/29/2010 04:49 PM, Doug Warner wrote:
I have a resource I'd like to manage via augeas (/etc/conf.d/net; it's a bash
variables file) but Im having problems figuring out how to set the values so
that all of the values in the array go in.
I would like it to look like this:
# cat /etc/conf.d/net
config_eth4=(192.168.128.2/24)
config_eth5=(192.168.129.2/24)
routes_eth5=(192.168.130.0/24 via 192.168.131.1)
But it ends up looking like this:
config_eth4=192.168.128.2/24
config_eth5=192.168.129.2/24
routes_eth5=192.168.130.0/24
The goal is to be able to assign multiple values to ip or routes for an
interface.
Is this something I might have to do w/ a custom type?
I'm trying to write a custom type based on the augeas type since I only need
to do a little bit of work, but I'm not used to ruby and don't know exactly
what's going. I'm trying to extend the augeas type to set the changes when I
pass in IP and routes, but my test type isn't working. So far I have:
require 'puppet/type/augeas'
Puppet::Type.newtype(:net_interface,
:parent = Puppet::Type::Augeas,
:context = /files/etc/conf.d/net,
:changes = set config_eth9/1 192.168.205.2/24
) do
@doc = Define a network interface
newparam (:name) do
desc The name of this task. Used for uniqueness
isnamevar
end
newparam (:ip) do
desc The IP addresses and netblocks for this interface
defaultto :false
end
newparam (:routes) do
desc The routes associated with this interface
defaultto :false
end
end
When I call this with:
net_interface { 'eth4': ip = [192.168.128.2/24] }
nothing happens.
What do I need to do here to stick values into the changes variable when
'ip' or 'routes' is set and have the augeas type run?
-Doug
signature.asc
Description: OpenPGP digital signature
Re: [Puppet Users] Re: Multiple repositories under one file
CraftyTech wrote:
Gotcha... and I may also not mind creating multiple files under the
repo directory, but how do I disable the default repos that come
with CentOS?
yumrepo { 'base': enabled = 0 }
You can use 'enabled = absent' to remove the repo definition from the
file entirely.
--
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Tell a man there are 300 billion stars in the universe, he'll believe
you. Tell him a bench has wet paint on it and he'll have to touch it
to be sure.
pgpexTkuZqbPN.pgp
Description: PGP signature
Re: [Puppet Users] Re: Wrong version in SPEC file
Douglas Garstang wrote: The spec file for for (whatever version this actually is), doesn't cleanly build an RPM either. + /usr/lib/rpm/find-debuginfo.sh /usr/src/redhat/BUILD/puppet-2.6.0 find: debug: No such file or directory + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-python-bytecompile + /usr/lib/rpm/redhat/brp-java-repack-jars error: Bad file: /usr/src/redhat/SOURCES/rundir-perms.patch: No such file or directory error: Bad file: /usr/src/redhat/SOURCES/puppet-2.6.0.tar.gz.sign: No such file or directory There's nothing on the download page about those two files. Where do I get them? I don't know what the earlier find error is about. Any reason to not use the packages from: http://tmz.fedorapeople.org/repo/puppet/epel/ The spec file included in the tarballs is not automatically synced up with each relesae, it's there simply as a convenience for folks that don't want to have to rewrite it from scratch. Personally, until 2.6.x is beat on a little more, we probably won't push it into EPEL. But until then, I plan to update my fedorapeople repo with the latest releases and release candidates. You could grab the yum repo file from there and then install puppet-2.6.0 explicitly if you don't want to run 2.6.1rc1. Or, grab the srpm and rebuild it if you like. You'll need to pass in some definitions that the Fedora/EPEL build system uses. rpmbuild --rebuild --define 'dist .el5' --define 'rhel 5' \ --define 'el5 1' /path/to/puppet*.src.rpm You can pass some options to disable augeas and selinux if you like as well. Also, from the /usr/src/redhat paths in your output, it looks like you're building as root. That's generally not a good idea. If you're on RHEL/CentOS, install rpmdevtools and run rpmdev-setuptree to setup a local user account for building. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Marriages are made in heaven. But so are thunder, lightning, and hail. pgpvV4j9WcmfJ.pgp Description: PGP signature
[Puppet Users] Re: Puppet dashboard and environments
You can use a wrapper for the external nodes script, that will intercept the YAMl from Dashboard and attach an environment to the YAML. You can put logic in there that says: if hostname =~ xyz, then environment = production (Or whatever criteria you want, instead of hostname) Foreman can do this out of the box, if you would rather not bother with a wrapper. This is a bit of a hack, but can help you have two manifiest directories on a single puppetmaster, based on the environment. On Jul 30, 8:36 am, Ben Tullis b...@tiger-computing.co.uk wrote: Hi Rein, OK, thanks for letting me know. I will press on with setting the environment with a suitable parameter then. Kind regards, Ben On Jul 30, 4:21 pm, Rein Henrichs r...@reductivelabs.com wrote: Excerpts from Ben Tullis's message of Fri Jul 30 04:29:46 -0700 2010: Why doesn't the dashboard understand which environment applies to the host, and return that in the yaml output? Is this something that is better handled another way, or is it on the roadmap for the puppet dashboard? Hi Ben, Dashboard doesn't currently handle environments but it is on the roadmap. Rein Henrichshttp://puppetlabs.com -- 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] parameterized class, external nodes?
How do you (if you can) represent a parameterized class reference in an external node YAML description (exec terminus)? -Alan -- 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] Status of Docs: Style Guide
On Fri, Jul 30, 2010 at 10:04 AM, Ding Deng ding.d...@gmail.com wrote: Hi, Is Docs: Style Guide[1] officially recommended? Styles are inconsistent across the documentation site, so either the guide or other docs have to be fixed. I personally recommend the Style Guide since I wrote a decent chunk of that document, however there is no official style since puppet is an open source project with a large and active community. The guide is a result of years of experience maintaining puppet manifests from multiple members of the community, so that hopefully provides credence, but should not be considered the only right way to write puppet manifests. Style will likely never be 100% consistent across our documentation site since many people are involved in the process of documenting puppet and style differs among these participants. I think this is a feature and not a bug of the community. To provide a little background, my contributions to the style guide result from a preference for readability over write-ability (code's read far more often), consistency to minimize surprises for newcomer, line-oriented for commit diffs, and vertical-orientation for showing off to groups and quickly scanning/reading the manifests. It also looks nice on a projector/beamer. =) To me at least... -- Jeff McCune http://www.puppetlabs.com/ -- 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] parameterized class, external nodes?
On Fri, Jul 30, 2010 at 5:01 PM, Alan Sparks aspa...@doublesparks.net wrote: How do you (if you can) represent a parameterized class reference in an external node YAML description (exec terminus)? -Alan You can't at the moment, unfortunately. If you have any thoughts about what this API should look like, please describe some of your use cases or how you'd like this interface to operate. It's definitely something that I'm thinking about as well, I just don't think anyone has hammered out a design yet. -- Jeff McCune http://www.puppetlabs.com/ -- 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] IP based node sections instead of hostname based?
On Fri, Jul 30, 2010 at 10:35 AM, Yushu Yao yao.yu...@gmail.com wrote: Hi experts, Is there a way to specify in the nodes.pp sections with the ip address of the client? Currently I only saw instructions to use wildcarded hostnames. Thanks a lot You can configure [1] the master to use facter rather than the certificate common name for the node name. Note, however, this poses a risk since the fact list is presented by the agent and may be forged. If you configure the master to use facter then you would have to force the hostname to actually be the ipaddress by modifying the hostname fact itself. I in no way recommend this configuration and actively discourage it. It should do what you want though. node_name How the puppetmaster determines the client’s identity and sets the ‘hostname’, ‘fqdn’ and ‘domain’ facts for use in the manifest, in particular for determining which ‘node’ statement applies to the client. Possible values are ‘cert’ (use the subject’s CN in the client’s certificate) and ‘facter’ (use the hostname that the client reported in its facts) Default: cert [1] http://docs.puppetlabs.com/references/latest/configuration.html#node_name Hope this helps, -- Jeff McCune http://www.puppetlabs.com/ -- 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 Dashboard 1.0.3 released
And we're back fast and furious with another Dashboard release ... 1.0.3 ... this one so hot we skipped 1.0.2 altogether. The 1.0.3 release is another maintenance release that fixes bugs and issues with the 1.0.1 release. We're planning a 1.1 release in the near future that will add additional features (you can see the Roadmap at http://projects.puppetlabs.com/versions/show/48) http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.0.3.tgz New installation instructions for both 0.25.x and 2.6.x are also available in the README: http://github.com/reductivelabs/puppet-dashboard/blob/master/README.markdown You will need to also perform a database migration as part of the upgrade - Rails applications use database migration to add new tables and columns to the database. In the Puppet Dashboard directory, for example /usr/share/puppet-dashboard, do: $ sudo RAILS_ENV=production rake db:migrate You'll need to restart your webserver/server after this migration to ensure everything is up-to-date. Fixed in this release is: v1.0.3 -- * MIGRATION: Added cache with node's latest report and success status to improve performance. * Added rake tasks to dump and restore the database, see README for details. * Added database check to ensure it's running the latest schema. * Added support for accepting Puppet 2.6 reports, with limited support for displaying their contents. * Fixed and improved the README documentation with much more complete installation instructions. * Fixed node categorization, added new categories to Nodes sidebar and highlighting of errors. * Fixed node failures causing them to be listed as failed forever. * Fixed exceptions and messages shown if no items to display on groups, classes and reports pages. * Fixed styling of icons, warning sections, autocomplete, etc. * Fixed chart rendering issues, including it being too wide to fit on the screen. * Fixed unintended dependencies on external Puppet and JSON gems. * Fixed confusing headers for node listings shown as part of other pages. * Improved reports by displaying logs sorted by severity level and highlighting these accordingly. * Improved performance of many pages by eliminating and optimizing database queries. * Improved performance by concatenating JavaScript and CSS files together. * Removed unused checkboxes. * Fixed exceptions on the node reports page. * Fixed chart headers so they are shown only once. * Fixed chart formatting errors. * Fixed homepage warning message boxes to look like errors. * Fixed errors in documentation. * Added userful menu bar. * Added version number to menu bar and release notes page. * Added missing favicon.ico, the lack of which was filling logs with errors. * Removed unused Register and Log in links. New packages are also available. We'd welcome reviews and feedback into our packaging processes too. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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] Bootstrap
Do you want to run it off the server or install it on the client? What OS? On Jul 29, 2010, at 9:02 PM, parag(PK) wrote: Can it be possible to boot up a bare metal client ,by downloding the whole OS from server .when the client is powered on . -- 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: Newbie question - package installation
On Jul 30, 2010, at 2:53 AM, quicksilver03 wrote: Try adding an ensure = present to your File resource and see if it avoids downloading the RPM file over and over again. I'm almost sure the problem is he's putting the rpm in /tmp which is nuked by the OS on reboot. One of my solutions was just to put them in a folder that isn't nuked on reboot. On Jul 29, 10:40 pm, Rustler coltsixshoo...@gmail.com wrote: I am using version 2.6 and it would be nice if you could use a puppet url for the package source, but that does not appear to work (docs say it has to be a local file). My other choices seem to be an nfs mount, or a local repo server. Thanks On Jul 29, 11:23 am, Patrick Mohr kc7...@gmail.com wrote: On Jul 29, 2010, at 9:45 AM, Rustler wrote: This code is working - but due to the file declaration it keeps downloading the rpm even after the package gets installed. 1. How do I stop the rpm from downloading after the package is installed? Best method: *) If at all possible you should just replace this with a real package repository. Should also work: *) Put the rpm files on a webserver and download them as needed. I think rpm can take URLs instead of local paths. or *)Install from a network drive like nfs Not recommended: *) Just put the rpms into a folder you create. It will keep growing forever, but it probably won't ever get very big unless you release a lot of packages. Trust me on this, pushing out big files with puppet is probably a mistake. It will put a large load on the puppetmaster, and if you are using a version of puppet less than 2.6.0, the RAM requirements on the client and serve will be horrendous. -- 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] Parameterised Classes in 2.6
On Wed, Jul 28, 2010 at 4:13 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
Has anyone gotten parameterised classes to work in puppet 2.6 yet?
No luck for me... Seems to be totally broken but I haven't had a
chance to file a bug against it yet.
Doug
So, I've been playing with this myself.
Seems the second class you try and declare always throws an error,
which isn't so useful.
Consider this trivial manifest:
# Namespace example
class my::funclass($message1, $message2=I'm the default) {
notify { greeting:
message = message1=[${message1}] message2=[${message2}];
}
}
class { my::funclass:
message1 = Hello world,
message2 = I'm NOT the default;
}
puppet apply will return the following (good) output:
notice: message1=[Hello world] message2=[I'm NOT the default]
notice: /Stage[main]/My::Funclass/Notify[greeting]/message: defined
'message' as 'message1=[Hello world] message2=[I'm NOT the default]'
Now, if you add a second class and declare it, it won't work... I
just appended to the file:
class another($color) {
notify { color: message = Color is [${color}] }
}
class { another: color = green }
And I get this back:
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid
resource type class at
/Users/jeff/plabs/puppet-samples/manifests/paramclass_twoclass.pp:15
on node danu.local
Line 15 is where class { another: color = green } is declared.
If you swap the two classes, the error happens on the second declaration again.
So... congrats, you're right, parameterized classes appear to be
rather broken in 2.6.0 and 2.6.1rc1.
Doug, would you mind filing this issue along with the information I've
discovered? If so, I'll go ahead and do it for you.
Thanks,
--
Jeff McCune
http://www.puppetlabs.com/
--
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.
