> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/how-to-identify-ephemeral-vs-boot-from-volume-instances-in-open.md).

# How to Identify Ephemeral vs Boot-From-Volume Instances in OpenStack

## Problem

In OpenStack, instances may be provisioned with either an [ephemeral](https://docs.openstack.org/arch-design/common/glossary.html#term-ephemeral-volume) storage or [persistent](https://docs.openstack.org/arch-design/common/glossary.html#term-persistent-volume) (volume) storage. How can the two be differentiated and filtered accordingly among currently-provisioned instances within a Platform9 Managed OpenStack environment?

## Environment

* Platform9 Managed OpenStack - All Versions
* Nova

## Procedure

### Clarity UI

1. In Clarity UI, navigate to the Instances tab.
2. Ensure that "attached volumes" is shown as an active column. If not, click on the cog icon and add it to the active columns.

<figure><img src="https://3413721029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8o9pwjt91cVZOj58RUXj%2Fuploads%2Fgit-blob-64d6bc8ea461323ae710f3c8677530b42563c697%2F1623345532.png?alt=media" alt="Screen_Shot_2020-11-05_at_2.01.18_PM.png"><figcaption><p>Screen_Shot_2020-11-05_at_2.01.18_PM.png</p></figcaption></figure>

3. Inspect the instances view. Boot from volume instances will show an attached volume, whereas ephemeral instances will not.

<figure><img src="https://3413721029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8o9pwjt91cVZOj58RUXj%2Fuploads%2Fgit-blob-6ec4bf40f2b4cc8e1dbe3098c09bcf74c3c05245%2F1623345534.png?alt=media" alt="Screen_Shot_2020-11-05_at_1_56_32_PM.png"><figcaption><p>Screen_Shot_2020-11-05_at_1_56_32_PM.png</p></figcaption></figure>

### OpenStack CLI

1. Query the list of instances, (optionally) filtered by host – selecting any where the "Image" value is populated, indicating they are **ephemeral** and **not** boot from volume.

{% tabs %}
{% tab title="None" %}

```none
openstack server list --all-projects --host=[HOST_UUID] -f json | jq -r '.[] | select(.Image != "").ID'
```

{% endtab %}
{% endtabs %}

**Note**: To select boot from volume instances, change '!=' to '==' and the opposite results would be shown.


---

# 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://platform9.com/kb/pmo/how-to/how-to-identify-ephemeral-vs-boot-from-volume-instances-in-open.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.