What was once VMTurbo is now turbonomic. The company has decided to shift focus away from the VM and focus more on the turbo in it’s name that is! I feel this is a great way to be agile like the customers are around you. Businesses today are not just focused on “VM” anymore there are more layers and technology coming into play. I am fortunate to be involved in blogger briefings from the company over the last few years.
It is all in a name right? Would Taco Bell be Taco Bell if its name was something different? I think if you take a look to back in the day when they use to ring a dinner bell and peoples love of tacos this was great brand strategy by Taco Bell. turbonomic took a slightly different approach but yet similar, by morphing “Turbo Speed, “automatic control” and “Economic Principles” and forming turbonomic. Not only did they incorporate what their customers are facing today, they implemented the concept and thinking of making the management of your environment as autonomic as your heart beat.
Understand that they do a little more then that, the green circle in the logo represents the green circle community. turbonomic has always been a great supporter of the community with it’s participation in vBlogs, bloggers, user groups and virtual design master, etc so to have a piece of that represented in the logo is awesome.
This is a bold statement and great transition period for companies like turbonomic, to be established then try and shake things up can be rewarding but also have it’s troubles. I am hoping for the best for the turbonomic team while they start this new adventure. If you check their twitter stream you can see it has given some fun spirits to the employees. They are keeping the community, it’s users, employees excited. In my opinion that is what a company should want to do. While I hope they do not change the name again nor does this work for all companies, but turbonomic hit the nail on the head with this move in my book.
*Disclaimer – VMTurbo is a sponsor of this blog*
On February 19th VMTurbo will be holding a webinar to introduce Operations Manager 5.1. As part of the webinar they will be giving away a free home lab kit featuring an Intel NUC i5 with 16GB of RAM and a 4-bay Synology DS415+ (diskless) and a few more goodies to round out the home lab; all in you would be into this setup for about $1600. Not to bad to attend a webinar about a product that could help you identify problems in your infrastructure ay?
*Disclaimer – VMTurbo is a sponsor of this blog. I was not asked to write this post nor was it reviewed prior to being published. The post simply represents my opinions as it relates to the first time use*
First I would like to thank the folks at VMTurbo for setting up NFR access and inviting me to their community site. I have never used VMTurbo before, however I have used vCenter Operations manager and Veeam One. VMTurbo comes as an appliance, I deployed mine in VMware Workstation, powered it on and was able to connect right to the web UI. Before I log in and get started though, I want to give it the appropriate DNS server IP instead of what DHCP is providing. Log into the console as ipsetup/ipsetup
You should now be able to navigate to the VMTurbo UI with the new IP address or FQDN. The initial login is administrator/administrator (though as the UI suggests you probably want to change that). Once logged in for the first time, you will run through an initial setup wizard.
Right away VMTurbo is able to look at resource utilization in the environment, as you can see from the charts below.
You can click through the various tabs in the UI to see different information, for example on the Suppy Chain tab I can see a map of my infrastructure. Using the navigator I can click on the components in my environment and instantly get information about that resource. For example here I clicked on Storage and can see my vxprt-esxi01-gold-local datastore is about about 60% utilization.
Beyond just monitoring, VMTurbo can also make recommendations about how to improve the environment. For example if you had a host over utilized, it could generate recommendations on how to resolve the problem and take action on it. I can also use VMTurbo to perform deployments; one thing I found interesting was that in addition to my existing vSphere templates, there were several already defined such as Microsoft_IIS-small which can help you determine the best location for a virtual machine and use the template to deploy the virtual machine.
I am really excited to watch VMTurbo in my lab over the next few days. It was by far the simplest deployment of this type of system that I have ever done – within minutes it was monitoring my environment. A lab may not be the best litmus test for VMTurbo, but given the ease of install and the fact it does not need any agents you may want to go ahead and see what it finds in a larger test or production environment. I’ll keep you posted on what other cool things I find as I explore the many options in VMTurbo Operations Manager.