In my virtual environment recently, I experienced two major failures. The first was with VMware vNetwork Distributed Switch and the second was related to the use of a VMware vShield. Both led to catastrophic failures, that could have easily been avoided if these two subsystems failed-safe instead of failing-closed. VMware vSphere is all about availability, but when critical systems fail like these, not even VMware HA can assist in recovery. You have to fix the problems yourself and usually by hand. Now after, the problem has been solved, and should not recur again, I began to wonder how I missed this and this led me to the total lack of information on how these subsystems actually work. So without further todo, here is how they work and what I consider to be the definition for fail-safe.
At last year’s VMworld in San Francisco Stephen Deasy (Director, R&D, VMware) and Srinivas Krishnamurti (Senior Director, Mobile Solutions, VMware) announced VMware’s plans for a type II mobile hypervisor platform. Three months later VMware and LG have announced a partnership to install VMware Mobile Virtualization Platform (MVP) on LG smart phones starting in 2011. While significant questions remain about the viability of this partnership, the need for a mobile virtualization solution cannot be stressed enough.
SolarWinds is betting that due to the size of its existing administrator community (the over 1M users of its free tools, and the 97,000 paying customers) that it can cost effectively reach the admin’s at the 225,000 VMware customers that are being under-served by the vendors targeting larger customers and larger VMware environments.
I have started the year 2011 out by looking at some of the different monitoring solutions available for us to have an insight into the health and welfare of the systems that we support. In your typical monitoring solution you would install the monitoring server in your environment and let the system discover all the devices in your infrastructure and or to control the licenses we would manually enter the devices that we want to monitor. Some of these monitoring servers solutions have to have a beefy box to begin with and all solutions will need a great deal of “tweaking” to control the number of false positives as well as time put in to be able to report on what exactly we care to be alerted about.
You heard the buzzwords and drunk the kool-aid and now you want to move to the cloud, how do you do this? This has been the a fairly interesting question on the VMware Communities Podcast yesterday, when the vCloud team showed up to talk about the current reference architecture. Yet almost all the questions were about going to the cloud and not about the architecture. Does this mean people do not understand what is required to go to the cloud? I think so. So to take a few elements from the podcast and put them in writing is the goal of this article. The Simple Steps to move to the cloud.
• • 1 Comment
If synthetic transactions are dead as an approach for determining availability and performance from the perspective of the end users of an application then something has to take their place. The two candidates are approaches that analyse data on the IP network, and client side agents. Both will likely rise in prominence as more applications become more dynamic.
• • 3 Comments
When considering a Virtual Desktop Design a good architect needs to ask “what is the best solution for this environment?” For many, once you’ve considered the needs of your users, it is a combination of desktop delivery models – some virtual, some physical. Ideally the user is unaware of which model is being delivered to them, they consume that service on an appropriate device, at an appropriate time. Ringcube perhaps first to market for this type of solution with their Workspace Virtualization Engine.
Monitoring the performance of the infrastructure, applications and services in IT as a Service environments will require that monitoring solutions become multi-tenant, can be instantiated by ITaaS management tools without any further configuration, and that they automatically “find” their back end management systems through whatever firewalls may be in place. These requirements will probably be the straw that breaks the camel’s back for the heavyweight complex legacy tools that were in place prior to to the onset of virtualization, the public cloud and now IT as a Service. ITaaS is the tipping point that should cause most enterprises ignore every monitoring tool that they have bought in the past and to start over with a clean sheet of paper.