The latest version of Turbonomic includes enhanced public cloud support; cloud cost tracking and budget management, as well as cloud migration planning. In this post we’ll look at the forecasting costs, and savings, for migration to public cloud using Turbonomic v5.9.
To upgrade to version 5.9 review the release notes here and follow the offline update steps outlined here. Further documentation for version 5.9 and previous versions can be found here. For assistance with installing Turbonomic from scratch see the Turbonomic Install Guide.
In order to display costings for public cloud you must add a cloud management target (such as AWS, Azure, etc.) to Turbonomic. If you haven’t already done this then see the post Configuring a Turbonomic Cloud Target. New features are available in the HTML5 web UI. Whilst the new web UI is cleaner and much easier to navigate, you may also want to review the HTML5 UI User Guide to help you get to grips with the new interface.
Plan Cloud Migration
Log into the Turbonomic web UI by browsing to the IP address or FQDN of your Turbonomic instance. When prompted select to try the new interface (you can reach this direct at https://IP/com.vmturbo.UX/app/index.html, replacing IP with the appropriate address).
From the left hand option pane select Plan. Click Create Plan.
Select Migrate to Public Cloud.
Choose the VMs or clusters you want to run the migration plan for and click Next. The health status for a VM or cluster is indicated next to the check box, you can expand an entity for further health information.
Select the destination cloud provider. As mentioned above, you must have a cloud provider added as a target for it to be displayed here. Click Migrate to Cloud to run the plan.
The cloud migration plan will run, once complete VM resource and costing outputs will be displayed.
Turbonomic 5.9 offers further enhancements around public cloud workloads; such as the ability to proactively effect performance and cost in real-time, billing of cloud services can be broken down into daily, weekly, or monthly cost based on your account with your own enterprise rates, ongoing forecast of how infrastructure costing can be reduced, scaling of cloud instances to meet application and budget demands. Processing times are also typically 100-400 times faster than previous versions. These are not the results of lab evaluations but have been proven in real life customer environments. Analysis of 18,000 VMs can produce results and actions in 30 seconds, ranging up to processing data for 100,000 VMs in 9 minutes.