Release notes

Updates for version 1.12.1

Features

Perform guest collection at scale

You can now perform guest collections in parallel for all VMs managed by a single VMware vCenter. This comes in handy for collecting information from large quantities of VMs having the same credentials.

To collect guest-level information from multiple VMs, run:

mfit discover vsphere guest all --url https://11.22.33.44

Changes

Update to Cloud Run fit assessment

Cloud Run fit assessment has been updated to accommodate improvements done in Cloud Run resources limitations. Previous values were 4 CPUs, 16 GB of memory, and the new limits are 8 CPUs, 32 GB of memory. See details at Cloud Run Quotas and Limits.

Unify report and assess commands

We simplified the process of assessing data and generating a report, by combining the two commands into one. In previous releases, you needed to first perform an assessment ($ mfit assess), and then you could generate a report on the collected data. Now you can run the report command, and the assessment is done automatically. The report command now has an optional --target-platform flag.

The available options are: gcp, anthos, anthosbm and all. Each option specifies a different set of journeys to evaluate. If you don't specify a target platform, all journeys are assessed.

gcp assesses shift journeys to Compute Engine, Google Cloud VMware Engine, and containerization journeys to Google Kubernetes Engine, Google Kubernetes Engine Autopilot and Cloud Run.
anthos assesses shift to Anthos on bare metal and containerization journeys to Google Kubernetes Engine and Cloud Run.
anthosbm is equivalent to anthos.
all assesses all possible journeys.

With this change, the report sample command replaces the now deprecated assess sample command.

Bug fixes

Fix mentions of private / public previews in html reports

In previous releases, any containerize target is shown as private preview. Now only Tomcat targets are shown as public preview.

mfit collection scripts cleanup temporary directory

In previous releases, collection scripts would create a temp directory on the guest, but didn't remove it. In the latest release, collection scripts automatically remove the temp directory.

Fix wrong RAM size conversions

We corrected a conversion where base 2 was mixed base 10 (MiB vs MB) and resulted in inaccurate conversions.

Windows guest collection

We fall back to non-WMI based collection methods for some data to avoid sporadic failures.

Updates for version 1.12.0

Changes

Assessment of VMs to Anthos on bare metal Attach mode was removed from the executive report and detailed assessment report.
Modified the default assessment of Anthos on bare metal as part of the executive report. In order to assess VMs for Anthos on bare metal you must run the command: mfit assess --target-platform anthosbm
You'll see a warning if you issue a CLI command that attempts to assess an empty DB.
Updated the default behavior of assess –target-platform flag to use the all option.

Bug fixes

Fixed a bug in the executive summary section which caused inaccurate counts of high CPU and high memory VMs.
Improved the sorting on the fit assessment full report, so that results sorted by rule ID are correctly sorted.
Improved the fit assessment full report middle chart sorting so rows sorted from highest to lowest aggregated fit score.
Fixed an incorrect regex in the Linux collect script affecting Tomcat assessment.
Fixed a bug that prevented correct detection of centos OS version name and caused empty OS names on fit assessment full report.
Fixed a bug which caused duplicated VM information when VMs were discovered multiple times.
Improved handling of partially collected VM information which may lead to inconsistent data. Warn users when collecting an asset with the inconsistent VM information and skip storing the VM data.

Updates for version 1.11.3

Features

Fit assessment cost analysis - Use this new section on the fit assessment report to estimate the cost of running modernized workloads in Google Cloud. The report groups your VMs by modernization strategy and shows the estimated costs by strategy, as well as an estimated total cost. Cost analysis will help you decide whether a low-effort or high modernization strategy suits your needs. To view the cost benefits of a modernization journey, you need to run the collection scripts on an assessed VM. For more detailed instructions, see Discover and collect data.
Improved recommendation listing for fit journeys - The full fit assessment report now sorts journeys based on their fit and the sum severity of all failed conditions. The first journey in the list has the highest recommendation, with journeys of higher failure severity ranking lower.

Bug fixes

Fixed an issue where features were only calculated when running the discover command.

Updates for version 1.11.2

Features

Report filter – A new filter was added on the fit assessment detailed report to enable filtering VMs which have fit for specific journeys. Once the filter is applied, only VMs which have a fit for the selected journey are listed.
StratoZone – Added mFIT collection script to StratoZone StratoProbe collector 5.0.2.1. The information required to make an assessment is collected by StratoProbe collector, and is made available for assessment for users that have deployed StratoProbe.

Minor changes

Added the option to purge the fit assessment local database by using the command mfit discover purge-db
Added information on the existence of VMware tools in the CSV report. To allow users to automate guest level data collection through automated scripts.
Added a (--minimal) flag to Windows collection script which helps to minimize the amount of collected information and provide only the specific information required for assessing containerization to Windows IIS applications.
Added the option to manually check for newer versions of the fit assessment tool by using the command mfit version --check.

Bug fixes

Removed the fit score column from full report table for better readability.
Updated fit assessment summary report to resolve mismatch of percentage presented on the summary part and guidance part of the report.
Changed the severity information to use text instead of numeric value on the summary report.
Fixed wrong identification of OS which was marked as Other OS on fit assessment reports.

Updates for version 1.11.1

Bug fixes.

Updates for version 1.11.0

Executive summary report – This release includes a new type of report, and a change in the default behavior. The new executive summary report gives you an overview of your modernization journeys. At a high level, the report sorts your modernization journeys into two different buckets: low effort versus high modernization. Looking at these two extremes, and the benefits and effort required, should help you make key business decisions. In addition, there are subsections of the report that show the fit and technical limitations of migrating VMs (lift and shift analysis), refactoring to containers, and on-premises VM modernization (via shifting or attaching VMs to Anthos clusters on bare metal). The default report type is the new executive summary report; in previous releases, the default report was a detailed report.
Assess workloads for migrating to Google Cloud VMware Engine – The fit assessment tool added new assessment capability to assess workloads for lift and shift to Google Cloud VMware Engine.

Updates for version 1.10.0

The fit assessment tool for version 1.10.0 adds new functionality, including: