Deployment with Rook

warning

The deployment of Ceph with Rook is a technical preview and not recommended for production use yet.

Deploy services.

When using Rook, all services are deployed via a single helm chart and at the same time. This could be altered by passing custom CRDs. See the Rook Configuration Guide.
- Deploy Kubernetes Cluster
- Deploy Rook Operator
```
osism apply rook-operator
```
- Deploy Ceph cluster
```
osism apply rook
```
- Copy Ceph keyrings to kolla directories (if deploying OpenStack)
```
osism apply rook-fetch-keys
```

Get Ceph keyrings. This places the necessary keys in /opt/configuration.

osism apply rook-fetch-keys

After run, these keys must be permanently added to the configuration repository via Git.

environments/infrastructure/files/ceph/ceph.client.admin.keyring
environments/kolla/files/overlays/gnocchi/ceph.client.gnocchi.keyring
environments/kolla/files/overlays/nova/ceph.client.cinder.keyring
environments/kolla/files/overlays/nova/ceph.client.nova.keyring
environments/kolla/files/overlays/cinder/cinder-backup/ceph.client.cinder.keyring
environments/kolla/files/overlays/cinder/cinder-backup/ceph.client.cinder-backup.keyring
environments/kolla/files/overlays/cinder/cinder-volume/ceph.client.cinder.keyring
environments/kolla/files/overlays/manila/ceph.client.manila.keyring
environments/kolla/files/overlays/glance/ceph.client.glance.keyring

You can also overwrite the rook_cephclients parameter to skip these keys.

environments/rook/configuration.yml
rook_cephclients: {}

A Ceph client, a wrapper on the manager for entering the Rook toolbox, can be deployed.
```
osism apply cephclient
```
You have to make sure the correct Configuration Options for the Rook Ceph Client Wrapper are net.
After getting the Ceph Keyrings, the OpenStack Deployment can optionally be done.

RGW service

Deployment of the Ceph RGW Service is enabled by default in Rook. This is done by creating a default CephObjectStore CRD. How the Ceph RGW service can be deployed and integrated into OpenStack is described here.

In the environments/rook/configuration.yml file you have to adapt accordingly to your environment at least like shown below:

environments/rook/configuration.yml
rook_cephconfig:
  client.rgw.rgw.a:
    rgw_keystone_verify_ssl: "false"
    rgw_verify_ssl: "false"
## keystone
rook_cephobjectstore_keystone_acceptedRoles:
  - admin
  - member
rook_cephobjectstore_keystone_implicitTenants: "true"
rook_cephobjectstore_keystone_url: "https://api-int.testbed.osism.xyz:5000"
rook_cephobjectstore_swift_urlPrefix: "swift"
## keystone user
rook_cephobjectstore_keystone_auth_type: "password"
rook_cephobjectstore_keystone_project_domain_name: "Default"
rook_cephobjectstore_keystone_project_name: "service"
rook_cephobjectstore_keystone_user_domain_name: "Default"
rook_cephobjectstore_keystone_username: "ceph_rgw"

As well as in the environments/rook/secrets.yml file:

environments/rook/secrets.yml
rook_cephobjectstore_keystone_passwor: supersecretpassword

RGW service​

RGW service