rgw: add support for keystone auth + swift/s3
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> * extend the API object specs for swift and keystone integration * adapt rgw to the new go-ceph version - The parameter lists of the API call have changes, as parameters ignored by the RGW Admin Ops API are no longer serialized, therefore the mock has to be adapted. - There is now validation for the user keys that are passed to the User get API, therefore things failed when we had empty keys in our User proxy object. * expand the reconcile loop for the swift and keystone integration * fix minor mistakes in design document * add env var to pass extra args to minikube Minikube decides CPU cores and memory automatically based on the available resources on the machine which may be insufficient to run rook. This commit adds an environment variable to add arbitrary arguments to the minikube command, so both can be specified if desired. * integration tests for swift and keystone The new integration of swift or s3 and keystone support by rook does not have any integration tests yet. This commit introduces integration tests for swift and keystone. The tests are done against a minimal keystone setup (keystone container image from Yaook-project (https://yaook.cloud), sqlite as database backend, cert-manager and trust-manager for test certificate setup). To prevent hardcoded credentials, passwords are generated by the tests. The integration tests use the openstack client (keystone- and swift-functionality) (https://docs.openstack.org/ python-openstackclient/ latest/). This was a concious design decision to use client tooling as close as possible to the end user instead of using other go-libraries (such as gophercloud). * add documentation on swift and keystone Currently there is no documentation on the use of Swift to access an object store as well as the use of OpenStack keystone for authentication. This commit adds documentation on the use of Swift and OpenStack keystone, as well as CRD-related documentation and an example setup. * add integration tests for S3 via keystone This commit introduces integration tests for s3 and keystone. The tests are run against the same minimal keystone setup that the tests for swift and keystone use. The integration tests use the aws s3 client to use client tooling as close as possible to the end user instead of using other go-libraries. Co-authored-by: Jan Klippel <jan.klippel@uhurutec.com> Co-authored-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Jan Klippel <jan.klippel@uhurutec.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
This commit is contained in:
1 parent
9c98467f3c
commit
ee8bcad49d
34 files changed
+2733
-89
No files matched your search
@@ -2,7 +2,7 @@
|
||||
title: Object Storage Overview
|
||||
---
|
||||
|
||||
Object storage exposes an S3 API to the storage cluster for applications to put and get data.
|
||||
Object storage exposes an S3 API and or a [Swift API](https://developer.openstack.org/api-ref/object-store/index.html) to the storage cluster for applications to put and get data.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -12,7 +12,7 @@ This guide assumes a Rook cluster as explained in the [Quickstart](../../Getting
|
||||
|
||||
Rook can configure the Ceph Object Store for several different scenarios. See each linked section for the configuration details.
|
||||
|
||||
1. Create a [local object store](#create-a-local-object-store) with dedicated Ceph pools. This option is recommended if a single object store is required, and is the simplest to get started.
|
||||
1. Create a [local object store](#create-a-local-object-store-with-s3) with dedicated Ceph pools. This option is recommended if a single object store is required, and is the simplest to get started.
|
||||
2. Create [one or more object stores with shared Ceph pools](#create-local-object-stores-with-shared-pools). This option is recommended when multiple object stores are required.
|
||||
3. Connect to an [RGW service in an external Ceph cluster](#connect-to-an-external-object-store), rather than create a local object store.
|
||||
4. Configure [RGW Multisite](#object-multisite) to synchronize buckets between object stores in different clusters.
|
||||
@@ -20,7 +20,11 @@ Rook can configure the Ceph Object Store for several different scenarios. See ea
|
||||
!!! note
|
||||
Updating the configuration of an object store between these types is not supported.
|
||||
|
||||
### Create a Local Object Store
|
||||
Rook has the ability to either deploy an object store in Kubernetes or to connect to an external RGW service.
|
||||
Most commonly, the object store will be configured in Kubernetes by Rook.
|
||||
Alternatively see the [external section](#connect-to-an-external-object-store) to consume an existing Ceph cluster with [Rados Gateways](https://docs.ceph.com/en/quincy/radosgw/index.html) from Rook.
|
||||
|
||||
### Create a Local Object Store with S3
|
||||
|
||||
The below sample will create a `CephObjectStore` that starts the RGW service in the cluster with an S3 API.
|
||||
|
||||
@@ -568,3 +572,10 @@ Multisite is a feature of Ceph that allows object stores to replicate its data o
|
||||
Multisite also allows object stores to be independent and isolated from other object stores in a cluster.
|
||||
|
||||
For more information on multisite please read the [ceph multisite overview](ceph-object-multisite.md) for how to run it.
|
||||
|
||||
## Using Swift and Keystone
|
||||
|
||||
It is possible to access an object store using the [Swift API](https://developer.openstack.org/api-ref/object-store/index.html).
|
||||
Using Swift requires the use of [OpenStack Keystone](https://docs.openstack.org/keystone/latest/) as an authentication provider.
|
||||
|
||||
More information on the use of Swift and Keystone can be found in the document on [Object Store with Keystone and Swift](ceph-object-swift.md).
|
||||
Reference in new issue
Block a user