Re: [Puppet Users] Installing and configuring puppetmaster-passenger
This is my puppetmaster configuration file. # Based on http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger Listen 8140 VirtualHost *:8140 ServerName ct-vospuppet SSLEngine on SSLProtocol -ALL +SSLv3 +TLSv1 SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/ct-vospuppet.pem SSLCertificateFile /var/lib/puppet/ssl/certs/ct-vospuppet.pem SSLCACertificateFile /var/lib/puppet/ssl/certs/ca.pem SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem # If Apache complains about invalid signatures on the CRL, you can try disabling # CRL checking by commenting the next line, but this is not recommended. SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem # Set to require if this puppetmaster doesn't issue certificates # to puppet clients. # NB: this requires SSLCACertificateFile /var/lib/puppet/ssl/certs/ca.pem # issuing puppet client certificate. SSLVerifyClient optional SSLVerifyDepth 1 SSLOptions +StdEnvVars # Passenger options that can be set in a virtual host # configuration block. PassengerHighPerformance on PassengerStatThrottleRate 120 PassengerUseGlobalQueue on RackAutoDetect Off RailsAutoDetect Off RackBaseURI / DocumentRoot /usr/share/puppet/rack/puppetmasterd/public Directory /usr/share/puppet/rack/puppetmasterd/ Options None AllowOverride None Order allow,deny allow from all /Directory /VirtualHost I have attached the apache error log with this. On Fri, Jul 13, 2012 at 10:05 PM, Jo Rhett jrh...@netconsonance.com wrote: Did you put all the passenger configuration, and Listen 8140 in the puppetmaster file? You should post both the config file and your apache error log here. On Jul 12, 2012, at 11:26 PM, kalaniS wrote: So I was trying to install puppetmaster-passenger in the server machine and configure it to communicate with the agent. My server machine and client machine are both running on Ubuntu 11.04. I installed puppetmaster-passenger through apt-get and in /etc/apache2/ sites-available/puppetmaster file, in between the VirtualHost tags put ServerName as ct-vospuppet. In the server machine's apache2/httpd.conf I put a record as ServerName ct-vospuppet. (The hostname of the server is ct-vospuppet) Then I restarted apache. In the puppet.conf file in the agent machine, I put a record server=ct- vospuppet. Then I tried @cd-vgpereravos:~$ sudo puppet agent --server ct-vospuppet --test -- debug and got the following output. debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/public_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ public_keys] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/ puppet/ssl] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/ puppet] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ lib/puppet/state] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ puppet] debug: /File[/var/lib/puppet/ssl/certs/cd- vgpereravos.virtusa.com.pem]: Autorequiring File[/var/lib/puppet/ssl/ certs] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/ lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/ var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys/cd- vgpereravos.domain.com.pem]: Autorequiring File[/var/lib/puppet/ssl/
Re: [Puppet Users] Re: Anyway to get the $name or $title of the resource being called?
On 14 July 2012 01:22, Nick Fagerlund nick.fagerl...@puppetlabs.com wrote:
You may be doing something weird, because $name and $title inside a defined
type definition should definitely still refer to the instance's title. In
fact, I just tested it to be sure:
define my_file ($message) {
notify {$title:
message = $message, and the title is still $title,
}
}
class my_class {
my_file {'the title of the resource, not the class':
message = This is the message,
}
}
include my_class
...should get you:
notice: This is the message, and the title is still the title of the
resource, not the class
notice: /Stage[main]/My_class/My_file[the title of the resource, not the
class]/Notify[the title of the resource, not the class]/message: defined
'message' as 'This is the message, and the title is still the title of the
resource, not the class'
notice: Finished catalog run in 0.05 seconds
Show us what you're doing, maybe?
I think the original poster referred to being able to access the title
of a resource inside a resource definition (not a defined type). For
example:
class example {
file { '/tmp/testfile': content = foo ${name} bar\n,
}
Here $name would refer to example, but he wants to access the name
'/tmp/testfile'. But as the resource definition doesn't create a new
scope there's no new variables in it.
--
Erik Dalén
--
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] Using catalog inventory/Puppet::Resource::Catalog?
I'm going to try this again and hope I forgot to hit submit rather than
having a message to the list pending for approval.
I want a list of classes contained in the puppet catalog that's been
applied to the node, not management classes. At least in mco 2.0.0 with
minimal configuration, an mco inventory some.host or mco rpc rpcutil
inventory -I some.host lists facts and mgmt classes. Now, I'm fairly new
to mcollective, so I might be missing something obvious, in which case I'd
greatly appreciate being told what :)
What I started with was as an erb template for facts.yaml:
%
# Gather all of our scope variables
gather_vars = scope.to_hash.reject{ |k,v| k.to_s =~
/(uptime|free|timestamp|id|name|title|rsa|dsa)/ }
# And then all of classes
gather_vars.store('classcatalog', classes.sort.uniq.join(', ')) -%
%= gather_vars.to_yaml %
And boom I can do an mco find --with-fact classcatalog=/corosync/ and it'll
list all my nodes which use my corosync modules.
Which appears to work, but I'm a bit leary of this since so much in puppet
depends on order of execution and I've seen some odd scoping issues with
staging. So while I have this being populated last, and use an ENC 90% of
the time(which populates the management classes), and it all works, it
might break in the future. I was hoping there was another way of exposing
this.
On Thursday, July 12, 2012 7:14:16 PM UTC-4, R.I. Pienaar wrote:
- Original Message -
From: Nick Cammorato nick_cammor...@terc.edu
To: puppet-users@googlegroups.com
Sent: Thursday, July 12, 2012 5:35:28 PM
Subject: [Puppet Users] Using catalog
inventory/Puppet::Resource::Catalog?
I'd like to be able to get a list of all of the classes being applied
to my nodes and insert this as a list into mcollective's facts.yaml
file. The reason for this is that I have a couple post-commit hooks
that parse out changes to specific modules/classes for changelog
purposes and I'm considering adding in a call to mco find to include
a list of affected nodes in the report. Which means the facts need
to be there to be found.
mcollective already knows what classes are on a host, you can access it
on the cli:
mco rpc rpcutil inventory -I some.host
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/5PJdUxXAAaYJ.
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: State of Puppet 3.0 and our commitment to quality
Hi Mike- Thanks for your announcement. Can you say a bit about where the hiera distribution fits into this? It is a little fuzzy to me during the 2.7/3.x transition which version/packages the community is supposed to use with 2.7.x in the meantime. The gem version (0.30)?, the one off HEAD in the github repos (1.0.0)?, the files in the puppetlabs repos (e.g. 1.0.0.0-01rc3 on apt.puppetlabs.com -- and hey, what about hiera-puppet 1.0.0-0.1rc1, where does that fit into the picture for the 2.7 branch?)? Thanks for any direction you can provide. -- dNb -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/lzK9pP745b8J. 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] Using catalog inventory/Puppet::Resource::Catalog?
- Original Message -
From: Nick Cammorato nick_cammor...@terc.edu
To: puppet-users@googlegroups.com
Sent: Saturday, July 14, 2012 3:04:48 PM
Subject: Re: [Puppet Users] Using catalog inventory/Puppet::Resource::Catalog?
I'm going to try this again and hope I forgot to hit submit rather
than having a message to the list pending for approval.
I want a list of classes contained in the puppet catalog that's been
applied to the node, not management classes. At least in mco 2.0.0
with minimal configuration, an mco inventory some.host or mco rpc
rpcutil inventory -I some.host lists facts and mgmt classes. Now,
I'm fairly new to mcollective, so I might be missing something
obvious, in which case I'd greatly appreciate being told what :)
What I started with was as an erb template for facts.yaml:
%
# Gather all of our scope variables
gather_vars = scope.to_hash.reject{ |k,v| k.to_s =~
/(uptime|free|timestamp|id|name|title|rsa|dsa)/ }
# And then all of classes
gather_vars.store('classcatalog', classes.sort.uniq.join(', ')) -%
%= gather_vars.to_yaml %
And boom I can do an mco find --with-fact classcatalog=/corosync/ and
it'll list all my nodes which use my corosync modules.
Which appears to work, but I'm a bit leary of this since so much in
puppet depends on order of execution and I've seen some odd scoping
issues with staging. So while I have this being populated last, and
use an ENC 90% of the time(which populates the management classes),
and it all works, it might break in the future. I was hoping there
was another way of exposing this.
I am not following, you do not need to gather this information for
mcollective to be aware of classes.
Puppet creates a file on every node that has a list of all the classes
on said node, on my machines this is in /var/lib/puppet/classes.txt
So I configure mcollective with:
classesfile = /var/lib/puppet/classes.txt
and now I can just do mco find -C /someclass/ and it does what you want
no need to try and turn those into a fact or anything like that.
And if I do 'mco inventory some.node' I get a section displayed like:
Configuration Management Classes:
apache apache::config
apache::installapache::logrotate
Does this method not work for you?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-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] Using catalog inventory/Puppet::Resource::Catalog?
Sorry, I should've clarified. I was hoping to use the management classes
for something other than puppet classes(more abstract things like nagios
hostgroups, some of which share names with classes). If I can't reliably
populate the facts with class information though, I might not have a choice.
On Saturday, July 14, 2012 11:36:50 AM UTC-4, R.I. Pienaar wrote:
- Original Message -
From: Nick Cammorato nick_cammor...@terc.edu
To: puppet-users@googlegroups.com
Sent: Saturday, July 14, 2012 3:04:48 PM
Subject: Re: [Puppet Users] Using catalog
inventory/Puppet::Resource::Catalog?
I'm going to try this again and hope I forgot to hit submit rather
than having a message to the list pending for approval.
I want a list of classes contained in the puppet catalog that's been
applied to the node, not management classes. At least in mco 2.0.0
with minimal configuration, an mco inventory some.host or mco rpc
rpcutil inventory -I some.host lists facts and mgmt classes. Now,
I'm fairly new to mcollective, so I might be missing something
obvious, in which case I'd greatly appreciate being told what :)
What I started with was as an erb template for facts.yaml:
%
# Gather all of our scope variables
gather_vars = scope.to_hash.reject{ |k,v| k.to_s =~
/(uptime|free|timestamp|id|name|title|rsa|dsa)/ }
# And then all of classes
gather_vars.store('classcatalog', classes.sort.uniq.join(', ')) -%
%= gather_vars.to_yaml %
And boom I can do an mco find --with-fact classcatalog=/corosync/ and
it'll list all my nodes which use my corosync modules.
Which appears to work, but I'm a bit leary of this since so much in
puppet depends on order of execution and I've seen some odd scoping
issues with staging. So while I have this being populated last, and
use an ENC 90% of the time(which populates the management classes),
and it all works, it might break in the future. I was hoping there
was another way of exposing this.
I am not following, you do not need to gather this information for
mcollective to be aware of classes.
Puppet creates a file on every node that has a list of all the classes
on said node, on my machines this is in /var/lib/puppet/classes.txt
So I configure mcollective with:
classesfile = /var/lib/puppet/classes.txt
and now I can just do mco find -C /someclass/ and it does what you want
no need to try and turn those into a fact or anything like that.
And if I do 'mco inventory some.node' I get a section displayed like:
Configuration Management Classes:
apache apache::config
apache::installapache::logrotate
Does this method not work for you?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/aTomd-7TN9sJ.
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] Using catalog inventory/Puppet::Resource::Catalog?
- Original Message - From: Nick Cammorato nick_cammor...@terc.edu To: puppet-users@googlegroups.com Sent: Saturday, July 14, 2012 5:02:29 PM Subject: Re: [Puppet Users] Using catalog inventory/Puppet::Resource::Catalog? Sorry, I should've clarified. I was hoping to use the management classes for something other than puppet classes(more abstract things like nagios hostgroups, some of which share names with classes). If I can't reliably populate the facts with class information though, I might not have a choice. i could add a feature where instead of just classes.txt it reads a list of files and search against them all, then you can use puppet classes as well as another file you manage in some other way -- 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] Using catalog inventory/Puppet::Resource::Catalog?
That would actually be nice for other reasons, but I think I can whip something up to do that on my own if I need it. After giving it a bit of thought, I realized this is yet another thing where I can do exactly what I'd like to do but just not quite exactly the way I'd like to do it. This seems to keep happening to me with anything related to ruby. I fight the framework for a while, bang my head into walls, then finally accept it and grow to love whatever it was I didn't initially like. There's no actual need to have puppet classes as facts and other information as management classes when I can just insert what I was going to insert as a management class in as a fact. IE: What I wanted to do was have a management class monitor that corresponds to a group of nodes residing in the same network/host segment that do different things, a fact class=monitor that corresponds to the puppet nagios servers class, a fact environment=monitor that dictates a puppet environment, and a hostgroups=monitor fact that corresponds to the nagios hostgroup monitor. Moving the class=monitor fact to the management class doesn't preclude me from adding a security-zone=monitor or a dozen other facts like that for the purposes of ridiculous granularity in categorization and that can be inserted in a number of different ways. It's just not quite the organizational hierarchy I originally envisioned, but it accomplishes exactly the same thing. I'm still kind of curious if there's a reliable way to access the class list or full catalog during any point in a puppet run though, because I can think of a few other things that might be useful for(and a few ways to make things spectacularly blow up). But now that's way more academic. On Saturday, July 14, 2012 12:33:02 PM UTC-4, R.I. Pienaar wrote: - Original Message - From: Nick Cammorato nick_cammor...@terc.edu To: puppet-users@googlegroups.com Sent: Saturday, July 14, 2012 5:02:29 PM Subject: Re: [Puppet Users] Using catalog inventory/Puppet::Resource::Catalog? Sorry, I should've clarified. I was hoping to use the management classes for something other than puppet classes(more abstract things like nagios hostgroups, some of which share names with classes). If I can't reliably populate the facts with class information though, I might not have a choice. i could add a feature where instead of just classes.txt it reads a list of files and search against them all, then you can use puppet classes as well as another file you manage in some other way -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7E1uLxzFaIsJ. 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] Using catalog inventory/Puppet::Resource::Catalog?
On 14 Jul 2012, at 18:36, Nick Cammorato nick_cammor...@terc.edu wrote: That would actually be nice for other reasons, but I think I can whip something up to do that on my own if I need it. After giving it a bit of thought, I realized this is yet another thing where I can do exactly what I'd like to do but just not quite exactly the way I'd like to do it. This seems to keep happening to me with anything related to ruby. I fight the framework for a while, bang my head into walls, then finally accept it and grow to love whatever it was I didn't initially like. I think that's quite a general thing though isn't it. Any system is designed with goals and some concept of what is The Right Thing and when you understand those and embrace then suddenly the system works best. There's no actual need to have puppet classes as facts and other information as management classes when I can just insert what I was going to insert as a management class in as a fact. IE: What I wanted to do was have a management class monitor that corresponds to a group of nodes residing in the same network/host segment that do different things, a fact class=monitor that corresponds to the puppet nagios servers class, a fact environment=monitor that dictates a puppet environment, and a hostgroups=monitor fact that corresponds to the nagios hostgroup monitor. Moving the class=monitor fact to the management class doesn't preclude me from adding a security-zone=monitor or a dozen other facts like that for the purposes of ridiculous granularity in categorization and that can be inserted in a number of different ways. It's just not quite the organizational hierarchy I originally envisioned, but it accomplishes exactly the same thing. You could just have a bunch of empty classes that you include on a node as a kind of tag which would probably have the same end result I'm still kind of curious if there's a reliable way to access the class list or full catalog during any point in a puppet run though, because I can think of a few other things that might be useful for(and a few ways to make things spectacularly blow up). But now that's way more academic. I dot think there is a reliable way really no On Saturday, July 14, 2012 12:33:02 PM UTC-4, R.I. Pienaar wrote: - Original Message - From: Nick Cammorato nick_cammor...@terc.edu To: puppet-users@googlegroups.com Sent: Saturday, July 14, 2012 5:02:29 PM Subject: Re: [Puppet Users] Using catalog inventory/Puppet::Resource::Catalog? Sorry, I should've clarified. I was hoping to use the management classes for something other than puppet classes(more abstract things like nagios hostgroups, some of which share names with classes). If I can't reliably populate the facts with class information though, I might not have a choice. i could add a feature where instead of just classes.txt it reads a list of files and search against them all, then you can use puppet classes as well as another file you manage in some other way -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/7E1uLxzFaIsJ. 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] RHEL group management with AD
Greetings, My question is about using Puppet to manage RHEL6 users' local group memberships when the users are served from AD using Winbind. I have RHEL6 x86_64 machines joined to a Windows 2003-level domain using Winbind with Kerberos for auth. To add a user-type to a local group, it appears that all groups are evaluated and are subsequently not found for the winbind-provided groups, which causes managing a user's group properties with the default of attribute_membership of minimum to fail. Have there been any known work arounds? (I think I'm hitting issue 1583: http://projects.puppetlabs.com/issues/1583) Thanks much, Eugene -- 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: [Puppet-dev] Re: Announce: Puppet Dashboard 1.2.10 Available
An additional note on this second release: The fix for the packaging issues encountered in the initial release of Puppet Dashboard 1.2.10 was provided by the contributions of Boyan Tabakov. The related commits are: a8a97dc Fixed linking of database.yml in debian postinst to use absolute path. d6619a1 Updated debian postinst script to link properly the settings.yml file to puppet-dashboard config directory. It is contributions such as these from our community members that help keep Puppet Labs' software great. Thanks, Moses Mendoza Release Engineer, Puppet Labs On Fri, Jul 13, 2012 at 2:37 PM, William Hopper whop...@puppetlabs.comwrote: All, New puppet-dashboard 1.2.10 deb packages are available on apt.puppetlabs.com that should resolve the issue of the missing configuration file. The package version is 1.2.10-1puppetlabs2. Thanks for your patience while we worked this fix out. Please let us know if you encounter any issues. Thanks, Will -- 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: Anyway to get the $name or $title of the resource being called?
Thanks Nick - it turned out that it was an issue on my end which was
exacerbated by a misunderstanding of the log message and then
misreading some online posts. Everything is working fine now.
Thanks!
On Jul 13, 4:22 pm, Nick Fagerlund nick.fagerl...@puppetlabs.com
wrote:
You may be doing something weird, because $name and $title inside a defined
type definition should definitely still refer to the instance's title. In
fact, I just tested it to be sure:
define my_file ($message) {
notify {$title:
message = $message, and the title is still $title,
}
}
class my_class {
my_file {'the title of the resource, not the class':
message = This is the message,
}
}
include my_class
...should get you:
notice: This is the message, and the title is still the title of the
resource, not the class
notice: /Stage[main]/My_class/My_file[the title of the resource, not the
class]/Notify[the title of the resource, not the class]/message: defined
'message' as 'This is the message, and the title is still the title of the
resource, not the class'
notice: Finished catalog run in 0.05 seconds
Show us what you're doing, maybe?
--
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: Anyway to get the $name or $title of the resource being called?
Nick actually was right - but I then ran into exactly what you're
saying Erik :) I fixed it by using a defined resource in place of the
plain file statement, basically how Nick was saying, and it worked
great.
Thanks for your help guys!
On Jul 14, 1:09 am, Erik Dalén erik.gustav.da...@gmail.com wrote:
On 14 July 2012 01:22, Nick Fagerlund nick.fagerl...@puppetlabs.com wrote:
You may be doing something weird, because $name and $title inside a defined
type definition should definitely still refer to the instance's title. In
fact, I just tested it to be sure:
define my_file ($message) {
notify {$title:
message = $message, and the title is still $title,
}
}
class my_class {
my_file {'the title of the resource, not the class':
message = This is the message,
}
}
include my_class
...should get you:
notice: This is the message, and the title is still the title of the
resource, not the class
notice: /Stage[main]/My_class/My_file[the title of the resource, not the
class]/Notify[the title of the resource, not the class]/message: defined
'message' as 'This is the message, and the title is still the title of the
resource, not the class'
notice: Finished catalog run in 0.05 seconds
Show us what you're doing, maybe?
I think the original poster referred to being able to access the title
of a resource inside a resource definition (not a defined type). For
example:
class example {
file { '/tmp/testfile': content = foo ${name} bar\n,
}
Here $name would refer to example, but he wants to access the name
'/tmp/testfile'. But as the resource definition doesn't create a new
scope there's no new variables in it.
--
Erik Dalén
--
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] execute a command if a package isn't installed, then install the package
Hi, I'm trying to install the 'unbound' dns resolver in ubuntu via puppet and I'm running into some issues. The issue isn't that the package doesn't install, but rather that apt automatically starts the daemon - and when the daemon starts, it updates resolv.conf in a way that breaks DNS. There's a command, 'resolvconf --disable-updates' that will stop unbound from making the change it wants to. What I'd like to do is: - If unbound isn't installed, then execute --disable-updates - Then install unbound - Then --enable-updates Is there anyway to do this? 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] execute a command if a package isn't installed, then install the package
On Jul 14, 2012, at 5:19 PM, loki77 lok...@gmail.com wrote: Hi, I'm trying to install the 'unbound' dns resolver in ubuntu via puppet and I'm running into some issues. The issue isn't that the package doesn't install, but rather that apt automatically starts the daemon - and when the daemon starts, it updates resolv.conf in a way that breaks DNS. There's a command, 'resolvconf --disable-updates' that will stop unbound from making the change it wants to. What I'd like to do is: - If unbound isn't installed, then execute --disable-updates - Then install unbound - Then --enable-updates Is there anyway to do this? Thanks. You can either write a custom fact that gets set when unbound is installed/active and use that in an if block around the stop-install-start procedure, or use the 'resolvconf --disable-updates' exec resource's 'unless' parameter to test for a running unbound daemon prior to installing the package. -- Peter Bukowinski -- 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] Puppet on Reddit
I figured I'd take to time to remind you guys of the r/puppet subreddit: http://www.reddit.com/r/puppet I'm hoping to see it grow more in the lead-up to PuppetConf, mostly because I want to see some interesting blog posts and such before September ;) Cheers - R. Tyler Croy -- Code: http://github.com/rtyler Chatter: http://twitter.com/agentdero rty...@jabber.org signature.asc Description: Digital signature
[Puppet Users] Re: RHEL group management with AD
On Jul 14, 2012, at 1:40 PM, Eugene Vilensky evilen...@gmail.com wrote: Have there been any known work arounds? (I think I'm hitting issue 1583: http://projects.puppetlabs.com/issues/1583) I should note unlike issue 1583, winbind enum groups is set to on in my configuration. -- 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] How to take away install privilege from users other than puppet?
Hi Guys, I am trying to configure to my client machine, I want prevent user don't do installation, All installation done through puppet only, How to do it, Guide me... -Ganesh. Did I learn something today? If not, I wasted it. -- 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.
