As a follow up to my prior post, we are now utilizing the all in one setup in a Dev, Test and Production Portal setup
We did the initial installation of both Test and Production in a morning.
But that was after we worked through a few issues with our Win 2012 Server R2 - portal wants .NET 3.5 so we had to install that first.
Our Dev and Test are setup as single boxes with the configuration files there on the local drive.
Production is setup for an HA setup down the road if necessary. i.e. configuration files are out on a shared drive/shared folder setup.
To do this you use a slightly different Chef json file that is found in the roles folder. It's clearly labeled for HA work.
I have had a 180 shift in thinking here. Originally I thought everything should be on separate boxes.
But the ease of putting it on one box made me think twice and then some other conversations convinced me to try this route.
I can always split out boxes if performance suffers.
But in our VMware Sphere environment, I can bump resources on the fly.
We are still configuring Portal so I can't report on how well it works in production yet.