[Puppet Users] Customizing a hostname facts
Hi,
I am trying to override a hostname.rp from path: *
/usr/lib/ruby/site_ruby/1.8/facter* as,
Facter.add(:hostname) do
confine :hostname = serialnumber
setcode do
Facter::Util::Resolution.exec('cat /sys/power/states')
end
end
Is the fact code correct as I want puppet to pick serialnumber instead of
hostname from facter ?
Thanks
mac01
--
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/-/dPw-mMSTV04J.
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] multiple resources dependencies
Dear all,
I have a class where I declare one file and many execs with
create_resources:
class module::yeah {
file {myfile}
$hash = parseyaml(inline_template('hereigeneratemynicehash.to_yaml'))
create_resources ('exec', $hash)
}
And I need to create a dependency of the kind inside that class:
File[myfile] - Exec[*]
I have tried setting require = File['myfile'] inside my template, but
File is not recognized inside the template. And if I quote it, Puppet
does not recognize it as a File resource.
Do you guys see a way how I can create the dependency?
Thanks!
Pablo
--
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: 2 package resources for the same package installation in two differents modules caused errors
Hello,
Thanks for your answer.
I understand the restriction about resource name uniqueness, but I
don't understand the practical usage of it on the package resources.
Let's say there is two modules totally different, written by two
different developpers, but both depending on the same debian
package :
the two developper wills use the simplified syntax of the package
resource such package { MODULE_NAME : ensure = installed }, like we
can see it on usual puppet sample on internet.
Then, when an administrator will include the two modules, it will fail
because the same package is defined twice, even if the description of
the resource is exactly the same.
It doesn't sound as a normal behavior to me, unless if a best practice
is to never use the simplified syntax for package resource ?
Or is there an other best practice for avoiding this situation ?
Thanks in advance for your answers.
Best regards.
Christophe
On 4 avr, 00:15, Miguel Di Ciurcio Filho miguel.fi...@gmail.com
wrote:
On Tue, Apr 3, 2012 at 3:33 PM, Christophe L cl.subscript...@gmail.com
wrote:
Hello,
We had the following situation where including two classes that were
ensuring the installation of the same package php5-imagick and it
was causing an error indicating that two ressources of the same name
are forbidden (sorry, I don't have the exact message error since we
fixed quickly the error).
By the nature of the Puppet's language, resources must have a unique
title and must have only one definition.
Quotinghttp://docs.puppetlabs.com/guides/language_guide.html#resources:
The field before the colon is the resource’s title, which must be
unique and can be used to refer to the resource in other parts of the
Puppet configuration.
Code causing the error:
/etc/puppet/modules/apache/manifests/init.pp
class apache::install {
...
package { [ php5, php5-cli, php5-gd, php5-imagick, php5-
mysql, phpmyadmin, mysql-client ]:
ensure = installed,
}
The line above is just a shortcut to this something like this:
package {php5: }
package {php5-cli: }
package {php5-imagick: }
So when Puppet compiles all your manifests, there can be only one
php5-imagick, in your case.
--
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] Why latest stable Debian Squeeze package is 2.6.2-5+squeeze4 please ?
Hello, I have installed puppet on debian-squeeze using aptitude / apt-get but I got the version 2.6.2 of Puppet. After some research, I have found that the last stable debian package version is puppet (2.6.2-5+squeeze4) [security] http://packages.debian.org/squeeze/puppet and that 2.7.12-3 is considered as unstable http://packages.qa.debian.org/p/puppet.html But on the puppet documentation, it is written that The latest stable release is 2.7.12 The latest maintenance release is 2.6.14 Could you explain me the reason why the latest stable release of puppet is considered as unstable on debian squeeze please ? Is there a way to install puppet 2.7.12 on debian squeeze and what are the risks if I do so please ? Thanks in advance for your answers Best regards, Christophe -- 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] Why latest stable Debian Squeeze package is 2.6.2-5+squeeze4 please ?
Latest stable means two different things between the maintainers of Debian and puppet. On Apr 5, 2012 7:19 AM, Christophe L cl.subscript...@gmail.com wrote: Hello, I have installed puppet on debian-squeeze using aptitude / apt-get but I got the version 2.6.2 of Puppet. After some research, I have found that the last stable debian package version is puppet (2.6.2-5+squeeze4) [security] http://packages.debian.org/squeeze/puppet and that 2.7.12-3 is considered as unstable http://packages.qa.debian.org/p/puppet.html But on the puppet documentation, it is written that The latest stable release is 2.7.12 The latest maintenance release is 2.6.14 Could you explain me the reason why the latest stable release of puppet is considered as unstable on debian squeeze please ? Is there a way to install puppet 2.7.12 on debian squeeze and what are the risks if I do so please ? Thanks in advance for your answers Best regards, Christophe -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: 2 package resources for the same package installation in two differents modules caused errors
Hi,
The best way to overcome the problem you're experiencing, is to use virtual
resources
http://docs.puppetlabs.com/guides/virtual_resources.html
So, for example, you would have a class that declares the resources:
class php_v_packages {
@package { [ php5, php5-cli, php5-gd, php5-imagick, php5-
mysql, phpmyadmin, mysql-client ]:
ensure = installed,
}
}
and when you need to use those virtual packages, include that class, and
realize the resources:
class apache::install {
include php_v_packages
realize Package [ [ php5], [php5-cli], [php5-gd], [php5-imagick]]
}
class cms::installpackage {
include php_v_packages
realize Package [php5-imagick]
}
That should do the trick :)
Cheers,
Andrew
On Thursday, April 5, 2012 12:11:40 PM UTC+1, Christophe L wrote:
Hello,
Thanks for your answer.
I understand the restriction about resource name uniqueness, but I
don't understand the practical usage of it on the package resources.
Let's say there is two modules totally different, written by two
different developpers, but both depending on the same debian
package :
the two developper wills use the simplified syntax of the package
resource such package { MODULE_NAME : ensure = installed }, like we
can see it on usual puppet sample on internet.
Then, when an administrator will include the two modules, it will fail
because the same package is defined twice, even if the description of
the resource is exactly the same.
It doesn't sound as a normal behavior to me, unless if a best practice
is to never use the simplified syntax for package resource ?
Or is there an other best practice for avoiding this situation ?
Thanks in advance for your answers.
Best regards.
Christophe
On 4 avr, 00:15, Miguel Di Ciurcio Filho miguel.fi...@gmail.com
wrote:
On Tue, Apr 3, 2012 at 3:33 PM, Christophe L cl.subscript...@gmail.com
wrote:
Hello,
We had the following situation where including two classes that were
ensuring the installation of the same package php5-imagick and it
was causing an error indicating that two ressources of the same name
are forbidden (sorry, I don't have the exact message error since we
fixed quickly the error).
By the nature of the Puppet's language, resources must have a unique
title and must have only one definition.
Quotinghttp://docs.puppetlabs.com/guides/language_guide.html#resources:
The field before the colon is the resource’s title, which must be
unique and can be used to refer to the resource in other parts of the
Puppet configuration.
Code causing the error:
/etc/puppet/modules/apache/manifests/init.pp
class apache::install {
...
package { [ php5, php5-cli, php5-gd, php5-imagick, php5-
mysql, phpmyadmin, mysql-client ]:
ensure = installed,
}
The line above is just a shortcut to this something like this:
package {php5: }
package {php5-cli: }
package {php5-imagick: }
So when Puppet compiles all your manifests, there can be only one
php5-imagick, in your case.
--
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/-/fnts8JOMwnIJ.
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] Somehow puppet is not able to start ossec service
Hi Friends, I have configured Puppet 2.7.12-1 on Centos 6 as server and various clients running on Redhat/Centos/Ubuntu etc.. The issue I am facing is that somehow Puppet is not able to start the ossec service on the client. If the service is stopped on the client then puppet is not able to start the service. Below are the logs of the Puppet client running on the Centos 5 machine. puppetd --test --server puppetmaster-del.example.com --debug debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Failed to load library 'rubygems' for feature 'rubygems' debug: Failed to load library 'selinux' for feature 'selinux' debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private]: 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/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/puppet] debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/linuxbackup-del4.synapse.com.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys/linuxbackup-del4.synapse.com.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/ssl/certs/linuxbackup-del4.synapse.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction -607017838 debug: /File[/var/lib/puppet/ssl/private]: 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/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys/linuxbackup-del4.synapse.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/certs/linuxbackup-del4.synapse.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/puppet] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/linuxbackup-del4.synapse.com.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: Finishing transaction -607864488 debug: Using cached certificate for ca debug: Using cached certificate for
[Puppet Users] Re: 2 package resources for the same package installation in two differents modules caused errors
On Apr 5, 6:11 am, Christophe L cl.subscript...@gmail.com wrote:
Hello,
Thanks for your answer.
I understand the restriction about resource name uniqueness, but I
don't understand the practical usage of it on the package resources.
Let's say there is two modules totally different, written by two
different developpers, but both depending on the same debian
package :
the two developper wills use the simplified syntax of the package
resource such package { MODULE_NAME : ensure = installed }, like we
can see it on usual puppet sample on internet.
Then, when an administrator will include the two modules, it will fail
because the same package is defined twice, even if the description of
the resource is exactly the same.
It doesn't sound as a normal behavior to me, unless if a best practice
is to never use the simplified syntax for package resource ?
Or is there an other best practice for avoiding this situation ?
Expanding somewhat on Andrew's response:
From a conceptual perspective, if two separate and independent modules
both require the same package, then clearly it is incorrect to model
that package as belonging to or being the responsibility of either
module. It is a more fundamental resource than either module
represents, else you would not have such a conflict in the first
place.
The correct solution, both conceptually and practically, is to manage
the package via a separate module that both of the others rely upon.
In your particular case, it looks like it would be very natural to
create and use a php or php5 module to manage all the PHP
packages. Your apache and cms modules would then both depend on
the new php module to ensure that the needed packages were
installed.
At the manifest level, suppose you put all the PHP package
declarations in class php::packages. Then both apache::install
and cms::installpackage would put this line at the beginning of
their bodies:
include php::packages
IMPORTANT: Puppet's 'include' function is *not* analogous to the C
preprocessor's #include directive: it does not interpolate anything.
It's much closer to Python's 'import' statement, which makes Python
modules visible to other Python modules.
If you don't necessarily need all of the PHP packages for every PHP
user, as it appears may be the case, then you can additionally declare
the PHP packages virtually in php::packages. Then, after
'include'ing php::packages, your other modules would also 'realize'
the packages they need.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Why latest stable Debian Squeeze package is 2.6.2-5+squeeze4 please ?
You can try the Debian packages at http://apt.puppetlabs.com/ to see if the Squeeze ones are more up to date (they will be, I think!) On Thu, Apr 5, 2012 at 7:19 AM, Christophe L cl.subscript...@gmail.comwrote: Hello, I have installed puppet on debian-squeeze using aptitude / apt-get but I got the version 2.6.2 of Puppet. After some research, I have found that the last stable debian package version is puppet (2.6.2-5+squeeze4) [security] http://packages.debian.org/squeeze/puppet and that 2.7.12-3 is considered as unstable http://packages.qa.debian.org/p/puppet.html But on the puppet documentation, it is written that The latest stable release is 2.7.12 The latest maintenance release is 2.6.14 Could you explain me the reason why the latest stable release of puppet is considered as unstable on debian squeeze please ? Is there a way to install puppet 2.7.12 on debian squeeze and what are the risks if I do so please ? Thanks in advance for your answers Best regards, Christophe -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: multiple resources dependencies
On Apr 5, 4:47 am, Pablo Fernandez pablo.fernan...@cscs.ch wrote:
Dear all,
I have a class where I declare one file and many execs with
create_resources:
class module::yeah {
file {myfile}
$hash = parseyaml(inline_template('hereigeneratemynicehash.to_yaml'))
create_resources ('exec', $hash)
}
And I need to create a dependency of the kind inside that class:
File[myfile] - Exec[*]
I have tried setting require = File['myfile'] inside my template, but
File is not recognized inside the template. And if I quote it, Puppet
does not recognize it as a File resource.
Do you guys see a way how I can create the dependency?
I see at least two possibilities:
1) Use resource chaining and tag-selected collections:
1a) either automatic tags: File[myfile] - Exec| tag =
'module::yeah' |
1b) or manual tags: File[myfile] - Exec| tag = 'tag-I-explicitly-
declared-via-my-hash' |
2) Use resource defaults:
class module::yeah {
file { 'myfile': }
# I think this is scoped to the class:
Exec { require = File['myfile'] }
$hash =
parseyaml(inline_template('hereigeneratemynicehash.to_yaml'))
create_resources ('exec', $hash)
}
Test these, of course. I am uncertain whether create_resources() has
different semantics in these cases than would ordinary resource
declarations.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: multiple resources dependencies
Hi John,
I like option 2) very much, but 1) opens new doors too :)
A small extract from the manual, just for clarification:
Defaults are not global — they only affect the current scope and
scopes below the current one. If you want a default setting to affect
your entire configuration, your only choice currently is to specify them
outside of any class.
I've tested it, and it seems to work fine. Thanks!
BR/Pablo
On 04/05/2012 03:01 PM, jcbollinger wrote:
On Apr 5, 4:47 am, Pablo Fernandezpablo.fernan...@cscs.ch wrote:
Dear all,
I have a class where I declare one file and many execs with
create_resources:
class module::yeah {
file {myfile}
$hash = parseyaml(inline_template('hereigeneratemynicehash.to_yaml'))
create_resources ('exec', $hash)
}
And I need to create a dependency of the kind inside that class:
File[myfile] - Exec[*]
I have tried setting require = File['myfile'] inside my template, but
File is not recognized inside the template. And if I quote it, Puppet
does not recognize it as a File resource.
Do you guys see a way how I can create the dependency?
I see at least two possibilities:
1) Use resource chaining and tag-selected collections:
1a) either automatic tags: File[myfile] - Exec| tag =
'module::yeah' |
1b) or manual tags: File[myfile] - Exec| tag = 'tag-I-explicitly-
declared-via-my-hash' |
2) Use resource defaults:
class module::yeah {
file { 'myfile': }
# I think this is scoped to the class:
Exec { require = File['myfile'] }
$hash =
parseyaml(inline_template('hereigeneratemynicehash.to_yaml'))
create_resources ('exec', $hash)
}
Test these, of course. I am uncertain whether create_resources() has
different semantics in these cases than would ordinary resource
declarations.
John
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Customizing a hostname facts
On Apr 5, 1:39 am, mac01 smilemukul2...@gmail.com wrote:
Hi,
I am trying to override a hostname.rp from path: *
/usr/lib/ruby/site_ruby/1.8/facter* as,
Facter.add(:hostname) do
confine :hostname = serialnumber
setcode do
Facter::Util::Resolution.exec('cat /sys/power/states')
end
end
Is the fact code correct as I want puppet to pick serialnumber instead of
hostname from facter ?
You are trying to confine the 'hostname' fact based on the value of
that same fact. I don't see how that could possibly work. Either it
will throw Facter into an infinite loop, or that version of the fact
will just never be chosen.
There is probably a better approach to your problem than redefining
the hostname fact. Not knowing what your actual problem is, I can
only speculate, but you might be better off creating and using a
serialnumber custom fact. You might also want to look into Puppet's
certname parameter.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: change host file depending on location
On Apr 4, 8:30 pm, Len Rugen lenru...@gmail.com wrote: We run Foreman, so I never think of parameterized classes :-) My esteem for Foreman has just gone up a notch. :) John -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: using content in file as input variables to a class/def?
On Apr 4, 10:51 am, Jaakan Shorter jaakanshor...@gmail.com wrote:
Here is the setup
Clients are all under /usr/home/ftp/$client
Internal Production is /usr/home/$internaluser
I need to make slinks for every client folder under every Internal
Production ie: ln -s /usr/home/ftp/$client /usr/home/$internaluser/$client
Is there a way to do this from a list with in two files ( one for client
name and the other for internal user names)? where the list format would be
like : username, uid
Supposing that you want to manage these links directly via Puppet
(instead of, for instance, via a script on each node) then you could
do something like this:
class ftp::data {
# More on these arrays later
$clientnames = ...
$internalusers = ...
}
define ftp::internaluserclientdir($internaluser) {
file { /usr/home/${internaluser}/${name}:
ensure = 'link',
target = /usr/home/ftp/${name}
}
}
define ftp::internaluser() {
include 'ftp::data'
file { /usr/home/${name}:
ensure = 'directory',
# ...
}
ftp::internaluserclientdir { ${ftp::data::clientnames}:
internaluser = ${name}
}
}
class ftp::clientdirs {
include 'ftp::data'
ftp::internaluser { ${ftp::data::internalusers}: }
}
Note that that manages the internal user directories themselves (which
you did not specify), but that's optional. On the other hand, it does
not manage the actual client directories, though it could be made to
do.
Now, as to the actual source of the data. If using a Puppet manifest
is an acceptable embodiment of storing the data in a file, then you
can just define the needed arrays directly in class ftp::data. It's
usually better, however, to pull the data out of your manifests, in
which case you should be looking at hiera. In that case the variable
declarations in class ftp::data would use hiera to load their array
values, or else class ftp::data could be dropped altogether, and
your other classes could call hiera directly to get the data.
John
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Update
I now have it listed in the console but I am now getting new errors err Could not retrieve catalog; skipping runPuppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param 'undef' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node agent Puppet 2012-04-05 10:22 EDT notice Using cached catalogPuppet 2012-04-05 10:22 EDT infoNot using expired catalog for agent from cache; expired at 2012-04-04 12:51:17 -0500 Puppet 2012-04-05 10:22 EDT debug catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using psonPuppet 2012-04-05 10:21 EDT -- 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] Re: HP-UX Puppet Agent
On Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz mfgl...@gmail.com wrote: I now have it communicate regularly between master and client but I am now getting some reporting issues. err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param 'undef' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node hpoktst3.ddmi.intra.renhsc.com Puppet 2012-04-05 10:22 EDT You are connecting a puppet agent to a puppet enterprise master. The pe_mcollective module needs a list of facts provided by the enterprise installer. If you look at /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt, you'll see the list of facts. Since the puppet installation was done from source, the system is also are missing mcollective and it's dependencies. I would remove the system from the default group in the puppet enterprise console so the pe_* modules are not part of the node. Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: HP-UX Puppet Agent
Removing the default group worked for the most part but I am still running into some issues It cataloged correctly and even ran the test class I created notice: Starting Puppet client version 2.7.12 debug: Finishing transaction 545631632 debug: Loaded state in 0.00 seconds processor - invalid major number usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c char_major] [-e major] [major] ... uname: illegal option -- p usage: uname [-amnrsvil] [-S nodename] debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent debug: Using cached certificate_revocation_list for ca info: Caching catalog for agent debug: Creating default schedules debug: Loaded state in 0.00 seconds info: Applying configuration version '1333637360' debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group changed 'sys' to 'root' debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: created debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group changed 'sys' to 'root' notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode changed '0444' to '0644' debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: Class[Core_permissions]: The container Stage[main] will propagate my refresh event debug: /Schedule[never]: Skipping device resources because running on a host debug: /Schedule[weekly]: Skipping device resources because running on a host debug: /Schedule[puppet]: Skipping device resources because running on a host debug: Finishing transaction 549485440 debug: Storing state debug: Stored state in 0.04 seconds notice: Finished catalog run in 0.11 seconds debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml I am now receiving this issue again mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT undefined method `each' for nil:NilClass Backtrace /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extend' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extended' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `extend' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `create_from_yaml' /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in `create_from_yaml_file' Also it automatically added the node back to default, anyway to prevent that? On Apr 5, 10:45 am, Nan Liu n...@puppetlabs.com wrote: On Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz mfgl...@gmail.com wrote: I now have it communicate regularly between master and client but I am now getting some reporting issues. err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param 'undef' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node hpoktst3.ddmi.intra.renhsc.com Puppet 2012-04-05 10:22 EDT You are connecting a puppet agent to a puppet enterprise master. The pe_mcollective module needs a list of facts provided by the enterprise installer. If you look at /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt, you'll see the list of facts. Since the puppet installation was done from source, the system is also are missing mcollective and it's dependencies. I would remove the system from the default group in the puppet enterprise console so the pe_* modules are not part of the node. Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: HP-UX Puppet Agent
On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz mfgl...@gmail.com wrote: Removing the default group worked for the most part but I am still running into some issues It cataloged correctly and even ran the test class I created notice: Starting Puppet client version 2.7.12 debug: Finishing transaction 545631632 debug: Loaded state in 0.00 seconds processor - invalid major number usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c char_major] [-e major] [major] ... uname: illegal option -- p usage: uname [-amnrsvil] [-S nodename] debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent debug: Using cached certificate_revocation_list for ca info: Caching catalog for agent debug: Creating default schedules debug: Loaded state in 0.00 seconds info: Applying configuration version '1333637360' debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group changed 'sys' to 'root' debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: created debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group changed 'sys' to 'root' notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode changed '0444' to '0644' debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: Class[Core_permissions]: The container Stage[main] will propagate my refresh event debug: /Schedule[never]: Skipping device resources because running on a host debug: /Schedule[weekly]: Skipping device resources because running on a host debug: /Schedule[puppet]: Skipping device resources because running on a host debug: Finishing transaction 549485440 debug: Storing state debug: Stored state in 0.04 seconds notice: Finished catalog run in 0.11 seconds debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml I am now receiving this issue again mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT undefined method `each' for nil:NilClass Backtrace /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extend' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extended' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `extend' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `create_from_yaml' /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in `create_from_yaml_file' If you are using ruby 1.9.1, it is known to be problematic: http://docs.puppetlabs.com/guides/faq.html Also it automatically added the node back to default, anyway to prevent that? Looks like there's a background task automatically adding nodes. I don't know a good way around this issue. You can move the pe-* class to another group but you will need to manually add nodes to that group afterwards. HTH, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: HP-UX Puppet Agent
On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu n...@puppetlabs.com wrote: On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz mfgl...@gmail.com wrote: Removing the default group worked for the most part but I am still running into some issues It cataloged correctly and even ran the test class I created notice: Starting Puppet client version 2.7.12 debug: Finishing transaction 545631632 debug: Loaded state in 0.00 seconds processor - invalid major number usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c char_major] [-e major] [major] ... uname: illegal option -- p usage: uname [-amnrsvil] [-S nodename] debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for agent debug: Using cached certificate_revocation_list for ca info: Caching catalog for agent debug: Creating default schedules debug: Loaded state in 0.00 seconds info: Applying configuration version '1333637360' debug: /Schedule[daily]: Skipping device resources because running on a host debug: /Schedule[monthly]: Skipping device resources because running on a host debug: /Schedule[hourly]: Skipping device resources because running on a host notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group changed 'sys' to 'root' debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: created debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container Class[Core_permissions] will propagate my refresh event notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group changed 'sys' to 'root' notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode changed '0444' to '0644' debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container Class[Core_permissions] will propagate my refresh event debug: Class[Core_permissions]: The container Stage[main] will propagate my refresh event debug: /Schedule[never]: Skipping device resources because running on a host debug: /Schedule[weekly]: Skipping device resources because running on a host debug: /Schedule[puppet]: Skipping device resources because running on a host debug: Finishing transaction 549485440 debug: Storing state debug: Stored state in 0.04 seconds notice: Finished catalog run in 0.11 seconds debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using yaml I am now receiving this issue again mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT undefined method `each' for nil:NilClass Backtrace /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `extended' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extend' /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in `extended' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `extend' /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in `create_from_yaml' /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in `create_from_yaml_file' If you are using ruby 1.9.1, it is known to be problematic: http://docs.puppetlabs.com/guides/faq.html Also it automatically added the node back to default, anyway to prevent that? Looks like there's a background task automatically adding nodes. I don't know a good way around this issue. You can move the pe-* class to another group but you will need to manually add nodes to that group afterwards. There's a cron job that calls a rake task that will automatically add nodes that it knows about to the default group. You will most likely need to A) move the offending classes out of the default group as Nan suggests, or B) disable the cron job and manually add new nodes to the appropriate groups, or C) write a new cron job/rake task that will only add the nodes you want. See /etc/cron.d/default-add-all-nodes on your PE console node. - Justin HTH, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send
Re: [Puppet Users] openstack-puppet mailing list
Will you get the google group listed on news.gmane.org to enable reading via news/nntp ? Regards - henrik On 2012-05-04 6:23, Dan Bode wrote: Hi all, I have been working to create a community around a set of modules for configuring and deploying OpenStack. For folks who are interested in our openstack efforts, I created a separate mailing list. http://groups.google.com/group/puppet-openstack I plan to be pretty verbose about the code as it progresses and I didn't want to flood the puppet users group with openstack specific messages. - Dan -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Why latest stable Debian Squeeze package is 2.6.2-5+squeeze4 please ?
On 12-04-05 07:19 AM, Christophe L wrote: After some research, I have found that the last stable debian package version is puppet (2.6.2-5+squeeze4) [security] http://packages.debian.org/squeeze/puppet and that 2.7.12-3 is considered as unstable http://packages.qa.debian.org/p/puppet.html In Debian's release cycle, the packages are freezed before a release. when this happens it means that package versions that are currently in the testing branch will be used for the next debian release, and will be used until the next release. the stable part in all that is the debian branch name that represents the current release, so what software they support. security patches will be backported to 2.6 as much as possible for as long as the current stable branch is the current one. for now, you can use the squeeze-backports[1] branch, in which you can find puppet 2.7 [1]: http://backports-master.debian.org/Instructions/ -- Gabriel Filion -- 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] newly added ruby function executes on the server instead of the node
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do |args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
--
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/-/2-Z1S6Xci2IJ.
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] newly added ruby function executes on the server instead of the node
On Thu, Apr 5, 2012 at 7:06 PM, vicki vickiko...@gmail.com wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
module Puppet::Parser::Functions newfunction(:write_line_to_file) do |args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}
The function does execute, but on the puppetmaster - not on the remote node.
Other two functions execute on the correct node. What am I missing?
Functions run on puppet master, facts and resource provider run on
puppet agent. Writing functions won't allow you to change puppet agent
files (unless you clone module and run puppet apply). If you are
trying to write line to a file either use augeas type or puppet
file_line from stdlib:
http://forge.puppetlabs.com/puppetlabs/stdlib
HTH,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] newly added ruby function executes on the server instead of the node
On Thu, Apr 05, 2012 at 07:14:10PM +, Nan Liu wrote:
On Thu, Apr 5, 2012 at 7:06 PM, vicki vickiko...@gmail.com wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
module Puppet::Parser::Functions newfunction(:write_line_to_file) do |args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}
The function does execute, but on the puppetmaster - not on the remote node.
Other two functions execute on the correct node. What am I missing?
Functions run on puppet master, facts and resource provider run on
puppet agent. Writing functions won't allow you to change puppet agent
files (unless you clone module and run puppet apply). If you are
trying to write line to a file either use augeas type or puppet
file_line from stdlib:
http://forge.puppetlabs.com/puppetlabs/stdlib
For more complicated things than a single line in a file (like RedHat-
style network configs), I've had success with using a template to emit
YAML and then having a puppetized script on the node execute to
complete the configuration. It's a half-decent way of puppetizing an
arbitrary number of files at once.
HTH,
Nan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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: newly added ruby function executes on the server instead of the node
Thank you for the quick reply! This explains the the behavior I see.
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do
|args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do
|args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do
|args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do
|args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
/etc/puppet/modules/write_line_to_file/lib/puppet/parser/functions/write_line_to_file.rb
:
*module Puppet::Parser::Functions newfunction(:write_line_to_file) do
|args|
filename = args[0]
str = args[1]
File.open(args[0], 'a') {|fd| fd.puts str }
end
end*
2) I invoked it in the
/etc/puppet/modules/write_line_to_file/manifest/init.pp like this:
*class write_line_to_file{
write_line_to_file('/tmp/some_file', Hello world!)
}*
3) And I also included this module into my /etc/puppet/manifests/nodes.pp
under the correct node:
*node default {}
node 'testnode.domain.com'
{
include hosts
include uninstall_screen
include write_line_to_file
}*
*
*The function does execute, but on the puppetmaster - not on the remote
node. Other two functions execute on the correct node. What am I missing?
Thank you!
Vicki
On Thursday, April 5, 2012 12:06:00 PM UTC-7, vicki wrote:
Hi,
1) I added this test function tom my
[Puppet Users] Getting started
I really hate poor documentation. I'm following along in PDF documentation I downloaded from the official site and I'm stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. Now where do I find an working example of puppetmaster.conf ? Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ? Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? I'm almost fed-up already and I've not even gotten 1 agent configured to talk to my sever Puppet seems way too clumber some with the amount of dependencies required so far. I almost feel like going back to hacking on my system based on Python Fabric :( --RB Please visit our website for important disclaimers/disclosures regarding Knight's products and services: http://knight.com/KnightEmailDisclaimer.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-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] Getting started
You've probably gone about this the hard way. It would be best to just get the server running without passenger and learn Puppet itself. You only need passenger when you exceed 50-100 systems. Anyway, to answer your questions the config.ru is available in share/puppet (exactly where depending on your OS), and puppetmaster.conf should have been installed when the gem/rpm was installed. But you should probably be using the docs on www.puppetlabs.com rather than the PDF, I suspect they are kept more up to date. On Apr 5, 2012, at 1:42 PM, Brown, Rodrick wrote: I really hate poor documentation. I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. Now where do I find an working example of puppetmaster.conf ? Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ? Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever Puppet seems way too clumber some with the amount of dependencies required so far. I almost feel like going back to hacking on my system based on Python Fabric L --RB Please visit our website for important disclaimers/disclosures regarding Knight’s products and services: http://knight.com/KnightEmailDisclaimer.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-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. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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] Getting started
In your position I would apt-get install puppet and then try out some manifests before running my own puppetmaster. Then I would apt-get install puppetmaster or something similar. Personally I have never installed from gems and I've been just fine. (Or pkg_add -r puppet or yum install puppet etc. etc.) On Thu, Apr 05, 2012 at 04:42:57PM -0400, Brown, Rodrick wrote: I really hate poor documentation. I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. Now where do I find an working example of puppetmaster.conf ? Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ? Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever Puppet seems way too clumber some with the amount of dependencies required so far. I almost feel like going back to hacking on my system based on Python Fabric L --RB Please visit our website for important disclaimers/disclosures regarding Knight’s products and services: http://knight.com/KnightEmailDisclaimer.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-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.
Re: [Puppet Users] Getting started
It might also be helpful to include your O/S, here ... as there are many linuxes where installing puppet can largely be reduced to installing the right RPMs out of one repository or another (so you worry less about compiling and manufacturing basic configs than just learning how to make puppet go). On Thu, Apr 5, 2012 at 1:42 PM, Brown, Rodrick rbr...@knight.com wrote: I really hate poor documentation. ** ** I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. ** ** Now where do I find an working example of puppetmaster.conf ? Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ? ** ** Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? ** ** I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever ** ** Puppet seems way too clumber some with the amount of dependencies required so far. ** ** I almost feel like going back to hacking on my system based on Python Fabric L ** ** --RB Please visit our website for important disclaimers/disclosures regarding Knight’s products and services: http://knight.com/KnightEmailDisclaimer.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-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.
Re: [Puppet Users] Getting started
Jo, Very good advice - Rodrick, I'd try the Learning Puppet VM to start and get used to the tool first. There's an excellent Learning Puppet doc as well - http://docs.puppetlabs.com/learning/ That should get you started. -Eric -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Thursday, April 5, 2012 at 5:14 PM, Jo Rhett wrote: You've probably gone about this the hard way. It would be best to just get the server running without passenger and learn Puppet itself. You only need passenger when you exceed 50-100 systems. Anyway, to answer your questions the config.ru (http://config.ru) is available in share/puppet (exactly where depending on your OS), and puppetmaster.conf should have been installed when the gem/rpm was installed. But you should probably be using the docs on www.puppetlabs.com (http://www.puppetlabs.com) rather than the PDF, I suspect they are kept more up to date. On Apr 5, 2012, at 1:42 PM, Brown, Rodrick wrote: I really hate poor documentation. I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. Now where do I find an working example of puppetmaster.conf ? Which config.ru (http://config.ru) should I be coping into /usr/share/puppet/rack/puppetmasterd ? Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever Puppet seems way too clumber some with the amount of dependencies required so far. I almost feel like going back to hacking on my system based on Python Fabric L --RB Please visit our website for important disclaimers/disclosures regarding Knight’s products and services: http://knight.com/KnightEmailDisclaimer.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-users@googlegroups.com (mailto:puppet-users@googlegroups.com). To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com (mailto:puppet-users+unsubscr...@googlegroups.com). For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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 (mailto:puppet-users@googlegroups.com). To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com (mailto: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.
Re: [Puppet Users] Getting started
I have to say I find the online documentation very helpful indeed... along with github once you get working with the module. On Thu, Apr 5, 2012 at 10:26 PM, Eric Shamow e...@puppetlabs.com wrote: Jo, Very good advice - Rodrick, I'd try the Learning Puppet VM to start and get used to the tool first. There's an excellent Learning Puppet doc as well - http://docs.puppetlabs.com/learning/ That should get you started. -Eric -- Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Thursday, April 5, 2012 at 5:14 PM, Jo Rhett wrote: You've probably gone about this the hard way. It would be best to just get the server running without passenger and learn Puppet itself. You only need passenger when you exceed 50-100 systems. Anyway, to answer your questions the config.ru is available in share/puppet (exactly where depending on your OS), and puppetmaster.conf should have been installed when the gem/rpm was installed. But you should probably be using the docs on www.puppetlabs.com rather than the PDF, I suspect they are kept more up to date. On Apr 5, 2012, at 1:42 PM, Brown, Rodrick wrote: I really hate poor documentation. ** ** I’m following along in PDF documentation I downloaded from the official site and I’m stuck after I installed rack passenger modules from rubygems. I ran the passenger build script and it compiled and installed into my local apache httpd server successfully. ** ** Now where do I find an working example of puppetmaster.conf ? Which config.ru should I be coping into /usr/share/puppet/rack/puppetmasterd ? ** ** Is there a guide on generate the pem files required for use when defining the virtual host settings in puppetmaster? ** ** I’m almost fed-up already and I’ve not even gotten 1 agent configured to talk to my sever ** ** Puppet seems way too clumber some with the amount of dependencies required so far. ** ** I almost feel like going back to hacking on my system based on Python Fabric L ** ** --RB Please visit our website for important disclaimers/disclosures regarding Knight’s products and services: http://knight.com/KnightEmailDisclaimer.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-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. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Why latest stable Debian Squeeze package is 2.6.2-5+squeeze4 please ?
Thank you all for your answers ! As a suggestion for the documentation, that would be nice to have information about the http://apt.puppetlabs.com/ apt repository on the puppet installation page. Best regards, Christophe On 5 avr, 20:58, Gabriel Filion lelu...@gmail.com wrote: On 12-04-05 07:19 AM, Christophe L wrote: After some research, I have found that the last stable debian package version is puppet (2.6.2-5+squeeze4) [security] http://packages.debian.org/squeeze/puppet and that 2.7.12-3 is considered as unstable http://packages.qa.debian.org/p/puppet.html In Debian's release cycle, the packages are freezed before a release. when this happens it means that package versions that are currently in the testing branch will be used for the next debian release, and will be used until the next release. the stable part in all that is the debian branch name that represents the current release, so what software they support. security patches will be backported to 2.6 as much as possible for as long as the current stable branch is the current one. for now, you can use the squeeze-backports[1] branch, in which you can find puppet 2.7 [1]:http://backports-master.debian.org/Instructions/ -- Gabriel Filion -- 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.
