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 any small downtime. Do
Hi Jamie,
On Tue, Dec 29, 2009 at 10:32 PM, Jamie wrote:
> Hi
>
> I was hoping there is a way to supress this type of log messages but
> cannot find anything to help.
>
> Tue Dec 29 12:04:53 -0800 2009 //yum/Package[autofs]/ensure (notice):
> created
> Tue Dec 29 12:04:54 -0800 2009 //yum/Packag
On Tue, Dec 29, 2009 at 9:31 PM, JL wrote:
> > > Does this problem still persist?
> yes
>
> > > Is it always on the same clients?
> It has happened on every client except (I think) the puppet server
> itself. The clients are Solaris 10 boxes with a mix of sparc and
> i386. It seems to be happen
JL wrote:
>>> Does this problem still persist?
>>>
> yes
>
>
>>> Is it always on the same clients?
>>>
> It has happened on every client except (I think) the puppet server
> itself. The clients are Solaris 10 boxes with a mix of sparc and
> i386. It seems to be happening about 10
berber wrote:
> If you look at the reply from Russ Allbery you will notice he wrote "
> We've only gotten bitten by this once, when there was a bug in Puppet
> that occasionally caused it to overwrite managed files with their own
> checksums."
>
> I'm thinking to myself that bugs will always happen
Hi
I was hoping there is a way to supress this type of log messages but
cannot find anything to help.
Tue Dec 29 12:04:53 -0800 2009 //yum/Package[autofs]/ensure (notice):
created
Tue Dec 29 12:04:54 -0800 2009 //yum/Package[attr]/ensure (notice):
created
Tue Dec 29 12:04:54 -0800 2009 //yum/Pack
> > Does this problem still persist?
yes
> > Is it always on the same clients?
It has happened on every client except (I think) the puppet server
itself. The clients are Solaris 10 boxes with a mix of sparc and
i386. It seems to be happening about 10x more on one particular
client, but I think t
hello,
- "berber" wrote:
> Now consider a company running hundreds of production servers with
> puppet running continuously every hour and over the night random
> servers start to fail. By the time someone understands that puppet is
> to blame and stops it (one may think there is an attack),
If you look at the reply from Russ Allbery you will notice he wrote "
We've only gotten bitten by this once, when there was a bug in Puppet
that occasionally caused it to overwrite managed files with their own
checksums."
I'm thinking to myself that bugs will always happen and that this
particular
Great - thanks for the feedback - working as expected now.
Thanks again all!
On 29 Dec, 17:27, Michael Gliwinski wrote:
> On Tuesday 29 December 2009 16:30:58 Ben wrote:
>
> > ok so just to confirm, if I understand correctly classes will not be
> > evaluted unless they are used within an include
On Tuesday 29 December 2009 16:30:58 Ben wrote:
> ok so just to confirm, if I understand correctly classes will not be
> evaluted unless they are used within an include.
yes
> I've restored my site.pp so now it's go two classes, "files1" and
> "files2" both managing file resources.
>
> I've also
On Tue, Dec 29, 2009 at 5:30 PM, Ben wrote:
> ok so just to confirm, if I understand correctly classes will not be
> evaluted unless they are used within an include.
>
> I've restored my site.pp so now it's go two classes, "files1" and
> "files2" both managing file resources.
>
> I've also specif
ok so just to confirm, if I understand correctly classes will not be
evaluted unless they are used within an include.
I've restored my site.pp so now it's go two classes, "files1" and
"files2" both managing file resources.
I've also specified all nodes using the default node function, all
nodes s
Hi all,
Groups and classes: Am I missing something or is there no way to
associate a class with a group using the dashboard? In the group
summary it shows "Params", "Classes", and "Nodes", but when you go to
edit it, you only have the option to add nodes or parameters.
Groups and precedence: It ap
The behaviour I'm expecting is that if there are no node definitions
then all resources and classes would be applied to all nodes but it's
not.
As for you're question, yes when I define a node (or use the default
node function) and with a include class then it works.
On 29 Dec, 15:59, Julian Si
Hi Ben,
> class files1 {
>file { "/etc/motd":
>group => "puppet",
>}
> }
>
> The problem is that it's not picking up the class when it compiles the
> catalogue.
>
resources within classes are not compiled into the catalog unless the class
is included.
>
> I've found th
Have you declared any nodes and included that class?
node default {
include files1
}
2009/12/29 Ben :
> Just to add some addtional detal about which versions I'm using
>
> [r...@xldn1784dis puppet]# puppetmasterd --version
> 0.24.5
> [r...@xldn1784dis puppet]# puppetd --version
> 0.24.5
> [r
Just to add some addtional detal about which versions I'm using
[r...@xldn1784dis puppet]# puppetmasterd --version
0.24.5
[r...@xldn1784dis puppet]# puppetd --version
0.24.5
[r...@xldn1784dis puppet]# ruby --version
ruby 1.8.5 (2006-08-25) [x86_64-linux]
[r...@xldn1784dis puppet]# facter --version
Hi
I've been scrathing my head at this for days, to point where I've
stripped down my site manifest, so it consists purely of a single
class called files1 managed a sinlge file resource.
class files1 {
file { "/etc/motd":
group => "puppet",
}
}
The problem is that it's no
On 21 Dic, 01:50, James Turnbull wrote:
> 2009/12/21 Julian Simpson :
> > 2009/12/18 Al @ Lab42 :
> > [snip]
> >> Now, as a user, I think that it is important to know how to start to
> >> write metadata files: format and minimal required parameters.
> >> A final (?) decision is not to be rushed,
I've uploaded version 0.3.2 of ssh::auth to
http://reductivelabs.com/trac/puppet/wiki/Recipes/ModuleSSHAuth . This
release fixes a couple of bugs since version 0.3:
* Fix parser error in ssh_auth_namecheck
* Fix wrong $home when user is specified separately for a client or server
In addition, th
> >>> 8- PROPOSAL (don't think it will be widely liked): Variables names
> >>> needed for module configuration (the ones used in templates, for
> >>> example) should have a my_ prefix, in order to easily distinguish
> >>> them
> >>> from fact variables.
>
> >> Glad you retracted this. :)
>
> > St
Hi,
I can't seem to get custom facts up and running .. its works if I run it
manually but when running puppetd its does not work.
puppet version 0.25.1-3
custom fact put in /etc/puppet/modules/hardware/lib/facter/raidcontroller.rb:
Facter.add("storagecontroller") do
confine :kernel => :
> Still I have something I don't understand. With the following I expect
> to log in as user1 with user2 key pair :
>
> class user::virtuals {
>
> @user { "user1":
> uid => "1001",
> gid => "group",
> comment => "name",
>
> Andrew, while you're in your code, can you let me know how I can
> achieve this :
>
> ssh::auth::server { "us...@lan": user => "user1" }
> ssh::auth::server { "us...@lan": user => "root" }
>
> I would like my big admin user to get access to several accounts. Is
> there any trick that would do o
25 matches
Mail list logo
