Column Descriptions of the Headers for AWS (IAAS)
AWS |
|
|---|---|
Summary Table |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of the asset group. If no name is assigned, machines are labeled “Default”. The Asset group is typically used to designate “Production”, “Development”, “Test”, “Data Center Name”, etc. |
Server Name | Your given machine name. |
IP Address | The IP address of the machine. |
OS | Installed operating system. Cloudamize can also indicate the following: Microsoft SQL Server Standard or Enterprise edition, Ubuntu. |
OS Version | The detailed version of the installed operating system. |
Recommended Instance | The recommended AWS instance type for that particular design/plan. |
Available vCPU | The available number of vCPU for the Recommended Instance. |
Recommended vCPU | The recommended number of vCPUs to provision the Recommended Instance with (core masking). This can be useful for licensing purposes. |
Tenancy | Shared or Dedicated Tenancy. Shared tenancy is the default tenancy. The dedicated tenancy is available in some designs and can also be configured in the Designer. |
MS SQL Edition | This specifies the edition of Microsoft SQL Server detected on an individual machine. |
SQL Version | This specifies the version number of the Microsoft SQL Server instance detected on the individual machine |
Annual Cost |
|
Total Cost ($) | The total annual 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. |
Data Source Information |
|
Data Source | Indicates the type of data considered for providing cloud recommendations, either real-time or historical |
Collection Time Span | Indicates the time duration for which the performance data of an instance is considered for providing cloud recommendations |
Intel Optimization |
|
Performance (x-times) | Indicates the number of times the performance increases from the base recommendation |
Compute Table |
|
Hierarchy |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of asset group. |
Instance Type |
|
Server Name | Your given machine name. |
IP Address | IP address of the Machine |
OS | Installed operating system. |
OS Version | The version of the operating system. |
Recommended Instance | The recommended AWS instance type. |
Available vCPU | The available number of vCPU for the Recommended Instance. |
Tenancy | Shared or Dedicated Tenancy. |
Constraint | 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 |
|
Observed vCPU | The number of cores/threads on the current machine. |
Recommended vCPU | The number of cores/threads on the recommended instance. |
CPU Utilization |
|
Current CPU Utilization (%) | The observed significant CPU utilization peak in the current environment. By default, this is calculated using the daily peak in the 95th percentile. |
Predicted CPU Utilization (%) | The predicted significant CPU utilization peak when running in AWS. |
Max Allowed CPU Utilization (%) | 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 |
|
Observed Memory Provisioned (GB) | Amount of allocated memory present in current machine. |
Peak Memory Used (GB) | Largest memory usage peak observed during the assessment. |
Instance Memory |
|
Recommended Available (GB) | Memory available on the recommended instance. |
Cost |
|
Total Annualized Cost ($) | Total annual compute cost. |
Annual Total 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 |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of asset group. |
Server Name | Your given machine name. |
Disk | Name of disk. |
Annual Cost |
|
Annual Cost ($) | The total annual cost of storage and IOPS. |
Region | The IaaS provider region. |
Observed Storage |
|
Observed Disk Capacity (GB) | This is the allocated capacity of the observed disk. |
Observed 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 |
|
Observed Throughput (MBps) | This column gives information on the observed peak throughput |
Recommended Throughput (MBps) | This column gives the information on the recommended Max throughput |
Peak IOPS | Observed maximum throughput in MB per second. |
recommended 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 |
Observed IOPS | The actual measured disk Input/Output Operations Per Second. |
Peak Type | Defines peak percentile such as 90th, 95th, 99th. |
Baseline IOPS | Baseline IOPS for this type of storage. |
Recommended IOPS | The proposed IOPS for the target cloud storage solution. |
Observed Throughput (MBps) | The actual measured data transfer rate in Megabytes per second |
Recommended Throughput (MBps) | The proposed data transfer rate for the target cloud storage solution. |
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 |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of the asset group. |
Server Name | Your given machine name. |
Recommended Instance | Type of a recommended instance |
Hyperthreading | Indicates whether hyperthreading is allowed for the instance or not. |
Tenancy | Indicates Tenancy for the Instance |
GB/month leaving server | The amount of data transmitted to the internet per month. |
GB/month from other Servers/Devices | The amount of data received from the internet per month. |
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 the recommended instance. |
Liscence
Hierarchy |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of asset group. |
Instance Type |
|
Server Name | Your given machine name. |
OS | Indicates installed operating system. |
OS Version | The version of the operating system. |
Recommended Instance | The recommended AWS instance type. |
Available vCPU | The available number of vCPUs for the Recommended Instance. |
Recommended vCPU | Indicates the recommended vCPU for the instance |
Hyperthreading | Indicates whether hyperthreading is allowed for the instance or not. |
Tenancy | Shared or Dedicated Tenancy. |
Constraint | Indicates the reason why we could not recommend a smaller instance |
Annual Total Cost ($) | Indicates the total annual cost for an instance. total annual cost = annual hourly cost + upfront/duration of Ris (reserved instance) + license cost |
Annual Hourly Cost ($) | indicates total annual hourly cost for an instance + license cost |
Annualized Upfront Cost ($) | Provides the Annualized Upfront Cost for Instance |
License Cost ($) | Indicates the License cost for the instance |
Annual Dedicated Instance Fees ($) | indicates annual dedicated instance fees for an instance |
Region | The IaaS provider region. |
Pricing Plan | Type of pricing plan from the IaaS provider. |
License Cost Reason | indicates the license cost reason for an instance |
Dedicated Host:
Dedicated Host Summary |
|
Host Type | This classification indicates the nature of the computing infrastructure. |
No of Hosts | Number of total Hosts |
Dedicated Host Details | |
Host Name | AWS Instance name with host number. |
Host Type | The specific AWS instance type name |
Region | The IaaS provider region. |
Pricing Plan | The specific AWS pricing model |
Sockets | The number of physical CPU sockets on the host. |
Cores | The total number of physical CPU cores across all sockets on the host. |
Available vCPUs | The total virtual CPU capacity provided by the host. |
Utilized vCPUs | The actual number of vCPUs being consumed by workloads on the host. |
Un-Utilized vCPUs | The remaining unused vCPU capacity on the host |
Unutilized Capacity (%) | The percentage of available vCPU capacity that is currently not being used. |
Hourly Cost ($) | The estimated cost per hour for this host is based on its type and pricing plan. |
Annual Cost ($) | The estimated cost per year for this host is based on its type and pricing plan |
Instance Count | The number of instances |
Dedicated Host Packaging | |
Host Name | AWS Instance name with host number. |
Asset | User-defined name of asset group. |
Server Name | Your given machine name. |
Recommended Instance | The suggested cloud instance type |
CPU Threads Observed | The total number of CPU threads (logical processors) identified on the source server. |
CPU Threads Recommended | The optimal number of CPU threads is suggested for the recommended cloud instance. |
OS | The operating system installed on the server |
OS Version | The specific version of the operating system |
Elastic VMware Service:
Column Name | Explanation |
|---|---|
EVS Cloud Summary | |
Cluster Type | Categorizes the type of virtual infrastructure cluster. This typically refers to the AWS bare-metal instance family (EVS currently supports i4i.metal in shared tenancy and i4i as dedicated hosts) used for the ESXi hosts, defining the cluster's compute, memory, and internal storage characteristics. |
Cluster Name | A unique identifier or label for a specific cluster configuration or recommendation within the report, aiding in distinction. |
External Storage Type | Specifies the type of external storage solution used to supplement the cluster's internal vSAN storage. Common examples in AWS environments include Amazon FSx for NetApp ONTAP. |
External Storage (GiB) | The total capacity of external storage required or recommended for the cluster, measured in Gibibytes (GiB). |
Storage Cost ($) | The estimated cost (in USD) of the external storage over the defined reporting period, based on its type and capacity. |
EVSControlPlane Cost ($) | The EVS Control Plane Licensing cost is AWS's hourly fee for managing and operating your Amazon Elastic VMware Service (EVS) environment. |
VPCRouteServer Endpoint Cost ($) | The VPC Route Server Endpoint cost is the hourly AWS charge for each active endpoint that enables dynamic routing of traffic from virtual network appliances directly into your Amazon VPC route tables. |
Compute Cost ($) | The estimated cost (in USD) of the ESXi hosts (compute resources) in the cluster over the reporting period, considering the host type, number of hosts, and chosen pricing model (e.g., On-Demand, Reserved Instance). |
Total Cost ($) | The overall estimated cost (in USD) for the specific cluster configuration over the reporting period, typically the sum of the Compute Cost and Storage Cost. |
No of Hosts | The number of ESXi hosts (bare-metal instances) recommended or required to form this cluster, as determined by the sizing analysis. |
EVS Host Details | |
Host Name | The unique name or identifier assigned to a specific ESXi host within your environment. |
Host Type | The model or type of the physical server (or bare-metal cloud instance) on which the ESXi hypervisor runs. For cloud environments like AWS, this refers to specific EC2 bare-metal instance types (e.g., i4i.metal in shared tenancy and i4i as dedicated hosts). |
Total vCPUs | The total number of virtual CPU cores that the ESXi host provides. This reflects the raw processing power available from the host's physical CPUs. |
Allotted vCPUs | The sum of all vCPUs that have been assigned or provisioned to all virtual machines configured to run on this specific host. This can be higher than Total vCPUs due to CPU overcommitment. |
Consumed vCPUs | The actual amount of vCPU resources actively used by all virtual machines on this host during the monitoring period. This indicates the real-world demand for CPU. |
Consumed vCPUs (%) | The percentage of the Total vCPUs that were actively consumed by VMs on the host. Calculated as (Consumed vCPUs / Total vCPUs) * 100. |
Total Memory (GiB) | The total amount of physical RAM (Random Access Memory) available on the ESXi host, measured in Gibibytes. |
Allotted Memory (GiB) | The sum of all memory (in GiB) that has been assigned or provisioned to all virtual machines configured on this host. |
Utilized Memory (GiB) | The amount of memory actively being used by the virtual machines as reported by their guest operating systems. |
Consumed Memory (GiB) | The actual amount of physical host memory (in GiB) that the ESXi hypervisor is actively using for the virtual machines on this host, accounting for hypervisor overhead and memory-saving techniques. This is often the most critical metric for host memory sizing. |
Consumed Memory (%) | The percentage of the Total Memory (GiB) that was actively consumed by VMs on the host. Calculated as (Consumed Memory (GiB) / Total Memory (GiB)) * 100. |
Total Storage (GiB) | The total raw storage capacity (in GiB) available to the ESXi host, typically from its internal disks contributing to a vSAN datastore, or from connected shared storage. |
Allotted Storage (GiB) | The total amount of storage (in GiB) that has been provisioned for all virtual disk files of VMs on storage accessible by this host. This can be higher than Total Storage if thin provisioning is used. |
Consumed Storage (GiB) | The actual amount of physical storage space (in GiB) actively being used by the virtual machines on storage accessible by this host, accounting for data reduction techniques like deduplication and compression. This represents the true storage footprint. |
Consumed Storage (%) | The percentage of the Total Storage (GiB) that was actively consumed. Calculated as (Consumed Storage (GiB) / Total Storage (GiB)) * 100. |
Compute Cost ($) | The estimated cost (in USD) for this individual ESXi host over a specific period, based on its Host Type and the chosen pricing model (e.g., On-Demand, 1-Year Reserved Instance, 3-Year Reserved Instance). |
Packed Instances | The number of virtual machines that are either currently running on this host or that have been recommended to be consolidated onto this single ESXi host as part of the sizing or optimization assessment. This indicates consolidation efficiency. |
EVS Host Packing (VM-Level Details) | |
Host Name | The name of the specific ESXi host on which this virtual machine currently resides or is planned to reside. |
VM Name | The unique name or identifier for the individual virtual machine being analyzed. |
vCPUs | The number of virtual CPUs (vCPUs) that have been allocated or assigned to this VM in its configuration. |
vCPU Per Core | Defines how the allocated vCPUs are presented to the VM's guest operating system in terms of virtual sockets and cores per socket. (e.g., 8 vCPUs could be 2 sockets x 4 cores/socket). |
Compute Utilization Ratio | A metric (often a percentile, like the 95th percentile, or a standard deviation) indicating the peak or consistent actual CPU utilization of the VM over a monitoring period. It helps identify if the VM is over- or under-provisioned on vCPUs. |
vRam (GiB) | The amount of virtual RAM (memory), measured in Gibibytes, that has been allocated or assigned to this VM in its configuration. |
vRam Consumed (GiB) | The actual amount of memory actively used by this VM over the monitoring period, as observed by the hypervisor or the guest operating system. |
Memory Utilization Ratio | Similar to Compute Utilization Ratio, this metric indicates the peak or consistent actual memory utilization of the VM over a monitoring period, helping to identify memory over-provisioning. |
VMDK Used (GiB) | The actual amount of disk space actively consumed by the VM's virtual disk files (VMDKs) on the underlying storage, measured in Gibibytes. This is the real footprint, which can be less than the provisioned size if thin provisioning is used. |
Read IOPS | The rate of read Input/Output Operations Per Second (IOPS) performed by this VM's storage during the monitoring period. A key measure of storage performance demand for reading data. |
Write IOPS | The rate of write Input/Output Operations Per Second (IOPS) performed by this VM's storage during the monitoring period. A key measure of storage performance demand for writing data. |
Read Throughput (MBps) | The rate of data being read from storage by the VM, measured in Megabytes per second (MBps). This indicates the volume of data being read. |
Write Throughput (MBps) | The rate of data being written to storage by the VM, measured in Megabytes per second (MBps). This indicates the volume of data being written. |
External Storage Vendor Type | Specifies the type or vendor of any external storage solution where this VM's data might reside, particularly if it's not on the host's internal (vSAN) storage. For AWS, this could indicate Amazon FSx for NetApp ONTAP, EBS, etc. |
Storage Preference | An indication or recommendation for the preferred storage performance tier or type for this specific VM's data (e.g., high-performance, standard, archival). This guides storage placement decisions in the target cloud environment. |
FSx Storage:
Hierarchy |
|
Group Name | This field indicates the infrastructure type. It's "Physical Infrastructure" if data is collected via an Agent or Agentless Data Collector (ADC) from individual machines, and "Virtual" if data is collected from a vCenter Server or hypervisor. |
Asset | User-defined name of asset group. |
Instance Type |
|
Server Name | Your given machine name. |
Single-AZ/Multi-AZ | Indicates the deployment type of the instance |
Storage Type (SSD/HDD) | Indicates the storage type of the instance |
Storage Capacity (GB) | Indicates the storage capacity of the instance |
Deduplication % | Indicates the deduplication percentage of the instance |
Effective Storage Capacity (GB) | Indicates the effective storage capacity of the instance |
Throughput (MBps) | indicates observed throughput of instance |
EC2 Compute Cost ($) | indicates the compute annual cost of the instance |
EBS Storage Cost ($) | indicates the storage annual cost of the instance |
Total Instance Cost ($) (EC2 Compute Cost + EBS Storage Cost) | indicates the total annual cost of the instance |
FSx Cost ($) | indicates fsx annual cost of the instance |
Annual Savings ($) (Total Instance Cost - FSx Cost) | indicates savings of 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. |