OpenStack Database As A Service (Trove)
4eef8d9a70
We'd like to enable the backups that are taken and stored as files in Swift, to be encrypted. We'll add some new config flags, to mark whether or not encryption is enabled. At this point, the encryption key will also be stored as a config value. When configured to encrypt, the whole process will be streamed to/from Swift, doing backup -> zip -> encrypt -> Swift and Swift -> decrypt -> unzip -> restore all during streaming, so we don't use up more disk space than needed. Blueprint: encrypted-backups Change-Id: I05447306f4249bfd8e02de7b008ebda3387b2fbd |
||
---|---|---|
bin | ||
contrib/dbaas-mycnf | ||
development | ||
etc | ||
reddwarf | ||
rsdns | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
LICENSE | ||
MANIFEST.in | ||
next_steps.txt | ||
openstack-common.conf | ||
README | ||
requirements.txt | ||
run_tests.py | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Reddwarf -------- Reddwarf is Database as a Service for Open Stack. To run all tests and PEP8, run tox, like so: $ tox To quickly run the tests for Python 2.7, run: $ tox -epy27 To generate a coverage report,run: $ tox -ecover (note: on some boxes, the results may not be accurate unless you run it twice) If you'd like to start up a fake Reddwarf API daemon for integration testing with your own tool, run: $ ./bin/start_server Stop the server with: $ ./bin/stop_server