Difference between revisions of "Trove/trove-capabilities"
< Trove
m (→Datastore Capabilities) |
(→Datastore Capabilities) |
||
| Line 1: | Line 1: | ||
| − | = | + | =Overview= |
This proposal includes the ability to setup different capabilities for different datastore types. | This proposal includes the ability to setup different capabilities for different datastore types. | ||
| Line 5: | Line 5: | ||
this capability,an ephemeral volume would be created on server create. A datastore without | this capability,an ephemeral volume would be created on server create. A datastore without | ||
this capability (such as redis) would not create a volume. | this capability (such as redis) would not create a volume. | ||
| + | |||
| + | =Database Schema= | ||
| + | |||
| + | TDB | ||
| + | |||
| + | = API Changes = | ||
| + | |||
| + | TBD | ||
Revision as of 19:06, 23 January 2014
Overview
This proposal includes the ability to setup different capabilities for different datastore types.
An example capability would be "ephemeral_volume". As a result of a datastore having this capability,an ephemeral volume would be created on server create. A datastore without this capability (such as redis) would not create a volume.
Database Schema
TDB
API Changes
TBD
