I recently upgraded my nodes from 96 GB of memory to 256 GB of memory, and someone on Twitter stated the following:
@Texiwill thought the trend today is scale out not scale up? #cloud
The implication was that you never upgrade your hardware: you buy new or you enter the cloud. Granted, both options are beneficial. However, buying new and adding to your environment may not be necessary, and you most likely have already entered the cloud with the use of SaaS applications and perhaps some IaaS. The question still remains: upgrade, enhance existing hardware, or buy net new somewhere? When should you do any of these? Or should you at all?
I have had the opportunity to perform a few VMware Capacity Planner assessments over the years and I have been, more the most part, pretty happy with the process and the results of the reports. The assessment is really pretty straight forward. We had physical servers to the project, making sure we have proper permissions to perform all the tasks and then let the process run over an extended period of time. For the most part, this way of sampling over an extended time frame will give you a very good idea what can be virtualized and the number of hosts that will be needed.
Whether you are building a new or adding to an existing virtual or cloud environment on a shoestring budget, whether for work or for home use, there is quite a bit to consider before you purchase anything and it all boils down to your requirements which will dictate the technology you need for your virtual environment. In addition, this is a perfect time to address any deficiencies in your environment to not only address capacity issues, requirements, and security. Along with those considerations, planning the environment for the next three to five years can help shape the overall design. In fact that design, will be based on the answers from a growing list of questions:
In the past, virtualization architects and administrators were told the best way forward is to buy as much fast memory as they could afford as well as standardize on one set of boxes with as many CPUs as they dare use. With vRAM Pool licensing this type of open-ended RAM architecture will change as now I have to consider vRAM pools when I architect new cloud and virtual environments. So let’s look at this from existing virtual environments and then onto new virtual and cloud environments. How much a change will this be to how I architect things today, and how much of a change is there to my existing virtual environments? Is it a better decision to stay at vSphere 4? Or to switch hypervisors entirely?
Yesterday, Simon Bramfit vSphere 5 – Did VMware Misjudge its Licensing Changes? requested a VDI only version of vSphere and yesterday VMware responded with vSphere Desktop which for VDI removes the vRAM Entitlement barrier. I see this as progress and that VMware is listening. Unfortunately, this is for new purchases and you cannot convert existing vSphere licenses into vSphere Desktop licenses.
In VMware and the Ionix Assets – A Deeper Look, we took a fairly in depth look at the four products that VMware bought from EMC, and posited that VMware was now well on its way to fulfilling its promised intentions of becoming a vendor of a management stack for virtualization. In this article we take a look at the impact of these acquisitions upon the virtualization performance management market and the ecosystem of solutions available in this market.
Citrix Edgesight for Load Testing has been quietly updated to version 3.5 with very little razzle or dazzle.
Citrix EdgeSight for Load Testing is an automated load and performance testing solution for Citrix Presentation Server environments. As of XenApp 5.0 Feature Pack 1, the Load Testing service is no longer a separate licensed product and is now a free component in XenApp. While we’ll gloss over the pique that customers who bought the licenses just before this was announced, it doesn’t detract from the fact that Citrix Edgesight for Load Testing is an incredibly useful tool for supporting and sizing even a small farm and is, arguably, a credible differentiator for using ICA over RDP.