Chapter 1. Configuring OpenStack
Before configuring the Ceph Object Gateway, configure Keystone so that the Swift service is enabled and pointing to the Ceph Object Gateway.
1.1. Creating the Swift Service
To use OpenStack to validate Swift users, first create the Swift service.
# openstack service create --name=swift --description="Swift Service" object-store
Creating the service will echo the service settings. For example:
| Field | Value |
|---|---|
| description | Swift Service |
| enabled | True |
| id | 37c4c0e79571404cb4644201a4a6e5ee |
| name | swift |
| type | object-store |
1.2. Setting the Endpoints
After creating the Swift service, point it to a Ceph Object Gateway. Replace {region-name} with the name of the gateway’s zone group name or region name. Replace the exemplary URLs with URLs appropriate for the Ceph Object Gateway.
# openstack endpoint create --region {region-name} \
--publicurl "http://radosgw.example.com:8080/swift/v1" \
--adminurl "http://radosgw.example.com:8080/swift/v1" \
--internalurl "http://radosgw.example.com:8080/swift/v1" \
swiftSetting the endpoints will echo the service endpoint settings. For example:
| Field | Value |
|---|---|
| adminurl | |
| id | e4249d2b60e44743a67b5e5b38c18dd3 |
| internalurl | |
| publicurl | |
| region | us-west |
| service_id | 37c4c0e79571404cb4644201a4a6e5ee |
| service_name | swift |
| service_type | object-store |
1.3. Verifying the Settings
After creating the Swift service and setting the endpoints, show the endpoints to ensure that all the settings are correct.
# openstack endpoint show object-store
Showing the endpoints will echo the endpoints settings, and the service settings. For example:
| Field | Value |
|---|---|
| adminurl | |
| enabled | True |
| id | e4249d2b60e44743a67b5e5b38c18dd3 |
| internalurl | |
| publicurl | |
| region | us-west |
| service_id | 37c4c0e79571404cb4644201a4a6e5ee |
| service_name | swift |
| service_type | object-store |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.