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, we're
>> just shooting in the dark.
>>
>>
> I have big data and I understand I can't make it disappear but I just
> want to know if there is any way to not put all these datas in the same
> file.
> Maybe I misunderstood but the solution of Ramin or Mason seem to just
> "move" all these datas in a other place/file.
>
Yes, you have misunderstood especially Mason's response.
>
> In short, I have to declare few hundred of resources on a node and each
> resources potentialy have specific param/datas.
> And my criteria is that I don't want to put all these declarations in a
> single file because it is too difficult to maintain.
>
>
You can divide your resource declarations among multiple classes and have
each node declare (only) the classes it needs. This is part of what Mason
was trying to tell you. Each class should be recorded in a separate file
anyway, so that achieves splitting up your data among multiple files. Each
class may contain as few or as many resource declarations as you like.
Also, if there is any overlap between the resources needed by different
nodes then you can reduce the overall volume of data by merging the common
bits into classes used by multiple nodes:
modules/zones/manifests/website1_com.pp:
----
class zones::website1_com {
bind::zone { 'website1.com':
expire => 604800,
minimum => 3600,
ttl => 38400,
…
records => [
'www IN A xxx.xxx.xxx.xxx'
…
]
}
}
modules/zones/manifests/website2_com.pp:
----
class zones::website2_com {
bind::zone { 'website2.com':
expire => 604800,
minimum => 3600,
ttl => 38400,
…
records => [
'www IN A yyy.yyy.yyy.yyy'
…
]
}
}
manifests/site.pp (or wherever you store your node definitions):
----
node /.*\.website1\.com$/ {
include zones::website1_com
}
node /.*\.website2\.com$/ {
include zones::website2_com
}
You can do the same thing with vhosts, of course.
Alternatively, if individual nodes are not unreasonably large by
themselves, then it might suit you to just split your node declarations
into separate files. That's actually pretty common:
manifests/site.pp:
----
import 'nodes/*.pp'
manifests/nodes/website1_com.pp
----
node /.*\.website1\.com$/ {
bind::zone { 'website1.com':
expire => 604800,
minimum => 3600,
ttl => 38400,
…
records => [
'www IN A xxx.xxx.xxx.xxx'
…
]
}
apache::vhost { ... }
...
}
manifests/nodes/website2_com.pp
----
node /.*\.website2\.com$/ {
bind::zone { 'website2.com':
expire => 604800,
minimum => 3600,
ttl => 38400,
…
records => [
'www IN A yyy.yyy.yyy.yyy'
…
]
}
apache::vhost { ... }
...
}
That's similar to what you're doing now, but it's safer. Of course, you
can combine those approaches, too.
Do note that Puppet's 'include' function is not analogous to
similarly-named directives in some programming languages. It does not
interpolate files; rather, it declares that the named class should be
included in the target node's catalog.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
