[Puppet Users] Puppetdashboard 1.1.0 spec file
Hello,
Does anyone have a good spec file for puppet dashboard 1.1.0, as the
one supplied in the sourcecode is for 1.0.4
and tries to copy some directories, that don't exist anymore.
I did some remodelling in the file, so it creates a rpm now, but I'm
not sure whether my fix is the only change needed.
my change:
replace
for plugin in authlogic inherited_resources jrails object_daddy
resources_controller timeline_fu will_paginate; do
cp -p -r vendor/plugins/$plugin %{buildroot}%{_datadir}/%{name}/
vendor/plugins/$plugin
done
cp -p -r vendor/gems %{buildroot}%{_datadir}/%{name}/vendor
cp -p -r vendor/rails %{buildroot}%{_datadir}/%{name}/vendor
with
cp -p -r vendor/* %{buildroot}%{_datadir}/%{name}/vendor
as that seems to be the result of the whole exercise before
Reason for asking, is the fact, that I now have a rpm, but it doesn't
seem fully functional
The webpage works, but the interface with puppet doesn't.
The program external_node doesn't seem to function; I keep getting:
/usr/lib/ruby/1.8/net/http.rb:560:in `initialize': getaddrinfo: Name
or service not known (SocketError)
from /usr/lib/ruby/1.8/net/http.rb:560:in `open'
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/timeout.rb:48:in `timeout'
from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout'
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
from /usr/lib/ruby/1.8/net/http.rb:542:in `start'
from /usr/share/puppet-dashboard/bin/external_node:42
It could also mean, I misconfigured something, but so far I haven't
found out if or what I misconfigured.
grtz
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] PSON! Grrr!
On Sat, Apr 2, 2011 at 4:07 PM, Nigel Kersten ni...@puppetlabs.com wrote: On Sat, Apr 2, 2011 at 11:13 AM, Douglas Garstang doug.garst...@gmail.com wrote: Ah, Ok. I was using passenger once as well, but wasn't able to implement it a second time. To get passenger to work with puppet, you need to have exactly the right combination of packages/RPM's available. To know the exact version combination of these packages, you need to wave a dead chicken around a midnight, while dressed in a pink tu-tu. It's good to know it's not just me. It would be nice to see the puppet gods weigh on on this. They've been silent about it so far, and a few of us have been asking about it in the mailing list for quite some time now. googling for puppet passenger brings up this as the first hit: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger Each time I've taken someone through those instructions they've got a fully functional Passenger install, and I don't see any mention of dead chickens there[1] Nigel [1] - It is a wiki though, so I won't be surprised if dead chickens end up on it by the time you read this. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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. +1 for the wiki. Jeff McCune actually published the correct version combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I believe there's even a module in the Forge ( http://forge.puppetlabs.com/puppetlabs/passenger). -- 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-users@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] PSON! Grrr!
On Wed, Apr 6, 2011 at 3:22 PM, Gary Larizza ccsh...@gmail.com wrote: +1 for the wiki. Jeff McCune actually published the correct version combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I believe there's even a module in the Forge (http://forge.puppetlabs.com/puppetlabs/passenger). Agreed, I've never had any issues when rolling out Passenger and Puppet, it defacto for even our test rig. I don't understand why anyone would use webbrick. Take a look at the excellent wiki, or http://m.etrono.me (how I do mine) -- $ echo kpfmAdpoofdufevq/dp/vl | perl -pe 's/(.)/chr(ord($1)-1)/ge' -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Puppetdashboard 1.1.0 spec file
On 6 Apr 2011, at 5:42 AM, JohnW wrote: Does anyone have a good spec file for puppet dashboard 1.1.0, as the one supplied in the sourcecode is for 1.0.4 and tries to copy some directories, that don't exist anymore. On a related note, will there be an RPM for Dashboard 1.1.0 added to the Puppet Labs yum repository in the near future? We've been running the official 1.0.4 RPM quite successfully, and it would be great to get those new features through the same channel. -- Ian Ward Comfort icomf...@stanford.edu Systems Team Lead, Academic Computing Services, Stanford University -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] sshauthkeys wrapper
Hi,
I just wanted to let you know I wrote a little wrapper for Puppet's
ssh key deployment, so you are able to deploy ssh keys for multiple
users and can easily deal with groups. You can find the module at:
https://github.com/damokles/puppet-sshauthkeys
The core syntax is:
# just enroll one key for root user
sshauthkeys{ root: keys = 'ad...@domain.tld' }
# enroll multiple keys for a user
sshauthkeys{ user: keys = [ 'ad...@domain.tld','u...@domain.tld'] }
# if you want to reuse a team, make it an array for multiple defines
$team = [ 'ad...@domain.tld', 'us...@domain.tld' ]
sshauthkeys{ user2: keys = $team }
sshauthkeys{ user3: keys = $team }
Please note, I wrote this module after few days of using Puppet, so
excuse any non standard coding.
Any hints on improvments and pull requests are welcome.
Best,
ccm.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] Blank lines in conditional templates
I'm writing ldirectord.cf files via puppet and unfortunately ldirectord is sensitive to blank lines in the file. I have the following code in my .erb file virtual=%= vip %:%= port % % if weights.empty? then -%% real_servers.each do |real_server| -% real=%= real_server %:%= port % gate % end -%% else -%% real_servers.zip(weights).each do | real_server, weight| -% real=%= real_server %:%= port % gate %= weight % % end -%% end -% % if not checktype.empty? then -%checktype=%= checktype -%% end -% % if not service.empty? then -%service=%= service %% end - % % if not checkcommand.empty? then -%checkcommand=%= checkcommand %% end -% protocol=%= protocol % scheduler=%= scheduler % persistent=%= persistent % This all works fine. If (say) checktype == 'fred' then I get a line checktype=fred My problem is that is checktype == '', the checktype = line isnt' printed (correct) but I get a blank line instead. e.g. virtual=192.168.1.1:53 real=192.168.1.2:53 gate real=192.168.1.3:53 gate protocol=udp scheduler=rr persistent=300 How can I stop those blank lines from appearing? Thanks Arthur -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Serverside concatenation and conditional checks
Hi,
I'm trying to configure sysconfig file for a module.
within modules, i have mod/files/ directory which contains sysconfig-base
and sysconfig-nodename files.
From the module's init.pp, I then want to create a final file that consists
of the concatenation of sysconfig-base and sysconfig-nodename (if
sysconfig-nodename exists). This is what I have:
file { '/etc/sysconfig/application':
source = puppet:///modules/mod/sysconfig-base
other_flags = all other required file flags configured
}
I am not sure how to concatenate the sysconfig-$hostname file on the server
side. I have installed r.i. pienaars concat module, but that seems to work
client-side, and not sure how to configure a conditional statement for
server-side module file after this. 1 way of implementing that will work is
by creating 2 files on the client: sysconfig.base and sysconfig.$hostname,
and THEN using the client-side concat module, but I don't think this is a
good way of implementing this.
alternatively: create a concat.rb ruby file (a new area of knowledge for
me) to define a server-side concat of the files from the module dir, and
then define the file above using content instead of source...
Any of these methods on the right puppetized way of doing things?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] SSL issues: Separate CA, multiple load balanced masters
Hi, I've been at it for about 4 days now and I just can't figure it out. I'm getting the following error when running puppet agent on my masters: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed At startup, I'm running ntpdate (I've read in a lot of places that this error occurs when date between servers is different, it's not). My setup is: CA: puppet.mydomain.com with config: certdnsnames = puppet.mydomain.com certname = puppet.mydomain.com server = puppet.mydomain.com Masters behind an Amazon ELB, with config: certdnsnames = master.mydomain.com ca_server = puppet.mydomain.com server = master.puppet.3ev.info ca = false Does anyone have any idea why this might happen? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Using puppet/augeas to manage config entry AND matching comment
Seems like Augeas doesn't have a really good concept of conf file
entry AND a comment that goes with it. I can 'ins' a comment before
the configuration item, but every time augeas runs, it will add
another.
I can re-'set' the comment before the existing configuration item, but
that won't work if the comment doesn't already exist. Kind of a
chicken and egg.
This is what I have, and it doesn't work. Probably the match fails on
the insert because the node doesn't exist at all -- too bad there
isn't an unless..
define sysctl::set($value, $comment=undef) {
include sysctl
$key = $name
if $comment {
$comment_use = $comment
} else {
$comment_use = Managed by puppet: $key = $value
}
$sysctl = '/files/etc/sysctl.conf'
augeas { sysctl::set $key = $value:
changes = [ set $sysctl/$key '$value, ],
notify = Service['sysctl'],
}
augeas { sysctl::set insert comment for $key = $value:
changes = [ ins #comment before $sysctl/$key ],
onlyif = match
$sysctl/#comment[following-sibling::*[1][self::$key]] size == 0,
require = Augeas[sysctl::set $key = $value],
}
augeas { sysctl::set change comment for $key = $value:
changes = [ set
$sysctl/#comment[following-sibling::*[1][self::$key]] '$comment_use'
],
onlyif = match
$sysctl/#comment[following-sibling::*[1][self::$key]] size 0,
require = Augeas[sysctl::set $key = $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-users@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: Using puppet/augeas to manage config entry AND matching comment
On Wed, Apr 6, 2011 at 11:14 AM, Rich Rauenzahn rraue...@gmail.com wrote:
Seems like Augeas doesn't have a really good concept of conf file
entry AND a comment that goes with it. I can 'ins' a comment before
the configuration item, but every time augeas runs, it will add
another.
I can re-'set' the comment before the existing configuration item, but
that won't work if the comment doesn't already exist. Kind of a
chicken and egg.
This is a better approximation -- the only bug in this now (I think)
is that if the comment is cleared, but still exists, it will add
another one. I could add an additional remove of the node if the size
is 0, before I insert, but I'm already invoking augeas more than I
want for one change.
define sysctl::set($value, $comment=undef) {
include sysctl
$key = $name
if $comment {
$comment_use = $comment
} else {
$comment_use = Managed by puppet: $key = $value
}
$sysctl = '/files/etc/sysctl.conf'
augeas { sysctl::set $key = $value:
changes = [ set $sysctl/$key '$value,
],
notify = Service['sysctl'],
}
augeas { sysctl::set insert comment for $key = $value:
changes = [ ins #comment before $sysctl/$key,
set
$sysctl/#comment[following-sibling::*[1][self::$key]] '$comment_use',
],
onlyif = match
$sysctl/#comment[following-sibling::*[1][self::$key]] size == 0,
require = Augeas[sysctl::set $key = $value],
}
augeas { sysctl::set change comment for $key = $value:
changes = [ set
$sysctl/#comment[following-sibling::*[1][self::$key]] '$comment_use'
],
onlyif = match
$sysctl/#comment[following-sibling::*[1][self::$key]] size 0,
require = Augeas[sysctl::set $key = $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-users@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] Puppetdashboard 1.1.0 spec file
Ian Ward Comfort wrote: On 6 Apr 2011, at 5:42 AM, JohnW wrote: Does anyone have a good spec file for puppet dashboard 1.1.0, as the one supplied in the sourcecode is for 1.0.4 and tries to copy some directories, that don't exist anymore. On a related note, will there be an RPM for Dashboard 1.1.0 added to the Puppet Labs yum repository in the near future? We've been running the official 1.0.4 RPM quite successfully, and it would be great to get those new features through the same channel. It's on my list of things to do. I need to make some modifications to the DEB and RPM specs that I haven't had time to do yet. James -- James Turnbull Puppet Labs 1-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-users@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] Deploying puppet with puppet, best practices
Our shop is newly adopting puppet. Our number of nodes is growing and my installation method is thus far manual and tedious. This will change when/if we migrate to Puppet Enterprise. My question is what's a best practice for managing puppet installations on client nodes? Is it possible to separate out the client portion of the install from the server or is that now fully integrated? The puppet.conf file could be templated for distribution. Thanks for any tips, etc. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Deploying puppet with puppet, best practices
On Wed, Apr 6, 2011 at 9:54 PM, Forrie for...@gmail.com wrote: Our shop is newly adopting puppet. Our number of nodes is growing and my installation method is thus far manual and tedious. This will change when/if we migrate to Puppet Enterprise. My question is what's a best practice for managing puppet installations on client nodes? Is it possible to separate out the client portion of the install from the server or is that now fully integrated? The puppet.conf file could be templated for distribution. Thanks for any tips, etc. -- You might consider using Foreman [1] for this task. Ohad [1] - http://theforeman.org You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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-users@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: Node classifier not loading any defined classes
Well I kind of figured it out (though not how I like). I had to move these lines node_terminus = exec external_nodes = /.foo/bin/puppet_node_classifier.sh out of my [development] area into my [main] in puppet.conf. Once I did that I was able to use the external classifier (though I only wanted it in development). -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] PSON! Grrr!
On Wed, Apr 6, 2011 at 8:54 AM, joel.merr...@gmail.com joel.merr...@gmail.com wrote: On Wed, Apr 6, 2011 at 3:22 PM, Gary Larizza ccsh...@gmail.com wrote: +1 for the wiki. Jeff McCune actually published the correct version combination, which is usually Rack version 1.0.1 and Passenger 2.2.11. I believe there's even a module in the Forge (http://forge.puppetlabs.com/puppetlabs/passenger). Agreed, I've never had any issues when rolling out Passenger and Puppet, it defacto for even our test rig. I don't understand why anyone would use webbrick. Take a look at the excellent wiki, or http://m.etrono.me (how I do mine) Because the correct combination of packages isn't always available as RPM's. This is a production environment. We don't install anything from gem's. 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-users@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] Deploying puppet with puppet, best practices
We use cobbler for client installs and that works well for our centos servers, foreman can handle more distributions. As for installing the client software itself, we use a custom RPM package that is installed at build time or anytime after. We are still building out our manifests so we are tackling one service at a time on each node type. Cheers, On 07/04/2011, at 5:11, Ohad Levy ohadl...@gmail.com wrote: On Wed, Apr 6, 2011 at 9:54 PM, Forrie for...@gmail.com wrote: Our shop is newly adopting puppet. Our number of nodes is growing and my installation method is thus far manual and tedious. This will change when/if we migrate to Puppet Enterprise. My question is what's a best practice for managing puppet installations on client nodes? Is it possible to separate out the client portion of the install from the server or is that now fully integrated? The puppet.conf file could be templated for distribution. Thanks for any tips, etc. -- You might consider using Foreman [1] for this task. Ohad [1] - http://theforeman.org You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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-users@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-users@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: Should @user with managehome also track the actual home directory?
Sounds like a bug to me. A user with managehome = true but no home directory should not be in sync. You may want to report this (or vote on the bug if it's been reported already). I wasn't able to find a bug similar to this based on the search criteria, so I filed bug #7002. In a virtual user configuration, what's the best way to ensure that the home directory is also present, in addition to the /etc/passwd entries (or, dependent on each other)? I don't understand what the user's being virtual has to do with this, please elaborate. What I mean is provided that managehome doesn't actually manage the directory after creation, what's a clever way to tie in this (somewhat obvious) dependency into the user creation/tracking. Perhaps with some wrapper around the call. A simple workaround is to wrap the user type in your own define. This define will manage the home dir as a file type resource and you don't use managehome at all. I think it's quite common to do that, since people probably want to ensure the existence of .ssh/authorized_keys or similar things as well. Thanks, yes I think I'm going to try doing this. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Kick with non-production environment?
Hello, I would like to use puppet kick with an environment other than production. I am using LDAP to store my nodes, and I expected that when I set the environment attribute to my dev environment that kicks would use that environment, but it appears that they do not. The steps I took: * Changed LDAP environment attribute on a test node to dev * Added [dev] section with modulepath to the master's puppet.conf When I stop the puppet agent daemon on the test node and run puppet agent --test --environment dev I see the correct resolution. When I changed the LDAP environment attribute, I saw that /var/lib/puppet/ yaml/node/test-node.yaml was updated to show environment: id003 dev. But when I run puppet kick --host test-node from the master, the log entries in /var/log/puppet/masterhttp.log show that it is resolving the catalog for the production environment, not the one I've specified in LDAP, and the node I kicked doesn't have its entitlements from the dev environment. Trying to use the -- environment flag on the kick command line does not seem to have any effect. Does puppet not respect the environment setting in LDAP for kicks, or did I miss a step to configure using environments? How else can I trigger a run from the master *and* use an environment other than production (since it looks like you can't do this through the master's REST API either)? I am running puppet version 2.6.4 (but willing to consider upgrading if this has been remedied in later versions), my puppetmaster is redhat 5.5 and puppet agent is ubuntu 10.10. 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-users@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] Can puppet client make immediate pull after a file's content change by user?
Hi all Firstly, I am new in configuration management and all I know about watching files is that client checks a file's check sum every t hour and if a change has occurred then it gets the file from the server. I wonder that if a user changes a file, does the puppet client wait end of the time (t) or is there way to say client if a change occurs in a specific file then make an immediate pull? I mean, I don't want to wait until the time is up. Is there a way to make this in puppet? Thanks in advance. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] erb including other erbs
In the puppet documentation, it is stated:
You can also use templates to fill in variables in addition to
filling out file contents.
template('/path/to/template1','/path/to/template2')
My question: is this done in the ERB file, or in the puppet manifest?
If done in the ERB file, I assume it also has to be within % % tags,
but unlike all the other examples in the documentation it is not
presented this way.
The /path/to/ - is there some way to properly do this, or do I need to
do '/etc/puppet/files/templates/./foo.erb' ?
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-users@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] erb including other erbs
On Wed, Apr 6, 2011 at 2:54 PM, draeath drae...@gmail.com wrote:
In the puppet documentation, it is stated:
You can also use templates to fill in variables in addition to
filling out file contents.
template('/path/to/template1','/path/to/template2')
I don't have the specific document, so not sure if I'm missing any
context, I presume this simply means:
$foo = template('/path/to/foo.erb')
file { '/etc/a':
content = template('/path/to/foo.erb')
}
My question: is this done in the ERB file, or in the puppet manifest?
If done in the ERB file, I assume it also has to be within % % tags,
but unlike all the other examples in the documentation it is not
presented this way.
The /path/to/ - is there some way to properly do this, or do I need to
do '/etc/puppet/files/templates/./foo.erb' ?
Please follow the modules convention:
http://docs.puppetlabs.com/guides/modules.html
For portability, place the file in $module_name/templates/ directory
and use the module name:
$foo = template(${module_name}/foo.erb)
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] Can puppet client make immediate pull after a file's content change by user?
On Wed, Apr 6, 2011 at 2:50 PM, John Chris Richards john.chris.richa...@gmail.com wrote: Hi all Firstly, I am new in configuration management and all I know about watching files is that client checks a file's check sum every t hour and if a change has occurred then it gets the file from the server. I wonder that if a user changes a file, does the puppet client wait end of the time (t) or is there way to say client if a change occurs in a specific file then make an immediate pull? I mean, I don't want to wait until the time is up. Is there a way to make this in puppet? Puppet agent runs periodically to enforce the catalog, it can replace the file if it detects any changes, but it doesn't monitor the file to trigger runs. I suppose you can run puppet continuously (not recommended), but perhaps if you give some insight on what you are trying to accomplish would give us a better idea how to achieve it with puppet. Are you trying to trigger a puppet run when a particular file changes? Are you trying to monitor several files? Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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: erb including other erbs
That didn't exactly help me out.
I would like to include one .erb from inside another .erb (vs
concatenating .erbs together, which is what I'm gathering is what
happens when done in the manifest).
The file path I gave was an example, as the one given is written in a
way that suggests absolute system paths.
This is the entry in question:
http://docs.puppetlabs.com/guides/templating.html#combining-templates
On Apr 6, 6:48 pm, Nan Liu n...@puppetlabs.com wrote:
On Wed, Apr 6, 2011 at 2:54 PM, draeath drae...@gmail.com wrote:
In the puppet documentation, it is stated:
You can also use templates to fill in variables in addition to
filling out file contents.
template('/path/to/template1','/path/to/template2')
I don't have the specific document, so not sure if I'm missing any
context, I presume this simply means:
$foo = template('/path/to/foo.erb')
file { '/etc/a':
content = template('/path/to/foo.erb')
}
My question: is this done in the ERB file, or in the puppet manifest?
If done in the ERB file, I assume it also has to be within % % tags,
but unlike all the other examples in the documentation it is not
presented this way.
The /path/to/ - is there some way to properly do this, or do I need to
do '/etc/puppet/files/templates/./foo.erb' ?
Please follow the modules
convention:http://docs.puppetlabs.com/guides/modules.html
For portability, place the file in $module_name/templates/ directory
and use the module name:
$foo = template(${module_name}/foo.erb)
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] Kick with non-production environment?
On Wed, Apr 6, 2011 at 2:24 PM, h.whisenhunt h.whisenh...@gmail.com wrote: Hello, I would like to use puppet kick with an environment other than production. I am using LDAP to store my nodes, and I expected that when I set the environment attribute to my dev environment that kicks would use that environment, but it appears that they do not. The steps I took: * Changed LDAP environment attribute on a test node to dev * Added [dev] section with modulepath to the master's puppet.conf When I stop the puppet agent daemon on the test node and run puppet agent --test --environment dev I see the correct resolution. When I changed the LDAP environment attribute, I saw that /var/lib/puppet/ yaml/node/test-node.yaml was updated to show environment: id003 dev. But when I run puppet kick --host test-node from the master, the log entries in /var/log/puppet/masterhttp.log show that it is resolving the catalog for the production environment, not the one I've specified in LDAP, and the node I kicked doesn't have its entitlements from the dev environment. Trying to use the -- environment flag on the kick command line does not seem to have any effect. Does puppet not respect the environment setting in LDAP for kicks, or did I miss a step to configure using environments? How else can I trigger a run from the master *and* use an environment other than production (since it looks like you can't do this through the master's REST API either)? The reason the client is not following the ENC environment is due to: http://projects.puppetlabs.com/issues/3910 A quick look at the code, it appears kick doesn't support environment option. I don't know if Puppet::Run supports the environment option (which would make this a fairly straightforward patch). Please file a feature request. Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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: Facter 1.5.9rc5
Facter 1.5.9rc5 is a maintenance release containing fixes and updates. This release candidate addresses an issue with EC2 facts. This ensures that ARP facts are only returned for EC2 hosts. (#6976) As always, please let us know if you run into any problems with any of the release candidates. This release is available for download at: http://puppetlabs.com/downloads/facter/facter-1.5.9rc5.tar.gz See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.5.9rc5: http://projects.puppetlabs.com/projects/facter/ CHANGELOG: 1.5.9rc5 acf0bb2 Ensures that ARP facts are returned only on EC2 hosts -- Jacob Helwig signature.asc Description: Digital signature
[Puppet Users] Ubuntu Execution of '/etc/puppet/etckeeper-commit-pre' returned 1:
Hi I have just put puppet onto a new Ubuntu install and it ran a couple of times but now I get Execution of '/etc/puppet/etckeeper-commit-pre' returned 1: whenever puppetd runs. Grepping on etckeeper-commit turns up lots of posts to ubuntu and debian forums about changes made in February. Does anyone know what the story is? I've ended up with a screwed pam configuration on the box and now can't change it because puppetd fails. Russell -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] SSL issues: Separate CA, multiple load balanced masters
On 7 April 2011 04:02, Andrei Serdeliuc and...@serdeliuc.ro wrote: Hi, I've been at it for about 4 days now and I just can't figure it out. I'm getting the following error when running puppet agent on my masters: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed It took me a bit longer than 4 days, but using http://bodepd.com/wordpress/?p=7 as a guide, I did this: 1. CA server is a puppet server with the exact same configuration on all puppet servers. ca_server is puppet-ca.example.com 2. Same certname everywhere: puppet.example.com. Manage the certs in puppet: $etc/ssl/ca/signed/puppet.example.com.pem $etc/ssl/certs/puppet.example.com.pem $etc/ssl/private_keys/puppet.example.com.pem $etc/ssl/public_keys/puppet.example.com.pem 3. Same certdnsname everywhere with every possible combination of name the client contacts the puppet master with. I have heard (but not tried) you can use wild cards. This includes puppet-ca.example.com, puppet.example.com, ... 4. I keep all $etc/ssl/ca files managed in puppet too Note that I use CNAMEs everywhere so I don't have to change certificates if I replace a machine. Adding machines will require a new cert Keep playing. Once it works, it works well. I can deploy a new puppet server in the blink of an eye! John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Can puppet client make immediate pull after a file's content change by user?
You can probably use inotify it something similar for this functionality On Apr 6, 2011 2:52 PM, John Chris Richards john.chris.richa...@gmail.com wrote: Hi all Firstly, I am new in configuration management and all I know about watching files is that client checks a file's check sum every t hour and if a change has occurred then it gets the file from the server. I wonder that if a user changes a file, does the puppet client wait end of the time (t) or is there way to say client if a change occurs in a specific file then make an immediate pull? I mean, I don't want to wait until the time is up. Is there a way to make this in puppet? Thanks in advance. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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-users@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] $environment in File source not working
am I doing something wrong? this seems to never find my .$env file: source = [ puppet:///modules/gu_puppet/puppet.conf.$fqdn, puppet:///modules/gu_puppet/puppet.conf.$environment, puppet:///modules/gu_puppet/puppet.conf.$operatingsystem, puppet:///modules/gu_puppet/puppet.conf ] It does find the $fqdn version if I create one, but not the $environment. and skips to the last version. am using 2.6.3 master and 2.6.6 client. Thanks, Mohamed. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] $environment in File source not working
On Wed, Apr 6, 2011 at 6:38 PM, Mohamed Lrhazi lrh...@gmail.com wrote: am I doing something wrong? this seems to never find my .$env file: source = [ puppet:///modules/gu_puppet/puppet.conf.$fqdn, puppet:///modules/gu_puppet/puppet.conf.$environment, puppet:///modules/gu_puppet/puppet.conf.$operatingsystem, puppet:///modules/gu_puppet/puppet.conf ] It does find the $fqdn version if I create one, but not the $environment. and skips to the last version. am using 2.6.3 master and 2.6.6 client. I'd add a notice and/or notify for $environment to check it's the value you're expecting it to be. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] ANNOUNCE: Puppet 2.6.7 final!
Is it easy enough to build the gem version out of the tarball? I dont see the gem in: http://projects.puppetlabs.com/projects/puppet/files Thanks. On Thu, Mar 24, 2011 at 6:47 PM, Jacob Helwig ja...@puppetlabs.com wrote: This release addresses issues with the Puppet 2.6.x series and adds the Inventory Service. Inventory Service: The inventory service is a way to track facts for all nodes. Preliminary documentation can be found here[1], which will be finalized by the time 2.6.7 is released. [1] https://github.com/puppetlabs/puppet-docs/blob/master/source/guides/inventory_service.markdown Bug #5073: Plugin sync works when using tags This fixes a regression from 0.25.x Bug #4922: Now 404s just cause a normal failure without affecting the file Bug #5428: Upgrading from 0.25.x caused problems with the data format that storeconfigs used, and previously you had to delete your old storeconfigs data to work with 2.6.x. 2.6.7 can now work with the old storeconfigs data. You can find the full release notes for Puppet at: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.7.tar.gz 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, using an affected version of 2.6.7: http://projects.puppetlabs.com/projects/puppet/ CHANGELOG: 2.6.7 = 17f673d Updated CHANGELOG for 2.6.7rc1 852fb97 (#5073) Download plugins even if you're filtering on tags 4f34dbf Fix #5610: Prevent unnecessary RAL lookups 9781032 Revert Merge branch 'ticket/2.6.x/5605' of git://github.com/stschulte/puppet into 2.6.next 25926d1 (#6723) Fix withenv environment restoration bug 093f162 (#6689) Remove extraneous include of Puppet::Util in InventoryActiveRecord 4c19299 Remove extra trailing whitespace from lib/puppet/resource.rb ff9e242 (#5428) More fully stub Puppet::Resource::Reference for use with storedconfigs 0262633 (#6707) Fix typo in rest_authconfig.rb 8858e40 (#6689) Make inventory_active_record terminus search quickly 285c4cc (#5392) Give a better error when realizing a non-existant resource cd5deda (#2645) Adding a less-stubby test to verify the system attribute's behavior 531e258 maint: Remove serialization of InventoryFact values 3489412 maint: Rename InventoryHost to InventoryNode 4bd5493 Fixed #2645 - Added support for creating system users a3f2357 maint: Remove spec run noise 7764412 maint:Refactor of mount provider integration tests 880d0c6 (#6338) Support searching on metadata in InventoryActiveRecord terminus f836366 (#6338) Implement search for InventoryActiveRecord facts terminus 8ce30c8 (#6338) Add an InventoryActiveRecord terminus for Facts 1ef83cb Added integration tests for the mount provider 64440e5 (#6513) Propagate the environment when doing variable lookup in settings 92dffb2 (#6513) Adjust P::U::Settings test name to reflect what it tests 5ef1031 (#6632) Adding a new mount no longer causes error with umount bd5517d Adjust Darwin mount provider tests to pass on Linux 9d2fceb Maint: Begin adding integration tests for the mount provider 23d1c03 Maint: Added the ability to replace the behavior of Puppet::Util.execute with an arbitrary code block for ease in spec testing. 455a891 (#5794) create reports directory when creating host specific directory 1b1e803 (5724) Prep for deprecation of DESTDIR f4a0af1 Refactoring duplicate code and logic in prep for DESTDIR deprecation. 7a00d6b (#6606) Inline docs: Document all autorequire relationships e3aec14 (#5148) Fix failing spec due to timezone 8bd80a9 (#5148) Add support for PSON to facts c3baa28 (#6338) Remove inventory indirection, and move to facts indirection 6c53eb3 (#6445) Fix inline docs: puppet agent does not accept --mkusers 4e29f43 (#6541) maint: whitespace cleanup on the file integration spec b907ba3 (#6541) Fix content with checksum truncation bug 422399b (#5466) Write specs for output of puppet resource 8cc390c (#5466) Monkey patch Symbol so that you can sort them 24eacb7 (#5466) Fixed puppet resource bug with trailing , 743e039 (#4922) Don't truncate remotely-sourced files on 404 bb69011 (#6338) Remove unused version control tags e2a5085 Maint: Align tabs in a code block in the Augeas type. 65a5496 (#6509) Inline docs: Fix erroneous code block in directoryservice provider for computer type ea9f1f0 Maint: Rewrite comments about symlinks to reflect best practice. 94f8ead (#6509) Inline docs: Fix broken lists in Launchd provider. c80a77d (#6509) Inline docs: Fix broken code blocks in zpool type 27863c3 (#6509) Inline docs: Fix code blocks in service type. f4034f7 (#6509) Inline docs: fix broken code blocks in schedule.rb. 6f6c4b5 (#6509) Inline docs: Fix broken code block in file type (content attribute) a949a83 Revert
[Puppet Users] Mutliple custom facts not showing in facter
Hi,
I've noticed that defining multiple facts in one file is possible, and
puppet can make use of them correctly, but when trying to call with facter
--puppet they are not shown, do I need something special to make them work
as any other single custom fact?
Master is running 2.6.7
This is a custom fact with two facts in it:
[modules/foobar/lib/facter/foobar.rb ]
require 'facter'
Facter.add(foo) do
setcode do
%x{/bin/date +%s}.chomp
end
end
Facter.add(bar) do
setcode do
%x{/bin/date +%s}.chomp
end
end
I used a simple notify in the node like this: notify{ custom_fact:
message = foo:$foo bar:$bar}
Tested with Puppet Agent 2.6.2 and 2.6.7
Pulling the fact and makes use of it:
# puppet agent -t --environment=test --pluginsync
info: Retrieving plugin
notice: /File[/var/lib/puppet/lib/facter/foobar.rb]/ensure: defined content
as '{md5}c28d8a783d44b9c15b7e61a6d90cf0e3'
notice: /File[/var/lib/puppet/lib/facter/utime.rb]/ensure: removed
info: Loading downloaded plugin /var/lib/puppet/lib/facter/foobar.rb
info: Loading facts in foobar
info: Loading facts in foobar
info: Caching catalog for squeeze.tonyskapunk.net
info: Applying configuration version '1302146930'
notice: foo:1302147318 bar:1302147318
notice: /Stage[main]//Node[squeeze.tonyskapunk.net]/Notify[custom_fact]/message:
defined 'message' as 'foo:1302147318 bar:1302147318'
notice: Finished catalog run in 0.07 seconds
But not able to call them with facter:
root@squeeze:~# facter --puppet foo
root@squeeze:~# facter --puppet bar
root@squeeze:~#
Tested with Facter 1.5.7 and 1.5.9
Thanks.
--
Tony
http://blog.tonyskapunk.net
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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] ANNOUNCE: Puppet 2.6.7 final!
Yeah, unpack tar.gz file and gem build file.gemspec On Wed, Apr 6, 2011 at 8:10 PM, Mohamed Lrhazi lrh...@gmail.com wrote: Is it easy enough to build the gem version out of the tarball? I dont see the gem in: http://projects.puppetlabs.com/projects/puppet/files Thanks. On Thu, Mar 24, 2011 at 6:47 PM, Jacob Helwig ja...@puppetlabs.com wrote: This release addresses issues with the Puppet 2.6.x series and adds the Inventory Service. Inventory Service: The inventory service is a way to track facts for all nodes. Preliminary documentation can be found here[1], which will be finalized by the time 2.6.7 is released. [1] https://github.com/puppetlabs/puppet-docs/blob/master/source/guides/inventory_service.markdown Bug #5073: Plugin sync works when using tags This fixes a regression from 0.25.x Bug #4922: Now 404s just cause a normal failure without affecting the file Bug #5428: Upgrading from 0.25.x caused problems with the data format that storeconfigs used, and previously you had to delete your old storeconfigs data to work with 2.6.x. 2.6.7 can now work with the old storeconfigs data. You can find the full release notes for Puppet at: https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes This release is available for download at: http://puppetlabs.com/downloads/puppet/puppet-2.6.7.tar.gz 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, using an affected version of 2.6.7: http://projects.puppetlabs.com/projects/puppet/ CHANGELOG: 2.6.7 = 17f673d Updated CHANGELOG for 2.6.7rc1 852fb97 (#5073) Download plugins even if you're filtering on tags 4f34dbf Fix #5610: Prevent unnecessary RAL lookups 9781032 Revert Merge branch 'ticket/2.6.x/5605' of git:// github.com/stschulte/puppet into 2.6.next 25926d1 (#6723) Fix withenv environment restoration bug 093f162 (#6689) Remove extraneous include of Puppet::Util in InventoryActiveRecord 4c19299 Remove extra trailing whitespace from lib/puppet/resource.rb ff9e242 (#5428) More fully stub Puppet::Resource::Reference for use with storedconfigs 0262633 (#6707) Fix typo in rest_authconfig.rb 8858e40 (#6689) Make inventory_active_record terminus search quickly 285c4cc (#5392) Give a better error when realizing a non-existant resource cd5deda (#2645) Adding a less-stubby test to verify the system attribute's behavior 531e258 maint: Remove serialization of InventoryFact values 3489412 maint: Rename InventoryHost to InventoryNode 4bd5493 Fixed #2645 - Added support for creating system users a3f2357 maint: Remove spec run noise 7764412 maint:Refactor of mount provider integration tests 880d0c6 (#6338) Support searching on metadata in InventoryActiveRecord terminus f836366 (#6338) Implement search for InventoryActiveRecord facts terminus 8ce30c8 (#6338) Add an InventoryActiveRecord terminus for Facts 1ef83cb Added integration tests for the mount provider 64440e5 (#6513) Propagate the environment when doing variable lookup in settings 92dffb2 (#6513) Adjust P::U::Settings test name to reflect what it tests 5ef1031 (#6632) Adding a new mount no longer causes error with umount bd5517d Adjust Darwin mount provider tests to pass on Linux 9d2fceb Maint: Begin adding integration tests for the mount provider 23d1c03 Maint: Added the ability to replace the behavior of Puppet::Util.execute with an arbitrary code block for ease in spec testing. 455a891 (#5794) create reports directory when creating host specific directory 1b1e803 (5724) Prep for deprecation of DESTDIR f4a0af1 Refactoring duplicate code and logic in prep for DESTDIR deprecation. 7a00d6b (#6606) Inline docs: Document all autorequire relationships e3aec14 (#5148) Fix failing spec due to timezone 8bd80a9 (#5148) Add support for PSON to facts c3baa28 (#6338) Remove inventory indirection, and move to facts indirection 6c53eb3 (#6445) Fix inline docs: puppet agent does not accept --mkusers 4e29f43 (#6541) maint: whitespace cleanup on the file integration spec b907ba3 (#6541) Fix content with checksum truncation bug 422399b (#5466) Write specs for output of puppet resource 8cc390c (#5466) Monkey patch Symbol so that you can sort them 24eacb7 (#5466) Fixed puppet resource bug with trailing , 743e039 (#4922) Don't truncate remotely-sourced files on 404 bb69011 (#6338) Remove unused version control tags e2a5085 Maint: Align tabs in a code block in the Augeas type. 65a5496 (#6509) Inline docs: Fix erroneous code block in directoryservice provider for computer type ea9f1f0 Maint: Rewrite comments about symlinks to reflect best practice. 94f8ead (#6509) Inline docs: Fix broken lists in Launchd provider. c80a77d (#6509) Inline docs: Fix broken code blocks in zpool type 27863c3 (#6509)
Re: [Puppet Users] erb including other erbs
On Wed, Apr 06, 2011 at 02:54:43PM -0700, draeath wrote:
You can also use templates to fill in variables in addition to
filling out file contents.
template('/path/to/template1','/path/to/template2')
This is for in the manifest, so combing them.
[ben@Paresthesia:~]% cat erb.pp
file{ '/Users/ben/test':
content = template('/Users/ben/one.erb','/Users/ben/two.erb')
}
[ben@Paresthesia:~]% cat one.erb
I am the %= fqdn %
[ben@Paresthesia:~]% cat two.erb
I am in the other file and am %= virtual %
[ben@Paresthesia:~]% puppet apply erb.pp
notice: Finished catalog run in 0.02 seconds
[ben@Paresthesia:~]% cat test
I am the Paresthesia.local
I am in the other file and am physical
My question: is this done in the ERB file, or in the puppet manifest?
It's in the manifest.
If done in the ERB file, I assume it also has to be within % % tags,
but unlike all the other examples in the documentation it is not
presented this way.
I don't think you can embed ERB inside more ERB. I tried a couple of
attempts and Ruby really wasn't keen on the idea.
The /path/to/ - is there some way to properly do this, or do I need to
do '/etc/puppet/files/templates/./foo.erb' ?
$mypath = '/etc/puppet/files/templates/./'
file{ '/tmp/foo':
content = template( $mypath/foo.erb )
}
Or if using modules, you can just specify the module name and it will use
the template named in there.
content = template( 'mymodule/mytemplate.erb' )
From mymodule/templates/mytemplate.erb
--
Ben Hughes || 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-users@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] ANNOUNCE: Puppet 2.6.7 final!
On Wed, Apr 6, 2011 at 8:10 PM, Mohamed Lrhazi lrh...@gmail.com wrote: Is it easy enough to build the gem version out of the tarball? I dont see the gem in: http://projects.puppetlabs.com/projects/puppet/files I just uploaded them. We haven't quite automated this step yet, but the historical download locations are always updated first. http://www.puppetlabs.com/downloads/gems http://www.puppetlabs.com/downloads/puppet http://www.puppetlabs.com/downloads/facter -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] $environment in File source not working
On Wed, Apr 6, 2011 at 9:18 PM, Nigel Kersten ni...@puppetlabs.com wrote: On Wed, Apr 6, 2011 at 6:38 PM, Mohamed Lrhazi lrh...@gmail.com wrote: am I doing something wrong? this seems to never find my .$env file: source = [ puppet:///modules/gu_puppet/puppet.conf.$fqdn, puppet:///modules/gu_puppet/puppet.conf.$environment, puppet:///modules/gu_puppet/puppet.conf.$operatingsystem, puppet:///modules/gu_puppet/puppet.conf ] It does find the $fqdn version if I create one, but not the $environment. and skips to the last version. am using 2.6.3 master and 2.6.6 client. Not completely related, but I was under the impression that clients shouldn't be higher than the masters, did that change on newer versions? I'd add a notice and/or notify for $environment to check it's the value you're expecting it to be. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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 http://blog.tonyskapunk.net -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] ANNOUNCE: Puppet 2.6.7 final!
On Wed, Apr 6, 2011 at 8:48 PM, Nigel Kersten ni...@puppetlabs.com wrote: On Wed, Apr 6, 2011 at 8:10 PM, Mohamed Lrhazi lrh...@gmail.com wrote: Is it easy enough to build the gem version out of the tarball? I dont see the gem in: http://projects.puppetlabs.com/projects/puppet/files I just uploaded them. We haven't quite automated this step yet, but the historical download locations are always updated first. http://www.puppetlabs.com/downloads/gems http://www.puppetlabs.com/downloads/puppet http://www.puppetlabs.com/downloads/facter Oh, and we update gemcutter, so you should be able to update using gem on the command line pretty quickly after release. http://rubygems.org/gems/puppet -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] $environment in File source not working
On Wed, Apr 6, 2011 at 8:51 PM, Tony G. tony...@gmail.com wrote: Not completely related, but I was under the impression that clients shouldn't be higher than the masters, did that change on newer versions? No, it hasn't changed, it's not supported, even though it may work fine. Always upgrade the master first. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@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] Blank lines in conditional templates
On Wed, Apr 06, 2011 at 10:22:19AM -0700, Arthur Clune wrote: I'm writing ldirectord.cf files via puppet and unfortunately ldirectord is sensitive to blank lines in the file. I have the following code in my .erb file I tried to recreate this, but your mailer has munged all the lines to fit in 80 columns, so I can't tell where all the breaks should be, so can't test it. Could you pastie or similar it? -- Ben Hughes || 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-users@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.
