Split install feature?

[arubdesu]

I'm trying to model my prod environ which has a split install(master/db/console) and don't see support for that setup in Oscar. Is that something you'd consider implementing?

[Nr18]

You could create 3 roles

• Master
• DB
• Console

Each invoking a different manifest or set certain facts on that particular machines that a puppet master could decide on if it is the DB or the Console and than apply certain classes to it. In PE 3.4 they have a cool feature where you could create groups based on rules and you can apply classes on that group.

Because PE 3.4 isn't out yet i solved it by creating a roles class that does that same logic but then from a module.

[arubdesu]

I have made three roles, and hacked the vmx's separately to meet minimum requirements, and modified the IP's in the hosts file and opened ports in the firewall... but the install fails post-puppetdb setup. I've pinged vagrant support and ask.puppetlabs about it, my (barely functional) vagrantfile is here: https://gist.github.com/b7c562a016766ebeffcb ...

[Nr18]

Looks like your not using oscar at all. Oscar allows you to split the configuration up into multiple files.

[arubdesu]

...and sorry to distract the thread further with my unrelated issue, but for those playing along at home, I closed my ask.puppetlabs question as for whatever reason turning off the instances firewalls altogether allowed the install to succeed with this vagrantfile. (Having an active wired connection may have contributed?) Hopefully I'll level-up my vagrant-fu sooner rather than later and document incorporating Oscar into the process.