> 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/managed-openstack/5.8/volumes-and-snapshots/storage-solidfire-integration.md).

# Integrating SolidFire with Cinder Block Storage

You can integrate SolidFire to work with Cinder block storage in Platform9 Managed OpenStack.

You must specify the login credentials for SolidFire in the Clarity UI when you authorize a host for block storage, or edit a host to configure it for block storage.

Follow the steps given below to integrate SolidFire with Cinder block storage.

1. Log in to Clarity with administrator credentials.
2. Click Infrastructure.
3. Select the host to be configured and then click Configure Host on the toolbar above the list of hosts.
4. Click Block Storage.
5. Select the Yes check box for Make host a Cinder Block Storage node.
6. Enter the identifier label in the Storage Backend Label. This is a label to identify the storage backend.
7. Select SolidFire as the Driver Type.
8. Enter the IP address of the Storage Area Network (SAN) with SolidFire storage.
9. Select the Add Block Storage Credentials to the Platform9 control plane check box.
10. Enter the SolidFire login ID in Login.
11. Enter the SolidFire password in Password.
12. Click Update Block Storage Details.

The host used for Cinder block storage is able to communicate with the SolidFire storage in the SAN, after configuration of the SolidFire credentials.


---

# 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/managed-openstack/5.8/volumes-and-snapshots/storage-solidfire-integration.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.