Project

General

Profile

Story #6721

Update replication and replication auditing for v2 API changes

Added by Skye Roseboom almost 10 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Chris Jones
Category:
d1_replication
Target version:
CCI-2.0.0
Start date:
2015-05-28
Due date:
% Done:

100%

Story Points:
Sprint:

Description

Encapsulate use of V1 or V2 REST API calls when requesting and processing replication and replication auditing.

Subtasks

Task #7134: Update replication component to encapsulate use of V1, V2 replication API and communication depending on MN supportClosedChris Jones

Task #7135: Update replication auditing component to encapsulate use of V1, V2 replication API and communication depending on MN supportClosedChris Jones

Related issues

Related to CN REST - Story #7216: Review replication auditor implementation and update for V2 support Closed 2015-06-16

History

#1 Updated by Chris Jones over 9 years ago

Just a note: Replication will also need to be aware of the V1 or V2 support level for the authoritative node. If the node supports only V1, then replication needs to treat the CN as authoritative for the system metadata of the object being replicated. If it supports V2, then the MN is authoritative.

#2 Updated by Dave Vieglais over 9 years ago

  • Target version changed from CCI-2.0.0 to CCI-2.0-RC1

#3 Updated by Dave Vieglais over 9 years ago

  • Related to Story #7216: Review replication auditor implementation and update for V2 support added

#4 Updated by Dave Vieglais over 9 years ago

  • Target version changed from CCI-2.0-RC1 to CCI-2.0.0

#5 Updated by Chris Jones over 9 years ago

  • Assignee changed from Skye Roseboom to Chris Jones

#6 Updated by Skye Roseboom almost 9 years ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

sub-tasks are complete.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)