Hi,
I'm a big fan of Puppet and managed to have my company accept it.
However, I'm having issues deploying it (I'm used to the debian version
which works perfectly out of the box) :
- There doesn't seem to be an official repository for Suse (I've seen it
mentionned in the bugtracker but yum.pup
Hi, thank you for your answer, I didn't know about your repository. It will
definitely help on my most recent servers.
However, that only solves part of my problem : about two thirds of my
servers still run SLES 10.
Even if SLES 10 isn't listed in the Supported Operating Systems page,
puppet (i
Hi,
Due to severe heterogeneity among my servers (OS and version), I started my
puppet infrastructure by deploying agents by hand (from the tarball). That
way, I'm sure that I have the same version everywhere.
Having found up-to-date repositories for most of my systems, I'm now
questioning tha
Well, that's more than I expected. I can easily ensure that my server is
up-to-date, and then use whatever package I find for the agents...
Thanks.
Le lundi 12 mars 2012 15:16:32 UTC+1, pmbuko a écrit :
>
> On Mar 12, 2012, at 10:03 AM, Julien C. wrote:
>
> Hi,
>
> Due
That would be great! Anything I can do to help?
Le lundi 12 mars 2012 15:26:19 UTC+1, Darin Perusich a écrit :
>
> You can still build for unsupported SuSE distro's via the build
> service, we're doing this in the server:monitoring repo for SLES10,
> you just need to manually add. them. It shouldn
Hi,
I tried using EPEL repositories as stated
here: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Red_Hat_Centos
The Puppet version there is 2.6.14 or did I miss something?
My concern is: will I have reports with that version? I'm using dashboard
to keep an eye on my deployment and
Answering to myself: no 2.6.14 doesn't send reports.
I'll have a look at yum.puppetlabs.com
Le mardi 13 mars 2012 10:16:11 UTC+1, Julien C. a écrit :
>
> Hi,
>
> I tried using EPEL repositories as stated here:
> http://projects.puppetlabs.com/projects/puppet/wiki/Pu
o's via the build
> service, we're doing this in the server:monitoring repo for SLES10,
> you just need to manually add. them. It shouldn't be a problem as long
> as all the ruby requirements are there. I'll take a look at enabling
> this.
>
> --
> Later,
&
Or fallback to 2.7.9 maybe ?
Le mardi 13 mars 2012 12:48:37 UTC+1, Ygor a écrit :
>
> You mean like 2.7.12 that was just announced ?
>
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg29190.html
>
> :)
>
> - Julien C. wrote:
> > By the way, I ju
Le mercredi 14 mars 2012 01:02:53 UTC+1, Todd Zullinger a écrit :
>
> Julien C. wrote:
> > Answering to myself: no 2.6.14 doesn't send reports.
>
> Is this only an issue with integrating with dashboard or are you not
> getting reports at all with 2.6.14? I'm us
Wow, I didn't even know it was out. Thanks !
Le mercredi 14 mars 2012 15:05:03 UTC+1, Darin Perusich a écrit :
>
> The package has been updated to 2.7.14 in the repo.
>
> --
> Later,
> Darin
>
> On Tue, Mar 13, 2012 at 7:38 AM, Julien C. wrote:
> > By the way,
Hi,
I'm using the following repository :
http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/openSUSE_12.1/
And I'm having a weird error when I try to update puppet-dashboard :
Problem: nothing provides ruby(abi) = 1.8.7 needed by
puppet-dashboard-1.2.7-6.1.noarch
My ruby (1.8.
Hi,
I'm trying to make all my servers send their logs to a central server.
Which seems quite simple, at first.
My problem is that my servers are on different versions of different
operating systems.
And each of them has a different syslog default provider (syslog, rsyslog,
syslog-ng...).
Which
Thanks to both of you for your answers.
I am aware of the operatingsystem and release variables, but I can't rely
on them because servers don't always use the default syslog provider, as
stated in my original post.
I can't enforce the same provider on every node because it would destroy
any cus
14 matches
Mail list logo
