On Wednesday, September 24, 2014 3:48:23 AM UTC-5, MezcalitoSCOP grenoble
wrote:
>
> Hi Jhon,
>
> Sorry, I just remark that I completely miss your answer a long time ago.
>
> Le vendredi 9 août 2013 15:54:35 UTC+2, jcbollinger a écrit :
>
>>
>> You can divide your resource declarations among mul
Hi Jhon,
Sorry, I just remark that I completely miss your answer a long time ago.
Le vendredi 9 août 2013 15:54:35 UTC+2, jcbollinger a écrit :
>
> You can divide your resource declarations among multiple classes and have
> each node declare (only) the classes it needs. This is part of what Ma
On Thursday, August 8, 2013 11:40:45 AM UTC-5, mezca...@gmail.com wrote:
>
>
>
>> Your core problem is that you have big data, and nothing we can suggest
>> will change that. So, what criteria are important to you in comparing
>> potential solutions? Without a better idea of what you're after
>
> Your core problem is that you have big data, and nothing we can suggest
> will change that. So, what criteria are important to you in comparing
> potential solutions? Without a better idea of what you're after, we're
> just shooting in the dark.
>
>
I have big data and I understand I can
On Thursday, August 8, 2013 4:48:02 AM UTC-5, mezca...@gmail.com wrote:
>
> In your example using hiera, you put all vhosts config data in one yaml
> file. This solution seems to be maintainable in this case but if I use this
> solution for bind::zone datas the yaml file still be very big and d
> You might consider using create_resources with hiera. Here's a simple
> example.
>
> yaml data
> ---
> apache::a2mods:
>expires: {}
>gnutls: {}
>headers: {}
>rewrite: {}
> apache::vhosts:
> statsstage.example.com:
> priority: '99'
> a_templa
Le mercredi 7 août 2013 16:13:26 UTC+2, Mason a écrit :
>
> Assuming all the dns servers are getting the same config, We break big
> chunks like that out into their own modules. So:
>
> node dns1.myco.com {
> include myco::dns
> }
>
> node web1.myco.com {
> include myco::web
> }
>
> If the se
On 8/7/2013 6:55 AM, mezcalit...@gmail.com wrote:
Hi,
I use puppet to manage servers in a mutualized hosting context and I get
some trouble concerning the node definitions.
For example on dns nodes I have to declare many `bind::zone` resources
like this:
bind::zone { ['website1.com']:
expir
Assuming all the dns servers are getting the same config, We break big chunks
like that out into their own modules. So:
node dns1.myco.com {
include myco::dns
}
node web1.myco.com {
include myco::web
}
If the servers have different configs, you can make myco::dns::common,
myco::dns::this m
Hi,
I use puppet to manage servers in a mutualized hosting context and I get
some trouble concerning the node definitions.
For example on dns nodes I have to declare many `bind::zone` resources like
this:
bind::zone { ['website1.com']:
expire => 604800,
minimum => 3600,
ttl => 38400,
…
10 matches
Mail list logo
