openstack/tripleo-docs
Code Issues Proposed changes

Documentation for Support for external swift proxy

Browse Source 
Users may have an external swift proxy already available (i.e. radosgw
from already existing ceph, or hardware appliance implementing swift
proxy). With this change user may specify an environment file that
registers the specified urls as endpoint for the object-store service.
The internal swift proxy is left as unconfigured.

Change-Id: I5f60f9cf321fcccdb9801f4678fd3cb922812548
Depends-On: I5e6f0a50f26d4296565f0433f720bfb40c5d2109
This commit is contained in:
Luca Lorenzetto 2017-04-14 13:48:52 +02:00
parent a53fb8f605
commit 09d5d755ce
2 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/advanced_deployment/backends.rst
View File

@ -14,3 +14,4 @@ OpenStack projects.
ceph_external
neutron_midonet
domain_specific_ldap_backends
swift_external

30
doc/source/advanced_deployment/swift_external.rst Normal file
View File

@ -0,0 +1,30 @@
Use an external Ceph cluster with the Overcloud
===============================================
|project| supports use of an external Swift proxy already available to the
operator, that may need to configure at deploy time.
This happens by enabling a particular environment file when deploying the
Overcloud, specifically `environments/swift-external.yaml`.
In the environment file above user must adjust the parameters to fit
its setup by creating a custom environment file (i.e.
*~/my-swift-settings.yaml*)::
parameter_defaults:
ExternalPublicUrl: 'http://swiftproxy:9024/v1/%(tenant_id)s'
ExternalInternalUrl: 'http://swiftproxy:9024/v1/%(tenant_id)s'
ExternalAdminUrl: 'http://swiftproxy:9024/v1/%(tenant_id)s'
ExternalSwiftUserTenant: 'service'
The user can create an environment file with the required settings
and add the files above to the deploy commandline::
openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/swift-external.yaml -e ~/my-swift-settings.yaml
Once the deploy has succeeded, user has to complete the
configuration on the external swift proxy, configuring it to use the
keystone authentication provider. This environment files creates also
a service user called *swift* that can be used for this purpose.