On Sun, Jun 7, 2009 at 6:35 PM, James Turnbull wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nigel Kersten wrote:
>> I find it difficult to work out how best to document all this given
>> that plugins in modules are still not particularly well supported with
>> environments, and m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Kersten wrote:
> I find it difficult to work out how best to document all this given
> that plugins in modules are still not particularly well supported with
> environments, and most people I've come across using environments
> heavily are still
I find it difficult to work out how best to document all this given
that plugins in modules are still not particularly well supported with
environments, and most people I've come across using environments
heavily are still using factsync, no matter how "legacy" it seems.
--~--~-~--~~-
James Turnbull wrote:
> Brad wrote:
>> On Jun 5, 12:39 am, James Turnbull wrote:
>>> But yes it was a little confusing. I've edited the page to make it
>>> easier to understand. Please let me know if that has helped.
>> Thanks but it still didn't seem very clear to me. Might as well just
>> expl
Brad wrote:
> On Jun 5, 12:39 am, James Turnbull wrote:
>> But yes it was a little confusing. I've edited the page to make it
>> easier to understand. Please let me know if that has helped.
>
> Thanks but it still didn't seem very clear to me. Might as well just
> explain the situation right at
On Jun 5, 12:39 am, James Turnbull wrote:
>
> But yes it was a little confusing. I've edited the page to make it
> easier to understand. Please let me know if that has helped.
Thanks but it still didn't seem very clear to me. Might as well just
explain the situation right at the top. I just ma
Brad wrote:
> On Jun 4, 8:27 pm, Brad wrote:
>> I'm working on a "real" fact by following these steps:
>>http://reductivelabs.com/trac/puppet/wiki/AddingFacts
>>
>> I verified that the custom fact works when run locally on the server.
>> On the client when I run:
>>puppetd --server hostnam
On Jun 4, 8:27 pm, Brad wrote:
> I'm working on a "real" fact by following these steps:
> http://reductivelabs.com/trac/puppet/wiki/AddingFacts
>
> I verified that the custom fact works when run locally on the server.
> On the client when I run:
> puppetd --server hostname --test --factsync
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad wrote:
> On Jun 4, 4:26 pm, Thomas Bellman wrote:
>> I would probably do it with something like this:
>>
>> class node::compute { ... }
>> class node::database { ... }
>>
>> node default
>> {
>> include "node::$nodet
On Jun 4, 4:26 pm, Thomas Bellman wrote:
> However, a "real"
> custom fact is probably cleaner.)
>
I'm working on a "real" fact by following these steps:
http://reductivelabs.com/trac/puppet/wiki/AddingFacts
I verified that the custom fact works when run locally on the server.
On the client
On Jun 4, 4:26 pm, Thomas Bellman wrote:
> I would probably do it with something like this:
>
> class node::compute { ... }
> class node::database { ... }
>
> node default
> {
> include "node::$nodetype"
> }
>
> and get myself a custom fact 'nodetype' that gets s
schickb wrote:
> I'd like to have the client specify their own node names. Actually,
> what I really want is for clients to specify a node "type". In other
> words, I don't care what the machine or domain name is... I just want
> to know the purpose of the node. Is a "compute" node or a "database
12 matches
Mail list logo
