The Anatomy of Cloud Costs Planning

Recently we had the pleasure of working with Polleo Systems to help them with their cost planning for the cloud. They have several hundred VMs and they were evaluating which of them to migrate to the cloud and why. Some word of mouth recommendations led them to ask us for a demo of our software.

Our contact, Brandon who is a system engineer at Polleo Systems, led us through his requirements –

  • Show them which cloud provider is most cost effective
  • Show them the costs of their on-prem VMs in AWS, Azure and SoftLayer
  • Show them savings in the cloud vs. on-prem
  • Be neutral – i.e, not affiliated with any cloud vendor

The first step in their Cloud Planning project was understanding the configuration of the on-prem VMs. Brandon downloaded Akasia SaaS’s “On-Premise Data Collector” and ran it in his data center. The Collector gathered information about the on-prem VMs, specifically –

  • Host configurations
  • VM configurations
  • VM utilization data

The Collector created 4 CSV files that Brandon then uploaded to the Akasia SaaS platform. The CSV files are human readable, allowing Brandon to ensure that no privileged data was leaving his data center.

The next step was to select the VMs that Brandon wanted to map to the cloud. He selected 50 of them and ran them through Akasia’s mapping engine. The output from the Akasia SaaS engine gave him

  • on-prem VM configs including “hidden cost items” such as network and I/O
  • equivalent cloud templates for each of his on-prem VMs and their prices
  • right-sized cloud templates for each of his on-prem VMs and their prices
  • prices of network, storage and I/O in each of the clouds

Next Brandon modeled his entire cloud environment in the Akasia SaaS platform by adding advanced cloud services such as OS licenses, ingress and egress traffic, load balancer, IP address and support licenses.

In the end he had complete clarity on what he needed to order (bill of materials) in each cloud, AWS, Azure and SoftLayer. He could compare his expected monthly cloud costs side by side to get a clear sense for where he would save the most. Akasia SaaS gave him details on the cloud options too – such as AWS On Demand and AWS Reserved Instance as well as SoftLayer Public Node and SoftLayer Private Node.

Armed with the costing data from Akasia SaaS Brandon was able to make a data driven case for migrating to his cloud vendor of choice – AWS. By working with our partner who performed the migration into AWS, Polleo ordered AWS line items as recommended in the Akasia output to build out their environment in AWS. The environment consisted of templates, S3 storage, network options as well as DB licenses.