openstack/storlets
Code Issues Proposed changes
Files
2d0db2c8ee044f96fd3517c84f88a858e64fb8f7
storlets/doc/source/s2aio.rst
Eran Rom b3f3e0c44c Add start / stop to s2aio 
s2aio uses a loop back device over a local file
as Swift device. This device may get corrupted
when rebooting the host while swift is running.
Adding the start and stop helps mitigate the problem

Also, with the recent move to devstack as the
installation script for Swift and Keystone
starting the swift and keystone services
have changed. Again, the s2aio start helps
here.

Change-Id: I3e3884a1a04888be577fe4f92d471a65f6f5ce5b
2017-06-11 23:10:00 -07:00

1.2 KiB
Raw Blame History

s2aio

s2aio is a script that installs Swift (with Keystone) and Storlets all on one. The script allows to do the installation either on the host where it is invoked or in a Docker container.

To install on the host:

To install in a Docker container follow the same steps, replacing the last command with:

./s2aio.sh install dev docker

If you do not have Docker installed on your host, the above script will install it and set docker to use "vfs" as the docker storage driver (instead of the default "aufs" storage driver). If you already have Docker installed, you may need to change its storage driver to "vfs". The created Docker container runs yet another container. Running Docker in Docker may require the usage of the "vfs" storage device.

When installed on the host, the script can be used to start and stop all relevant services using:

./s2aio.sh stop

and

./s2aio.sh start

For the Swift data, the s2aio installation uses a loopback device over a .img file. When shutting down the host, the .img file may get corrupted. Thus, the above stop and start commands are useful when using s2aio.sh for in a long lived hosts that can get rebooted from time to time.