swift/doc/source/install/finalize-installation-rdo.rst
zengjia 2c4f284055 Modify the version path URL of the configuration file
In the main branch, I think it is necessary to modify
the configuration file path in the document as the
main branch path, and to change the path to a stable
version when the version is released.

Change-Id: Ib1bc4c59ed4c7624782b8b1cdea20847c14c90bf
2019-05-23 10:53:31 +08:00

3.4 KiB

Finalize installation for Red Hat Enterprise Linux and CentOS

Note

Default configuration files vary by distribution. You might need to add these sections and options rather than modifying existing sections and options. Also, an ellipsis (...) in the configuration snippets indicates potential default configuration options that you should retain.

This section applies to Red Hat Enterprise Linux 7 and CentOS 7.

  1. Obtain the /etc/swift/swift.conf file from the Object Storage source repository:

    # curl -o /etc/swift/swift.conf \
      https://opendev.org/openstack/swift/raw/branch/master/etc/swift.conf-sample
  2. Edit the /etc/swift/swift.conf file and complete the following actions:

    • In the [swift-hash] section, configure the hash path prefix and suffix for your environment.

      [swift-hash]
      ...
      swift_hash_path_suffix = HASH_PATH_SUFFIX
      swift_hash_path_prefix = HASH_PATH_PREFIX

      Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values.

      Warning

      Keep these values secret and do not change or lose them.

    • In the [storage-policy:0] section, configure the default storage policy:

      [storage-policy:0]
      ...
      name = Policy-0
      default = yes
  3. Copy the swift.conf file to the /etc/swift directory on each storage node and any additional nodes running the proxy service.

  4. On all nodes, ensure proper ownership of the configuration directory:

    # chown -R root:swift /etc/swift
  5. On the controller node and any other nodes running the proxy service, start the Object Storage proxy service including its dependencies and configure them to start when the system boots:

    # systemctl enable openstack-swift-proxy.service memcached.service
    # systemctl start openstack-swift-proxy.service memcached.service
  6. On the storage nodes, start the Object Storage services and configure them to start when the system boots:

    # systemctl enable openstack-swift-account.service openstack-swift-account-auditor.service \
      openstack-swift-account-reaper.service openstack-swift-account-replicator.service
    # systemctl start openstack-swift-account.service openstack-swift-account-auditor.service \
      openstack-swift-account-reaper.service openstack-swift-account-replicator.service
    # systemctl enable openstack-swift-container.service \
      openstack-swift-container-auditor.service openstack-swift-container-replicator.service \
      openstack-swift-container-updater.service
    # systemctl start openstack-swift-container.service \
      openstack-swift-container-auditor.service openstack-swift-container-replicator.service \
      openstack-swift-container-updater.service
    # systemctl enable openstack-swift-object.service openstack-swift-object-auditor.service \
      openstack-swift-object-replicator.service openstack-swift-object-updater.service
    # systemctl start openstack-swift-object.service openstack-swift-object-auditor.service \
      openstack-swift-object-replicator.service openstack-swift-object-updater.service