Chapter 17. Storage configuration

Procedure

1. Create a new file named swift-external-params.yaml with the following content:

   • Replace EXTERNAL.IP:PORT with the IP address and port of the external proxy and

   • Replace AUTHTOKEN with the authtoken password for the external proxy on the SwiftPassword line.

     parameter_defaults:
       ExternalPublicUrl: 'https://EXTERNAL.IP:PORT/v1/AUTH_%(tenant_id)s'
       ExternalInternalUrl: 'http://192.168.24.9:8080/v1/AUTH_%(tenant_id)s'
       ExternalAdminUrl: 'http://192.168.24.9:8080'
       ExternalSwiftUserTenant: 'service'
       SwiftPassword: AUTHTOKEN

2. Save this file as swift-external-params.yaml.

3. Deploy the overcloud with the following external Object Storage service environment files, as well as any other environment files that are relevant to your deployment:

   openstack overcloud deploy --templates \
   -e [your environment files] \
   -e /usr/share/openstack-tripleo-heat-templates/environments/swift-external.yaml \
   -e swift-external-params.yaml

Procedure

1. Add the following parameter_defaults to a custom environment file, for example, swift-external-params.yaml, and adjust the values to suit your deployment:

   parameter_defaults:
      ExternalSwiftPublicUrl: 'http://<Public RGW endpoint or loadbalancer>:8080/swift/v1/AUTH_%(project_id)s'
      ExternalSwiftInternalUrl: 'http://<Internal RGW endpoint>:8080/swift/v1/AUTH_%(project_id)s'
      ExternalSwiftAdminUrl: 'http://<Admin RGW endpoint>:8080/swift/v1/AUTH_%(project_id)s'
      ExternalSwiftUserTenant: 'service'
      SwiftPassword: 'choose_a_random_password'

   Note

   The example code snippet contains parameter values that might differ from values that you use in your environment:

   • The default port where the remote RGW instance listens is 8080. The port might be different depending on how the external RGW is configured.
   • The swift user created in the overcloud uses the password defined by the SwiftPassword parameter. You must configure the external RGW instance to use the same password to authenticate with the Identity service by using the rgw_keystone_admin_password.

2. Add the following code to the Ceph config file to configure RGW to use the Identity service. Replace the variable values to suit your environment:

       rgw_keystone_api_version = 3
       rgw_keystone_url = http://<public Keystone endpoint>:5000/
       rgw_keystone_accepted_roles = member, Member, admin
       rgw_keystone_accepted_admin_roles = ResellerAdmin, swiftoperator
       rgw_keystone_admin_domain = default
       rgw_keystone_admin_project = service
       rgw_keystone_admin_user = swift
       rgw_keystone_admin_password = <password_as_defined_in_the_environment_parameters>
       rgw_keystone_implicit_tenants = true
       rgw_keystone_revocation_interval = 0
       rgw_s3_auth_use_keystone = true
       rgw_swift_versioning_enabled = true
       rgw_swift_account_in_url = true

   Note

   Director creates the following roles and users in the Identity service by default:

   • rgw_keystone_accepted_admin_roles: ResellerAdmin, swiftoperator
   • rgw_keystone_admin_domain: default
   • rgw_keystone_admin_project: service
   • rgw_keystone_admin_user: swift

3. Deploy the overcloud with the additional environment files with any other environment files that are relevant to your deployment:

   openstack overcloud deploy --templates \
   -e <your_environment_files>
   -e /usr/share/openstack-tripleo-heat-templates/environments/swift-external.yaml
   -e swift-external-params.yaml

Verification

1. Log in to the undercloud as the stack user.

2. Source the overcloudrc file:

   $ source ~/stackrc

3. Verify that the endpoints exist in the Identity service (keystone):

   $ openstack endpoint list --service object-store
   
   +---------+-----------+-------+-------+---------+-----------+---------------+
   | ID | Region    | Service Name | Service Type | Enabled | Interface | URL |
   +---------+-----------+-------+-------+---------+-----------+---------------+
   | 233b7ea32aaf40c1ad782c696128aa0e | regionOne | swift | object-store | True    | admin     | http://192.168.24.3:8080/v1/AUTH_%(project_id)s |
   | 4ccde35ac76444d7bb82c5816a97abd8 | regionOne | swift | object-store | True    | public    | https://192.168.24.2:13808/v1/AUTH_%(project_id)s |
   | b4ff283f445348639864f560aa2b2b41 | regionOne | swift | object-store | True    | internal  | http://192.168.24.3:8080/v1/AUTH_%(project_id)s |
   +---------+-----------+-------+-------+---------+-----------+---------------+

4. Create a test container:

   $ openstack container create <testcontainer>
   +----------------+---------------+------------------------------------+
   | account | container | x-trans-id |
   +----------------+---------------+------------------------------------+
   | AUTH_2852da3cf2fc490081114c434d1fc157 | testcontainer | tx6f5253e710a2449b8ef7e-005f2d29e8 |
   +----------------+---------------+------------------------------------+

5. Create a configuration file to confirm that you can upload data to the container:

   $ openstack object create testcontainer undercloud.conf
   +-----------------+---------------+----------------------------------+
   | object          | container     | etag                             |
   +-----------------+---------------+----------------------------------+
   | undercloud.conf | testcontainer | 09fcffe126cac1dbac7b89b8fd7a3e4b |
   +-----------------+---------------+----------------------------------+

6. Delete the test container:

   $ openstack container delete -r <testcontainer>

Procedure

1. To configure cinder as the Image service back end, add the following line to an environment file:

   parameter_defaults:
     GlanceBackend: cinder

2. If the cinder back end is enabled, the following parameters and values are set by default:

   cinder_store_auth_address = http://172.17.1.19:5000/v3
   cinder_store_project_name = service
   cinder_store_user_name = glance
   cinder_store_password = ****secret****

3. To use a custom user name, or any custom value for the cinder_store_ parameters, add the ExtraConfig parameter to parameter_defaults and include your custom values:

   ExtraConfig:
       glance::config::api_config:
         glance_store/cinder_store_auth_address:
           value: "%{hiera('glance::api::authtoken::auth_url')}/v3"
         glance_store/cinder_store_user_name:
           value: <user-name>
         glance_store/cinder_store_password:
           value: "%{hiera('glance::api::authtoken::password')}"
         glance_store/cinder_store_project_name:
           value: "%{hiera('glance::api::authtoken::project_name')}"

Procedure

1. In an environment file, set the value of the GlanceCacheEnabled parameter to true, which automatically sets the flavor value to keystone+cachemanagement in the glance-api.conf heat template:

   parameter_defaults:
       GlanceCacheEnabled: true

2. Include the environment file in the openstack overcloud deploy command when you redeploy the overcloud.

3. Optional: Tune the glance_cache_pruner to an alternative frequency when you redeploy the overcloud. The following example shows a frequency of 5 minutes:

   parameter_defaults:
     ControllerExtraConfig:
       glance::cache::pruner::minute: '*/5'

   Adjust the frequency according to your needs to avoid file system full scenarios. Include the following elements when you choose an alternative frequency:

   • The size of the files that you want to cache in your environment.
   • The amount of available file system space.
   • The frequency at which the environment caches images.