97ac081975
Each config option has limitation for type and value. In production code, oslo.conf can ensure user's input is valid, but in unit test, test methods can pass if we use method CONF.set_override without parameter enforce_type=True even we pass wrong type or wrong value to config option. This commit makes sure calling method CONF.set_override with enforce_type=True Change-Id: I2ec6f354e43ccbe5e9f0e3907d558673ac88c860 Closes-Bug: #1517839 |
||
---|---|---|
devstack | ||
doc | ||
etc | ||
karbor | ||
releasenotes/notes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Karbor |
Application Data Protection as a Service for OpenStack
Mission Statement
To protect the Data and Metadata that comprises an OpenStack-deployed Application against loss/damage (e.g. backup, replication) by providing a standard framework of APIs and services that allows vendors to provide plugins through a unified interface
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/karbor
- Source: http://git.openstack.org/cgit/openstack/karbor
- Bugs: http://bugs.launchpad.net/karbor
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