>>> As the number of servers I am using puppet on is increasing, I'm wondering 
>>> what the best practices is for the nodes. Currently they all sit in the one 
>>> file /etc/puppet/manifests/nodes.pp.
>>>
>>> What I'm wondering is whether this is the best way to go (that is, one 
>>> large file) or is it better to split the nodes into individual files or 
>>> some other logical segregation?
>> Using external is quite mandatory when things grow. See
>> http://reductivelabs.com/trac/puppet/wiki/ExternalNodes for more
>> informations.
> 
> I REALLY disagree with this. How do you version control your nodes if
> they are stored externally?

with a version control? for example if you have a little rails app for
your node setup with acts_as_versionable on your model. Or if you do it
with ldap: how do you do version controle in ldap if you have things for
your infrastructure there? A very straightforward way would be to dump
the ldap-data regularly (after a change?) and version that one.

Well either you stick with plain text files you can version control as
you are used to. But this can get very messy very fast. Or you use
something else for a source for your external nodes. For example some
kind of central inventory system your company strategy leader xy senior
manager has bought... ;)

There are so many ways people can be forced to get their node
information from, it can't be up to puppet to care about versioning of
all these issues.

Anyway if somebodies xy super inventory product is so critical for their
infrastructure it should provide some kind of versioning, shouldn't it?

cheers pete

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to