I was doing my morning news scan and came across Accelerate virtualization adoption--Seven tips to smart growth by John Suit, CTO at Fortisphere. Although the comments appear to address the adoption of virtual machine software to create virtual servers or virtual clients rather than a broader view of virtualization. That being said, many of the suggestions John makes are likely to be useful to those working with other forms of virtualization as well.
Virtual resources have characteristics that make them a bit different than physical resources. I addressed that topic in Virtual Machines You Have to See Them to Manage Them. If you're interested. Here's a snip from that document.
The simple answer to this question is that virtual resources are different than physical resources in several ways. These differences mean that traditional approaches often don't work in a virtual world.
Most organizations don't have standard processes to collect and maintain lifecycle information about virtualized resources. Much of this critical information doesn't really fit into their usual tracking systems.
For example, one simply doesn't install a physical system one morning and retire it that afternoon. Virtual systems are often created, used and then destroyed in a day's time.
Furthermore, it is unlikely that a physical system would be picked up and moved from one side of the datacenter to another several times a day. In a virtual world, this is quite possible. There are many vendors offering orchestration tools that can move virtual systems from one physical machine to another or change it from being a virtual resource to a physical resource based upon polices or to achieve service level objectives.
Do you agree with John's suggestions? Did he leave anything out?