rpedde

Environment Hackery

Sometimes the assumptions in swift-private-cloud are wrong. They don't fit the customer environment, or a one-off configuration makes the assumptions invalid (this never happens).

When it does happen, you'll be happy to know that the swift-private-cloud cookbooks are much more configurable than the old swift cookbooks, and significantly more configurable than the nova cookbooks as well.

If you are thinking you need to override something, or change the behavior of a deployed swift cluster, you probably can. Without having to drop the cluster out of config management.

Built-in Assumptions

rpedde

Installing Custom Middleware

Sometimes, middleware needs to be added or configured differently than the assumptions made in the swift-private-cloud cookbook.

Fortunately, there are provisions for modifying to configurations to achieve different goals.

As an example, let's install Swift's "Static Web" middleware, as described in the [OpenStack Object Storage

rpedde

#!/bin/bash

set -e

dsh -Mcg swift-storage sudo /usr/local/bin/swift-partition.sh xvdb
dsh -Mcg swift-storage sudo /usr/local/bin/swift-format.sh xvdb1
dsh -Mcg swift-storage sudo mkdir -p /srv/node/disk1
dsh -Mcg swift-storage sudo mount /dev/xvdb1 /srv/node/disk1
dsh -Mcg swift-storage sudo chown -R swift: /srv/node/disk1