[Puppet Users] facter values in upper case
Hi,
facter variables typically have values in lower case. We are looking
into moving to puppet for our config administration and are currently
using a system where we do file name matching dependent on specific
suffixes - for example a file named *--LAPTOP will only be deployed
on machines tagged as laptops.
I would like to keep this naming convention and observed that facter
has a type variable that on laptops will contain the value laptop
- but of course i want it in upper case for, in my opinion, better
clarity. Is there some smart way of doing this?
I guess i could do something like
if $type == laptop {
$type = LAPTOP
}
but im looking to see if there is any other smarter ways of doing
this.
Thanks,
//Adam Winberg
--
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] facter values in upper case
you can use inline_template to sanitize your values.. e.g.:
$my_type = inline_template(%= type.upcase %
Ohad
On Fri, May 28, 2010 at 2:44 PM, Adam Winberg adam.winb...@gmail.comwrote:
Hi,
facter variables typically have values in lower case. We are looking
into moving to puppet for our config administration and are currently
using a system where we do file name matching dependent on specific
suffixes - for example a file named *--LAPTOP will only be deployed
on machines tagged as laptops.
I would like to keep this naming convention and observed that facter
has a type variable that on laptops will contain the value laptop
- but of course i want it in upper case for, in my opinion, better
clarity. Is there some smart way of doing this?
I guess i could do something like
if $type == laptop {
$type = LAPTOP
}
but im looking to see if there is any other smarter ways of doing
this.
Thanks,
//Adam Winberg
--
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 Labs Announces Puppet Forge, a Central Repository for Puppet Modules
Haha! So much for my purchase of puppetstrings.net! I guess I can scrap the crappy code I had put together, too. :-P --Paul [Mr Gabriel Says ...] Then maybe grab a few guys from this list, and get them to help you transfer everything to puppetforge :) Content, content content, any takers? Latest Article :- The Puppet Module Tool The Puppet Apprentice :- http://puppetnewbie.blogspot.com Follow me on twitter:- http://twitter.com/mritguru Puppet #tags on twitter :- #puppet #puppetforge IRC :- itguru ON irc.freenode.org (feel free to say hi!) -- 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: SuSE and zypper
2010/5/28 jb jeffb...@gmail.com: looks like a typo/omission. Add: commands :zypper = /usr/bin/zypper to zypper.rb or change :rub to :zypper would probably be the right thing to do? Yes, that was actually fixed. Check out http://projects.puppetlabs.com/issues/3802. -- 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] facter values in upper case
ok, interesting!
however i cant make it work:
$my_type = inline_template(%= type.upcase %)
notify { type is set to $my_type:; }
and log output on client:
puppetd[13739]: type is set to Notebook
i was expecting to see NOTEBOOK there, but no luck. I'm new to puppet and
my ruby is rubbish, am i doing something wrong?
//Adam
On 28 May 2010 08:53, Ohad Levy ohadl...@gmail.com wrote:
you can use inline_template to sanitize your values.. e.g.:
$my_type = inline_template(%= type.upcase %
Ohad
On Fri, May 28, 2010 at 2:44 PM, Adam Winberg adam.winb...@gmail.comwrote:
Hi,
facter variables typically have values in lower case. We are looking
into moving to puppet for our config administration and are currently
using a system where we do file name matching dependent on specific
suffixes - for example a file named *--LAPTOP will only be deployed
on machines tagged as laptops.
I would like to keep this naming convention and observed that facter
has a type variable that on laptops will contain the value laptop
- but of course i want it in upper case for, in my opinion, better
clarity. Is there some smart way of doing this?
I guess i could do something like
if $type == laptop {
$type = LAPTOP
}
but im looking to see if there is any other smarter ways of doing
this.
Thanks,
//Adam Winberg
--
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.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] facter values in upper case
you are right, it seems that type is a reserved word in ruby :(
using another variable name should work.
I'll play and see if I can come up with something
On Fri, May 28, 2010 at 4:13 PM, Adam Winberg adam.winb...@gmail.comwrote:
ok, interesting!
however i cant make it work:
$my_type = inline_template(%= type.upcase %)
notify { type is set to $my_type:; }
and log output on client:
puppetd[13739]: type is set to Notebook
i was expecting to see NOTEBOOK there, but no luck. I'm new to puppet and
my ruby is rubbish, am i doing something wrong?
//Adam
On 28 May 2010 08:53, Ohad Levy ohadl...@gmail.com wrote:
you can use inline_template to sanitize your values.. e.g.:
$my_type = inline_template(%= type.upcase %
Ohad
On Fri, May 28, 2010 at 2:44 PM, Adam Winberg adam.winb...@gmail.comwrote:
Hi,
facter variables typically have values in lower case. We are looking
into moving to puppet for our config administration and are currently
using a system where we do file name matching dependent on specific
suffixes - for example a file named *--LAPTOP will only be deployed
on machines tagged as laptops.
I would like to keep this naming convention and observed that facter
has a type variable that on laptops will contain the value laptop
- but of course i want it in upper case for, in my opinion, better
clarity. Is there some smart way of doing this?
I guess i could do something like
if $type == laptop {
$type = LAPTOP
}
but im looking to see if there is any other smarter ways of doing
this.
Thanks,
//Adam Winberg
--
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.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.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 Labs Announces Puppet Forge, a Central Repository for Puppet Modules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Lathrop wrote: Haha! So much for my purchase of puppetstrings.net! I guess I can scrap the crappy code I had put together, too. :-P Well if you have features you had done or had in mind - we'd welcome the input. Cheers James -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS/+suiFa/lDkFHAyAQJTtgf9EesVA4GoaZ8yH2Vw5ofZUwHgkfz/SDBf RyTpqDj39DRKPMv86gNG6J0ystWaByRlsQEDvcFl370zLbTkU+RMVFpjt+mb4cOj gc3XawiAn6ozIakAmKa7HNjtpwJmEtXBfURXGd28j4AhZw9N/Kdzq4Kh+HJleZgN nD7QPvmmMupH3RwNO/M6Lt47o+BcPBobUnVBEtotYHQuINdi1se3z8OE9zBB4ycK m9YE52NgReZB/3NawG0QgKqVJ8jSYZRVBESyRBD/Z3J2mfQ+Rdv3m+2BTHrLJCCy zaDVesxi2Fer1FK8hoivf+VcykU4eUdveoVkHd/RsdVQzZ3fkkTeUQ== =40ea -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] facter values in upper case
Ohad Levy ohadl...@gmail.com writes:
you are right, it seems that type is a reserved word in ruby :(
Just don't try using the variable 'fork' in your templates. ;)
using another variable name should work.
Theoretically you might be able to use a lookup function to get the value, but
practically it is (sadly) simpler to deal with Ruby being a bit kooky, and
just use a different fact or variable name.
Daniel
On Fri, May 28, 2010 at 4:13 PM, Adam Winberg adam.winb...@gmail.com wrote:
ok, interesting!
however i cant make it work:
$my_type = inline_template(%= type.upcase %) notify { type is set to
$my_type:; }
and log output on client:
puppetd[13739]: type is set to Notebook
i was expecting to see NOTEBOOK there, but no luck. I'm new to puppet and
my ruby is rubbish, am i doing something wrong?
//Adam
On 28 May 2010 08:53, Ohad Levy ohadl...@gmail.com wrote:
you can use inline_template to sanitize your values.. e.g.:
$my_type = inline_template(%= type.upcase %
Ohad
On Fri, May 28, 2010 at 2:44 PM, Adam Winberg adam.winb...@gmail.com
wrote:
Hi,
facter variables typically have values in lower case. We are looking into
moving to puppet for our config administration and are currently using a
system where we do file name matching dependent on specific suffixes - for
example a file named *--LAPTOP will only be deployed on machines tagged
as laptops.
I would like to keep this naming convention and observed that facter has a
type variable that on laptops will contain the value laptop - but of
course i want it in upper case for, in my opinion, better clarity. Is
there some smart way of doing this?
I guess i could do something like if $type == laptop { $type = LAPTOP
}
but im looking to see if there is any other smarter ways of doing this.
Thanks,
//Adam Winberg
-- 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.
-- 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.
--
✣ 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.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] facter values in upper case
way to make it work:
$my_type = $type
$my_type = inline_template(%= my_type.upcase %)
notify { type is set to $my_type:; }
thanks for your help!
//Adam
On 28 May 2010 13:47, Daniel Pittman dan...@rimspace.net wrote:
Ohad Levy ohadl...@gmail.com writes:
you are right, it seems that type is a reserved word in ruby :(
Just don't try using the variable 'fork' in your templates. ;)
using another variable name should work.
Theoretically you might be able to use a lookup function to get the value,
but
practically it is (sadly) simpler to deal with Ruby being a bit kooky, and
just use a different fact or variable name.
Daniel
On Fri, May 28, 2010 at 4:13 PM, Adam Winberg adam.winb...@gmail.com
wrote:
ok, interesting!
however i cant make it work:
$my_type = inline_template(%= type.upcase %) notify { type is set
to
$my_type:; }
and log output on client:
puppetd[13739]: type is set to Notebook
i was expecting to see NOTEBOOK there, but no luck. I'm new to puppet
and
my ruby is rubbish, am i doing something wrong?
//Adam
On 28 May 2010 08:53, Ohad Levy ohadl...@gmail.com wrote:
you can use inline_template to sanitize your values.. e.g.:
$my_type = inline_template(%= type.upcase %
Ohad
On Fri, May 28, 2010 at 2:44 PM, Adam Winberg adam.winb...@gmail.com
wrote:
Hi,
facter variables typically have values in lower case. We are looking
into
moving to puppet for our config administration and are currently using
a
system where we do file name matching dependent on specific suffixes -
for
example a file named *--LAPTOP will only be deployed on machines
tagged
as laptops.
I would like to keep this naming convention and observed that facter
has a
type variable that on laptops will contain the value laptop - but
of
course i want it in upper case for, in my opinion, better clarity. Is
there some smart way of doing this?
I guess i could do something like if $type == laptop { $type =
LAPTOP
}
but im looking to see if there is any other smarter ways of doing
this.
Thanks,
//Adam Winberg
-- 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.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.compuppet-users%2bunsubscr...@googlegroups.com.
For more options, visit this
group at http://groups.google.com/group/puppet-users?hl =en.
--
✣ 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] package question
The ICAClient package requires the 32 bit versions of libXp and
openmotif. I have this class defined:
class icaclient{
case $architecture {
i386: {
package { ICAClient:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
ICAClient-11.100-1.i386.rpm,
ensure = installed,
}
}
x86_64: {
package { libXp-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
libXp-1.0.0-8.1.el5.i386.rpm,
ensure = installed,
}
package { openmotif-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
openmotif-2.3.1-2.el5_4.1.i386.rpm,
ensure = installed,
require = Package[libXp-32bit],
}
package { ICAClient:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
ICAClient-11.100-1.i386.rpm,
ensure = installed,
require = Package[openmotif-32bit, libXp-32bit],
}
}
}
}
On the initial run of puppetd on a 64 bit system I see these lines:
notice: //icaclient/Package[libXp-32bit]/ensure: created
notice: //icaclient/Package[openmotif-32bit]/ensure: created
notice: //icaclient/Package[ICAClient]/ensure: created
Everything installed correctly and the ICAClient works.
On subsequent puppetd executions I get these:
err: //icaclient/Package[libXp-32bit]/ensure: change from absent to
present failed: Execution of '/bin/rpm -i --oldpackage /net/rfns1/vol/
flexsrc/kickstart/config/ICAClient/RHEL5/libXp-1.0.0-8.1.el5.i386.rpm'
returned 1: warning: /net/rfns1/vol/flexsrc/kickstart/config/ICAClient/
RHEL5/libXp-1.0.0-8.1.el5.i386.rpm: Header V3 DSA signature: NOKEY,
key ID 37017186
package libXp-1.0.0-8.1.el5.i386 is already installed
Why is it attempting to install libXp again? Shouldn't the ensure =
installed prevent that from happening? Or does it have something to do
with the fact it is a duplicate package name but with a different
architecture?
Lastly, does anyone have a suggestion on what to do to prevent this
error?
Thanks,
Ed
--
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] package question
On 2010-05-28 15:19, ed-rfmd wrote:
package { libXp-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
libXp-1.0.0-8.1.el5.i386.rpm,
ensure = installed,
}
package { openmotif-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
openmotif-2.3.1-2.el5_4.1.i386.rpm,
ensure = installed,
require = Package[libXp-32bit],
}
Why is it attempting to install libXp again? Shouldn't the ensure =
installed prevent that from happening? Or does it have something to do
with the fact it is a duplicate package name but with a different
architecture?
Because the package type uses the name you have specified to see
if the package is already installed. The packages are not really
named libXp-32bit and openmotif-32bit, are they? They are
more likely named libXp.i386 and openmotif.i386; use that as
package names, and it should work better.
/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: package question
That took care of it . I changed the names to libXp.i386 and
openmotif.i386. I was not using the package name properly, I was using
it as a generic identified instead of the actual package name.
Thanks again,
Ed
On May 28, 9:25 am, Thomas Bellman bell...@nsc.liu.se wrote:
On 2010-05-28 15:19, ed-rfmd wrote:
package { libXp-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
libXp-1.0.0-8.1.el5.i386.rpm,
ensure = installed,
}
package { openmotif-32bit:
provider = rpm,
source = $kickstart/ICAClient/RHEL5/
openmotif-2.3.1-2.el5_4.1.i386.rpm,
ensure = installed,
require = Package[libXp-32bit],
}
Why is it attempting to install libXp again? Shouldn't the ensure =
installed prevent that from happening? Or does it have something to do
with the fact it is a duplicate package name but with a different
architecture?
Because the package type uses the name you have specified to see
if the package is already installed. The packages are not really
named libXp-32bit and openmotif-32bit, are they? They are
more likely named libXp.i386 and openmotif.i386; use that as
package names, and it should work better.
/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] Question about templates from variables
This seems like it's a bug with plusassignment to me, can you open a
ticket on this?
I had a moment of inspiration this morning and figured out what I needed to
do to get this working the way I wanted:
class foo {
$file_content = template('foo/foo-base','foo/foo-bar')
file { /etc/foo:
content = $file_content,
}
}
class foo::bab inherits foo {
$foo::file_content += template('foo/foo-bab')
File[/etc/foo]{
content = $foo::file_content,
}
}
I believe this is the way the plussignment operator should work, so you can
avoid the hackish use of variables like I'm doing above.
My primary motivation for this is something like sudoers, where certain
system roles require sudoers commands for different groups to use. A
perfect example from our environment is any system that has an
Oracle-related role requires sudoers commands for the DBAs, on top of the
base roles we as Linux admins require on every system. Essentially I want
to avoid having to list every template combination for every possible
permutation of roles.
An alternative to this would be to allow the template() function to take a
list as a variable, something like this:
$template_list = [template1,template2,template3]
content = template($template_list),
When I try that currently, I get the following error (which is a weird
error in and of itself):
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Syntax error at '['; expected ']' at ...
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
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] combining arrays in site.pp
I'm running 0.25.4. What I'd like to do is place an array of users
under the default node. These users rarely change. Then within each
subsequent node, have another array of users added to the original
array. These users change more frequently. These users are then be
snarfed into a template. The setup I've been using is adding all the
users to one array in each node definition.
I've read that using += will add arrays to one another, but I keep
getting a Could not parse for environment testing: Syntax error at
'='; expected '}' at /etc/puppet/manifests/testing/site.pp:54 error.
Is += just not allowed in site.pp?
This is an example of what I have.
site.pp
-
node basenode {
$users_group = ['user0', 'user1']
}
node server1 inherits basenode {
$users_group += ['user2', 'user3', 'user4']
}
-
What I'm expecting from the above is $users_group = ['user0', 'user1',
'user2', 'user3', 'user4']
Thanks for any help.
Kent
--
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] Toplevel domain and facter
On 05/27/2010 02:51 PM, Klaus Ethgen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Do den 27. Mai 2010 um 17:57 schrieb Nigel Kersten: You'll need to be logged in. Ah. Bad. I have no account there and I dislike the idea to create a account anywhere to just report a bug. I have that many accounts sprayed around the net that I do not want to manage one more, sorry. That's kind of a crappy approach don't you think? Do you really think so? Have you ever dealt with a bug reporter that accepts anonymous bug reports? Do you know debian? Do you know /usr/bin/reportbug? Do you know RT? There are many bug tracker out there where reporting by e-mail is the usual way. It's almost impossible to treat such reports seriously as you're often not quite sure whether you've fixed the issue or not because you can't get in contact with the original reporter. With bug reports by e-mail this is normally not anonymous. Also usual you can get in contact with the reporter. More over, you do not need to go to any web page, you even need no web browser. You can write comfortable with your preferred mail reader and editor. There are many bugs out there. Sometimes they can be reported by the distribution bug tracker but if you install software directly or know that the bug is upstream it is of no use to have a maintainer between. And if you need to register with your shoe size (attention, I do exaggerate) often at least I let the bug be and might fix it locally so the software will not get better. This registration stuff for all is such a broken concept at all! Also mailing lists is not the best form of communication but it is ok that far as I can configure it in my mail reader to sort it in a nice way. (Ever use nntp? This concept is much better than Foren and mailing lists!) However, I will not create a user account on this site too. Take the bug report I gave here or let it be. If you are not interested in the report, well, that's yours. If you are interested, I stay here or by PM to answer questions or doing debugging. (And you might notice that I am not anonymous, I even sign my mails.) Regards Klaus - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgenkl...@ethgen.de Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEVAwUBS/6/Pp+OKpjRpO3lAQr/vwf/Q7cJW+djFrQQJCCEFzGCNhJ7+CBXDlsM cDNthtphyWZKfk3EL8q4P+QDSw1MOuylkcTvGFzmcDPQz1yqVZ2KhDP3CTMWLOG7 8Zg3Ip93K5ZPLnTF28xgPsLGLjMEODTB9bDh6fymGCHYIVt8YW2lG+uN7EkJMy6e f8iAdmRZWCEdT57uHpDwBmNMoSYDZd2RY5Qhor75YI9G5ikGqyvjbYlAlKmSYfFd 8eJkXbwoJb+2AuzplrUn6nl4Kb0tKxmWeNM3GMnpRRe4iJCuqXbMI+azakngIt0s DTKoEvSK8bpSmEHBixfz9NLzKnGoaJodlJOe6FE+k4Uee2Qw5EeXBA== =cz9H -END PGP SIGNATURE- Regardless of your intentions, etc, this is somewhat insulting IMO to an open-source/foss project. It's almost like saying Well I appreciate the thousands of lines of code you've given me for free, and the man-hours it took to write that code, and the man-hours you've saved me, but I'm not willing to give you five minutes to create a log in to your bug tracker. Just sayin'. If you really can't be bothered feel free to hop on IRC, I will file the bug for you. -- Joe McDonagh Operations Engineer 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.
Re: [Puppet Users] Nagios checks
On 05/27/2010 02:37 PM, Peter Berghold wrote: Has anybody out there written a custom check for Nagios to determine if puppetd and/or puppetmasterd is running? I am considering writing one if not. -- 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. I use the one that came with the source download, however it requires a rubygem that IMO it probably shouldn't use. -- -- Joe McDonagh Operations Engineer 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.
Re: [Puppet Users] Toplevel domain and facter
Rather than continue with this sort of semi-argument, I've gone and created an issue in redmine, #3909. -- -- Joe McDonagh Operations Engineer 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.
Re: [Puppet Users] combining arrays in site.pp
On Fri, May 28, 2010 at 11:57 AM, Kenton Brede kbr...@gmail.com wrote:
I'm running 0.25.4. What I'd like to do is place an array of users
under the default node. These users rarely change. Then within each
subsequent node, have another array of users added to the original
array. These users change more frequently. These users are then be
snarfed into a template. The setup I've been using is adding all the
users to one array in each node definition.
I've read that using += will add arrays to one another, but I keep
getting a Could not parse for environment testing: Syntax error at
'='; expected '}' at /etc/puppet/manifests/testing/site.pp:54 error.
Is += just not allowed in site.pp?
This is an example of what I have.
site.pp
-
node basenode {
$users_group = ['user0', 'user1']
}
node server1 inherits basenode {
$users_group += ['user2', 'user3', 'user4']
}
Puppet uses + for appending to arrays.
Here's the feature where it was added:
http://projects.puppetlabs.com/issues/1584
--Michael
--
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] External Nodes Require a Forklift?
What's the state of storedconfigs these days? Doug. In what sense? I am using it right now for other pieces of infrastructure, works pretty nicely but I am not exactly large scale. What did you want to accomplish with it? -- -- Joe McDonagh Operations Engineer 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.
Re: [Puppet Users] Question about templates from variables
James Cammarata j...@sngx.net writes: This seems like it's a bug with plusassignment to me, can you open a ticket on this? I had a moment of inspiration this morning and figured out what I needed to do to get this working the way I wanted: [...] My primary motivation for this is something like sudoers, where certain system roles require sudoers commands for different groups to use. FWIW, my short term solution to that problem is to use a concatenated file module, which allows me to incorporate arbitrary ordered fragments into the output file. Those can be nicely generated from a puppet define, wrapping up the process in a way that is reasonably error-checked and in which the nasty implementation details are hidden from the end users in my sysadmin team. 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.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Question about templates from variables
$template_list = [template1,template2,template3] content = template($template_list), Puppet has a split() function that splits a string into an array, that should do what you want there. template(split($template_list)) --Michael -- 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] Question about templates from variables
On Fri, May 28, 2010 at 12:40 PM, Michael DeHaan mich...@puppetlabs.com wrote: $template_list = [template1,template2,template3] content = template($template_list), Puppet has a split() function that splits a string into an array, that should do what you want there. template(split($template_list)) --Michael Sorry, I posted too quickly, you can also specify the delimiter: http://docs.puppetlabs.com/references/latest/function.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] combining arrays in site.pp
On Fri, May 28, 2010 at 11:15 AM, Michael DeHaan mich...@puppetlabs.com wrote:
On Fri, May 28, 2010 at 11:57 AM, Kenton Brede kbr...@gmail.com wrote:
I'm running 0.25.4. What I'd like to do is place an array of users
under the default node. These users rarely change. Then within each
subsequent node, have another array of users added to the original
array. These users change more frequently. These users are then be
snarfed into a template. The setup I've been using is adding all the
users to one array in each node definition.
I've read that using += will add arrays to one another, but I keep
getting a Could not parse for environment testing: Syntax error at
'='; expected '}' at /etc/puppet/manifests/testing/site.pp:54 error.
Is += just not allowed in site.pp?
This is an example of what I have.
site.pp
-
node basenode {
$users_group = ['user0', 'user1']
}
node server1 inherits basenode {
$users_group += ['user2', 'user3', 'user4']
}
Puppet uses + for appending to arrays.
Here's the feature where it was added:
http://projects.puppetlabs.com/issues/1584
Doh! Looks like me just being an idiot. I won't even tell you.
:) Anyway += is working just fine in my site.pp now.
Thanks,
Kent
--
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] Question about templates from variables
On Sat, 29 May 2010 02:30:03 +1000, Daniel Pittman dan...@rimspace.net wrote: James Cammarata j...@sngx.net writes: This seems like it's a bug with plusassignment to me, can you open a ticket on this? I had a moment of inspiration this morning and figured out what I needed to do to get this working the way I wanted: [...] My primary motivation for this is something like sudoers, where certain system roles require sudoers commands for different groups to use. FWIW, my short term solution to that problem is to use a concatenated file module, which allows me to incorporate arbitrary ordered fragments into the output file. Those can be nicely generated from a puppet define, wrapping up the process in a way that is reasonably error-checked and in which the nasty implementation details are hidden from the end users in my sysadmin team. That sounds like just what I need, any documentation on the web for that, or anything you can share? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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] accessing client certname in manifests?
I mentioned we had a custom fact for the client certname in IRC the other day and someone poked fun at me as it's apparently built in. For the life of me I can't work out what variable it is. Anyone know? (our certnames bear no relationship to any other attribute, fqdn etc) -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] accessing client certname in manifests?
On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten nig...@google.com wrote: I mentioned we had a custom fact for the client certname in IRC the other day and someone poked fun at me as it's apparently built in. if that's the case, then the following ticket needs to be closed. http://projects.puppetlabs.com/issues/3021 For the life of me I can't work out what variable it is. Anyone know? (our certnames bear no relationship to any other attribute, fqdn etc) -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.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] accessing client certname in manifests?
On Fri, May 28, 2010 at 12:00 PM, Dan Bode d...@puppetlabs.com wrote: On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten nig...@google.com wrote: I mentioned we had a custom fact for the client certname in IRC the other day and someone poked fun at me as it's apparently built in. if that's the case, then the following ticket needs to be closed. http://projects.puppetlabs.com/issues/3021 Yeah, I don't think it is built in, and people just access fqdn or some other equivalent that happens to have the same value as the certname. I'd love it if someone proves me wrong though. For the life of me I can't work out what variable it is. Anyone know? (our certnames bear no relationship to any other attribute, fqdn etc) -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.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.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] accessing client certname in manifests?
I can't find it. I just use $fqdn mostly with the exception of a few DHCP boxes. On May 28, 2010, at 2:02 PM, Nigel Kersten wrote: On Fri, May 28, 2010 at 12:00 PM, Dan Bode d...@puppetlabs.com wrote: On Fri, May 28, 2010 at 11:52 AM, Nigel Kersten nig...@google.com wrote: I mentioned we had a custom fact for the client certname in IRC the other day and someone poked fun at me as it's apparently built in. if that's the case, then the following ticket needs to be closed. http://projects.puppetlabs.com/issues/3021 Yeah, I don't think it is built in, and people just access fqdn or some other equivalent that happens to have the same value as the certname. I'd love it if someone proves me wrong though. For the life of me I can't work out what variable it is. Anyone know? (our certnames bear no relationship to any other attribute, fqdn etc) -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- 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] accessing client certname in manifests?
On Fri, May 28, 2010 at 4:19 PM, James Turnbull ja...@lovedthanlost.netwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nigel Kersten wrote: I mentioned we had a custom fact for the client certname in IRC the other day and someone poked fun at me as it's apparently built in. For the life of me I can't work out what variable it is. Anyone know? (our certnames bear no relationship to any other attribute, fqdn etc) It is not built-in - someone has misled you young man. Anyone see any problems with doing it like this? require 'puppet' Facter.add(certname) do setcode do Puppet[:config] = /etc/puppet/puppet.conf Puppet.parse_config Puppet[:certname] end end Regards James Turnbull - -- Author of: * Pro Linux Systems Administration (http://www.amazon.com/gp/product/1430219122/) * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/159059/) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBTABPZiFa/lDkFHAyAQLkywgAl1tn3QraNmZLn3Tsdt1Ymt7gOuVoISzX bz1BxW+QDWGVZZFw0hYZ8ob1kgiCgdkrZkLtjIzQbzJNR2yNY0PURqUvpGNpfoVi wB2O2JmtNu3v1mFovvHrSTtcruQ53VBpOaL2wdKcoPX+IF/sZbeQic1RTLS2S0YZ fa/iRRABidN7g5BSIiK5xPmRBbTuG25BngWs242p/vFeIbHOn57ix3dBVKZpZHnO DT0mt8uCYz2pEEVHVVDXwf4GL43jbATGRCgWuXKt0WATvwg06a8/njDmXTV45OEC 6FL2/yETt6sUk9snXyKyTWtTzKN++gXNadtPs+/LaJPwVHh0AHyzhQ== =M0AA -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
