I’ve been working with Horizon Workspace since it went GA in March. At this point in time, I’m happy to say that I’ve got Workspace set up in a production environment.
In this series, I will be covering how I configured each part of this suite. I would expect that this process will become exponentially easier as time goes on. One thing to note is that I will write these posts assuming that you are at least moderately familiar with linux and Workspace. I will not go into details on how to install packages, deploy the VA, use the web interface. Use Google if you’re looking for that boring stuff 🙂 Here we go!
Due to the reliance that the business will put on the Workspace, my definition of Production is as follows:
- Externally Accessible
- One URL to rule them all, both internal and external
- Load Balanced from within DMZ
- Multiple Load Balancers – no single point of failure!
- Multiple Virtual Appliances
- At LEAST 2 of every VA that comes with Workspace (Gateway, Connector, Service, Data)
- External Postres SQL Database
- Third Party SSL Certificate
- I used Godaddy, but if I had to do it again, I’d go with Verisign, or a more reputable CA. This should be fixed in Workspace 1.5, which should be released by the end of July.
- Data is stored on NFS rather than on local vmdk
Throughout this (we’ll call it an adventure) I’ve learned a lot about the product.Most importantly, it’s become clear to me that this is not a product easily administered by a “VMware Admin”. Horizon Workspace is built on top of Suse Enterprise Linux 11, relies heavily on Zimbra for the data component, and uses nginx for everything else.
Sound like greek? Don’t panic, you can set up a good amount of Horizon Workspace without being a linux guru, however, imho, most of the things you’ll need to do in a production environment will require at least a moderate familiarity with the linux command line.