Hello Andy. I will explain what we have now. That will probably be helpful for you to understand what we would want to do in the future.
We run a datacenter with multiple customers with >300 server installations. The central management that we have now is done with cfengine and our own customizations plus jinja for templating. We have one master repository in SVN where our own staff has access. Each customer has their own repository where they have write access. Then we combine the master repository and client repository on the cfengine server and run the customizations and templating there. This works because the jinja engine is sanboxed so it cannot hurt the server or see into the next customer's files. The customers can commit their changes into svn and trigger (using a http call) the commit process to happen on the cfengine server. This is what we like to do in puppet too. What we are thinking now is that we install one puppet master per client and use a puppetmastermaster to control those. Thank you, -jk -- Nam in omnibus fere minus valent praecepta quam experimenta. -Quintilian Jaska Kivelä | Cybercom Finland | gsm 040 576 2988 [email protected] | Pakkahuoneenaukio 2 A | fax 010 665 3060 specialist | PL 13, 33201 TAMPERE | OCP - RHCE - JNCIA -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
