With VMware’s success, vendors have begun touting virtualization products for every layer of the infrastructure, but management and security lag behind.
An FAQ on virtualization.
What is the ideal way to deploy virtualization?
What are the drawbacks of using virtualization?
What is the status of virtualization standards?
When is a product not really virtualization but something else?
What is virtualization?
Virtualization is software that separates a run-time process from the underlying infrastructure that supports the process. Server virtualization, for instance, separates the application from the physical server. It is the most widely deployed example but virtualization vendors are emerging for every layer in the infrastructure including network, storage, desktop, application, database, user interface – even security and mobility.
What is the ideal way to deploy virtualization?
Although enterprises gain incremental benefits from applying virtualization in one area, they gain much more by using it across every tier of the IT infrastructure. For example, when server virtualization is deployed with network and storage virtualization, servers gain the ability to boot in a different data center for disaster-recovery purposes.
What are the drawbacks of using virtualization?
Not all virtualization technologies are equally mature. Whereas server virtualization has hit its stride, other areas are not as far along. And getting the various virtualized pieces to work together cohesively can be a big challenge. When performance issues crop up, conducting a root cause analysis becomes more difficult.
Also, many security systems do not yet support virtualization. For instance, common security devices, such as firewalls, may still operate on the assumption that an IP address represents a static association to a specific piece of equipment. This makes it difficult to move resources around without impacting the security device. Technologies such as federated ID and digital certificates are heading in the right direction, and recent moves by Cisco and others to add more security within switches and routers also are positive signs. But placing the security in the virtualization product itself would be the best solution.
What is the status of virtualization standards?
True open standards for getting all the layers talking and working together aren’t ready yet, let alone giving users interoperable choices between competitive vendors. Users are forced to rely on de facto standards at this time. For instance, users can deploy VMware and Microsoft Virtual Server within one environment, as each provides the ability to import virtual machines from the other. But that’s about as far as interoperability currently extends.
When is a product not really virtualization but something else?
Application vendors have been known to overuse the term and label their product “virtualization ready.” But by definition, the application can’t tell whether it’s on a virtualized platform or not. Some vendors also label their isolation tools as virtualization. To isolate an application means files are installed but are redirected or shielded from the operating system. That’s not the same as true virtualization, which lets you change any underlying component, even network and operating system settings, without having to tweak the application.
Previous story: The Buzz Issue | Next story: Virtualization hits the big time >
