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
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
pac
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 co
Latest stable means two different things between the maintainers of Debian
and puppet.
On Apr 5, 2012 7:19 AM, "Christophe L" 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
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
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 s
On Apr 5, 6:11 am, 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
> differe
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 wrote:
> Hello,
>
> I have installed puppet on debian-squeeze using aptitude / apt-get but
> I got the version 2.6.2
On Apr 5, 4:47 am, Pablo Fernandez 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)
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 o
On Apr 5, 1:39 am, mac01 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
>
On Apr 4, 8:30 pm, Len Rugen 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
On Apr 4, 10:51 am, Jaakan Shorter 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
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 /op
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 '
On Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz 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 s
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 maj
On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz 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 545
On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu wrote:
> On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz 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
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
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
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
On Thu, Apr 5, 2012 at 7:06 PM, 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]
> st
On Thu, Apr 05, 2012 at 07:14:10PM +, Nan Liu wrote:
> On Thu, Apr 5, 2012 at 7:06 PM, 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 newfu
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::Pa
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.
N
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 dependin
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 puppe
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).
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/
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 wrote:
> Jo,
>
> Very good advice - Rodrick, I'd try the Learning Puppet VM to start and
> get used to the tool first. Ther
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 wrote:
> On 12-04-05 07:19 AM, Christophe
Hi All,
Hope you people are doing good.
I have a manifest file :
lass profile {
# setup profile parms. We dont handle non Ubuntu OS yet
if ("$operatingsystem" == "Ubuntu") {
file {
"/etc/profile.d":
ensure => directory,
purge => true,
33 matches
Mail list logo
