VMTurbo was originally “AgilITy”

August 7th, 2014 by

What few probably know is that my first name for VMTurbo wasn’t VMTurbo – the first name that came to mind was “AgilITy”. One of the key facets in my founding vision to revolutionize IT Operations management was to increase IT agility, by reducing vendor lock-in to preserve flexibility for future needs. Ergo, AgilITy.

Agility has always been key to our vision here at VMTurbo. Think about it: why are your VMs tied to any one vendor or technology? Is it for a specific technical need? Perhaps – there are arguments for specific technologies for specific workload demands – but in reality often your VMs are tied to a specific technology due to ELAs or some other contract “lock-in” reason, rather than pure technology.

At VMTurbo our mission is simple: set your workloads free!

Stop being locked into ANY technology – choose whatever technology you need to best deliver your service to your customers, and maintain maximum flexibility to stay agile to take advantage of any opportunity the future may hold. Stop being a hostage to any vendor, no matter how awesome it may seem today…

When we architected VMTurbo, we focused first on the abstraction layer: abstracting every entity in the virtualized IT stack into a marketplace of resources. This allowed us to avoid having to collect massive amounts of data to work, and overcome the challenge of identifying signal from all the noise typical of IT operations. As one of my favorite engineers explains it, with our abstraction “we transform your software-defined datacenter into a software-defined commodity market.”

To create this abstraction, VMTurbo creates a common currency to assign a price to each entity – thereby enabling comparison of previously incomparable resources like RAM and IOPS as as like commodities – commodities to be bought and sold by datacenter entities as needed. Selling entities price their commodities based on utilization (demand), while buyers continuously shop for the best price for the resources they require (supply). This common data model abstracts away limitless detail and provides a common interface for controlling the environment. Just as important, it enables us to simply extend this abstraction to add new entities to the marketplace.

This is how we fulfill the mission of setting your workloads free (and controlling them in a healthy, “desired” state).

In service of this mission, we’re announcing VMTurbo Cloud Control for OpenStack – and we’re not only supporting OpenStack, we’re contributing back to the community to further enhance the OpenStack platform.

VMWorld Release: VMTurbo Offers Control for OpenStack

IT Agility, however, was only one of the tenets on which VMTurbo was founded. We’ve always believed that by re-imagining the way IT Operations worked we could help IT assure performance while maximizing efficiency while increasing agility. Performance. Efficiency. Agility. In IT, each is difficult to achieve individually; but to achieve each in tandem with the others has been viewed by many as impossible. We disagree.

To keep achieving the impossible, we’re constantly expanding the power of Software-Driven Control across (and deeper into) the IT stack through the abstraction of our marketplace. That is our relentless pursuit, and the first half of 2014 was no different. Which made it really exciting.

Here are some highlights:

  • We’ve built new hardware support into our Control Modules for Storage and Fabric. This expanded support provides customers the ability to drive more comprehensive management of virtualized workloads in converged infrastructure such as Flexpod and Vblock, as well as in storage control, including support for EMC VNX, enabling up to 30% improvement in utilization
  • As I mentioned earlier, we’ve built new support for OpenStack (in our new Cloud Control module), including contributions back to the community building instrumentation for Software-Driven Control into the OpenStack Java SDK, as well as contributing to Ceilometer (OpenStack Unified Instrumentation/Metering) and Nova (OpenStack Compute) projects, joining our existing support for VMWare, Microsoft, RedHat and Citrix environments
  • The new ability to reserve capacity for future workloads, by enabling not only the scheduling of those workloads but for VMTurbo to reserve adequate capacity for those workloads to launch when needed – this is something that our customers have been asking for, and we delivered
  • Patents covering proprietary uses of economic principles in the management and control of IT environments
  • Numerous improvements in VMTurbo’s patented, award-winning Software-Driven Control including:
  • Cluster Flattening enabling vMotions across cluster boundaries
  • Broader APIs, for example action settings, inventory information
  • Resource pools as VDCs enabling users to Control resource pools as well as visualize resource pool dependencies via nested pools hierarchy
  • Action management enabling users to compare the cost of action vs. impact of action

These are all extraordinary innovations, and I’m extremely proud of the achievements of the team in our labs as well as across VMTurbo. But like any innovator, we must keep our eyes more focused on the horizon than on any of our past achievements.

Expect more great things later this year and next as VMTurbo expands Software-Driven Control further up into the application layer, delivering control that is not only application-aware, but application-driven.

As well as a new way of imagining clusters in a Software-Defined world, helping you move to SDN safely without the risk of introducing unintended latency.

Come to think of it, the second half of 2014 may end up being even more exciting than the first. Stay tuned…

Leave a Reply

Your email address will not be published. Required fields are marked *