Label Types
Label | Description |
|---|---|
Role | This label type allows you to describe a workload's role (or function). In a simple two-tier application consisting of a web server and a database server, there would be two roles: Web and Database. You can use the same role many times as you want in other application rule sets. |
Application | This label type allows you to describe the application that a workload supports. When two servers in a two-tier application have a relationship because one provides a service (like a database) to another, they likely constitute an application. If an organization has 100 applications, each with a separate web role and a separate database role, the application role separates each web and database role. |
Environment | This label type allows you to describe a workload based on its stage in the product development lifecycle, such as QA, staging, and production. |
Location | This label type allows you to describe a workload based on its location. For example, Germany, the US, Europe, and Asia. Or, Rack #3, Rack #4, Rack #5; or data center AWS-east1, AWS-east2, and so on. |
Flexible labels | You can define custom label types to reflect additional characteristics of the workloads in your installation. Create any label type that meets your organization's business needs. For example, you might label workloads according to their operating systems. The maximum number of labels is 20. |
Additional Dimensions
A given workload cannot have more than one label per type. It’s possible to allow a workload that uses a service or services across boundaries to communicate; for example, if a server plays multiple roles, such as a database server used by two different applications, Illumio recommends creating different role labels for that workload.