Hi,
On 01/28/2012 04:35 PM, Trevor Vaughan wrote:
> Drawbacks:
>
> * Requires the user to have an explicit working knowledge of all
modules and namespaces
> * Adds a lot of random logic to the code (unless it becomes a
metaparam of some sort)
You skipped the most important drawback: Commitment
NixFU wrote (ao):
> We don't frankly see having all our application teams use puppet or
> anything else to actively manage their applications. What we would
> like to do is watch the applications and know when things change.
> Basically, watch the directories that the developers put their
> applic
On 01/28/2012 12:17 AM, jblaine wrote:
> Trashing the entire defined resource idea 30 mins ago, and
> simply trying:
But why?
> class ldapclient::config {
> case $sys_sshortai {
> 'RH6': {
> file { '/etc/openldap/ldap.conf':
> mode => '444',
>
Had a bunch more thoughts on this topic, and I feel I agree with
Brian: a forge with one module for every purpose, supported maybe by
library modules (like linux) would be the best. It would mean
consolidating the 17 ssh modules that exist now into one all
encompassing ssh module. In the case of SS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It is annoying to have everything in a single place that defines the state of
your nodes but, as you point out, this seems to be the model if you're
using an ENC and that seems to be the recommended practice across the mailing
list for any sort of sc
On Jan 23, 3:45 am, Jos Houtman wrote:
> Hello list,
>
> I am looking for advice/best-practices on how to handle inter module
> dependency's.
[...]
> Without stages we tried three ways of doing this:
> Creating a dependency chain between classes.
> Class['Ldap'] -> Class['Mysql'].
> This is ve
On Monday, January 30, 2012 4:41:40 AM UTC-5, Felix.Frank wrote:
>
> On 01/28/2012 12:17 AM, jblaine wrote:
> > Trashing the entire defined resource idea 30 mins ago, and
> > simply trying:
>
> But why?
>
Felix, thanks for the reply.
I was just trying stuff out while waiting to see what fleshed ou
On 01/30/2012 03:50 PM, jblaine wrote:
> So there's nothing I can refer to inside a basic file resource declaration
> which refers to the file resource "title". That's what I wanted to know
> (assuming I understand everyone correctly).
That's correct, yes.
--
You received this message because y
On Jan 30, 2:51 am, Felix Frank
wrote:
> Hi,
>
> On 01/28/2012 04:35 PM, Trevor Vaughan wrote:> Drawbacks:
>
> > * Requires the user to have an explicit working knowledge of all
>
> modules and namespaces> * Adds a lot of random logic to the code (unless it
> becomes a
>
> metaparam of some s
On Sat, Jan 28, 2012 at 10:39 PM, Brian Gupta wrote:
> Nigel,
>
> It frightens me a bit that I think the "correct" solution, will be to
> replicate what the distros are doing in Puppetforge. Basically turning
> puppetforge into a massive cross distro metadata repo, with very strict
> contribution
Olivier.
here is what the password part of our user resources looks like.
The actual command is just a wrapper around finding the crypt and
returning something appropriate.
password => generate('/site/bin/getups', '-u', "$name"),
Make sure the script you are calling with generate
On 27/01/12 18:27, jcbollinger wrote:
>> Anyway, I need to get back to work, I'll try to say more in a later email.
>
>
> That would help me to determine what I think about the idea. As it
> is, I suspect I don't quite understand what you are hoping to
> accomplish with it.
Ok, here's a couple
Hi, I run into problems with the ipaddress fact using the latest
Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work
perfectly fine on SLES10 SP3.
The problem: running "facter" without arguments results in an error,
even though the erroring fact "ipaddress" is ok.
test:~ # cat /
Hi,
thanks for your elaborate design sketch.
Sorry for limiting my quote severely.
On 01/30/2012 06:28 PM, Nick wrote:
> +package { 'libfoo': ensure => present }
Is this different from John's "constraint" proposal?
To me this didn't become clear: Does the manifest still need to declare
an ac
Hi,
concerning your question why everything seems to work pretty well:
On 01/27/2012 04:59 AM, Romeo Theriault wrote:
> Jan 26 17:09:41 ppt01 puppet-agent[27357]: Using cached catalog
Your agent is using a cached catalog.
puppet agent --test should fail. Also, changing the manifest for this
nod
Thanks guys.. I'll check out mcollective. Yeah, the root password 60
times is a bit painful, but the ssh loop would help. If I remember
right, there is an API/REST call for Foreman that will give me a list of
the hosts not responsive.
The problem here is that puppet was in memory, and runnin
This smells like you have a second copy of facter or some other facts
somewhere in your RUBYLIB, as the latest version no longer uses
Facter::IPAddress. Are you sure you haven't got an RPM or local copy
installed somewhere else?
Try running facter --trace as well so we can see the output. The path
- Original Message -
> Thanks guys.. I'll check out mcollective. Yeah, the root password 60
> times is a bit painful, but the ssh loop would help. If I remember
> right, there is an API/REST call for Foreman that will give me a list
> of the hosts not responsive.
>
> The problem here i
For the purposes of this email I need to make a distinction between my
Production puppet master and my Development puppet master. In either
case, my /etc/puppet/puppet.conf is:
[main]
ssldir=$vardir/ssl
[master]
certname=puppet
Development puppet master is run:
# puppetmaste
On 30/01/12 17:48, Felix Frank wrote:
> Hi,
>
> thanks for your elaborate design sketch.
>
> Sorry for limiting my quote severely.
>
> On 01/30/2012 06:28 PM, Nick wrote:
>> +package { 'libfoo': ensure => present }
>
> Is this different from John's "constraint" proposal?
It did sound similar
All,
I ended up posting the question to ServerFault, where it was answered.
http://serverfault.com/questions/355214/why-does-this-nginx-thin-run-puppet-master-interpret-paths-differently-than-a-lo
On Mon, Jan 30, 2012 at 3:54 PM, Brian Troutwine wrote:
> For the purposes of this email I need to
Recently I rigged up a script to email me a list of agents that did not
send any reports to puppet server in last 24 hours. Each night it lists
about a dozen agents, mostly but not always the same ones.
They share a common pattern:
Agent is running in deamon mode but makes no updates.
Each time
2012/1/26 Juan José Presa Rodal :
(I noted that; since this topic was followed up elsewhere I figured to
repeat myself. :)
> Ok Daniel, thanks for your reply, but I have not control about these
> individual "noreplace" files because are $hostname dependent.
Generally, what we would encourage is
23 matches
Mail list logo
