zengchen 968db961de Optimize time trigger: use instance of time format instead of class itself
Optimize time trigger in several aspects. This patch is the fourth
phase, which will use an instance of time format in time trigger
instead of class.

Change-Id: I9f7bff41d4b42a7f38e2d7dae17bbd3ba57dd736
Closes-Bug: #1611232
2016-11-22 14:22:35 +08:00
2016-09-30 04:27:39 +08:00
2016-11-10 07:52:36 +00:00
2016-08-18 22:55:34 +08:00
2016-10-31 08:50:43 +00:00
2016-08-18 22:55:34 +08:00
2015-11-08 13:35:36 +02:00
2016-08-18 22:55:34 +08:00
2015-11-08 13:35:36 +02:00
2016-08-18 22:55:34 +08:00
2016-08-18 22:55:34 +08:00
2015-11-08 13:35:36 +02:00
2016-08-18 22:55:34 +08:00
2016-11-16 16:41:45 +02:00
2016-11-16 10:29:42 +02:00

Karbor

Application Data Protection as a Service for OpenStack

Karbor

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

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
Description
RETIRED, Application Data Protection as a Service in OpenStack
Readme 26 MiB