Difference between revisions of "Trove/Blueprints/vertica-db-support"
(→Use Case Requirements) |
(→Public API) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Description == | == Description == | ||
− | + | Add Vertica analytical database in trove datastores. | |
== Use Case Requirements == | == Use Case Requirements == | ||
− | The implementation would provide | + | The implementation would provide additional feature to trove to support new datastore Vertica and specific operations for this datastore. |
Described operations: | Described operations: | ||
− | A. Instance creation with | + | |
+ | A. Instance creation with Vertica datastore. | ||
B. Common database operations: | B. Common database operations: | ||
Line 13: | Line 14: | ||
# Revoke, grant user access | # Revoke, grant user access | ||
− | C. | + | C. Back-up and restore functionality for Vertica datastore. |
== Scope == | == Scope == | ||
Line 29: | Line 30: | ||
=== Public API === | === Public API === | ||
− | No API calls are altered. | + | No API calls are altered. Response to API calls would be similar for Vertica datastore. |
=== Internal API === | === Internal API === |
Latest revision as of 05:43, 29 January 2015
Contents
Description
Add Vertica analytical database in trove datastores.
Use Case Requirements
The implementation would provide additional feature to trove to support new datastore Vertica and specific operations for this datastore.
Described operations:
A. Instance creation with Vertica datastore.
B. Common database operations:
- Database : create, list, delete
- User : create, list, delete
- Revoke, grant user access
C. Back-up and restore functionality for Vertica datastore.
Scope
Implement all sections of Use Case Requirements.
Impacts
This change would impact mainly guestagent, as new datastore will be added.
Configuration
Configuration will be changed as per datastores. There is a proposed re-structuring for "ignoring users" as per datastore.
Database
This change has no impact on existing database tables.
Public API
No API calls are altered. Response to API calls would be similar for Vertica datastore.
Internal API
No change
Guest Agent
Vertica datastore specific guestagent code needs to be added. It will be compatible with the existing API structure and taskmanager.