In-cloud Costs

The following rules are applied in the calculation of in-cloud VM cost.

  • Compute - Compute costs are determined by first mapping the VM to a best-fit cloud instance, based on CPU and memory usage.

  • Storage - After a Cloud instance has been determined, Migrate then determines if the instance can support the required storage capacity. If not, it remaps to a different instance that can support the required storage capacity.

  • Additional:

    • Cloud storage capacity mapped = Current used capacity + 10%

    • VM storage capacity required = Current total used capacity across all drives. Mapping is done with the aggregated capacity and not by individual volumes.

    • VM storage capacity required = Current total used capacity across all drives regardless of where the drives are provisioned For example, it is irrelevant if the infrastructure is comprised of servers with some local and some external SAN.

    • Cloud storage capacity mapped does not comprise storage included with the compute instance. For example, if a VM needs 500GB of storage and is mapped to a cloud VM instance that includes 40GB of storage natively, this 40GB is ignored and cost of 500GB is attached to the cloud VM.

    • Mapped storage is standard EBS or equivalent as described below:

      • AWS: EBS General Purpose SSD (gp3)

      • Azure: Managed Disk Standard SSD

      • Google: Standard persistent disk (SSD)

      • IBM: Endurance Disk(IOPS tier - 0.25 to 10 IOPS/GB)

      • Oracle: Block Volume (NVMe SSDs)

    • I/O volume and storage performance (IOPs) are not factored in storage cost calculations.