On 13.12.2009 23:09, Douglas Garstang wrote:
> So, I've been doing something like this for applications that have a
> client and server component...
>
> node base_node {
> include syslog_ng::client
> }}
>
> node app_node inherits base_node {
> }
>
> node syslog_server inherits base_node {
>
Yeah, I can update the external nodes page no problem.
On Mon, Dec 14, 2009 at 3:54 PM, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Teyo
>
> If you have a chance do you want to throw your email and my email
> into the External nodes page? It really needs some mor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teyo
If you have a chance do you want to throw your email and my email
into the External nodes page? It really needs some more explanation.
Or I can if you're busy.
Cheers
James Turnbull
- --
Author of:
* Pro Linux System Administration (http://t
On Mon, Dec 14, 2009 at 2:10 AM, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Douglas Garstang wrote:
>> On Sun, Dec 13, 2009 at 11:29 PM, Peter Meier wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
I'm no expert at external nodes, so I went an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas Garstang wrote:
> On Sun, Dec 13, 2009 at 11:29 PM, Peter Meier wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>> I'm no expert at external nodes, so I went and read:
>>> http://reductivelabs.com/trac/puppet/wiki/ExternalNodes
There are many reasons... e.g. if you dont want to allow other people access
to your manifests, or you want a web gui to manage your nodes (e.g. foreman)
etc
maybe you nodes follow a name standards (which should define your host names
etc)
and probably I've missed many other good arguments.
Ohad
On Sun, Dec 13, 2009 at 11:29 PM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> I'm no expert at external nodes, so I went and read:
>> http://reductivelabs.com/trac/puppet/wiki/ExternalNodes
>>
>> That doc still really doesn't say exactly what external nodes are.
>> It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm no expert at external nodes, so I went and read:
> http://reductivelabs.com/trac/puppet/wiki/ExternalNodes
>
> That doc still really doesn't say exactly what external nodes are.
> It's a way of storing node info in an external source such as MyS
Douglas Garstang wrote:
> I don't think you understood my question Scott.
>
Ah, yes and no. I incorrectly assumed you had the syslog_ng::server class
managing itself as a
client as well.
> That doc still really doesn't say exactly what external nodes are.
> It's a way of storing node info in
On Sun, Dec 13, 2009 at 9:25 PM, James Turnbull wrote:
> 2009/12/14 Douglas Garstang :
>> I don't think you understood my question Scott.
>>
>> In any case, I'm avoiding external nodes because you lose all ability
>> to version control.
>
> How do you lose version control? You can easily version
2009/12/14 Douglas Garstang :
> I don't think you understood my question Scott.
>
> In any case, I'm avoiding external nodes because you lose all ability
> to version control.
How do you lose version control? You can easily version a whole
variety of external node stores. You can even include th
I don't think you understood my question Scott.
In any case, I'm avoiding external nodes because you lose all ability
to version control.
I found the solution anyway. It's to include the client node further
up the node hierarchy, since all nodes will have the client, and then
further down the nod
Douglas Garstang wrote:
> What's the best approach for this? I could combine both the client and
> server into one module and simple use case statements to serve out
> files based on their hostname, but that seems ugly. Is there a better
> idea? Can I "UN" include a class?
>
If you use external n
So, I've been doing something like this for applications that have a
client and server component...
node base_node {
include syslog_ng::client
}}
node app_node inherits base_node {
}
node syslog_server inherits base_node {
include syslog_ng::server
}
... because I want the client portion,
14 matches
Mail list logo