Vote with your fingers
Shameless plug, but it has to be done! Voting is now open to the public to choose VMworld sessions! Awesome idea by the VMware team: well done!
As one of the people who worked at VMware on several previous VMworlds I know that choosing sessions is incredibly hard and people are often disappointed. The problem is, what we often *think* is a good session is sometimes rated *poor* by the attendees, and previous scores are a key part of the next VMworld decision process. There’s a balance to be achieved that has so many pressures: it’s a tough job and you have to respect the VMworld organisers even if the decision doesn’t go your way.
I think VMware are doing something awesome in they are extending this scoring system to a public voting system so they have more data on which to make the final decision.
I’m hoping you, Dear Reader, will take some time out of your busy day to vote for my session if you think it would be of interest. Here’s the link and the description of my proposal:
Private Cloud Management – A7792 - Turning VMs into job queues for maximum ROI
Most vSphere implementations have excess capacity that could be used by the business instead of just burning money without return. To get these two benefits (business agility and increased ROI) you need two operational abilities: 1) Understanding what excess capacity is available and when. 2) A method for scheduling workloads to use that excess capacity. An example of using the excess capacity is bringing up a database system to do more business data crunching, or deploying a Hadoop cluster to run scheduled jobs against large datasets. This session will demonstrate these two operational capabilities and how they deliver the two benefits of getting IT to do more for the business.
This session is all about using the Stranded Capacity that is so ubiquitous in enterprise computing (unlike Amazon Cloud which has a more even distribution): so this session describes one method of exploiting that capacity to run other workloads.
Think: VDI running on ESX is *mostly* busy between 6am and 10pm. That means eight hours a day, fifty-six hours a week and nearly three thousand hours a year there is some measure of excess capacity.
If you could exploit that with minimal risk, would you? Could you? I think so, and so do others… vote for me and find out why and how! This will be a practical demo followed by a discussion. More detail and data, less theory.
Comments