I'm hoping to get some insight from you guys. I'm using roles and profiles in my puppet set up and I'm struggling a little with a particular role.
I leverage the puppetlabs-tomcat module in my tomcat profile but I find that I have applications that reside on different tiers and it's not fully functional as is. In my production environment each tier resides on their own set of VMs, each VM contains only a single instance of tomcat with a single war file, but in some of my development and QA environments the tiers can be co-located on the same VM, with different instances and different war files on the same VM. My current tomcat profile works perfectly where the tiers are separate, but needs some enhancement if they are co-located. All of my data is defined within my hiera hierarchy. My current profile only considers that you have a single instance, and a single war. What I would like to do is to be able to do multiple instances, with multiple wars on the same VM using the same puppet code, not my current code of course. I know there are several possible solutions to this, but I'm wondering if someone else has solved this and would be willing to offer some advice. I've thought about maybe using a profile "instance" that I could do more than one of and that may be the simpler solution. I've also thought about using some sort of hash in my hiera that I could merge and then do some sort of create_resources call that would then instantiate my "profiles". I don't want to make this needlessly complex if I don't have to, so if someone else has any suggestions I would appreciate it. Thanks, Drew -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a1ab0fa6-9eb9-4131-a8d0-a156cbdc6a29%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.