API for promoting a backend to master

Registered by Alex Meade on 2016-04-23

If backend A is replicating to backend B and we failover to backend B because A has been destroyed, we need a mechanism to say B is the new master so we can begin replicating to C. Currently this is done by hacking the DB, we should have an admin API to trigger this.

Blueprint information

Status:
Not started
Approver:
Sean McGinnis
Priority:
Medium
Drafter:
Alex Meade
Direction:
Approved
Assignee:
Jon Bernard
Definition:
Approved
Series goal:
Accepted for queens
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/replication-backend-promotion,n,z

Addressed by: https://review.openstack.org/312591
    Promote backend after failover (cheesecake)

Addressed by: https://review.openstack.org/408830
    Update cheesecake promotion specification

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.