> For the complete documentation index, see [llms.txt](https://docs.trilio.io/openstack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/openstack/t4o-5.x/advanced-configuration/advanced-ceph-configurations/additions-for-multiple-ceph-configurations.md).

# Additions for multiple CEPH configurations

It is possible to configure Cinder and Ceph to use different Ceph users for different Ceph pools and Cinder volume types. Or to have the nova boot volumes and cinder block volumes controlled by different users.

{% hint style="info" %}
If multiple Ceph storages are configured/integrated with the OpenStack, please ensure that respective conf and keyring files are present in /etc/ceph directory.
{% endhint %}

In the case of multiple Ceph users, it is required to delete the keyring extension from the triliovault-datamover.conf inside the Ceph block by following below mentioned steps:

1. Deploy Trilio as per the documented steps.
2. Post successful deployment, please modify the `triliovault-datamover.conf` file present at following locations on all compute nodes.

   *For RHOSP* : `/var/lib/config-data/puppet-generated/triliovaultdm/etc/triliovault-datamover/`

   *For Kolla* : `/etc/kolla/triliovault-datamover/`
3. Modify `keyring_ext` value with valid keyring extension (eg. .keyring). This extension is expected to be same for all the keyring files. It will be present under `[ceph]` block in `triliovault-datamover.conf` file.

Sample conf entry below. This will try all files with the extension keyring that are located inside /etc/ceph to access the Ceph cluster for a Trilio related task.

```

...

[ceph]
keyring_ext = .keyring

...

```

4. Restart `triliovault_datamover` container on all compute nodes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trilio.io/openstack/t4o-5.x/advanced-configuration/advanced-ceph-configurations/additions-for-multiple-ceph-configurations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.