Classify Host(s)¶

You can classify host(s) based on the 6R's principles.

What is the 6R's Principle?¶

Reinvest¶

This strategy is typically used for applications that are strategic. Organizations are ready to invest additional efforts, time, and money to keep the application up to date and useful. The sub-categories of actions in this category are Rehost, Replatform, or Refactor.

Replatform¶

The replatform strategy involves moving applications almost as-is, but replacing some components to take advantage of the cloud. CHAI™ enables replatform in multiple ways. We enable application teams a choice of rationalizing the application environments used to host the applications to leaner and cost-effective options. This also helps in moving qualified services from Windows operating systems to Linux OS as applicable.

Refactor¶

This strategy calls for an overhaul of the application to adapt it to cloud-native architecture. It is valuable when you have a strong business need for cloud-native features, such as improved development agility, scalability, or performance. CHAI™ specializes in getting started on your refactoring journey that can lead to breaking up the application into independent services and transitioning to a microservices architecture. CHAI™ makes it possible to get started on this path depending on organizational skills and abilities.

Rehost¶

This strategy involves moving applications from the on-premises environment to the cloud without modification. It is commonly used to migrate large-scale legacy applications to meet specific business objectives such as an accelerated product launch timeline.

Retain¶

This doesn't involve migrating the application to the cloud:

The business is heavily invested in the on-premises application and may have currently active development projects
Legacy operating systems and applications are not supported by cloud environments
The application is working well—no business case for the cost and disruption of migration
For industries which must adhere to strict compliance regulations that require data to be on-premises
For applications that require very high performance, the on-premises option may prove the better choice

Retire¶

This doesn't involve migrating the application to the cloud:

In many cases, during a migration project, you can identify applications that are redundant, and shutting them down can represent a cost saving
There may already be existing plans to decommission the application or consolidate it with other applications

Classification in Detail¶

Steps to Classify the Host(s)¶

Login to the CHAI™ portal.

Step 2: Navigate to Rationalize Tab¶

Click on the project where you want to create an application and navigate to the Rationalize tab.

Step 3: Navigate to Hosts Tab¶

Click on the Hosts tab.

Click Host

Step 4: Enable Edit Mode¶

Click Edit host details and the screen will be editable as shown below.

Edit Host

Step 5: Select Classification¶

In the Classification column, against the host you want to update, click on the current value (default is Retain).

Classify Host

Step 6: Update Classification¶

Select the appropriate value from the dropdown in the Final classification dropdown, enter a description, and click Save.

Note:
The classification value selected here will be used in report generation.

Step 7: Update OS Support Expiry (Optional)¶

You can update the OS support expiry value.

OS Expiry

Step 8: Save Changes¶

Click Save changes.