{"id":12952,"date":"2012-06-25T09:00:00","date_gmt":"2012-06-25T08:00:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=12952"},"modified":"2012-06-25T09:00:00","modified_gmt":"2012-06-25T08:00:00","slug":"how-to-scale-beyond-a-hyper-v-cluster-in-a-box","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=12952","title":{"rendered":"How To Scale Beyond A Hyper-V Cluster-In-A-Box"},"content":{"rendered":"

Earlier this week I posted some notes<\/a> from a TechEd North America 2012 session that discussed the Cluster-In-A-Box solution.  Basically, this product is a single box unit, probably with two server blades, all the cluster networking, and JBOD storage attached by SAS Expanders, all in a single chassis.  For a small implementation, you can install Hyper-V on the blades in the box, and use the shared JBOD storage to create a small, economic cluster.<\/p>\n

I\u2019ve been thinking about the process for expanding our scaling beyond this box.  At the moment, without playing with it because it doesn\u2019t exist in the wild yet, I can envision three scenarios.<\/p>\n

Scale Up<\/u><\/strong><\/p>\n

On the left I have put together a cluster-in-a-box.  It has 2 server blades and a bunch of disk.  Eventually the company grows.  If the blades can handle it, I can add more CPU and RAM.  It is likely that the box solution will also allow me to add one or more disk trays.  This would allow me to scale up the installation.<\/p>\n

\"image\"<\/a><\/p>\n

Scale Out<\/u><\/strong><\/p>\n

I\u2019ve reset back to the original installation, and the company wants to grow once again.  However, circumstances have changed.  Maybe one of the following is true:<\/p>\n