window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-16803030-1');


Quest for the Perfect Social Platform–Part 2

By Patrick Tredway | Sep 12, 2011 | Insights

Let’s call this Quad day 1 and what a ride its been so far. Admittedly, my Linux skills are limited and that most certainly did not help in this process. There’s been quite a bit of learning about command and control of files systems and mount points that I had previously been able to get through life with which not having to become so familiar. This is all without brining up the oracle discussion…which I’ll skip, for now.


As it stands right now, I have created and deployed twelve, count them, twelve virtual machines to support this meager deployment. This sounds like an extraordinary number of servers, and it is, except for the fact that it’s all running on only two UCS B-Series blades and barely touching the CPU and RAM counts. Each blade has a single 6 core processor and 48GB or RAM.




For performance and failover testing reasons, I have all images running from one host and it’s topping out at less that 10% average CPU and 21GB of RAM consumed.




The number of virtual machines and the subsequent installation of each was initially disconcerting. Having said that, through the install process I have gathered a pretty good understanding of each machine and the role it provides. The manner in which Quad separates services would easily allow for rapid growth and roll out capacity to the tens or even hundreds of thousands of users. This isn’t all that surprising when you take into account Cisco’s history or delivering a product for the enterprise market and over time bringing it downstream.


Cisco’s approach to separating services isn’t all that different that say SharePoint; however, SharePoint allows for database, search, web, and cache services to be installed co-resident. Quad is in essence doing the same thing except that its abstracting the services out at the virtualization layer as opposed to a windows service layer. If anything, this gives Quad a bit of an advantage from flexibility and agility in allow services to be moved around or scaled without having to re-spin. 


Now that we’ve completed  the installation phase of this little project, we move into usability testing. Over the next few weeks I’ll be making a number of integrations with Communications Manager for phone services, Unity Connection for voicemail presentation, Exchange 2010 for calendar accessibility, and the WebEx Connect cloud for presence federation. It’s going to be an exciting few weeks. More info to come!

Leave a Reply

Your email address will not be published. Required fields are marked *