> 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/reference-request.md).

# Reference request

All three implementation paths use the same logical request. These are real values from the public-safe reference lab, not production recommendations.

| Input                     | Reference-lab value                      | Decision carried by the input                     |
| ------------------------- | ---------------------------------------- | ------------------------------------------------- |
| Project                   | `demo`                                   | Administrative and quota boundary.                |
| VM                        | `web-01`                                 | Compute resource to create.                       |
| Image                     | `ubuntu`                                 | Approved operating-system source.                 |
| Flavor                    | `m1.tiny`                                | 1 virtual CPU, 512 MiB RAM and a 4 GiB root disk. |
| VM network                | `demo-network`                           | Project network for the VM port.                  |
| Floating-IP network       | `external-network`                       | Active external pool for address allocation.      |
| Security group            | `web-https`                              | Network policy attached to the VM port.           |
| Ingress rule              | IPv4 TCP 443 from `198.51.100.0/24`      | Documented example source range.                  |
| Data volume               | `web-01-data`, 1 GiB, type `__DEFAULT__` | Persistent data separated from the root disk.     |
| Compute availability zone | `nova`                                   | Nova placement input.                             |
| Volume availability zone  | `nova`                                   | Separately discovered Cinder placement input.     |

`198.51.100.0/24` is reserved for documentation by RFC 5737 and does not provide real client access.[\[15\]](https://datatracker.ietf.org/doc/html/rfc5737) The Nova and Cinder availability zones happen to share the label `nova` in this environment. Equal names do not prove shared placement semantics or attachment compatibility. We discover both service inputs separately.


---

# 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/reference-request.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.