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 to demonstrate the newest features being rolled out in the CloudRecon Portal in March 2023. Customers will be able to use this document as a guide to utilize the variety of features offered by CloudRecon.
This document is to be used as a reference regarding new features for all internal CloudAtlas users.
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 new reports offered are Workload Priority Application and Wave Plan Application.
The Workload Priority Application section provides a detailed analysis of the application migration assessment and an outline of your cloud migration journey status. This section is divided into six categories - 5 R Analysis, Apps Workload Details, Apps Readiness, App Details, Other Workloads & Rules.
The Five Rs were originally developed by Gartner to clarify options when considering modernizing applications to the cloud. Since being developed, the model has evolved and CloudRecon includes six Rs, but we'll refer to it as the Five Rs as that is the commonly accepted term. The purpose of Five R analysis in a cloud environment is to evaluate the application(s) based on the business goals such as increased innovation, fast migration, cost efficiency, etc. This allows you to maximize the benefits of the cloud and minimize costs to improve resource utilization.
CloudRecon now includes recommendations on the optimal Five R approach based on the code-level analysis of the application(s). Under the Migration Assist left side-menu, click on "Workload Prior Apps" to access this feature.
Rehost : This is the simplest migration strategy, where the application is moved to a new environment without making any changes to the code or architecture.
Refactor : This involves making changes to the code or architecture to optimize it for the new environment, while retaining the existing functionality of the application.
Rebuild : This strategy involves completely rebuilding the application from scratch, taking advantage of new technology and architecture patterns.
Replace : This involves replacing the existing application with a different solution that provides equivalent functionality.
Retire : This strategy involves retiring the application, either because it is no longer needed or because a viable substitute has been found.
Retain : In some instances it might be advisable to retain the application on premises due to the nature of the application itself, the investment required to modernize or very specific or specialized compliance and regulatory requirements that might not yet be available in the cloud.
In the 'Apps Workload Details' Tab, you can see Application Workload Details. Application workload details refer to the specific information about the resource requirements and characteristics of an application that are necessary for efficient and effective resource allocation.
The "Apps Readiness" section provides various details relating to the compatibility and readiness for deployment on a specific platform or environment.
In the 'App Details' tab, you can search and select individual applications or servers and retrieve information about the application, including, function, owner, status, and other technical details.
There are several types of application workloads that can place different demands on computing resources. In the 'Other Workloads' Tab, you can retrieve information about other application workloads.
There are several types of application workloads that can place different demands on computing resources. In the 'Other Workloads' Tab, you can retrieve information about other application workloads.
The "Wave Plan Application" tab on CloudRecon simplifies the migration process by breaking it down into manageable phases, or "waves," and provides a structured approach to executing each wave. Using wave planning can minimize downtime, reduce costs, and avoid potential issues such as performance degradation, security vulnerabilities, and data loss during the migration process. This section is divided into three categories - Summary, Wave Plan Details, and Wave Groups.
In the 'Summary' tab, you get data relating to total number of waves, groups, applications, and servers as well as summary information on app complexity, server criticality, the make-up of the different waves and a view of the Five R analysis.
The 'Wave Plan Details' tab provides application-level data such as Application and Infrastructure Complexity, Workload Criticality, Machine Names, Migration Approach, and which migration Wave and Group the application belongs to.
In the 'Wave Groups' tab you can find the grouping details of applications according to several factors including complexity score and ease of migration. These groups are migrated on a priority basis - where Group 1 applications will be migrated first, followed by Group 2 and Group 3, as shown in the figure below.
This section explains the updated features in the CloudRecon Portal.
The 'Data Estate' section now provides additional information about migration from Oracle to PostgreSQL. There are three tiers - single server, flexible server, and hyperscale server. Previously, hyperscale server was part of Azure PostgreSQL. Now the hyperscale server has been moved to Cosmos DB. Oracle using hyperscale servers will be migrated to Cosmos DB. PostgreSQL and Cosmos DB Pricing have been separated, and the costing summary reflects these changes.
The sustainability Report in CloudRecon offers data and graphs representing the environmental impact of IT infrastructure, including energy usage and carbon emissions, and compares with the post cloud migration scenarios. This feature can be accessed from the 'Cloud Migration Premium' menu. The Sustainability Report has now been updated with two new reports - Electricity (On-Premises vs Azure), and Office & Water Consumption.
Summary comprehensively represents the infrastructure's carbon emissions such as - Electricity Savings, Power consumption attributed greenhouse emissions, water consumption etc.
This tab provides power consumption of each machine on Azure based on the machine-level details vs. three efficiency levels of on-premises datacenters.
Measuring and managing water consumption is important for office infrastructure as it can help identify areas for water conservation and efficiency improvements, reduce water bills, and support sustainability efforts. This Tab represents the office water consumption comparison of On-premises vs Azure.