2009/12/30 berber webersi...@gmail.com:
I'm starting to wonder, put bluntly so don’t get mad, if “Lazy” system
admins run puppet continuously in production, while putting their
systems in harm way due to a possible bug in puppet, corruption of the
source, accidental changes to the manifest, etc…
Is this the case or am I missing out on the big picture? Since when
does “being productive” come before production integrity?
I've seen production integrity used as an excuse for not delivering
new services, costing the business $$$. There has to be a balance...
--
You received this message
berber wrote:
This doesn't sound very professional. You would risk your production
environment because it's uncomfortable for the sys admin to remember
he needs to roll back a change in 10 minutes or 10 hours?
Assume we are talking about a business that looses tens of thousands
of $$$ for
Bugs happen in any service. This is the classical dilemma of plugging
out your computer from the network vs connectivity (usability in this
case). From my perspective high security risk bugs happen rarely enough
to use both puppet and any other service I use.
IMHO misconfiguration has a
I'm not mad, I take pride in my laziness, I'm more efficient that way.
On Laziness:
Wall along with Randal L. Schwartz and Tom Christiansen writing in the
second edition of Programming Perl, outlined the Three Virtues of a
Programmer:
Laziness - The quality that makes you go to great effort to
Hello.
I'm a about 2 months into a puppet poc. I've got the low hanging
fruit taken care of and have the standard manifests which apply to
every host of a given operating system. Basically just schlepping
lot's of standard files out to every host of a given OS type. No real
decision making
Hi Dan
Thanks for the pointer to the bug. I actually used purge in my
manifest because when I tried absent I would get errors about not
being able to remove a package because it was needed by something
else.
On Dec 29, 10:04 pm, Dan Bode d...@reductivelabs.com wrote:
Hi Jamie,
On Tue, Dec
Hi,
On Wed, Dec 30, 2009 at 6:54 PM, Jamie gojamieg...@gmail.com wrote:
Hi Dan
Thanks for the pointer to the bug. I actually used purge in my
manifest because when I tried absent I would get errors about not
being able to remove a package because it was needed by something
else.
yeah,
Answering my own question here. As it turns out, the source parameter
does work as I was expecting it to, but only in puppet versions 0.24.5
and greater. I was trying with 0.24.4.
On Dec 24, 1:00 pm, byron appelt byron.app...@gmail.com wrote:
I am trying to use the package class to manage
Hi,
On Wed, Dec 30, 2009 at 9:52 PM, Sukh Khehra skhe...@proofpoint.com wrote:
Hi,
I am running puppet version 0.25.1 on both the server and client and am
getting the following error on a puppet run:
err: Could not apply complete catalog: Could not retrieve dependency
'Class[http]' of
On Wed, Dec 30, 2009 at 10:45 PM, Sukh Khehra skhe...@proofpoint.comwrote:
Thanks Dan. Unfortunately, this did not work for me.
err: Could not apply complete catalog: Could not retrieve dependency
'Class[::http]' of Class[puppet::http]
Does anyone know of another way to fully qualify
deet wrote:
Obviously I hadn't taken into consideration on how I could support
multiple zpools on one host. Just figured this out as I went to add a
second zpool to the node headbone. So am I wanting to use
definitions to support creating multiple zpools (or whatever) per
In your case,
On Dec 29, 1:10 pm, Andrew Schulman google-groups-
and...@sneakemail.com wrote:
There are actually two problems here:
(1) ssh::auth was trying to authorize the us...@lan key in the wrong place,
i.e.
in /home/user2/.ssh/authorized_keys. I just uploaded a new release, 0.3.2,
that
fixes
I spent some time to find the subtle difference (regarding $home)
between :
ssh::auth::server { r...@ssh: }
And :
ssh::auth::server { r...@ssh:
user= root,
}
;)
Please, enlighten me. If it's not right, I'll correct it.
Just find me a
Oops, I've been too fast. When I try to ssh::auth::key (realize
Ssh::Auth::Key[$keyname]) and ssh::auth::server without
ssh::auth::client on a node, it fails on the master :
err: Failed to realize virtual resources Ssh::Auth::key[...@ssh]
ssh::auth::key can't be made into a virtual resource
15 matches
Mail list logo
