Update swift configuration for Mitaka. 1) Change configuration file branch from liberty to mitaka. 2) Change keystone middleware to use domain name instead of domain ID. 3) Use OpenStack client instead of swift client to download object. Considerably slower, but works. 4) Remove workaround for using the Identity v3 API because the entire guide continues to use "versioned" endpoints. Implements: bp installguide-mitaka Change-Id: I3115c11b55764dc321459d7e9f11b49982cdd11e
6.7 KiB
Finalize installation
ubuntu or rdo or debian
Obtain the
/etc/swift/swift.conf
file from the Object Storage source repository:# curl -o /etc/swift/swift.conf \ https://git.openstack.org/cgit/openstack/swift/plain/etc/swift.conf-sample?h=stable/mitaka
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
Copy the
swift.conf
file to the/etc/swift
directory on each storage node and any additional nodes running the proxy service.
obs
- 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
- Copy the
swift.conf
file to the/etc/swift
directory on each storage node and any additional nodes running the proxy service.
ubuntu or debian
On all nodes, ensure proper ownership of the configuration directory:
# chown -R root:swift /etc/swift
On the controller node and any other nodes running the proxy service, restart the Object Storage proxy service including its dependencies:
# service memcached restart # service swift-proxy restart
On the storage nodes, start the Object Storage services:
# swift-init all start
Note
The storage node runs many Object Storage services and the
swift-init
command makes them easier to manage. You can ignore errors from services not running on the storage node.
rdo
On all nodes, ensure proper ownership of the configuration directory:
# chown -R root:swift /etc/swift
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
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
obs
On all nodes, ensure proper ownership of the configuration directory:
# chown -R root:swift /etc/swift
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
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