Column Descriptions of the Headers for AWS (IAAS)
AWS |
|
|---|---|
Summary Table |
|
Asset Group | User defined name of asset group. |
Instance Name | Your given machine name. |
OS | Installed operating system. |
OS Version | The version of the operating system. |
Recommended Instance | The recommended AWS instance type. |
Reduced cores | - |
HyperThreading | Yes(Hyperthreading improves performance for some applications by allowing one process per hyperthread) |
Tenancy | Shared or Dedicated tenancy. |
Annual Cost |
|
Total Cost ($) | Total cost of running the workload in AWS. |
Compute Cost ($) | Total annual compute cost. |
Storage Cost ($) | Total annual storage cost. |
Network Cost ($) | Total annual network cost. The designs labeled “OLA” show the cost of 10% of the total network traffic. This assumption is that most network traffic will not leave the AWS network. |
|
|
Compute Table |
|
Hierarchy |
|
Asset Group | User defined name of asset group. |
Instance Type |
|
Instance Name | Your given machine name. |
OS | Installed operating system. |
OS Version | Version of operating system. |
Recommended Instance | The recommended AWS instance type. |
Reduced Cores | The number of hardware/CPU threads recommended for the machine and this value is the same as “Recommended (Instance)” in CPU threads. Analytics will try to reduce no. of CPU threads to reduce a license cost for MS SQL Server software product. So this “Reduced CPU threads” will occur for a machine where MS SQL server is installed. Moreover, in a pricing plan, one of license optimization options should be selected. They are “Optimize Cost and Reduce Number of Cores”, “Optimize Number of Threads”, “Disable Hyperthreading”. |
Hyperthreading | With license optimization options, Analytics can recommend optimal instance type with or without hyperthreading. Enabled hyperthreading means two hardware/CPU threads in each core are used. Disabled hyperthreading means only one hardware thread in each core is used. |
Tenancy | Shared or Dedicated tenancy. |
EBS Optimized | Does the recommended instance require provisioned IOPS? |
Bottleneck | What issue(s) would be caused if a smaller instance was recommended. |
On Time |
|
On Time (%) | Amount of time the machine was powered on during the assessment. |
Recommended Daily ON Time (%) | Machine on-time percentage of representative one day. In other words, it is daily on-time percentage. Each day’s on-time over all days during data collection are used to derive this daily (representative one day) on-time percentage. On-time percent from 0 to 24 hours. |
Recommended Weekly ON Time (%) | Machine on-time percentage of representative one week. In other words, it is weekly on-time percentage. Each week’s on-time over all days during data collection are used to derive this weekly (representative one week) on-time percentage. On-time percent from Sunday to Saturday. |
CPU Threads |
|
Current (Observed) | The number of cores/threads on the the current machine. |
Recommended (Instance) | The number of cores/threads on the the recommended instance. |
CPU Utilization |
|
Current (%) | The observed significant CPU utilization peak in the current environment. By default this is calculated using the daily peak in the 95th percentile. |
Predicted (%) | The predicted significant CPU utilization peak when running in AWS. |
SLT (%) | Service Level Target: The maximum predicted CPU % allowed. If the predicted peak CPU utilization goes above this threshold more than 10% of the time the next larger instance is recommended. |
Observed Memory |
|
Currently Available (GB) | Amount of allocated memory present in current machine. |
Peak Used (GB) | Largest memory usage peak observed during the assessment. |
Instance Memory |
|
Recommended Available (GB) | Memory available on the recommended instance. |
Recommended Max Available(GB) | Maximum memory on the recommended instance (includes disk cache). |
Cost |
|
Total Annualized Cost ($) | Total annual compute cost. |
Annual Hourly Cost ($) |
|
Annualized Upfront Cost ($) |
|
Annual Dedicated Instance Fees ($) |
|
Region | The IaaS provider region. |
Pricing Plan | Type of pricing plan from the IaaS provider. |
|
|
Storage Table |
|
Asset Group | User defined name of asset group. |
Instance Name | Your given machine name. |
Disk | Name of disk. |
Mount Point | Mount point. |
Annual Cost |
|
Cost ($) | Total annual cost of storage and IOPS. |
Recommended Region | The IaaS provider region. |
Observed Storage |
|
Current Disk Capacity (GB) | This is the allocated capacity of the observed disk. |
Disk Occupancy (GB) | This is the occupied capacity of the observed disk. |
Storage Configuration |
|
Recommended Storage Type | Recommended storage type. |
Recommended Cloud Capacity | It gives the details on the recommended cloud capacity based on the usage. |
Number of RAID 0 Disks | The number of disks to split data evenly across. |
Performance |
|
Required Peak Throughput(MBps) | This columns gives the information on required peak throughput |
Available Max Throughput(MBps) | This columns gives the information on available Max throughput |
Required Peak IOPS | Observed maximum throughput in MB per second. |
Available Max IOPS | Maximum available throughput in MB per second. |
Recommended Storage Details |
|
Annual cost($) | Total annual cost for this type of storage. |
Required Capacity for Storage (GB) | Required storage capacity in GB. |
Required Capacity for Performance (GB) | Required storage capacity for performance in GB. |
Available Capacity (GB) | Available storage capacity in GB for this type of storage. |
Required Number of Volumes | Required Number of Volumes --for some storage |
Required Peak IOPS | Required number of peak IOPS. |
Peak Type | Defines peak percentile such as 90th, 95th, 99th. |
Baseline IOPS | Baseline IOPS for this type of storage. |
Available Max IOPS | Maximum available number of IOPS for this type of storage. |
Required Peak Throughput (MBps) | Required peak throughput in MB per second. |
Available Max Throughput (MBps) | Maximum available throughput in MB per second for this type of storage. |
Baseline Throughput (MBps) | Baseline Throughput (MBps) --for some storage |
Required Number of Volumes for IOPS | Required Number of Volumes for IOPS –for some storage |
Required Number of Volumes for Throughput | Required Number of Volumes for Throughput --for some storage |
Required Number of Volumes for Capacity | Required Number of Volumes for Capacity --for some storage |
Max Allowed Number of Volumes | Max Allowed Number of Volumes --for some storage |
Ops per Month (Millions) | Ops per Month (Millions) --for some storage |
Annual IOPS Cost($) | Annual IOPS Cost($) --for some storage |
Annual Throughput Cost ($) | This column gives information on Annual Throughput Cost ($) |
Annual Storage Cost($) | This column gives information on Annual storage Cost ($) |
Network Table |
|
Asset Group | User defined name of asset group. |
Instance Name | Your given machine name. |
Instance type | Type of a recommended instance |
GB/Month to the internet | This is the estimated egress network traffic from the machine to anywhere. We don’t determine the traffic destination (anywhere). “Estimated” means given a time-series of network throughput (data rate), we determine egress network traffic. |
GB/Month to the internet or other regions | This is the estimated ingress network traffic from anywhere to the machine. We don’t determine the traffic source (anywhere). |
Predicted Peak(%) | It gives the information on predicted peak % details |
Annual cost for Transmitted Data($) | The total annual cost for transmitted data |
Annual cost for received Data($) | The total annual cost for received data |
Annual cost($) |
|
Region | The IaaS provider region. |
Total Cost($) | TCO of recommended instance. |
Planner Icons |
|
|---|---|
Fit in Bounds | When “Fit In Bounds” is clicked, the entire graph in migration planner is nicely fit with centering. |
Zoom Out | Zoom out means to make the image look smaller for pinching out. |
Zoom In | Zoom in means focusing on a particular place on a image to increase its size or make the image look larger by pinching in |
Collapse all assets | It will collapse the modified/changed assets |
Clear All | It will clear any mapped dependencies |
Undo Migration Planner Changes | Will revert the changes made in Migration Planner |
Application Inventory Settings | By clicking Application Inventory Settings, it will allow us to select the applications that you want to migrate |
Build Application-Based Move Groups | Move groups can be built in multiple ways, by default Move groups are built on application categories, the Cloudamize Platform allows for the creation of new groups or assets by creating Application-Based Move Groups. To make adjustments, click on the More Tools button, and select Build-Application Based Move Groups |
Build Machine-Based Move Groups | In addition to Application-Based Move Groups, the Cloudamize Platform allows for the creation of Machine-Based Move Groups To make adjustments, click on the More Tools button, and select Build-Machine Based Move Groups. A new window will open with two sections, the bottom section lists all processes found during the assessment and the top section, is where we will be adding rules for these machines. |
Advanced Filtering | Advanced Filtering allows you to create move groups based on nearly any metric collected by the Cloudamize platform. |
Migrate Your environment | This Option allows us to know how to migrate a set of machines to respective IAAS using Application Migration Service (MGN). After an installation key has been provided, the MGN agent can be downloaded and installed from the Cloudamize application. Machines which are candidates for migration to AWS will then be available in the MGN dashboard. |
Upload File | An option to be used to upload a .CSV file |
CSV Builder | The Cloudamize CSV Builder allows you to create custom CSV outputs to provide you with the data which is most important to you. You can choose the categories to display as columns in the downloadable CSV output and you can reorder the columns to fit your needs. Select columns based on machine-centric data such as observed and recommended number of CPU threads, allocated memory, operating system, and many more and the templates can also be created based on application-centric data such as the application category, description, vendor, process, etc. |
CSV Exporter | This option lets you create a custom template by using an option of drop-down list to select a plan and to apply to the data in the selected templates |
SQL Server and License Usage | Using the Migration Planner, Cloudamize now provides a more in-depth look at the SQL Servers found in the assessed infrastructure. The information provided within the SQL Server and License Usage machine allows you to gain further insight into the on-premise licensing data and view a comparison of host-based versus VM-based SQL licensing. This feature also provides an overview of necessary on-cloud SQL licensing. |
Migration Planner Table | |
|---|---|
Number Of Nodes | The number of nodes in an asset. |
Number Of Communicating Apps | The number of communicating unique applications in an asset. This app can be a client or server app. |
Number Of Inter-Communicating Clients | The number of inter-communicating client nodes in other assets to a server node in this asset. Note that this is a node-level, not an app-level. This shows how many client nodes in other assets communicate to this asset. |
Number Of Inter-Communicating Servers | The number of inter-communicating server nodes in other assets from a client node in this asset. Note that this is a node-level, not an app-level. This shows how many server nodes in other assets are communicated by this asset. |
Number Of Proprietary Apps | The number of proprietary applications. Seems not supported |
Number Of Specialized Apps | The number of specialized applications. Seems not supported |
Number Of Autoscalable Nodes | The number of auto-scalable nodes where node does not run SQL server and the CPU utilization performance is suitable for auto-scaling. |
Number Of Nodes Suitable For GP-SSD | he number of nodes where disk IOPS performance are bursty and suitable for GP-SSD. |
Number Of Nodes Suitable For The t2 Family | The number of nodes where the recommended instance type is t2 family. |
Suitable Instance Types Are Available | The recommended instance type meets the performance requirement with CPU and memory workload. |