On Dec 8, 2010, at 11:09 AM, Ken Barber wrote:
> (cross posting here as I originally posted in puppet-users - I figure the
> question is more of a dev one then for puppet-users)
>
> Hi everyone,
>
> I'm experimenting with converting some of my live puppet content to
> Ruby DSL and have found a
Much appreciated, the good advice. Thanks. That makes total sense,
--
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+u
On Fri, Dec 10, 2010 at 15:00, Kevin Beckford wrote:
> So, my configuration attempts are aimed at Linodes. Ubuntu 10.10 to be exact.
> Linodes are libcloud enabled as well as basically provisioned. What I seek
> to do is add to that, not build from nothing, since libcloud et. al. give me
> a b
So, my configuration attempts are aimed at Linodes .
Ubuntu 10.10 to be exact.
Linodes are libcloud enabled as well as basically provisioned. What I
seek to do is add to that, not build from nothing, since libcloud et.
al. give me a base to work with.
What is the canonical way to manage this
Ah, What I was looking for originally was a higher level of granularity
besides modules.
Classes, in particular seems to be what I was originally seeking.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to pup
On Thu, Dec 9, 2010 at 5:38 PM, R.I.Pienaar wrote:
>
>
> On 10 Dec 2010, at 00:55, Nigel Kersten wrote:
>
>> On Thu, Dec 9, 2010 at 1:34 PM, Brice Figureau
>> wrote:
>>> On 09/12/10 21:36, Chris C wrote:
I planned on moving to Passenger very soon.
What about the file server? Is t
I get the following error:
... Failed to retrieve current state of resource: Could not retrieve
information from source(s) ...
My understanding is that the file server had trouble pulling the
metadata for the file (on the server side). This could be due to a
connectivity issue, or a permissions
On 10 Dec 2010, at 00:55, Nigel Kersten wrote:
> On Thu, Dec 9, 2010 at 1:34 PM, Brice Figureau
> wrote:
>> On 09/12/10 21:36, Chris C wrote:
>>> I planned on moving to Passenger very soon.
>>>
>>> What about the file server? Is there any worth in moving from
>>> nfs/autofs to puppet fileser
On Thu, Dec 9, 2010 at 1:34 PM, Brice Figureau
wrote:
> On 09/12/10 21:36, Chris C wrote:
>> I planned on moving to Passenger very soon.
>>
>> What about the file server? Is there any worth in moving from
>> nfs/autofs to puppet fileserver?
>
> The only reason I can see is security, access contro
On Fri, Dec 10, 2010 at 09:02, Sid wrote:
> We would like to set the txqueuelen on an ethernet interface in a
> Linux box using Puppet. Has anyone done this before?
No, though I have done other similar level things. I would very
strongly advice that you use the network tools supplied with the O
Thats good news, then. Great news, in fact!
--
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.
Hi,
We would like to set the txqueuelen on an ethernet interface in a
Linux box using Puppet. Has anyone done this before?
Sid
--
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.
On 09/12/10 21:36, Chris C wrote:
> I planned on moving to Passenger very soon.
>
> What about the file server? Is there any worth in moving from
> nfs/autofs to puppet fileserver?
The only reason I can see is security, access control and auditing.
Every access is protected through SSL, can be l
On Thu, Dec 9, 2010 at 12:12 PM, Kevin Beckford wrote:
> distribute2 is the way forward, not pip, I believe.
Distribute is taking over for setuptools for building packages. Pip
is taking over for easy_install for installing packages from the
central PyPI repository.
--
You received this messag
I planned on moving to Passenger very soon.
What about the file server? Is there any worth in moving from nfs/autofs to
puppet fileserver?
/C
On Thu, Dec 9, 2010 at 2:25 PM, Patrick wrote:
>
> On Dec 9, 2010, at 9:45 AM, Chris C wrote:
>
> > How robust and secure is the embedded fileserver i
distribute2 is the way forward, not pip, I believe.
--
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...@goog
Thanks. I did see those before. At the time of my original question, I
was looking for sets of modules, which do not seem to exist per se. The
urgency has passed, I did it by hand. This however is a terrible way to
think ;) so I am relearning puppet for the next time. I think I get it
now, what I w
On Dec 9, 2010, at 9:45 AM, Chris C wrote:
> How robust and secure is the embedded fileserver in puppet?
>
> So far my environment consists of 15 nodes with about 80 checks per node.
> I'm doing alot of md5 checks on files. I anticipate ~150 nodes. I am
> currently using autofs and the so
On 09/12/10 19:19, Patrick wrote:
>
> On Dec 9, 2010, at 10:07 AM, Brice Figureau wrote:
>
>> On 09/12/10 03:38, Daniel Pittman wrote:
>>> Sadly, no. I very much missed the feature. We ended up using the apt
>>> preferences file to implement that behaviour
>>>
>>> If I was doing it over I would u
Helpful indeed.
While reading the description, one thing puzzled me. Is it true that
"the required resource will be instantiated after the requiring
resource" when building the dependency graph model? I would have
expected it to be the other way around...
Thanks,
Kenn
--
You received this mess
On Dec 9, 2010, at 10:07 AM, Brice Figureau wrote:
> On 09/12/10 03:38, Daniel Pittman wrote:
>> Sadly, no. I very much missed the feature. We ended up using the apt
>> preferences file to implement that behaviour
>>
>> If I was doing it over I would use a define that added the package
>> resour
On Dec 9, 2010, at 9:14 AM, luke.bigum wrote:
> Interesting, I've noticed that puppet runs triggered from a daemonised
> puppetd aren't affected by the problem (as Dashboard and /var/log/
> messages says their is no errors), but when run from the command line
> as puppetd --test it fails as usual
On 09/12/10 03:38, Daniel Pittman wrote:
> Sadly, no. I very much missed the feature. We ended up using the apt
> preferences file to implement that behaviour
>
> If I was doing it over I would use a define that added the package
> resource and also used concat to automatically build up the prefer
How robust and secure is the embedded fileserver in puppet?
So far my environment consists of 15 nodes with about 80 checks per node.
I'm doing alot of md5 checks on files. I anticipate ~150 nodes. I am
currently using autofs and the source for my files is
/net/netapp/puppet/files/
Righ
Let's say I have a define in class 'foo' called 'foo::bar':
define foo::bar ($var1, $var2) {
...
}
Then I have a ruby hostclass
hostclass :foo do
...
}
I see I can successfully set the parameters by doing:
environment.known_resource_types.definitions['foo::bar'].set_arguments :
Interesting, I've noticed that puppet runs triggered from a daemonised
puppetd aren't affected by the problem (as Dashboard and /var/log/
messages says their is no errors), but when run from the command line
as puppetd --test it fails as usual for me:
err: /Stage[main]/Fh_freetds/Exec[change /etc/
On Thu, 09 Dec 2010 15:28:22 +0100
Felix Frank wrote:
> On 12/09/2010 03:12 PM, Arnau Bria wrote:
> > Hi all,
> >
> > thanks for your replies.
> >
> > So doc is confusing here:
> >
> > http://projects.puppetlabs.com/projects/1/wiki/Puppet_Templating
> > [...]
> > content => template("tr
>
> On Dec 8, 2010, at 4:13 AM, john maclean wrote:
>
>> Morning chaps,
>>
>> From my understanding the puppet master must have a hostname of
>> "puppet". Is this correct? I'd like to be able to call this box
>> whatever I like. I think that I can do that within
>> /etc/puppet/puppet.conf.
>>
>>
>>
Hi Rudy,
I'm not sure if you fixed this yet, but I ran into the same problem
using grep in an unless parameter of an exec resource.
I went looking through the Ruby code, in /usr/lib/ruby/site_ruby/1.8/
puppet/type/exec.rb on line 571. I changed these four lines:
unless FileTest.executable?
On 08-12-10 21:10, Jason Lavoie wrote:
> On 12/08, Martijn Grendelman wrote:
>> I would like to have the possibility to tell Puppet to queue the trigger,
>> and when the currently running catalog run is finished, process it and do
>> another run.
>>
>> Does this sound like a good idea?
>
> I thoug
BTWmy normal check in time is 12 secs.not 76 secs. ;)
I was running a mysql query on that box in another terminal.
/C
On Thu, Dec 9, 2010 at 9:58 AM, Chris C wrote:
> Good thinking Felix.
>
> I changed the class name to syslogngcrctesting and wahlah! the client pulls
> and applies th
Found out the error. Both the master and client were showing the same
time. But they happened to be on different time zones. AHH!
On Dec 8, 1:19 pm, Kikanny wrote:
> Hi Nan
>
> Thanks for your response. I tried that. But it says that everything is
> okay. I get "verify return 1" instead of saying
I made a small mistake. Please see at the bottom.
On 09-12-10 15:30, Martijn Grendelman wrote:
> An example: add the following to
>
> /modules//lib/facter/augeas_available.rb
>
> -- cut here --
> require 'facter'
>
> Facter.add("augeas_available") do
>
> setcode do
>
> avail = "no
Good thinking Felix.
I changed the class name to syslogngcrctesting and wahlah! the client pulls
and applies the catalog.
[r...@syslogng ~]# puppetd --test --verbose
notice: Ignoring --listen on onetime run
info: Caching catalog for syslogng.akc.org
info: Applying configuration version '129190655
Hi Felix,
> You want to include httpd, not inherit it.
>
> Or are there any resource overrides in your vhost classes? I
> shouldn't think so.
You are right. There is no reason to override the httpd class with vhost
classes.
I now include the httpd class and after that include the neccessary
vhos
On 09-12-10 09:44, Hubert Krause wrote:
> Hello,
>
> Am Wednesday 08 December 2010 22:22:10 schrieb Patrick:
>> What distro are you using?
>
> CentOS and Debian. New server will always be Debian. Our Puppet Server is
> CentOS at the moment.
>
>> Why not just install Augeas when you install pupp
On 12/09/2010 03:12 PM, Arnau Bria wrote:
> Hi all,
>
> thanks for your replies.
>
> So doc is confusing here:
>
> http://projects.puppetlabs.com/projects/1/wiki/Puppet_Templating
> [...]
> content => template("tracsite.erb"),
> [...]
Ah, but that document assumes that your templates ar
> [r...@puppetmaster manifests]# cat site.pp
> import "classes/redhat/prod/inf/syslogng/class.pp"
>
> node syslogng {
> include syslogng
> }
Maybe an issue with classname == nodename?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
Thanks for reminding me about this
[r...@puppetmaster manifests]# cat classes/redhat/prod/inf/syslogng/class.pp
class syslogng inherits all_hosts_redhat {
$dir = "redhat/prod/inf/syslogng"
file { "check_logserver":
name => "/usr/lib64/nagios/plugins/check_logserver.py",
Hi all,
thanks for your replies.
So doc is confusing here:
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Templating
[...]
content => template("tracsite.erb"),
[...]
Cheers,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group
>> What exactly do you need class inheritance for in your case? You may
>> be able to circumvent the inheritance using additional parameters.
>
> I want to assign the different virtual hosts to the nodes. By assigning
> the class for the virtual host I want to have the base configuration of
> the
Hi Frank,
> Heh - this is not at all what you originally presented.
That's right. Old problem of a developer who diggs through the problem
bit by bit and when asks a questions about a concrete detail.
> There are two different definitions of class base? This can't be
> right. Please try and illu
> class base($param1, $param2) {
> ...
> }
>
> class base {
> class first inherits base {
> }
> }
Heh - this is not at all what you originally presented.
There are two different definitions of class base? This can't be right.
Please try and illustrate the structure more pointedly.
Otherwise
Hi Felix,
> What are the versions of your master and client, btw?
I'm running the latest version 2.6.4 both on the master and the client /
agent.
Regards
Sebastian
--
*Sebastian Hempel*
Veilchenweg 4 · 95195 Röslau · Germany
eMail: sebast...@hempel-roeslau.de
--
You received this message beca
Hi Daniel,
> Can you verify that works for you? Obviously, change my node name
> to your test node name; I just wrote that to test.pp and ran 'puppet
> test.pp' to verify. :)
I copied the class and node to a file test.pp and run 'puppet test.pp'
which successfully displayed the notice.
The mech
On Thu, Dec 9, 2010 at 23:17, Arnau Bria wrote:
> content => template("baculafd.erb"); }
content => template('computing_bacula/baculafd.erb')
You need to prefix the template with the module name, which is what
puppet uses to locate it.
Regards,
Daniel
--
✣ Daniel Pi
On 12/09/2010 01:17 PM, Arnau Bria wrote:
> Hi all,
>
> I'd like to start using templates and I'm doing some test with one of
> my already working class (bacula).
>
> Following dir structure:
> module_name/manifests/init.pp
>/templates/file.erb
>
>
> my template wants to copy a file
Hi all,
I'd like to start using templates and I'm doing some test with one of
my already working class (bacula).
Following dir structure:
module_name/manifests/init.pp
/templates/file.erb
my template wants to copy a file and change a value for client hostname:
init.pp:
[...]
On 12/09/2010 11:24 AM, Sebastian Hempel wrote:
> Hello,
>
> I searched through the archive of the google group but did not found any
> solution or hint for my problem.
>
> I want to assign the following parameterized class to a node.
>
> class httpd($certMail, $certOU) {
> ...
> }
>
> This
On Thu, Dec 9, 2010 at 21:57, Sebastian Hempel
wrote:
>> Here you have cert *NO E* Mail, and later you use it with an E, so I
>> suspect a simple typo.
>
> I changed that typo - thanks - and also changed all characters to lower
> case. But the error described did not disappear.
>
> Any ideas left
Hi Daniel,
> Here you have cert *NO E* Mail, and later you use it with an E, so I
> suspect a simple typo.
I changed that typo - thanks - and also changed all characters to lower
case. But the error described did not disappear.
Any ideas left?
Best regards
Sebastian
--
*Sebastian Hempel*
Veilc
On 10/26/2010 10:46 PM, Andrew Forgue wrote:
> On Oct 26, 1:00 pm, Taylor Leese wrote:
>> Patrick,
>>
>> Any idea if people are using versions > 2.2.5 in the wild
>> successfully? I tried to revert back to 2.2.2 previously, but I
>> received a number of compilation errors when running passenger-
On Thu, Dec 9, 2010 at 21:24, Sebastian Hempel
wrote:
> Hello,
>
> I searched through the archive of the google group but did not found any
> solution or hint for my problem.
>
> I want to assign the following parameterized class to a node.
>
> class httpd($certMail, $certOU) {
Here you have cert
On 08/12/10 10:54, Adrian wrote:
> Hello everybody,
>
>
> Is there a way when installing a package like this :
>
> package { "rubygems":
> ensure => installed,
> }
>
> to pass -t parameter to apt-get in order to use a specific apt
> source ? EG : apt-get install -t lenny-backports
Try using "before" or "require" in your classes like so:
class one {
exec { "echoone":
command => "/bin/echo $var1",
before => Class["two"],
}
}
class two {
exec { "echotwo":
command => "/bin/echo $var2",
before => Class["three"],
}
}
class three {
Hello,
I searched through the archive of the google group but did not found any
solution or hint for my problem.
I want to assign the following parameterized class to a node.
class httpd($certMail, $certOU) {
...
}
This is the node statement to assign the class to a node.
node "someserver"
On Dec 8, 2010, at 11:45 PM, Felix Frank wrote:
> On 12/09/2010 05:13 AM, Patrick wrote:
>>
>> On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
>>
>>> Sadly, no. I very much missed the feature. We ended up using the apt
>>> preferences file to implement that behaviour
>>>
>>> If I was doing i
Hello,
Am Wednesday 08 December 2010 22:22:10 schrieb Patrick:
> What distro are you using?
CentOS and Debian. New server will always be Debian. Our Puppet Server is
CentOS at the moment.
> Why not just install Augeas when you install puppet? That's usually much
> easier.
Yes, but I want some
On 12/07/2010 08:52 PM, Douglas Garstang wrote:
> If I'm pushing out a bunch of files in a directory, like this...
>
> file {
> "/usr/local/lg/bin/":
> source => "puppet://${server}/usr/local/lg/bin",
> mode => 755,
> owner => "root",
> group
59 matches
Mail list logo
