On 27.06.2013 12:16, DEGREMONT Aurelien wrote:
Le 27/06/2013 03:38, Nigel Kersten a écrit :
On Wed, Jun 26, 2013 at 9:41 AM, Nan Liu nan@gmail.com
mailto:nan@gmail.com wrote:
On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien
aurelien.degrem...@cea.fr
On Thursday, June 27, 2013 1:30:42 PM UTC-5, Vasiliy Boulytchev wrote:
Sir, have you been able to find a solution?
The approach the OP proposed is not supported by Puppet. Among the
alternatives are:
- Use the Concat module. This allows each contributing node to export
one or
On Thursday, June 27, 2013 5:38:07 AM UTC-5, Nicholas Shanks wrote:
I have a Vagrant-controlled VM and I am trying to copy in files and
directories when the VM gets provisioned. I have tried file:///, drive name
with slashes and drive name with backwards slashes. Cannot get any of those
Running Amazon Linux (which is essentially Centos5.5).
Anyone seen random yum errors like this one? I don't think
it's necessarily related to Puppet, but it randomly fails my puppet runs
and I don't know how to fix it.
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
Not puppet related, no. Every rpm deep. Solver as yum, zipper etc put a lock
for protecting the rpm db from concurrent access. So if you are using puppet be
sure to not having long running yum daemons, but if you also use some patch
management system - spacewalk, red hat satellite - this could
Good idea, and much needed IMHO. Thanks!
Martijn
Op maandag 24 juni 2013 15:26:50 UTC+2 schreef Jens Braeuer het volgende:
So I would like to make you aware of one of my side-projects called
Raziel.
https://github.com/jbraeuer/raziel/
http://bit.ly/raziel-slides
--
You received this
Hi all,
I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos
Linux (6.3).
Unfortunately there are two varnish RPMs (which seem to have circular
dependencies):
varnish-3.0.4-1.el6.x86_64
varnish-libs-3.0.4-1.el6.x86_64
When using ensure for downgrading I get a bunch of
Is there anything in the Puppet/Passenger setup process that edits httpd.conf
and sets the User/Group running apache to puppet ?
A master I set up several months ago is configured that way.
I do not recall doing it.
But then the high voltage electroshock therapy does have its side effects :)
In my experience, exporting nagios_command resources doesn't work so well.
What I've found works best, is to define nagios_command{}'s directly on the
server, rather than exporting and collecting them there later.
In my setup, the only resource that export is the nagios_host. I define
commands
Hi
I am just testing file_line type in puppetlabs stdlib library. It is a
very simple line
file_line { 'testing file_line' :
ensure = present,
line = 'This is a test'
path = '/etc/puppet/puppet-test'
}
It works but when I look at client log
On 06/28/2013 04:57 PM, Stephen Jahl wrote:
In my experience, exporting nagios_command resources doesn't work so
well. What I've found works best, is to define nagios_command{}'s
directly on the server, rather than exporting and collecting them there
later.
In my setup, the only resource that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I try to cleanup my config due to some deprecation warnings but with
inline_template i run into some trouble.
This is my class:
1 class test { 2 $var1 = 'foo' 3 $var2 = 'bar' 4 $vars =
[var1,var2] 5 notice($var1) 6 notice($var2) 7
On 01/08/2013 10:07 PM, mmcbr...@spryinc.com wrote:
I know this isn't traditionally how puppet works, but I was
curious as to any trick that may accomplish something like this.
I'm afraid you answered your own question in the first part of the
sentence. It's not possible AFAIK.
And why
On 6/28/2013 7:41 AM, Dan White wrote:
Is there anything in the Puppet/Passenger setup process that edits
httpd.conf and sets the User/Group running apache to puppet ?
A master I set up several months ago is configured that way.
I do not recall doing it.
But then the high voltage electroshock
I understand that, but the apache/httpd processes are also owned by puppet
because the User/Group parameters in httpd.conf were changed to puppet.
If I did it manually, I would hope I would have remembered doing it and/or made
notes to remind me.
I do not remember, and I find no notes, so I
Ubuntu 11.10 Oneiric Ocelot reached end of life on 2013-05-09 [1], so
we are no longer building new packages for it and it will be removed
from our apt repository on Friday, July 9.
[1] https://lists.ubuntu.com/archives/ubuntu-announce/2013-May/000174.html
--
Moses Mendoza
Puppet Labs
Join us
All-
We have some custom types providers related to mysql (mysql_user,
mysql_grant, mysql_db) written by an admin that's no longer here. The
provider just uses the mysql command to run various commands, e.g:
Puppet::Type.type(:mysql_user).provide(:mysql) do
desc Provider for a mysql user
On Fri, Jun 28, 2013 at 2:03 PM, Tim Mooney tim.moo...@ndsu.edu wrote:
We have some custom types providers related to mysql (mysql_user,
mysql_grant, mysql_db) written by an admin that's no longer here. The
provider just uses the mysql command to run various commands, e.g:
Hi Stefan,
I've run into similar issues before… I don't have module code handy, but
what I ended up doing was creating an exec which performed something
similar to:
exec{'nuke_pesky_pkg':
command = 'rpm -e $package; touch /etc/package.removed',
creates = '/etc/package.removed'
}
which I
19 matches
Mail list logo
