This document outlines the new features that are being pushed on to CloudRecon Prod environment. Customers will be able to leverage these new features by taking this document as a guideline.
This document is an outline of the new features that are being rolled out on CloudRecon portal in December 2022. Customers will be able to use this document as a guide to leverage the benefits of these new features.
This document is to be used as a reference with target audience which includes company internal personnel, customers, and partners
This section explains the new features added to the CloudRecon portal.
The Migration Assist section offers a list of updates that improve your migration experience. These reports give you a detailed analysis of your infrastructure and application migration process. The reports offered are Workload Priority Infrastructure and Wave Plan Infrastructure.
The Workload Priority Infrastructure section provides a detailed analysis of the infrastructure migration assessment and an outline of your cloud migration journey status. This section is divided into four categories – Overview, Infrastructure Workload Details, Workload Details, and Rules.
In the Overview Tab, your organization’s VMs will be sorted according to migration preference. ‘Rehost’ represents the most easily migrated machines and ‘Retire' represents the non-migrating machines.
Rehost effort moves a current state asset to Azure, with minimal changes to the overall architecture. It is synonymous with Lift & Shift migration, and helps achieve rapid ROI in the organization’s Cloud Investment.
RefactorRefactor refers to the process of refactoring the code of existing assets to fulfil new business. opportunities. Refactoring is done to fit a PaaS-based model and helps achieve greater Cloud efficiency from a perspective of cost management and efficiency.
Re-Arch/RebuildAssets that cannot be supported on the Cloud, need to be re-architected in order to avail their functionality on the Cloud. This helps achieve application scale and agility and eases the adoption of Cloud capabilities.
ReplaceThese workloads can be scheduled for future replacement and can be set aside from the current migration efforts. Usually, a SaaS application can help establish functionalities for the hosted application.
RetainMachines that need to be retained for their inability to migrate to the Cloud. Retainment helps avoid inefficiency and lack of functionality on the Cloud, until the application can be successfully migrated once the core functionalities are adopted to the Cloud.
RetireMachines that cannot be adapted to the Cloud and hence, need to be retired.
In the ‘Infra Workload Details’ Tab, you can see various details such as source server list, infrastructure complexity, Workload Criticality IaaS and Platform.
In the ‘Workload Details’ Tab, you can see infrastructure details sorted by database servers, application servers, Website applications, Enterprise servers, Middleware Servers, and Roles
In the ‘Rules’ Tab, you can get data about attributes on which the machines are ranked and grouped for migration.
The Wave Plan Infrastructure section provides insights into the Waves and Grouping of VMs according to migration order. Infrastructure Wave Plan analysis represents statistical data relating to the Waves and Grouping of VMs in order of ease of migration. This section is divided into four categories – Summary, Wave Plan Details, Waves and Groups, and Server Details.
In the ‘Summary’ Tab, you get data relating to total number of servers, total groups of servers and total waves of servers. This data is sorted according to Server Complexity and Server Criticality. Source Server names are listed below with multiple data-points about the migration efforts.
In the ‘Infra Workload Details’ Tab, you can see various details such as source server list, infrastructure complexity, Workload Criticality IaaS and Platform.
The ‘Waves and Groups’ Tab, you can find the grouping details of servers according to score and ease of migration. Priority of migration is based on nomenclature, where Group 1 machines will be migrated first, followed by Group 2 and Group 3 machines, as shown in the figure below.
In the ‘Server Details’ Tab, you can search server names on the search box, to get complete details about specific servers that are part of the Waves and Groups of the migration process, as shown in the figure below.
Server Details such as Hardware Details, Workload Details, OS Name, Azure Pricing, Server Detail, Complexity, Criticality and Migration approach are displayed once a specific server name is searched for.
Server Details such as Hardware Details, Workload Details, OS Name, Azure Pricing, Server Detail, Complexity, Criticality and Migration approach are displayed once a specific server name is searched for.
This section explains the updated features in the CloudRecon Portal.
The Cloud Migration Standard Report section has been updated with the Azure Dedicated Host Report.
These reports will help you understand the configuration and how many number of dedicated hosts required on to run your infrastructure to handle your entire workload. The Azure Dedicated Host Report section has two components – Cost Summary, and Dedicated Hosts.
2.1.2 Cost SummaryIn the ‘Cost Summary’ Tab, you can find sizing details relating to Azure Dedicated Host service. You will get access to data such as – On-Premises vs Azure costs, 1 Year and 3 Year RI’s, Cost Comparison, Lift & Shift Costs, and Dedicated Host Costs.
In the ‘Dedicated Hosts’ Tab, you can find the relevant details of Dedicated Host Groups, VMs and Servers.
You can now activate Cloud Migration Premium reports using the CloudRecon Dashboard. Follow the steps below to activate Premium reports.