> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno.md).

# Módulo 2: dimensionamiento y diseño

- [Descripción general](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno/02-sizing-design.md): Requisitos de hardware, arquitecturas de referencia y ejercicios de definición de alcance para clientes para implementaciones de VergeOS.
- [Requisitos de hardware](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno/01-hardware-requirements.md): Especificaciones mínimas y recomendadas de hardware para nodos controladores, nodos de almacenamiento y nodos solo de cómputo de VergeOS, además de los límites máximos admitidos.
- [Laboratorio: ejercicio de dimensionamiento y diseño](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno/lab.md): Diseñar una implementación de VergeOS para un escenario de cliente, incluida la selección de la topología y el dimensionamiento del hardware.
- [Arquitecturas de referencia](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno/02-reference-architectures.md): Tres modelos de despliegue de VergeOS: HCI, HCI + cómputo dedicado y UCI, con un marco de decisión, diagramas de topología y orientación para escenarios de edge y CSP.
- [Definición de alcance con el cliente](https://docs.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno/03-customer-scoping.md): Metodología de recopilación de requisitos, traducción de cargas de trabajo a recursos, planificación de nodos de inquilino, marco de selección de topología y entregables de documentación para despliegues de VergeOS.


---

# 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.verge.io/learn-the-platform/es/modulo-2-dimensionamiento-y-diseno.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.