> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.6/infrastructure/host-aggregates/infrastructure-host-aggregates.md).

# What is a Host Aggregate

A **Host aggregate** is a group of hosts that share a common attribute or capability, eg a group of hosts with same hardware configuration.

You can create efficient and scalable resource tiers using host aggregates.

You can do the following with host aggregates.

* Create virtual clusters or tiers of resources by grouping together one or more hypervisors by using simple key-value pair tagging.
* Utilize the tiers across different tenants, to restrict placement of specific groups of virtual machines solely to the tier that is applicable to them.

For example, a solid state drive (SSD) tier can be created to ensure that all production workloads get efficient and fast storage I/O access. Similarly, a production tier and development-test tier strategy can be used to separate your workloads.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-openstack/5.6/infrastructure/host-aggregates/infrastructure-host-aggregates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.