Re: [Puppet Users] which is more efficient?
On Wed, Jun 30, 2010 at 11:57 AM, Brice Figureau
wrote:
> On 30/06/10 20:48, Marcus, Allan B wrote:
>> We need to put a script into /usr/local/bin. Which is more efficient, put
>> the text into a variable and use content =>, or put the file on the
>> puppetmaster server and use source =>
>
> Definitely source.
I'm in the process of setting up performance testing for this sort of
question, but my intuition tells me otherwise. With source =>, the
puppet master still needs to determine a hash of the file to include
in the catalog, which isn't an inexpensive operation.
If you use content => file('/tmp/foo.txt'), the master still needs to
hit the filesystem, but it doesn't need to calculate a checksum.
In addition, if you're using cached catalogs, the agent doesn't need
to do a round trip to the puppet master file server to manage the file
resource if it's out of state, since the contents are directly in the
catalog.
Just my intuition, I hope to have data to back up my hypothesis by the
end of next week.
--
Jeff McCune
http://www.puppetlabs.com/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] ERB / Tagging...
On Wed, Jun 30, 2010 at 10:40 AM, CraftyTech wrote:
> Hello All,
>
> Can someone point me in the right direction here. I'm trying to
> create an erb template for my /etc/hosts file, so that when executed,
> it populates the /etc/hosts file only with entries that are tag
> relevant. For instance, if a server is tagged apache, only the apache
> tagged entries would be populated into the /etc/hosts file. Thanks in
> advance for you help.
I recommend using the built in host type to model and manage entries
in /etc/hosts rather than a template.
Modeling your configuration using a type rather than a file will allow
you to declare the resources as virtual, then simply realize them if
they're tagged with the tag you care about. In addition, you'll
receive a bunch of additional features "for free" like the
relationship graph, meta-parameters, reporting, etc...
For example:
class apache {
@host { "zaphod": ip => "1.2.3.4" }
}
# Realize host entries tagged with "apache"
Host <| tag == "apache" |>
--
Jeff McCune
http://www.puppetlabs.com/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Interesting "Bad Certificate" Problem
On Thu, Jul 1, 2010 at 1:36 PM, Aaron Blew wrote: > All, > I'm having an interesting certificate problem with a host I provisioned > today. Have you checked your clocks? Is the client in sync with the server? -- Jeff McCune http://www.puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Splitting classes into separate files
On Thu, Jul 1, 2010 at 6:03 PM, Chuck wrote:
> Move the classes directory to
>
> /etc/puppet/modules/repo/manifests/classes
>
With puppet 0.25.x, you should no longer need to use any import
statements at all. The autoloader will import the correct manifest
file so long as you follow the standard.
A typical module for apache contains:
a class named apache
a class named apache::disable to disable the service
a defined type named apache::virtualhost to model a virtual host.
In this module, if you use the following orginization puppet will
autoload everything:
manifests/init.pp contains class apache { }
manifests/disable.pp contains class apache::disable inherits apache {}
manifests/virtualhost.pp contains define apache::virtualhost(){}
If you want additional namespaces, they go in directories.
class apache::service::disable would go in manifests/service/disable.pp
I highly recommend against using import today and in the future.
Hope this helps,
--
Jeff McCune
http://www.puppetlabs.com/
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] vardir variable not coming through
Peter Meier wrote: >> I am running puppet 0.25.5, and have the puppetmasterd and puppetd on >> the same server. When I start the puppetd client, it gets an empty >> $vardir, and tries to create /touch instead of /var/xyz/puppet/touch. > >> What am I missing? > > afair config variables are not yet present in the manifests. I'm not > sure if there is bug report for that. But remember: catalogs are > compiled on the master, so which $vardir should be used? the one from > the master or the client one? There might be use for both cases. > > cheers pete These settings will be available in your manifests in version 2.6 and later. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet-tool modules not working
I have opened a ticket against puppet http://projects.puppetlabs.com/issues/4135 this is just a warning, and only occurs when the file is synced. The files are still synced correctly. Engineering is aware of this issue. thanks for reporting it :) On Fri, Jul 2, 2010 at 1:04 AM, SyRenity wrote: > Hi. > > I created a new module using puppet-tool, but Puppet shows following > error when trying to synchronize it: > README.markdown:2: syntax error ==^ /var/lib/puppet/lib/puppet/ > facter/README.markdown:7: syntax error on site-specific data that just > isn’t available via Facter. The ^ /var/lib/puppet/ > lib/puppet/facter/README.markdown:7: Invalid char `\342' in > expression /var/lib/puppet/lib/puppet/facter/README.markdown:7: > Invalid char `\200' in expression /var/lib/puppet/lib/puppet/facter/ > README.markdown:7: Invalid char `\231' in expression /var/lib/puppet/ > lib/puppet/facter/README.markdown:9: syntax error then be distributed > to Puppet clients and are available for use in ^ /var/lib/puppet/ > lib/puppet/facter/README.markdown:13: syntax error /var/lib/puppet/lib/ > puppet/facter/README.markdown:14: syntax error `hardware_platform`, > defined like this: ^ /var/lib/puppet/lib/puppet/ > facter/README.markdown:14: syntax error /var/lib/ > Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded > file /var/lib/puppet/lib/puppet/parser/functions/README.markdown: /var/ > lib/puppet/lib/puppet/parser/functions/README.markdown:2: syntax error > =^ /var/lib/puppet/lib/puppet/parser/functions/ > README.markdown:6: syntax error /var/lib/puppet/lib/puppet/parser/ > functions/README.markdown:7: syntax error `myfunction`, defined like > this: ^ /var/lib/puppet/lib/puppet/parser/functions/ > README.markdown:7: syntax error /var/lib/puppet/lib/puppet/parser/ > functions/README.markdown:13: syntax error ) do |vals| ^ / > var/lib/puppet/lib/puppet/parser/functions/README.markdown:17: syntax > error Should be found in `myfunction.rb` in this > directory. ^ /var/lib/puppet/lib/puppet/parser/ > functions/README.markdown:17: syntax error Should be found in > `myfunction.rb` in this > directory. ^ /var/lib/puppet/lib/ > puppet/parser/functions/README.markdown:17: syntax error > Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded > file /var/lib/puppet/lib/puppet/provider/README.markdown: /var/lib/ > puppet/lib/puppet/provider/README.markdown:2: syntax error > =^ /var/lib/puppet/lib/puppet/provider/README.markdown:7: > syntax error example, a provider `myprovider` for a resource type > `mytype`, defined like this:^ /var/lib/puppet/lib/ > puppet/provider/README.markdown:7: syntax error example, a provider > `myprovider` for a resource type `mytype`, defined like > this: ^ /var/lib/puppet/lib/puppet/ > provider/README.markdown:7: syntax error example, a provider > `myprovider` for a resource type `mytype`, defined like > this: > ^ /var/lib/puppet/lib/puppet/provider/README.markdown:9: syntax error / > var/lib/puppet/lib/puppet/provider/README.markdown:12: syntax error > Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded > file /var/lib/puppet/lib/puppet/type/README.markdown: /var/lib/puppet/ > lib/puppet/type/README.markdown:2: syntax error ==^ / > var/lib/puppet/lib/puppet/type/README.markdown:4: syntax error Define > resource types in this directory. ^ /var/lib/ > puppet/lib/puppet/type/README.markdown:6: syntax error /var/lib/puppet/ > lib/puppet/type/README.markdown:7: syntax error type `mytype`, defined > like this:^ /var/lib/puppet/lib/puppet/ > type/README.markdown:9: syntax error /var/lib/puppet/lib/puppet/type/ > README.markdown:12: syntax error > > Any idea? > > Regards. > > -- > 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] selboolean with selinux disabled
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/07/2010 05:20, Patrick Mohr wrote: > > On Jul 1, 2010, at 6:31 PM, Markus Falb wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> err: //cobbler::web/Selboolean[httpd_can_network_connect]: Failed to >> retrieve current state of resource: Execution of '/usr/sbin/getsebool >> httpd_can_network_connect' returned 1: /usr/sbin/getsebool: SELinux is >> disabled >> >> >> Is this behaviour intentional ? I mean, with selinux disabled it does >> not make sense to call getsebool or setsebool. For what I want to >> achieve (httpd can network connect) a disabled selinux is as good as >> setsebool. > > That isn't quite true because if SELinux is ever re-enabled it might give the > admin a nasty surprise if he thought the policies were actually set. Correct, of course. Or do not play with such things on production machines. Or manage selinux permissive/enforcing/disabled through puppet as well as things like httpd can network connect. > I don't have anything else to say because everything else I was going to say > is covered better by Frank's email. > thanks to Frank. thanks to you too, Patrick. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwuLGcACgkQYoWFBIJE9eV33wCfcnuLzlYtP9qK0nk7CsLD2mAD 0NQAn0ISyhatHFmZw6iq8R6kS3mD2ToK =ITuS -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] Setting permissions on nagios service check file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 06:39 PM, Joe McDonagh wrote: > On 07/02/2010 12:11 PM, Druwerd wrote: >> Is there a better way to set the permissions on the cfg files >> generated by the nagios_service type? >> I want each nagios service check to have it's own file, but don't want >> to write it out each time. Is there a way to set default permissions >> for the nagios_service cfg files? or you use a definition to wrap these 2 statements up into one and call the definition. cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwuInUACgkQbwltcAfKi3+BBwCfQsnp9NqMy7KdZ1zpPubGOdKA 8JgAnR//t2duOvEpqYHLIfcRaqCEMCIL =W4xq -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] Setting permissions on nagios service check file
On 07/02/2010 12:11 PM, Druwerd wrote:
Is there a better way to set the permissions on the cfg files
generated by the nagios_service type?
I want each nagios service check to have it's own file, but don't want
to write it out each time. Is there a way to set default permissions
for the nagios_service cfg files?
# Monitor ntp services
@@nagios_service{ "nrpe_ntp":
target => "/etc/nagios/conf.d/
services/${fqdn}_nrpe_ntp.cfg"
check_command => "check_nrpe!check_ntp_time"
}
# Change the permissions of the nagios ntp check file
@@file{ "/etc/nagios/conf.d/services/${fqdn}_nrpe_ntp.cfg":
owner => root,
group => root,
mode => 444,
require => Nagios_service["nrpe_ntp"],
tag => "nagios",
}
You use a combination of overrides and an exec that fixes the permissions.
Nagios_service {
notify => Exec["fix_nagios_perms"];
}
exec {
"fix_nagios_perms":
command => "/bin/chmod -R 755 /etc/nagios3",
notify => Service["nagios"],
refreshonly => "true";
service {
"nagios":
ensure => "running";
}
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] [puppet-users] apt and gem package with the same name
* hernan [2010/06/30 17:02]:
> I'm building a puppet manifest for an Ubuntu machine that needs to
> have both of these on it:
>
> package { "memcached":
> provider => gem,
> ensure => "0.18.0"
> }
>
> package { "memcached":
> provider => apt,
> ensure => installed
> }
I think this should work:
package { "memcached-gem":
name => "memcached",
provider => gem,
ensure => "0.18.0"
}
package { "memcached-apt":
name => "memcached",
provider => apt,
ensure => installed
}
--
Time passes, but love remains.
--
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] vardir variable not coming through
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I am running puppet 0.25.5, and have the puppetmasterd and puppetd on > the same server. When I start the puppetd client, it gets an empty > $vardir, and tries to create /touch instead of /var/xyz/puppet/touch. > > What am I missing? afair config variables are not yet present in the manifests. I'm not sure if there is bug report for that. But remember: catalogs are compiled on the master, so which $vardir should be used? the one from the master or the client one? There might be use for both cases. cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwuEpcACgkQbwltcAfKi39zlwCfYh5iY4+8Jh41JYtE28TW/5NQ VMoAn2e+RuOF5UQ7NtKQOyHOIYtkKgYP =Tvv8 -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] vardir variable not coming through
* noob-puppeteer [2010/07/01 18:00]:
> I must be missing something with how puppet.conf works.
>
> I have configured puppet.conf like so:
> [main]
> vardir = /var/xyz/puppet
>
> I have a very simple site.pp
>
> file { "$vardir/touch":
> ensure => present,
> }
>
> I am running puppet 0.25.5, and have the puppetmasterd and puppetd on
> the same server. When I start the puppetd client, it gets an empty
> $vardir, and tries to create /touch instead of /var/xyz/puppet/touch.
>
> What am I missing?
Facter doesn't make puppet configuration variables available in your
manifests, so you can't reference $vardir, $confdir, and so on
unless you write custom facts to make them available.
--
Make something future-proof and the universe will invent a worse future.
-- David Cantrell
--
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] Setting permissions on nagios service check file
Is there a better way to set the permissions on the cfg files
generated by the nagios_service type?
I want each nagios service check to have it's own file, but don't want
to write it out each time. Is there a way to set default permissions
for the nagios_service cfg files?
# Monitor ntp services
@@nagios_service{ "nrpe_ntp":
target => "/etc/nagios/conf.d/
services/${fqdn}_nrpe_ntp.cfg"
check_command => "check_nrpe!check_ntp_time"
}
# Change the permissions of the nagios ntp check file
@@file{ "/etc/nagios/conf.d/services/${fqdn}_nrpe_ntp.cfg":
owner => root,
group => root,
mode => 444,
require => Nagios_service["nrpe_ntp"],
tag => "nagios",
}
--
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] Data Backup
Alex Howells wrote: > On 1 July 2010 14:13, Demitrius Robinson wrote: >> Most backup software programsdata offer some form of data . >> Filtering allows you to filter certain types of files for backup. For >> example, you can select to backup all of the images in your hard drive- >> giving you the freedom to refine your data backup in ways that best >> suit your needs. This tool is also available on most backup software. >> http://www.geekzwa.com.au > > One would presume the group isn't immune to spam? > No mailing list is. I think we have about two a year that slip through. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Managing some (but not all) user files
Use "recurse => remote". See this thread too: http://groups.google.com/group/puppet-users/browse_thread/thread/8eb0bc8a117924b8/e509c1ff40c25296. -- 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] Data Backup
On 1 July 2010 14:13, Demitrius Robinson wrote: > Most backup software programs data offer some form of data . > Filtering allows you to filter certain types of files for backup. For > example, you can select to backup all of the images in your hard drive- > giving you the freedom to refine your data backup in ways that best > suit your needs. This tool is also available on most backup software. > http://www.geekzwa.com.au One would presume the group isn't immune to spam? -- 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 requires....
On Jul 1, 2010, at 10:45 PM, Douglas Garstang wrote:
> On Thu, Jul 1, 2010 at 9:11 PM, Patrick Mohr wrote:
>>
>> On Jul 1, 2010, at 9:05 PM, christopher floess wrote:
>>
>> Hey, this is sort of hijacking the thread, so if need be, please, I can
>> start another thread for it, but could someone explain the code from the OP
>> here. I feel like this is sort of the next step in puppet functionality that
>> I need to learn (I'm still new).
>>
>> I'll start by pointing out three things that tripped me up:
>>
>> 1. I've read about the difference between Package (capitalized), and package
>> (lowercase), but in practice I don't understand it.
>>
>> When declaring a resource, use the lowercase one. When referring to an
>> existing resource, use the uppercase one.
>>
>> 2. In the Package { require => Class['yum::client']}, why isn't there a
>> name?
>>
>> This says take care of the whole yum::client class before installing
>> any package. (Technically this is only almost true. There are exceptions.)
>
> Eeeek! What are the exceptions?
First, if you set a require on the resource using "=>" it overrides the global.
Use "+>" to add a require. I also remember hearing something about overriding
resources using inheritance, but I don't remember that.
Second, I assume, but I'm not sure, that declaring two dependencies like the
example below, overrides instead of stacking, but I'm not sure.
site.pp
Package {
require => Exec["global-package-setup"]
}
node 'test-node' {
include install-stuff-class
}
class install-stuff-class {
Package {
require => Exec["extra-package-setup"]
}
package { firefox:
ensure => present
}
}
In this example, I don't know if both execs are guaranteed to run before
firefox is installed.
--
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] Variable Scoping: What do you want?
On 6/30/2010 5:07 PM, Patrick Mohr wrote:
By the way, ignoring the technical aspect, how do you think defined
should work in this case? In this case, what aleart should be printed,
or what error should be printed? This is a rather contrived example, but
I'm not really sure what puppet should actually do here with your
suggestion. (Please excuse my syntax errors).
node 'test-node' {
include classA
include classB
}
class classA {
if !defined Package['apache']
{
package { 'apache':
ensure => installed,
}
alert("Package apache included by classA")
}
}
class classB {
if !defined Package['apache']
{
package { 'apache':
ensure => installed,
}
alert("Package apache included by classB")
}
}
In an ideal world, this is an invalid manifest. Especially when you add
more resources in there, that have different properties in classA vs
classB. The correct way to implement that would be to extract the
conditional resources into a common class.
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Variable Scoping: What do you want?
On 6/30/2010 10:57 AM, Matt wrote:
On 29 June 2010 17:22, Luke Kanies wrote:
Hi all,
Given the number of threads on variable scoping recently, it's pretty clear
we need to change how it works. Markus has a lot of this redone in his
futures branch, and I'm asking him to fully describe what the results will
be when that's merged, but my guess is that there are different expectations
for what people want to see.
So, my question is, what behaviour changes would you like to see in how
variable scoping works? How would you like the edge cases that are
currently hurting you to behave?
I'd like to see the ability to reference and change variables from
other classes.
class httpd { $monitor::services += 'httpd1' }
class nginx { $monitor::services += 'nginx' }
And if $monitor::services doesn't exist then it's just created with
one of the above rather than having to specify $monitor::services = []
Or use the new staging feature for ordering where I could do:
stage 1 includes class monitor { $monitor::services = [] }
stage 2 includes class httpd, nginx as above
How is $monitor::service used, that this cannot read
class httpd { monitor::service { 'httpd1': } }
class nginx { monitor::service { 'nginx': } }
?
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Variable Scoping: What do you want?
On 6/30/2010 1:47 AM, Joe McDonagh wrote:
Also, it would be *huge* to be able to append to vars. Right now I open
fw ports via a variable in the node def like:
$open_tcp_ports = "22,443"
If I could always open 22 in the node def, but += inside classes for
httpd, nfs, etc. things would be nice. I'm guessing this might be a
little difficult because all the variables in the catalog would have to
be assembled before applying the catalog.
Please model your ports as resources:
fw::port { 20: ensure => open }
Even if this only drops a concat snippet somewhere, this is brings you
so much benefits I don't know where to start.
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet-tool modules not working
Hi. I created a new module using puppet-tool, but Puppet shows following error when trying to synchronize it: README.markdown:2: syntax error ==^ /var/lib/puppet/lib/puppet/ facter/README.markdown:7: syntax error on site-specific data that just isn’t available via Facter. The ^ /var/lib/puppet/ lib/puppet/facter/README.markdown:7: Invalid char `\342' in expression /var/lib/puppet/lib/puppet/facter/README.markdown:7: Invalid char `\200' in expression /var/lib/puppet/lib/puppet/facter/ README.markdown:7: Invalid char `\231' in expression /var/lib/puppet/ lib/puppet/facter/README.markdown:9: syntax error then be distributed to Puppet clients and are available for use in ^ /var/lib/puppet/ lib/puppet/facter/README.markdown:13: syntax error /var/lib/puppet/lib/ puppet/facter/README.markdown:14: syntax error `hardware_platform`, defined like this: ^ /var/lib/puppet/lib/puppet/ facter/README.markdown:14: syntax error /var/lib/ Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded file /var/lib/puppet/lib/puppet/parser/functions/README.markdown: /var/ lib/puppet/lib/puppet/parser/functions/README.markdown:2: syntax error =^ /var/lib/puppet/lib/puppet/parser/functions/ README.markdown:6: syntax error /var/lib/puppet/lib/puppet/parser/ functions/README.markdown:7: syntax error `myfunction`, defined like this: ^ /var/lib/puppet/lib/puppet/parser/functions/ README.markdown:7: syntax error /var/lib/puppet/lib/puppet/parser/ functions/README.markdown:13: syntax error ) do |vals| ^ / var/lib/puppet/lib/puppet/parser/functions/README.markdown:17: syntax error Should be found in `myfunction.rb` in this directory. ^ /var/lib/puppet/lib/puppet/parser/ functions/README.markdown:17: syntax error Should be found in `myfunction.rb` in this directory. ^ /var/lib/puppet/lib/ puppet/parser/functions/README.markdown:17: syntax error Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded file /var/lib/puppet/lib/puppet/provider/README.markdown: /var/lib/ puppet/lib/puppet/provider/README.markdown:2: syntax error =^ /var/lib/puppet/lib/puppet/provider/README.markdown:7: syntax error example, a provider `myprovider` for a resource type `mytype`, defined like this:^ /var/lib/puppet/lib/ puppet/provider/README.markdown:7: syntax error example, a provider `myprovider` for a resource type `mytype`, defined like this: ^ /var/lib/puppet/lib/puppet/ provider/README.markdown:7: syntax error example, a provider `myprovider` for a resource type `mytype`, defined like this: ^ /var/lib/puppet/lib/puppet/provider/README.markdown:9: syntax error / var/lib/puppet/lib/puppet/provider/README.markdown:12: syntax error Jul 2 08:00:29 localhost puppetd[2893]: Could not load downloaded file /var/lib/puppet/lib/puppet/type/README.markdown: /var/lib/puppet/ lib/puppet/type/README.markdown:2: syntax error ==^ / var/lib/puppet/lib/puppet/type/README.markdown:4: syntax error Define resource types in this directory. ^ /var/lib/ puppet/lib/puppet/type/README.markdown:6: syntax error /var/lib/puppet/ lib/puppet/type/README.markdown:7: syntax error type `mytype`, defined like this:^ /var/lib/puppet/lib/puppet/ type/README.markdown:9: syntax error /var/lib/puppet/lib/puppet/type/ README.markdown:12: syntax error Any idea? Regards. -- 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] Could not retrieve information from source(s) puppet://puppet/plugins error message
Hi. After I upgraded to latest puppet, I started receiving this message both in clients and in master. Following the advice below, i create an empty stub module, with empty "lib" directory: http://projects.puppetlabs.com/issues/2244 Any idea if this is a clean solution, or there is another, better fix? Regards. -- 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.
