> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-3/project-identity-and-quota.md).
# Project, identity and quota
A **project** is the OpenStack boundary in which resources and role assignments are grouped. A participant may operate the cloud, work on a platform operated by another organisation or use a managed OpenStack service. In each case, we begin with an existing project and an approved identity. The reference lab uses the project name `demo`.[\[2\]](https://docs.openstack.org/horizon/latest/user/log-in.html)
A role permits actions within its assigned scope. A cloud profile in `clouds.yaml` tells a client which authentication endpoint, region and credential method to use. Its profile name, such as `my-cloud`, is local client configuration rather than an OpenStack resource.[\[8\]](https://docs.openstack.org/python-openstackclient/latest/configuration/index.html)
Quota limits how much of a resource the project may consume. It does not guarantee physical capacity, placement, image bootability or network reachability. Before creating anything, we compare current use and limits for one instance, one virtual CPU, 512 MiB RAM, one 1 GiB volume, one port, one security group, its rules and one floating IP. A limit of `-1` means that the deployment has not set a project quota for that resource. It does not mean that capacity is unlimited.
Figure 2. Horizon exposes project usage. Storage and floating-IP pages complete the quota view used by the lab.
The first lab step performs the same check through Horizon and the API, then records only approved values in a local environment contract: [Lab 01, Discovery and environment contract](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/lab/walkthroughs/01-discovery.md). Video route: [C3-I2, Boundaries, quota and evidence](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/VIDEO_SCOPES.md#user-content-c3-i2-boundaries-quota-and-evidence) and [C3-P1, Discover and approve the lab inputs](https://git.vanillacore.net/giga/content/src/branch/main/chapter-3/VIDEO_SCOPES.md#user-content-c3-p1-discover-and-approve-the-lab-inputs).
---
# 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://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-3/project-identity-and-quota.md?ask=&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.
