Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ceph: add ceph_kolla_keys parameter #394

Merged
merged 1 commit into from
Mar 26, 2024
+9 −2
Merged

ceph: add ceph_kolla_keys parameter #394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions docs/guides/deploy-guide/services/ceph.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,15 @@ volumes must be completed. The steps that are required for this can be found in
environments/kolla/files/overlays/glance/ceph.client.glance.keyring
```

If the `osism apply copy-ceph-keys` fails and the keys are not found in the `/share`
directory, this can be solved with `osism apply ceph-fetch-keys`.
If the `osism apply copy-ceph-keys` fails because the keys are not found in the `/share`
directory, this can be ignored. The keys of the predefined keys (e.g. for Manila) were
then not created as they are not used. If you only use Ceph and do not need the predefined
keys for OpenStack at all, you can also overwrite the `ceph_kolla_keys` parameter to skip
these keys.

```yaml title="environments/ceph/configuration.yml"
ceph_kolla_keys: []
```

3. After the Ceph keys have been persisted in the configuration repository, the Ceph
client can be deployed.
Expand Down
Loading