how to generate puppet modules or manifests files according to different groups of servers dynamically?

[Robert Chen]

hi all,

my company has a huge number of servers which are doing different functionalities and these are changing everyday.  I want to make the customers to customized their requirements in a YAML file and then generate puppet manifests for modules dynamically. 

For example, a new groups of servers are coming to CMDB, then they make the configuration requirements in a YAML file. Then I write a script to convert YAML to puppet modules or manifests. Nothing is certain.  Probably different function put into different git repositories, like SiteLogin,  SiteRegistration, SiteCheckout...? 

Anyone has this experience or please share your idea. 

thanks,

Robert

[jcbollinger]

I recommend against attempting to generate manifests dynamically, but you absolutely can use data to drive what classes (among those available) are declared for each machine.  Under control of those classes, you can, to varying extents, use data to control which resources are managed on each machine.  Connecting external data (YAML-formatted, even) to your classes is what Puppet's "Hiera" subsystem is all about.  Instead of dynamic manifest-writing (and re-writing), changing the data is sufficient by itself.

You may also consider looking into Puppet Enterprise, The Foreman, or a similar product that builds on the Puppet capabilities just described.  Perhaps one of them would provide some of the other pieces of the picture for you.

Overall, however, your question is both broad and somewhat abstract.  It's hard to give any specific advice, but yes, Puppet can play in that arena.


John