Difference between revisions of "Trove/Blueprints/vertica-db-support"
< Trove
(→Impacts) |
(→Use Case Requirements) |
||
| Line 3: | Line 3: | ||
== Use Case Requirements == | == Use Case Requirements == | ||
| − | + | Following are the details: | |
| − | A. | + | A. Common database operations: |
| − | # | + | # Database : create, list, delete |
| − | # | + | # User : create, list, delete |
| + | # Revoke, grant | ||
| + | |||
| + | B. back-up and restore functionality for vertica datastore. | ||
== Scope == | == Scope == | ||
Revision as of 11:02, 24 April 2014
Contents
Description
Include vertica analytical database in trove datastores.
Use Case Requirements
Following are the details:
A. Common database operations:
- Database : create, list, delete
- User : create, list, delete
- Revoke, grant
B. 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
- Does this impact any existing tables? If so, which ones?
- Are the changes forward and backward compatible?
- Be sure to include the expected migration process
Public API
No API calls are altered. Responce to API calls are similar for vertica Datastore.
Internal API
No change
Guest Agent
Vertica datastore specific guestagent code needs to be added.
