As a Cloudamize customer, you have access to a wide range of resources designed to assist you with software installation and data collection. We want you to know what to expect from each installation method and the data they provide. You deserve excellent service during your time using our product and we measure our success by your satisfaction.
This document has been produced to provide guidelines and reference materials for the methods of installing our software and how each collects data. Within we will provide the following:
An introduction to the different installation types
Provide information in regards to the data collected for each installation type
Roles and responsibilities for installation and data collection troubleshooting
Outline the assessment projected timeline
Cloudamize can be installed on many different Linux flavors and Windows Server OSes. Click here for a full list of installation prerequisites. We can also collect data from many vCenter versions and Microsoft HyperV. Cloudamize is not intended to be installed on Desktop or Laptops Operating Systems. Unix systems and non-x86/64-based systems, such as ARM or Mainframes, are not supported.
Agent data collection
The Cloudamize Agent collects performance metrics, application dependencies, and SQL data from many Linux flavors and Windows Servers OSes.
Note: Cloudamize won't be able to collect the data for storage from the servers that use NFS mounts, this is applicable for both the Agent and Agentless Data Collection methods. Though Cloudamize will be able to provide the results for the NFS-mounted servers, but the results will not have accurate information for storage mapping. This includes both storage amount and performance characteristics such as IOPS and throughput.
Agentless data collection
The Cloudamize Agentless Data Collector (ADC) collects performance metrics and application dependencies from each server discovered. The Agentless method can now be used to discover SQL workloads, though Agent-Based methods are still superior for this particular task.
Each ADC can collect metrics for up to 500 machines across your network. The ADC has an agent component that installs on the OS, and data from the OS is captured in that manner. This is important to note if installing an ADC on a hypervisor.
The ADC uses WMI to authenticate and collect data from Windows, and SSH to authenticate and collect data from Linux.
Note: There are key metrics that aren’t captured with the ADC and subsequently several features will not be available. Please reference the detailed feature comparison list before deciding on an installation method.
Hypervisor data collection
Cloudamize supports performance-level data collection from both vCenter and HyperV hypervisors. Speak with your Account Manager about collecting data from hypervisors.
Note: Unsupported hypervisors, such as KVM, will block CPU info from the Cloudamize agent and require manual entry by our support team.
When an agent is installed on a HyperV machine it will capture performance-level data from the hypervisor level for all connected VMs. Each connected VM will account for (1) license. It is important to note this method only captures performance data and will not give you access to the Cloudamize Migration Planner.
To gain access to the Cloudamize Migration Planner while still capturing performance-level data from a hypervisor you will also install an agent on each VM, or add each VM to an ADC to collect application-level data.
Before choosing this installation type it is recommended you speak with your Account Manager to go over the specifics of collecting data using 2 different sources, and how to tell data collection is properly reconciled.
Note: Within 24 hours of installation the application will reconcile the server count so that machines captured at the hypervisor level and have an agent or are being collected from an ADC will get reconciled. Meaning only (1) license will be used for each machine.
Getting Started Installing Cloudamize
Cloudamize is a platform which enables you to capture detailed analysis of your predicted costs and performance, as well as design a successful roadmap for cloud migration based on application dependencies, suitability, and readiness while ensuring cost-performance optimization at the moment applications are ready to migrate to the cloud.
Prior to Installation
Every Cloudamize installation method will need to communicate back to our server(s) over port 443, while others will require WMI and SSH to be configured internally to collect data. Additionally, the install may require data to be sent through a proxy server, which may require our data collection server(s) to be whitelisted. It is important to know which systems, servers, or network administrators/technicians you will need for proper installation and effective troubleshooting during the planning phase.
The Cloudamize Agent and ADC use the utility ‘curl’ to test connectivity to our servers during installation and data collection. It is recommended that you test and resolve any communication issues prior to having your account provisioned.
See the troubleshooting documents in the Installation & Troubleshooting section to test connectivity.
The Cloudamize agent and ADC run obfuscated code to protect our intellectual property. Additionally, the ADC machine will try to communicate with upwards of 500 machines. Each of these individually or together could set off A/V software to flag Cloudamize as malicious. Whitelisting the software prior to installation is highly recommended.
Click here if your ADC gets quarantined by A/V software.
When using the ADC you will be required to authenticate to each server using a domain administrator account for Windows and an account in the wheel group (root or sudo) for Linux.
It is recommended that you reset the account password(s) which will be used for data collection prior to server discovery so they will not need to be rotated during data collection. If it is not possible due to your organization's policies a password reset utility is provided.
What makes a server unique?
Cloudamize software uses each server's UUID as its unique identifier. In some instances, we’ve seen VMs cloned with the same UUID. This is not supported by Cloudamize and will need to be resolved before installation begins. If a VM is cloned and rebooted with a new UUID, but is running the same workload as prior to the reboot, this machine will be captured as a new VM and consume another license. Citrix VDI environments are an example of an unsupported environment.
Conversely, if the IP address or hostname of a server changes during data collection, it will have not create a duplicate record.
Data Collection Duration and Scope
By default, Cloudamize collects data for 11 days with 3 days of processing time for a total of 2 weeks from Assessment start to Results Delivery. The duration of data collection can be extended provided it’s within the scope of the total assessment duration.
It is important to know if there are specific workloads you need to capture during the data collection period, e.g., month end, database replication, etc., to accurately scope your project before your order is provisioned.
“After installation is completed on all necessary machines and all machines are included in the ‘Assessment Scope' with a status of ‘Collecting Data’, you are ready to click on the 'Start Assessment’ button. You will first be prompted to agree to the license total. Once you have agreed to the license total you will then be prompted to select a region and configure the assessment duration.
The region you select, is considered for the pricing in the TCO results. We recommend selecting a region that is closest to the physical location of your machines as possible. Assessment duration should be configured as per the below guidelines to ensure the necessary amount of data is collected and time allowed for processing.”
Date Ranges mentioned below for the reference:
Start Data Processing: select the Date on when you would like to start assessment
End Data Processing: The tool will not allow you to select an End Data Processing date less than 11 days from the Start Data Processing date. You can request a shorter data collection period from the Delivery Manager. The Expected Assessment Completion date must be no less than 3 days more than the End Data Processing date. Requests for a shorter completion period are not possible.
Expected Assessment completion: Need at least 3 working days to process the collected data, and in selecting the assessment completion dates cannot be on the weekends(Sat and Sun)
Ex: If the End Data Processing is on “Thursday” and then the Expected Assessment completion date would be on coming “Monday” since the assessment completion dates cannot be selected for Weekends.
Note: For the node count of above 1000 added to the assessment, then the duration b/w the End Data Processing and Assessment completion Date should be 5 days.
Once your Assessment has started you will see the following page. click on the name of your assessment and click Settings to get back to the Inventory Settings page.
It is important to log in to your assessment frequently to check the status of data collection. The three statuses are as follows:
COLLECTING DATA: Data collection is working.
SLEEPING: We have a connection to the server but data collection has stopped and/or the agent is not running. Refer to the troubleshooting guides in the Index.
INACTIVE: We do not have an active connection to your server. Refer to the troubleshooting guides in the Index.
After a period of 2-3 days depending on your Preliminary Hardware Results will be available. When you log in to your assessment you will see the following screen. Please note there will not be Network data at this point. Click here to read about Preliminary Hardware Results.
Once full results populate you will have Network Data, as well as access to the Designer and Migration Planner features.
Note: Migration Planner is not available in hypervisor only installs. Agent or Agentless Data Collector data are required.