Paul Lathrop writes:
> On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman wrote:
>> Paul Lathrop writes:
>>
>>> I've open-sources Digg's apache module:
>>> http://github.com/plathrop/puppet-module-apache
>>>
>>> I know this isn't much more advanced than what I've seen a lot of people
>>> using.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/05/10 12:33 PM, Daniel Pittman wrote:
>
> * the module enable/disable feature also ships appropriate configuration and
>installs the appropriate packages for the platform.
>
There's also this that I and Teyo wrote - that manages Apache
mo
On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman wrote:
> Paul Lathrop writes:
>
>> I've open-sources Digg's apache module:
>> http://github.com/plathrop/puppet-module-apache
>>
>> I know this isn't much more advanced than what I've seen a lot of people
>> using.
>
> It looks very much like our in
Did Isaac just volunteer to be the canary for CentOS/RHEL/Fedora?
Seriously, I will integrate these various modules, including bringing
in any distribution-specific stuff I can find, but I don't have any
experience with the CentOS, etc. family of distributions.
Related, though, is the concept tha
All,
Does the file hierarchy provided below follow current best practices:
lib/
manifests/
---site.pp
---templates.pp
---nodes.pp
modules/
---{modulename}/
--depends/
--files/
--manifests/
-init.pp
-defaults.pp
--lib/
-puppet/
parser/
--
Paul Lathrop writes:
> I've open-sources Digg's apache module:
> http://github.com/plathrop/puppet-module-apache
>
> I know this isn't much more advanced than what I've seen a lot of people
> using.
It looks very much like our internal, not-able-to-release version. The two
features we have that
Dan Bode writes:
> On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote:
>> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote: > >
>> - "Brian Gallew" wrote: > >> in nodes and have them
>> propagate to their children, then I submit that >> nodes are so
>> fundamentally broken as to make no
+1 for this. But let's not forget the CentOS/RHEL/Fedora folks out
there. Minor but key differences in directory structure, permissions,
SELinux policies, etc.
On 5/11/10 9:56 PM, James Turnbull wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul
These are the ones I know about:
ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul
These are the ones I know about:
http://github.com/camptocamp/puppet-apache
http://github.com/wesabe/puppet-apache2
http://github.com/puppet-modules/puppet-apache
http://github.com/simpsonjulian/puppet-apache-ubuntu
http://github.com/ohlol/puppe
+1
Here is another apache module that I wrote:
http://github.com/ohadlevy/puppet-foreman/tree/master/apache2/
Thanks,
Ohad
On Wed, May 12, 2010 at 8:27 AM, Paul Lathrop wrote:
> I'll even do the integration work, just link me to your module and
> I'll try to integrate its feature set into mine.
I'll even do the integration work, just link me to your module and
I'll try to integrate its feature set into mine.
On Tue, May 11, 2010 at 5:17 PM, Nigel Kersten wrote:
> On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop wrote:
>> Hey all,
>>
>> I've open-sources Digg's apache module:
>> http://git
On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop wrote:
> Hey all,
>
> I've open-sources Digg's apache module:
> http://github.com/plathrop/puppet-module-apache
>
> I know this isn't much more advanced than what I've seen a lot of
> people using. Here's my proposition, though. Let's get all the
> dis
Hey all,
I've open-sources Digg's apache module:
http://github.com/plathrop/puppet-module-apache
I know this isn't much more advanced than what I've seen a lot of
people using. Here's my proposition, though. Let's get all the
disparate "apache" modules out there merged together into One Awesome
M
On Tue, May 11, 2010 at 3:31 PM, Dan Bode wrote:
> On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote:
>>
>> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote:
>> >
>> > - "Brian Gallew" wrote:
>> >
>> >> in nodes and have them propagate to their children, then I submit that
>> >> nodes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/05/10 5:05 AM, Brian Gallew wrote:
> Actually, the case I'm demonstrating is NOT covered in that FAQ. The
> nodes *only* set variables. No includes happen until the final,
> selective node (in this case "pslave1").If you cannot set variable
"Haven't gotten there yet".
In my case, I'm specifically choosing to use a node-based classifier for
building the puppetmasters from the master-master. 8/ The puppetmasters,
in turn, will use a database. But I've still got to build a half-dozen
puppetmasters (network separation), so to get ther
On Tue, May 11, 2010 at 3:27 PM, Nigel Kersten wrote:
> On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote:
> >
> > - "Brian Gallew" wrote:
> >
> >> in nodes and have them propagate to their children, then I submit that
> >> nodes are so fundamentally broken as to make node inheritance
> >>
On Tue, May 11, 2010 at 3:19 PM, R.I.Pienaar wrote:
>
> - "Brian Gallew" wrote:
>
>> in nodes and have them propagate to their children, then I submit that
>> nodes are so fundamentally broken as to make node inheritance
>> completely useless, in which case node inheritance should be pulled.
- "Brian Gallew" wrote:
> in nodes and have them propagate to their children, then I submit that
> nodes are so fundamentally broken as to make node inheritance
> completely useless, in which case node inheritance should be pulled.
that sums it up well.
--
You received this message becaus
0.24 puppetmaster don't work with 0.25 puppet client.
Upgrade your puppetmaster to 0.25.4 (and facter to 1.5.7).
You can use ubuntu "lucid" packages.
Benoit
Le 11/05/2010 22:40, FAZANG a écrit :
On my puppet master i have installed
ruby1.8 1.8.7.72-3lenny1
puppetmaste
0.24 puppetmaster don't work with 0.25 puppet client.
Upgrade your puppetmaster to 0.25.4 (and facter to 1.5.7).
You can use ubuntu "lucid" packages.
Benoit
Le 11/05/2010 22:40, FAZANG a écrit :
On my puppet master i have installed
ruby1.8 1.8.7.72-3lenny1
puppetmaste
On my puppet master i have installed
ruby1.8 1.8.7.72-3lenny1
puppetmaster0.24.5-3
facter 1.5.1-0.1
On my SLES10.2 client i have installed
ruby-1.8.4-17.16 from the SDK DVD i got off novell site
puppet-0.25.4-4.1 RPM
facter-1.5.
Dear All,
I've finally managed to get xen installed on a remote system via puppet
http://puppetnewbie.blogspot.com/2010/05/installing-xen-instance.html
I was about to create my test machines manually, when it occurred to me,
that I should be doing this via puppet. Hence my question in the
subject
Actually, the case I'm demonstrating is NOT covered in that FAQ. The nodes
*only* set variables. No includes happen until the final, selective node
(in this case "pslave1").If you cannot set variables in nodes and have
them propagate to their children, then I submit that nodes are so
fundamen
All,
How can I stop the "returns successfully" messages from the exec {}
type unless their is a failure? Don't really want to see it. Using
logoutput => on_failure with exec doesn't seem to work (as this person
says here
http://unimpressed.org/post/93835992/disabling-puppets-executed-successfully
I decided to simplify every that I was doing. I noticed that I had begun
to overthink things, and I decided that KISS, is still the best way to
go.
This has turned out to be something like this;
***
File xenmaster.testdomain.com.pp
node xenmaster.testdomain.com {
include xen
}
Where xen has be
On 05/11/2010 02:11 AM, Brian Gallew wrote:
(vastly trimmed code)
/manifests/site.pp:/
import "base"
/module/base/manifests/init.pp/:
import "baselines/*.pp"
import "infrastructures/*.pp"
import "nodes.pp"
/nodes.pp:
/node 'pslave1' inherits rnc {
notice($my_puppet_master)
}
/infrastructure
I use this to create two variables that I can use in a cron type:
# The variable boot_time is set on the client in the /etc/init.d/
puppet-at-boot script
# as a FACTER environmental variable i.e. export
FACTER_BOOT_TIME=`date '+%H:%M'`
$boot_hour = regsubst($boot_time,'^([0-9]+)[:]([0-9]+)','\1')
On 05/11/2010 05:45 AM, Dick Davies wrote:
I've been using Puppet very happily for the last 6 months
or so to manage our CentOS and RHEL servers.
Over the summer I want to knock things up a notch,
and part of that is going to be supporting a wider range of OSes.
First on the hit list are likely
On 05/11/2010 05:45 AM, Dick Davies wrote:
I've been using Puppet very happily for the last 6 months
or so to manage our CentOS and RHEL servers.
Over the summer I want to knock things up a notch,
and part of that is going to be supporting a wider range of OSes.
First on the hit list are likely
I have a dozen use cases for some sort of
Puppet 'proxy' client that could supply facts and
act as a provider for
(e.g. load balancers, rackspace cloud, web services,
embedded devices) where running Puppet locally was not practical.
Does anyone know of such a thing?
On Thu, May 6, 2010 at 4:35 P
I've been using Puppet very happily for the last 6 months
or so to manage our CentOS and RHEL servers.
Over the summer I want to knock things up a notch ,
and part of that is going to be supporting a wider range of OSes.
First on the hit list are likely to be Solaris 10 and Suse (SLES).
I know a
32 matches
Mail list logo
