RETIRED, Application Data Protection as a Service in OpenStack
Go to file
zengchen 0c01e63cb0 authentication fails by keystonemiddleware
In order to pass througth the authentication of keystonemiddleware, I add a function "create_smaug_accounts" to create an account in Keystone in the plugin.sh.
There are 4 steps in "create_smaug_accounts" :
1. create a user "smaug".
2. bind the user with the project "service" and grant the role "service" to the user.
3. create a service "smaug".
4. create an endpoint.

Change-Id: I7644e568a8912f48e54b15cf897afe67a81c2e4a
Closes-Bug: #1526638
2015-12-17 10:48:04 +08:00
devstack authentication fails by keystonemiddleware 2015-12-17 10:48:04 +08:00
doc Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
etc Initial devstack script 2015-12-09 09:33:27 +02:00
smaug basic API service 2015-12-08 18:55:43 +08:00
.coveragerc Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
.gitignore Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
.gitreview Added .gitreview 2015-11-05 08:28:05 +00:00
.mailmap Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
.testr.conf Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
HACKING.rst Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
LICENSE Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
MANIFEST.in Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
README.rst Resize project logo images 2015-11-08 15:45:25 +02:00
babel.cfg Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
openstack-common.conf Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
requirements.txt basic API service 2015-12-08 18:55:43 +08:00
setup.cfg basic API service 2015-12-08 18:55:43 +08:00
setup.py Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
test-requirements.txt Initial Cookiecutter Commit. 2015-11-08 13:35:36 +02:00
tox.ini basic API service 2015-12-08 18:55:43 +08:00

README.rst

Smaug

Application Data Protection as a Service for OpenStack

Smaug

Mission Statement

  • Formalize Application Data Protection in OpenStack (APIs, Services, Plugins, …)
  • Be able to protect Any Resource in OpenStack(as well as their dependencies)
  • Allow Diversity of vendor solutions, capabilities and implementations without compromising usability

Open Architecture

Design for multiple perspectives:

  • User : Protect App Deployment
    • Configure and manage custom protection plans on the deployed resources (topology, VMs, volumes, images, …)
  • Admin : Define Protectable Resources
    • Decide what plugins protect which resources, what is available for the user
    • Decide where users can protect their resources
  • Vendors : Standard API for protection products
    • Create plugins that implement Protection mechanisms for different OpenStack resources

Smaug

Features

Version 0.1

  • Resource API
  • Plan API
  • Bank API
  • Ledger API
  • Cross-resource dependencies

Limitations

  • Only 1 Bank plugin per Protection Plan
  • Automatic object discovery not supported