About groups of assets in StratoZone

Stay organized with collections Save and categorize content based on your preferences.

The first step to perform any assessment with StratoZone is to create groups of assets.

Asset groups allow you to organize your inventory to simplify planning and implementing a migration. For example, you can choose which groups to migrate first based on application or environment. You can also apply different optimization levels to different groups to enhance the performance or reduce the costs.

StratoZone automatically creates solution groups based on the installed software packages. Additionally, you can create application groups based on your CMDB or naming convention, or group assets based on the environment with build groups. Grouping allows you to view the Google Cloud pricing per build groups or per application group.

Available group types

The following sections describe the group types available in StratoZone, and how to choose them depending on how you want to group your assets.

Dependency groups

Dependency groups allow you to view the network map of a cluster of servers, and in particular of application clusters.

Solution groups

StratoZone automatically generates solution groups by grouping assets based on the software installed.

Solution groups identify the most common enterprise applications, such as SAP, and map to Google Cloud solutions for your environment. For example, depending on the solution installed, StratoZone makes the following recommendations:

  • For SQL Server, PostgreSQL, or MySQL databases: Cloud SQL
  • For MongoDB: Atlas MongoDB
  • For Oracle DB: Oracle BMS

Build groups

Create build groups when you need lists of assets with no specific constraints. Build groups are fully customizable, and you can include a single asset in several build groups.

Use build groups to experiment with rightsizing and pricing options.

Application groups

Create application groups to group the assets according to functional dependencies, analyse the application's topology, and specify application tiers. This is especially useful for large or complex applications.

Consumption groups

Create consumption groups to specify migration waves. For each wave, you can specify the assets to migrate, as well as the intended migration window.

Tag groups

Use tags to specify key-value pairs to organize your assets in a hierarchical way.

What's next