RETIRED, Application Data Protection as a Service in OpenStack
| devstack | ||
| doc | ||
| etc | ||
| smaug | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| babel.cfg | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| openstack-common.conf | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Smaug
Application Data Protection as a Service for OpenStack
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
Links
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/smaug
- Source: http://git.openstack.org/cgit/openstack/smaug
- Bugs: http://bugs.launchpad.net/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