I'm working on rolling out Puppet, but I'm stuck and I know somebody has
solved this problem...
We have an engineering environment of around 200 Centos servers, plus a
production environment of roughly the same size. Currently, when we roll out
a new server, we do a 'yum update' so the new server
On Sep 22, 2010, at 8:06 AM, Leslie Giles wrote:
> We have an engineering environment of around 200 Centos servers, plus a
> production environment of roughly the same size. Currently, when we roll out
> a new server, we do a 'yum update' so the new server has the latest packages;
> however thi
Hi Lezz,
Another approach is to maintain your own repos by freezing them over time,
e.g. monthly pull the latest packages for your repos and put them as your
frozen repo, provide these frozen repos through puppet and once you have
validated all the updates in the frozen repos you can relase those
I am using puppet 2.6 with Nexenta ncp 3.0.1 - an OpenSolaris distro
with Ubuntu userland. Most things work great, only a few make trouble.
A big problem is creating a (Solaris-) Zone with Puppet. It does not
work with puppetmasterd only if run it with puppet manually:
puppet --debug --verb
On Wednesday, September 22, 2010, qutic development
wrote:
[snip]
> Is there any way to set the path for every system command puppet is
> executing? I didn´t found it in the puppet code. Any hints?
Yes, the path parameter of the exec type will allow you to manage the
PATH environment variable of
I purged the entire database and things are working again. I did lose
some valuable settings from Foreman, but restarting with a clean slate
was worth the hassle. I'll look into integrating some DB snapshots
into my setup. That way I'll be able to revert to a previous database
snapshot if need b
On Wed, 22 Sep 2010, Leslie Giles wrote:
We have an engineering environment of around 200 Centos servers, plus a
production environment of roughly the same size. Currently, when we roll out
a new server, we do a 'yum update' so the new server has the latest
packages; however this means that just
On 09/22/2010 04:31 PM, qutic development wrote:
> ...
> I figured out that it must be a path issue. Running with puppetmasterd
> the path is not set to the default value for nexenta:
>
> PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
>
> Is there any way to set the path for ev
I've been looking at this example in the puppetdocs.pdf
class nagios-target {
@@nagios_host { $fqdn:
ensure => present,
alias => $hostname,
address => $ipaddress,
use => "generic-host",
}
@@nagios_service { "check_ping_${hostname}":
check_command => "check_ping!100.0,20%!500.0,60%",
use => "gener
On 09/22/2010 09:10 AM, Baker, Luke wrote:
I've been looking at this example in the puppetdocs.pdf
class nagios-target {
@@nagios_host { $fqdn:
ensure => present,
alias => $hostname,
address => $ipaddress,
use => "generic-host",
}
@@nagios_service { "check_ping_${hostname}":
check_com
Hi all..
Having a strange problem and searhed through the groups, can't find
anything. Have a couple of chrooted daemons that are giving an error
with "ensure => running", even with a "hasrestart = true"
Simply put it errors with a return code of 1 saying "xyzzy start
returned 1" and yet if I run
I have an environment where there is a huge amount of political strife
as well as disparate divisional and departmental LANS. Some are tied
via rather unreliable connectivity. My predecessor sold the campus on
the idea of deploying puppet in a tier of top level masters
configuring departmental mast
take a look at this thread:
http://groups.google.com/group/puppet-users/browse_thread/thread/20fcb69d59a09979/40d3b0894ea9effe?lnk=gst&q=jewels#40d3b0894ea9effe
I am doing the same thing -- a puppet master populates an area on
another puppet master, which then configures hosts that I do not
contro
Thanks Jewels. Looks like we are on similar paths. I really appreciate
the info.
On Sep 22, 3:11 pm, Jewels wrote:
> take a look at this
> thread:http://groups.google.com/group/puppet-users/browse_thread/thread/20fc...
>
> I am doing the same thing -- a puppet master populates an area on
> anoth
Mikel King ha scritto:
> Thanks Jewels. Looks like we are on similar paths. I really appreciate
> the info.
>
> On Sep 22, 3:11 pm, Jewels wrote:
>> take a look at this
>> thread:http://groups.google.com/group/puppet-users/browse_thread/thread/20fc...
>>
You may want to take a look at this, as
On Wed, Sep 22, 2010 at 11:20 AM, Mikel King wrote:
> I have an environment where there is a huge amount of political strife
> as well as disparate divisional and departmental LANS. Some are tied
> via rather unreliable connectivity. My predecessor sold the campus on
> the idea of deploying puppet
I chose to manage users with puppet. The only thing I did not like was
password management. I did not want to put user's password in the
manifest files. Instead I execute two commands when a user is created
(only once): set an empty password (usermod -p '"" username) and set
the password to expired
On Tue, Sep 21, 2010 at 09:43:26AM +1000, Daniel Pittman wrote:
> > I read up on user and group creation and ssh key distribution. The only
> > thing i cant wrap my head around is how i should handle passwords.
>
> I would strongly advise that you deploy an LDAP backed PAM and NSS system,
> rather
On Sep 22, 2010, at 1:56 PM, Radek wrote:
> I chose to manage users with puppet. The only thing I did not like was
> password management. I did not want to put user's password in the
> manifest files. Instead I execute two commands when a user is created
> (only once): set an empty password (user
Hello
it is possible to define something like this?
exec { "openvpn_reload" :
command => "/etc/init.d/openvpn reload",
user => root,
require => [ File[ "openvpn_client.conf"] OR File
["openvpn_server"] ]
}
is possible what would be the correct syntax?
thanks
--
-
On Wed, Sep 22, 2010 at 5:55 PM, Luc Suryo wrote:
> Hello
>
> it is possible to define something like this?
>
> exec { "openvpn_reload" :
> command => "/etc/init.d/openvpn reload",
> user => root,
> require => [ File[ "openvpn_client.conf"] OR File
> ["openvpn_server"]
Hi Jeff
well the thing is a client uses openvpn_client.conf and the server
openvpn_server.conf (our setup)
so i wanted to do
service { "openvpn" :
ensure => runnning,
require => [ Package["openvpn"], File[ "openvpn.conf"] ]
}
then i have a client.pp and server.pp for
On Sep 22, 2010, at 6:14 PM, Luc Suryo wrote:
> Hi Jeff
>
> well the thing is a client uses openvpn_client.conf and the server
> openvpn_server.conf (our setup)
> so i wanted to do
>
>
> service { "openvpn" :
> ensure => runnning,
> require => [ Package["openvpn"],
yes I just did that., and yes I do know that openvpn will start the conf
file as defined in the
/etc/sysconfig/openvpn or /etc/default/openvpn
just it would had been nice to define and OR for other special cases :)
just implemented a work around and it works
thanks
On Wed, Sep 22, 2010 at 6:3
On Sep 22, 2010, at 6:40 PM, Luc Suryo wrote:
> yes I just did that., and yes I do know that openvpn will start the conf file
> as defined in the
> /etc/sysconfig/openvpn or /etc/default/openvpn
>
>
> just it would had been nice to define and OR for other special cases :)
The problem is that
Network segmentation and firewalling prevents that option...
>
> Why not have a single puppet server with teams owning different
> environments and/or modules?
>
> That's what we do here.
>
>
>
> > Cheers,
> > m
--
You received this message because you are subscribed to the Google Groups
"Puppe
On Wed, Sep 22, 2010 at 6:40 PM, Luc Suryo wrote:
> yes I just did that., and yes I do know that openvpn will start the conf
> file as defined in the
> /etc/sysconfig/openvpn or /etc/default/openvpn
>
>
> just it would had been nice to define and OR for other special cases :)
Like what? I can't
Hi all
Due to the late pull out of one of our potential speakers we have a
speaking spot open for Puppet Camp in SFO
(http://www.puppetlabs.com/community/puppet-camp/puppet-camp-sf-2010-info/).
So this is your big chance to make your mark on the Puppet community and
tell us about the cool th
28 matches
Mail list logo
