b3f3e0c44c
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
22 lines
655 B
Plaintext
22 lines
655 B
Plaintext
# This is a cross-platform list tracking distribution packages needed by tests;
|
|
# see http://docs.openstack.org/infra/bindep/ for additional information.
|
|
|
|
build-essential [platform:dpkg]
|
|
gcc [platform:rpm]
|
|
gettext
|
|
liberasurecode-dev [platform:dpkg]
|
|
liberasurecode-devel [platform:rpm]
|
|
libffi-dev [platform:dpkg]
|
|
libffi-devel [platform:rpm]
|
|
memcached
|
|
python-dev [platform:dpkg]
|
|
python-devel [platform:rpm]
|
|
rsync
|
|
xfsprogs
|
|
libssl-dev [platform:dpkg]
|
|
openssl-devel [platform:rpm]
|
|
|
|
# N.B. uwsgi-plugin-python is needed only for s2aio.sh start/stop for keystone
|
|
# so that we will be able to remove if devstack or devstack plugin installs it
|
|
uwsgi-plugin-python
|