Difference between revisions of "Trove/Blueprints/vertica-db-support"

Latest revision as of 05:43, 29 January 2015

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.

@@ Line 1: / Line 1: @@
 == Description ==
-Include vertica analytical database in trove datastores.
+Add Vertica analytical database in trove datastores.
 == Use Case Requirements ==
-While the specific details of each datastore need to be investigated against this list, these are seen as the use-cases that would motivate the replication feature:
+The implementation would provide additional feature to trove to support new datastore Vertica and specific operations for this datastore.
-A. TEST HEADING
+Described operations:
-# bullet 1
-# bullet 2
+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 ==
-Phase I implementation, targeted for the Juno release, will implement Use Case A core functionality and the MySql datastore replication support. Replication support for other datastores beyond MySQL are beyond the scope of this blueprint and will be covered elsewhere.
+Implement all sections of Use Case Requirements.
 == Impacts ==
-This change would impact all components of Trove.
+This change would impact mainly guestagent, as new datastore will be added.
 === Configuration ===
-There should be no changes to configuration files required.
+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?
+This change has no impact on existing database tables.
-* Are the changes forward and backward compatible?
-* Be sure to include the expected migration process
 === Public API ===
-* Does this change any API that an end-user has access to?
+No API calls are altered. Response to API calls would be similar for Vertica datastore.
-* Are there any exceptions in terms of consistency with other APIs?
-The addition of a replication feature would required changes to the trove command and corresponding APIs.  At a minimum, there would need to be APIs to add a slave to a master, and to remove a slave from a master.  Additionally, there may be changes to how a potential master site is created.
 === Internal API ===
-* Does this change any internal messages between API and Task Manager or Task Manager to Guest
+No change
-There would be API changes at every level to support replication.
 === Guest Agent ===
-* Does this change behavior on the Guest Agent? If so, is it backwards compatible with API and Task Manager?
+Vertica datastore specific guestagent code needs to be added.
+It will be compatible with the existing API structure and taskmanager.
-The guest agent would require support for the new replication operations, but backward compatibility should be maintained.