Skip to content

Clusters

Oftentimes a set of cloud resources that serve a common purpose can be viewed as a single entity from the user perspective. In many cases, resources are not intended to run independently and are created/terminated simultaneously while sharing an attribute like tag value that connects them together. Such groups of resources can be merged into clusters making them stand-alone virtual resources in DigiUsher for better management options.

Sub-resources are added into clusters automatically based on cluster type definitions that are created by the Organization Manager (a user with the Manager role).

To set up a new cluster, go to the main page and select “Cluster Types” in the left sidebar and then Add. DU CLUSTERS DU CLUSTERS2

A definition consists of the following two parameters:

  • cluster type name - must be unique within the organization.
  • tag key - a common parameter to be used for consolidating sub-resources. DU CLUSTERS1

Cluster type definitions are automatically applied to resources upon their discovery in DigiUsher (through billing or direct discovery) for consolidation even before any existing assignment rules take effect.

The list of cluster types is prioritized to avoid any conflicts. A new cluster type is placed at the bottom of the list so it does not affect existing clusters and can be prioritized manually later on.

Clicking on the Re-apply cluster types button triggers a new resource allocation sequence that uses the current order of cluster types as a rule.

A cluster type can be deleted from the same page. Upon deletion, all clusters of this type are disassembled as well.

In the Resources section, items that are part of a cluster are marked with the DU_CLUSTERS3 symbol to distinguish them among usual resources. Clicking on their names will bring up the Cluster Details page that lists all included sub-resources, their total expenses, and constraints that are applied throughout the cluster.

When a resource becomes part of a cluster, it can no longer be reassigned separately or receive an individual constraint in DigiUsher.