> 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/private-cloud-director/storage/storage-overview.md).

# Overview

This tutorial reviews different storage options available in <code class="expression">space.vars.product\_name</code>, and the use cases for each.

## PCD Storage Options At A Glance

There are currently **two** storage options available in <code class="expression">space.vars.product\_name</code>: **ephemeral storage & block storage.** The type of storage you use for a virtual machine depends on how you create it.

## Ephemeral Storage

An ephemeral disk is created for the root disk of the virtual machine.

Read more here about [Ephemeral Storage](/private-cloud-director/storage/ephemeral-storage.md).

## Block Storage

Block storage support in <code class="expression">space.vars.product\_name</code> enables the use of persistent block storage volumes with virtual machines. This is the most popular and recommended way to configure storage for your production virtual machines. Block storage volumes can be configured to persist even when the VMs they are attached to are deleted.

Read more here about [Block Storage](/private-cloud-director/storage/block-storage.md) support in <code class="expression">space.vars.product\_acronym</code>.


---

# 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/private-cloud-director/storage/storage-overview.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.