Open Stack

https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API#REPLICATION

I have updated the wiki page to reflect the current proposal for
replication verbiage with some explanation of the choices.  I would like to
open discussion here regarding that verbiage.  Without completely
duplicating everything I just wrote in the wiki here are the proposed words
that could be used to describe replication between two datastore instances
of the same type.  Please take a moment to consider them and let me know
what you think.  I welcome all feedback.

replicates_from:  This term will be used in an instance that is a slave of
another instance. It is a clear indicator that it is a slave of another
instance.

replicates_to: This term will be used in an instance that has slaves of
itself. It is a clear indicator that it is a master of one or more
instances.

writable: This term will be used in an instance to indicate whether it is
intended to be used for writes. As replication is used commonly to scale
read operations it is very common to have a read-only slave in many
datastore types. It is beneficial to the user to be able to see this
information when viewing the instance details via the api.

The intention here is to:
1.  have a clearly defined replication contract between instances.
2.  allow users to create a topology map simply by querying the api for
details of instances linked in the replication contracts
3.  allow the greatest level of flexibility for users when replicating
their data so that Trove doesn't prescribe how they should make use of
replication.

I also think there is value in documenting common replication topologies
per datastore type with example replication contracts and/or steps to
recreate them in our api documentation.  There are currently no examples of
this yet

e.g. To create multi-master replication in mysql...

As previously stated I welcome all feedback and would love input.

Regards,

Daniel Salinas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140205/30e1f10d/attachment.html>