Virtualisation has changed from a gadget to a hype to a proven solution. There is a myriad of products providing Virtualisation from servers, desktop, applications, appliances and data centers. The advantages are clear, but choosing which steps to take is often unclear.
An Organisation can choose to become a "Microsoft Shop or VMware Shop" and use only Virtualisation products from that Vendor. With that comes vendor lock-in but also good integration and management. A mixed Vendor solution is also possible, which requires more effort in setting up integration and management.
From an Infratesting perspective whatever solution you choose is irrelevant, every solution can be tested. What is important, is that there is a clear Architectural view and Roadmap for Virtualisation. Virtualisation often starts bottom up and is IT driven. This could result in the wrong choice for a solution.
Therefor Virtualisation should be lifted to a higher level and give a top down approach.
That is the only way to get a Real instead of a Virtual Solution.
While surfing the Web I came across an interesting post on Test Republic. One of the Member Pradeep C asked a question "Wanted to understand the definition, and process involved for Infrastructure Testing". He got a reply by Michael Bolton which, although it had some valid points, was not really an answer to his question.
Virtualisation has changed from a gadget to a hype to a proven solution. There is a myriad of products providing Virtualisation from servers, desktop, applications, appliances and data centers. The advantages are clear, but choosing which steps to take is often unclear.
Ever since the launch of Windows Vista there has been a debat about migrating or not. There were issues with Performance, Availability of drivers and Compatibility with older Software. At a certain point even Microsoft advised to wait with Windows Vista. In the mean time Gartner's advice was clear, "don 't skip ". Recently Microsoft changed their view and now advise to migrate.
