Difference between revisions of "Trove/Blueprints/Trove-v1-MySQL-Replication"
< Trove
Doug Shelley (talk | contribs) (Created page with "== Description == Describe the purpose of the enhancement == Justification/Benefits == * What is the driving force behind this change? * Does it allow for great flexibility...") |
Doug Shelley (talk | contribs) (→Description) |
||
| Line 1: | Line 1: | ||
== Description == | == Description == | ||
| − | + | Providing support for the various replication use cases is critical for use of Trove in production. This will describe the various use cases and related requirements and then propose a scoping for an initial V1 implementation for MySQL. | |
== Justification/Benefits == | == Justification/Benefits == | ||
Revision as of 22:07, 4 March 2014
Contents
Description
Providing support for the various replication use cases is critical for use of Trove in production. This will describe the various use cases and related requirements and then propose a scoping for an initial V1 implementation for MySQL.
Justification/Benefits
- What is the driving force behind this change?
- Does it allow for great flexibility? Stability? Security?
Impacts
Configuration
- Does this impact any configuration files? If so, which ones?
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
- Does this change any API that an end-user has access to?
- Are there any exceptions in terms of consistency with other APIs?
Internal API
- Does this change any internal messages between API and Task Manager or Task Manager to Guest
Guest Agent
- Does this change behavior on the Guest Agent? If so, is it backwards compatible with API and Task Manager?
