bind zones, virtual mailboxes or other mass-services.
We currently don''t know how to handle so many vhosts through puppet. We
saw that puppet can read node information in a ldap db, but puppet can
only read NODE information, not vhosts parameters. As for today, is it
(in your point of view) a clean way to do this with puppet ?
We tried to found some way that may (or may not) work (some of these
will be harder to implement though ...)
* Use a template system in our code to generate vhosts files in puppet
and upload them to the web nodes using puppet:// standard.
* Generate puppet arrays in our code and use puppet recipes to read them
and create the vhosts files.
* Create a simple shell or perl script that will read the vhosts
parameters from the central sql database and generate the vhosts, and
use puppet only to upload this script to the web nodes.
* add ruby code to puppet so that we can inject directly AST or objects
to puppet, that will be converted to vhosts files on the web nodes.
I didn''t find anything related to this in puppet trac doc, so do you
have any advice about this ?
Thanks a lot for your help,
Best regards,
Benjamin Sonntag
AlternC team.
