Configuring a Migrate to Cloud Plan

For an overview of setting up plan scenarios, see Setting Up Plan Scenarios.

1. Scope

Select the VMs that you want to migrate. You can select VM groups and/or individual VMs.

If you select an Auto Scaling Group, Turbonomic simulates migrating the VMs individually, and not as a group.

2. Where to Migrate

Choose a billing account (AWS account or Azure subscription).

Choose a region. Turbonomic shows all the regions that you can access from your target cloud accounts.

By default, Turbonomic considers all instance types in the selected region when making placement decisions for the scoped VMs and the volumes they use. However, you may have set up constraints in policies that limit migration to certain instance types. If there are VMs and volumes in your scope that are affected by those policies, Turbonomic will only consider the instance types defined in the policies.

3. Licensing (OS Migration Profile)

Select an OS Profile for this migration.

On the cloud, instances usually include an OS platform to run processes on the VM. As you migrate VMs to the cloud, you can specify the OS you prefer to run. You can keep the same OS that the original VM has, or map it to a different OS.

  • Include OS cost

    As Turbonomic calculates placement for the migrated workloads, it will include costs for instances that provide the same OS that the VM already has.

  • BYOL (Bring your own license)

    This is the same as the Include OS cost option, except the plan does not include OS licensing costs in any of the cost calculations for on-cloud placement.

  • Custom OS

    For each of the listed OS types, map the migrated VM to the OS you choose. The OS types are:

    • Linux – Any open source distribution of Linux. For the migration, Turbonomic will choose instances that provide the Linux platform that the cloud service provider delivers as a free platform. Note that this is always BYOL, because it assumes a free OS license.

    • RHEL (Red Hat Enterprise Linux)

    • SLES (SUSE Linux Enterprise Server)

    • Windows

    If you enable BYOL for RHEL, SLES, or Windows, Turbonomic assumes that you are paying for the OS license, and will not include the license cost in the plan results. If you do not enable BYOL, Turbonomic gets the license cost from the service provider and includes that cost in the plan results.

4. Reserved Instances Settings

For Plan RI Inventory, the RIs for the current scope are selected by default. Click Edit to make changes.

For RI Purchase Profile, the settings that you have set up for real-time analysis are selected by default. You can change the settings to see how they affect costs. For more information about RI Purchase, see RI Purchase Profile.

  • OFFERING CLASS

    For AWS environments, choose the offering class that corresponds to the RI types that you typically use in your environment.

  • TERM

    For AWS and Azure environments, choose the payment terms you contract for your RIs. TERM can be one of 1 Year or 3 Year. Typically, longer term payment plans cost less per year.

  • PAYMENT

    The payment option that you prefer for your AWS RIs:

    • All Upfront – You make full payment at the start of the RI term.

    • Partial Upfront – You make a portion of the payment at the start of the term, with the remain cost paid at an hourly rate.

    • No Upfront – You pay for the RIs at an hourly rate, for the duration of the term.