blob: 713b38c74608ddae622f7f62914d0268e2d26c83 [file] [log] [blame]
Attila Fazekasece6a332012-11-29 14:19:41 +01001# lib/swift
2# Functions to control the configuration and operation of the swift service
3
4# Dependencies:
5# ``functions`` file
6# ``DEST``, ``SCREEN_NAME``, `SWIFT_HASH` must be defined
7# ``SWIFT_DATA_DIR`` or ``DATA_DIR`` must be defined
8# ``lib/keystone`` file
9# ``stack.sh`` calls the entry points in this order:
10#
11# install_swift
12# configure_swift
13# init_swift
14# start_swift
15# stop_swift
16# cleanup_swift
17
18# Save trace setting
19XTRACE=$(set +o | grep xtrace)
20set +o xtrace
21
22
23# Defaults
24# --------
25
26# <define global variables here that belong to this project>
27
28# Set up default directories
29
30SWIFT_DIR=$DEST/swift
31SWIFTCLIENT_DIR=$DEST/python-swiftclient
Dean Troyer64ab7742012-12-28 15:38:28 -060032SWIFT_AUTH_CACHE_DIR=${SWIFT_AUTH_CACHE_DIR:-/var/cache/swift}
Attila Fazekasece6a332012-11-29 14:19:41 +010033
34# TODO: add logging to different location.
35
36# Set ``SWIFT_DATA_DIR`` to the location of swift drives and objects.
37# Default is the common DevStack data directory.
38SWIFT_DATA_DIR=${SWIFT_DATA_DIR:-${DATA_DIR}/swift}
39
40# Set ``SWIFT_CONFIG_DIR`` to the location of the configuration files.
41# Default is ``/etc/swift``.
42SWIFT_CONFIG_DIR=${SWIFT_CONFIG_DIR:-/etc/swift}
43
44# DevStack will create a loop-back disk formatted as XFS to store the
45# swift data. Set ``SWIFT_LOOPBACK_DISK_SIZE`` to the disk size in bytes.
46# Default is 1 gigabyte.
47SWIFT_LOOPBACK_DISK_SIZE=${SWIFT_LOOPBACK_DISK_SIZE:-1000000}
48
49# The ring uses a configurable number of bits from a path’s MD5 hash as
50# a partition index that designates a device. The number of bits kept
51# from the hash is known as the partition power, and 2 to the partition
52# power indicates the partition count. Partitioning the full MD5 hash
53# ring allows other parts of the cluster to work in batches of items at
54# once which ends up either more efficient or at least less complex than
55# working with each item separately or the entire cluster all at once.
56# By default we define 9 for the partition count (which mean 512).
57SWIFT_PARTITION_POWER_SIZE=${SWIFT_PARTITION_POWER_SIZE:-9}
58
59# Set ``SWIFT_REPLICAS`` to configure how many replicas are to be
60# configured for your Swift cluster. By default the three replicas would need a
61# bit of IO and Memory on a VM you may want to lower that to 1 if you want to do
62# only some quick testing.
63SWIFT_REPLICAS=${SWIFT_REPLICAS:-3}
64SWIFT_REPLICAS_SEQ=$(seq ${SWIFT_REPLICAS})
65
66# Set ``OBJECT_PORT_BASE``, ``CONTAINER_PORT_BASE``, ``ACCOUNT_PORT_BASE``
67# Port bases used in port number calclution for the service "nodes"
68# The specified port number will be used, the additinal ports calculated by
69# base_port + node_num * 10
70OBJECT_PORT_BASE=6010
71CONTAINER_PORT_BASE=6011
72ACCOUNT_PORT_BASE=6012
73
74# Entry Points
75# ------------
76
77# cleanup_swift() - Remove residual data files
78function cleanup_swift() {
79 rm -f ${SWIFT_CONFIG_DIR}{*.builder,*.ring.gz,backups/*.builder,backups/*.ring.gz}
80 if egrep -q ${SWIFT_DATA_DIR}/drives/sdb1 /proc/mounts; then
81 sudo umount ${SWIFT_DATA_DIR}/drives/sdb1
82 fi
83 if [[ -e ${SWIFT_DATA_DIR}/drives/images/swift.img ]]; then
84 rm ${SWIFT_DATA_DIR}/drives/images/swift.img
85 fi
86}
87
88# configure_swift() - Set config files, create data dirs and loop image
89function configure_swift() {
90 local swift_auth_server
91 local node_number
92 local swift_node_config
93 local swift_log_dir
94
95 setup_develop $SWIFT_DIR
96
97 # Make sure to kill all swift processes first
98 swift-init all stop || true
99
100 # First do a bit of setup by creating the directories and
101 # changing the permissions so we can run it as our user.
102
103 USER_GROUP=$(id -g)
104 sudo mkdir -p ${SWIFT_DATA_DIR}/drives
105 sudo chown -R $USER:${USER_GROUP} ${SWIFT_DATA_DIR}
106
107 # Create a loopback disk and format it to XFS.
108 if [[ -e ${SWIFT_DATA_DIR}/drives/images/swift.img ]]; then
109 if egrep -q ${SWIFT_DATA_DIR}/drives/sdb1 /proc/mounts; then
110 sudo umount ${SWIFT_DATA_DIR}/drives/sdb1
111 fi
112 else
113 mkdir -p ${SWIFT_DATA_DIR}/drives/images
114 sudo touch ${SWIFT_DATA_DIR}/drives/images/swift.img
115 sudo chown $USER: ${SWIFT_DATA_DIR}/drives/images/swift.img
116
117 dd if=/dev/zero of=${SWIFT_DATA_DIR}/drives/images/swift.img \
118 bs=1024 count=0 seek=${SWIFT_LOOPBACK_DISK_SIZE}
119 fi
120
121 # Make a fresh XFS filesystem
122 mkfs.xfs -f -i size=1024 ${SWIFT_DATA_DIR}/drives/images/swift.img
123
124 # Mount the disk with mount options to make it as efficient as possible
125 mkdir -p ${SWIFT_DATA_DIR}/drives/sdb1
126 if ! egrep -q ${SWIFT_DATA_DIR}/drives/sdb1 /proc/mounts; then
127 sudo mount -t xfs -o loop,noatime,nodiratime,nobarrier,logbufs=8 \
128 ${SWIFT_DATA_DIR}/drives/images/swift.img ${SWIFT_DATA_DIR}/drives/sdb1
129 fi
130
131 # Create a link to the above mount and
132 # create all of the directories needed to emulate a few different servers
133 for node_number in ${SWIFT_REPLICAS_SEQ}; do
134 sudo ln -sf ${SWIFT_DATA_DIR}/drives/sdb1/$node_number ${SWIFT_DATA_DIR}/$node_number;
135 drive=${SWIFT_DATA_DIR}/drives/sdb1/${node_number}
136 node=${SWIFT_DATA_DIR}/${node_number}/node
137 node_device=${node}/sdb1
138 [[ -d $node ]] && continue
139 [[ -d $drive ]] && continue
140 sudo install -o ${USER} -g $USER_GROUP -d $drive
141 sudo install -o ${USER} -g $USER_GROUP -d $node_device
142 sudo chown -R $USER: ${node}
143 done
144
145 sudo mkdir -p ${SWIFT_CONFIG_DIR}/{object,container,account}-server /var/run/swift
146 sudo chown -R $USER: ${SWIFT_CONFIG_DIR} /var/run/swift
147
148 if [[ "$SWIFT_CONFIG_DIR" != "/etc/swift" ]]; then
149 # Some swift tools are hard-coded to use ``/etc/swift`` and are apparently not going to be fixed.
150 # Create a symlink if the config dir is moved
151 sudo ln -sf ${SWIFT_CONFIG_DIR} /etc/swift
152 fi
153
154 # Swift use rsync to synchronize between all the different
155 # partitions (which make more sense when you have a multi-node
156 # setup) we configure it with our version of rsync.
157 sed -e "
158 s/%GROUP%/${USER_GROUP}/;
159 s/%USER%/$USER/;
160 s,%SWIFT_DATA_DIR%,$SWIFT_DATA_DIR,;
161 " $FILES/swift/rsyncd.conf | sudo tee /etc/rsyncd.conf
162 # rsyncd.conf just prepared for 4 nodes
Vincent Untzc18b9652012-12-04 12:36:34 +0100163 if is_ubuntu; then
Attila Fazekasece6a332012-11-29 14:19:41 +0100164 sudo sed -i '/^RSYNC_ENABLE=false/ { s/false/true/ }' /etc/default/rsync
165 else
166 sudo sed -i '/disable *= *yes/ { s/yes/no/ }' /etc/xinetd.d/rsync
167 fi
168
169 if is_service_enabled swift3;then
170 swift_auth_server="s3token "
171 fi
172
173 # By default Swift will be installed with the tempauth middleware
174 # which has some default username and password if you have
175 # configured keystone it will checkout the directory.
176 if is_service_enabled key; then
177 swift_auth_server+="authtoken keystoneauth"
178 else
179 swift_auth_server=tempauth
180 fi
181
182 SWIFT_CONFIG_PROXY_SERVER=${SWIFT_CONFIG_DIR}/proxy-server.conf
183 cp ${SWIFT_DIR}/etc/proxy-server.conf-sample ${SWIFT_CONFIG_PROXY_SERVER}
184
185 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT user
186 iniset ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT user ${USER}
187
188 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT swift_dir
189 iniset ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT swift_dir ${SWIFT_CONFIG_DIR}
190
191 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT workers
192 iniset ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT workers 1
193
194 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT log_level
195 iniset ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT log_level DEBUG
196
197 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT bind_port
198 iniset ${SWIFT_CONFIG_PROXY_SERVER} DEFAULT bind_port ${SWIFT_DEFAULT_BIND_PORT:-8080}
199
200 # Only enable Swift3 if we have it enabled in ENABLED_SERVICES
201 is_service_enabled swift3 && swift3=swift3 || swift3=""
202
203 iniset ${SWIFT_CONFIG_PROXY_SERVER} pipeline:main pipeline "catch_errors healthcheck cache ratelimit ${swift3} ${swift_auth_server} proxy-logging proxy-server"
204
205 iniset ${SWIFT_CONFIG_PROXY_SERVER} app:proxy-server account_autocreate true
206
207 # Configure Keystone
208 sed -i '/^# \[filter:authtoken\]/,/^# \[filter:keystoneauth\]$/ s/^#[ \t]*//' ${SWIFT_CONFIG_PROXY_SERVER}
209 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken auth_host $KEYSTONE_AUTH_HOST
210 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken auth_port $KEYSTONE_AUTH_PORT
211 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken auth_protocol $KEYSTONE_AUTH_PROTOCOL
212 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken auth_uri $KEYSTONE_SERVICE_PROTOCOL://$KEYSTONE_SERVICE_HOST:$KEYSTONE_SERVICE_PORT/
213 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken admin_tenant_name $SERVICE_TENANT_NAME
214 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken admin_user swift
215 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken admin_password $SERVICE_PASSWORD
Dean Troyer64ab7742012-12-28 15:38:28 -0600216 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:authtoken signing_dir $SWIFT_AUTH_CACHE_DIR
Attila Fazekasece6a332012-11-29 14:19:41 +0100217
218 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} filter:keystoneauth use
219 iniuncomment ${SWIFT_CONFIG_PROXY_SERVER} filter:keystoneauth operator_roles
220 iniset ${SWIFT_CONFIG_PROXY_SERVER} filter:keystoneauth operator_roles "Member, admin"
221
222 if is_service_enabled swift3; then
223 cat <<EOF >>${SWIFT_CONFIG_PROXY_SERVER}
224# NOTE(chmou): s3token middleware is not updated yet to use only
225# username and password.
226[filter:s3token]
227paste.filter_factory = keystone.middleware.s3_token:filter_factory
228auth_port = ${KEYSTONE_AUTH_PORT}
229auth_host = ${KEYSTONE_AUTH_HOST}
230auth_protocol = ${KEYSTONE_AUTH_PROTOCOL}
231auth_token = ${SERVICE_TOKEN}
232admin_token = ${SERVICE_TOKEN}
233
234[filter:swift3]
235use = egg:swift3#swift3
236EOF
237 fi
238
239 cp ${SWIFT_DIR}/etc/swift.conf-sample ${SWIFT_CONFIG_DIR}/swift.conf
240 iniset ${SWIFT_CONFIG_DIR}/swift.conf swift-hash swift_hash_path_suffix ${SWIFT_HASH}
241
242 # This function generates an object/account/proxy configuration
243 # emulating 4 nodes on different ports
244 function generate_swift_config() {
245 local swift_node_config=$1
246 local node_id=$2
247 local bind_port=$3
248
249 log_facility=$[ node_id - 1 ]
250 node_path=${SWIFT_DATA_DIR}/${node_number}
251
252 iniuncomment ${swift_node_config} DEFAULT user
253 iniset ${swift_node_config} DEFAULT user ${USER}
254
255 iniuncomment ${swift_node_config} DEFAULT bind_port
256 iniset ${swift_node_config} DEFAULT bind_port ${bind_port}
257
258 iniuncomment ${swift_node_config} DEFAULT swift_dir
259 iniset ${swift_node_config} DEFAULT swift_dir ${SWIFT_CONFIG_DIR}
260
261 iniuncomment ${swift_node_config} DEFAULT devices
262 iniset ${swift_node_config} DEFAULT devices ${node_path}
263
264 iniuncomment ${swift_node_config} DEFAULT log_facility
265 iniset ${swift_node_config} DEFAULT log_facility LOG_LOCAL${log_facility}
266
267 iniuncomment ${swift_node_config} DEFAULT mount_check
268 iniset ${swift_node_config} DEFAULT mount_check false
269
270 iniuncomment ${swift_node_config} ${server_type}-replicator vm_test_mode
271 iniset ${swift_node_config} ${server_type}-replicator vm_test_mode yes
272 }
273
274 for node_number in ${SWIFT_REPLICAS_SEQ}; do
275 swift_node_config=${SWIFT_CONFIG_DIR}/object-server/${node_number}.conf
276 cp ${SWIFT_DIR}/etc/object-server.conf-sample ${swift_node_config}
277 generate_swift_config ${swift_node_config} ${node_number} $[OBJECT_PORT_BASE + 10 * (node_number - 1)]
278
279 swift_node_config=${SWIFT_CONFIG_DIR}/container-server/${node_number}.conf
280 cp ${SWIFT_DIR}/etc/container-server.conf-sample ${swift_node_config}
281 generate_swift_config ${swift_node_config} ${node_number} $[CONTAINER_PORT_BASE + 10 * (node_number - 1)]
Attila Fazekas83e10952012-11-30 23:28:07 +0100282 iniuncomment ${swift_node_config} app:container-server allow_versions
283 iniset ${swift_node_config} app:container-server allow_versions "true"
Attila Fazekasece6a332012-11-29 14:19:41 +0100284
285 swift_node_config=${SWIFT_CONFIG_DIR}/account-server/${node_number}.conf
286 cp ${SWIFT_DIR}/etc/account-server.conf-sample ${swift_node_config}
287 generate_swift_config ${swift_node_config} ${node_number} $[ACCOUNT_PORT_BASE + 10 * (node_number - 1)]
288 done
289
290 swift_log_dir=${SWIFT_DATA_DIR}/logs
291 rm -rf ${swift_log_dir}
292 mkdir -p ${swift_log_dir}/hourly
293 sudo chown -R $USER:adm ${swift_log_dir}
294 sed "s,%SWIFT_LOGDIR%,${swift_log_dir}," $FILES/swift/rsyslog.conf | sudo \
295 tee /etc/rsyslog.d/10-swift.conf
296
297}
298
299# configure_swiftclient() - Set config files, create data dirs, etc
300function configure_swiftclient() {
301 setup_develop $SWIFTCLIENT_DIR
302}
303
304# init_swift() - Initialize rings
305function init_swift() {
306 local node_number
307 # Make sure to kill all swift processes first
308 swift-init all stop || true
309
310 # This is where we create three different rings for swift with
311 # different object servers binding on different ports.
312 pushd ${SWIFT_CONFIG_DIR} >/dev/null && {
313
314 rm -f *.builder *.ring.gz backups/*.builder backups/*.ring.gz
315
316 swift-ring-builder object.builder create ${SWIFT_PARTITION_POWER_SIZE} ${SWIFT_REPLICAS} 1
317 swift-ring-builder container.builder create ${SWIFT_PARTITION_POWER_SIZE} ${SWIFT_REPLICAS} 1
318 swift-ring-builder account.builder create ${SWIFT_PARTITION_POWER_SIZE} ${SWIFT_REPLICAS} 1
319
320 for node_number in ${SWIFT_REPLICAS_SEQ}; do
321 swift-ring-builder object.builder add z${node_number}-127.0.0.1:$[OBJECT_PORT_BASE + 10 * (node_number - 1)]/sdb1 1
322 swift-ring-builder container.builder add z${node_number}-127.0.0.1:$[CONTAINER_PORT_BASE + 10 * (node_number - 1)]/sdb1 1
323 swift-ring-builder account.builder add z${node_number}-127.0.0.1:$[ACCOUNT_PORT_BASE + 10 * (node_number - 1)]/sdb1 1
324 done
325 swift-ring-builder object.builder rebalance
326 swift-ring-builder container.builder rebalance
327 swift-ring-builder account.builder rebalance
328 } && popd >/dev/null
329
Dean Troyer64ab7742012-12-28 15:38:28 -0600330 # Create cache dir
331 sudo mkdir -p $SWIFT_AUTH_CACHE_DIR
332 sudo chown `whoami` $SWIFT_AUTH_CACHE_DIR
333 rm -f $SWIFT_AUTH_CACHE_DIR/*
Attila Fazekasece6a332012-11-29 14:19:41 +0100334}
335
336function install_swift() {
337 git_clone $SWIFT_REPO $SWIFT_DIR $SWIFT_BRANCH
338}
339
340function install_swiftclient() {
341 git_clone $SWIFTCLIENT_REPO $SWIFTCLIENT_DIR $SWIFTCLIENT_BRANCH
342}
343
344
345# start_swift() - Start running processes, including screen
346function start_swift() {
347 # (re)start rsyslog
348 restart_service rsyslog
349 # Start rsync
Vincent Untzc18b9652012-12-04 12:36:34 +0100350 if is_ubuntu; then
Attila Fazekasece6a332012-11-29 14:19:41 +0100351 sudo /etc/init.d/rsync restart || :
352 else
353 sudo systemctl start xinetd.service
354 fi
355
356 # First spawn all the swift services then kill the
357 # proxy service so we can run it in foreground in screen.
358 # ``swift-init ... {stop|restart}`` exits with '1' if no servers are running,
359 # ignore it just in case
360 swift-init all restart || true
361 swift-init proxy stop || true
362 screen_it swift "cd $SWIFT_DIR && $SWIFT_DIR/bin/swift-proxy-server ${SWIFT_CONFIG_DIR}/proxy-server.conf -v"
363}
364
365# stop_swift() - Stop running processes (non-screen)
366function stop_swift() {
367 # screen normally killed by unstack.sh
368 swift-init all stop || true
369}
370
371# Restore xtrace
372$XTRACE