
Keystone has stopped providing or reffering `_member_` role for a while, thus role should not be refferenced anymore. Moreover, with 2023.1 service policies have dropped `_member_` which resulted in the role to be insufficient for basic operations. Change-Id: I4d6eacae2041b0a00114dda4e8315d4ec6295319 Related-Bug: #2029486
36 lines
1.1 KiB
ReStructuredText
36 lines
1.1 KiB
ReStructuredText
`Home <index.html>`_ OpenStack-Ansible Swift
|
|
|
|
Add to existing deployment
|
|
==========================
|
|
|
|
Complete the following procedure to deploy swift on an
|
|
existing deployment.
|
|
|
|
#. `The section called "Configure and mount storage
|
|
devices" <configure-swift-devices.html>`_
|
|
|
|
#. `The section called "Configure an Object Storage
|
|
deployment" <configure-swift-config.html>`_
|
|
|
|
#. Optionally, allow all keystone users to use swift by setting
|
|
``swift_allow_all_users`` in the ``user_variables.yml`` file to
|
|
``True``. Any users with the ``member`` role (all authorized
|
|
keystone users) can create containers and upload objects
|
|
to swift.
|
|
|
|
If this value is ``False``, by default only users with the
|
|
``admin`` role or role set in ``swift_operator_role`` can create
|
|
containers or manage tenants.
|
|
|
|
When the backend type for the glance is set to
|
|
``swift``, glance can access the swift cluster
|
|
regardless of whether this value is ``True`` or ``False``.
|
|
|
|
#. Run the swift play:
|
|
|
|
.. code-block:: shell-session
|
|
|
|
# cd /opt/openstack-ansible/playbooks
|
|
# openstack-ansible os-swift-install.yml
|
|
|