Project

General

Profile

Actions

Task #2400

closed

Determine the necessary changes to use current Chronosync as dependency

Added by Vince Lehman about 9 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
01/20/2015
Due date:
% Done:

100%

Estimated time:

Description

Currently, NLSR uses its own forked and modified version of Chronosync.
Updates and bug fixes to Chronosync are not being incorporated or tracked.

Ideally, NLSR should use Chronosync directly and not maintain its own version.

This task should determine the effort and changes necessary to stop using a forked version of Chronosync and instead use the main repo.


Related issues 5 (0 open5 closed)

Related to NLSR - Task #2375: Jenkins fails build during OpenSSL linkingClosed01/13/2015

Actions
Related to NLSR - Bug #4513: Need to use a fixed session name for ChronoSync socketsClosed02/20/2018

Actions
Blocks NLSR - Task #1523: Use separate name prefix and sequence number for each LSA type in ChronoSyncClosedAshlesh Gawande04/21/201405/26/2017

Actions
Blocked by ChronoSync - Bug #3990: ERROR: Interest size exceeds maximum limit on exclude interest for large topologiesClosedAshlesh Gawande03/09/2017

Actions
Blocked by ChronoSync - Feature #4032: Allow applications to set sequence numberClosedAshlesh Gawande04/04/2017

Actions
Actions #1

Updated by Vince Lehman almost 9 years ago

  • Target version set to v0.5.0
Actions #2

Updated by Vince Lehman almost 8 years ago

  • Assignee deleted (Vince Lehman)
Actions #3

Updated by Ashlesh Gawande over 7 years ago

  • Blocks Task #1523: Use separate name prefix and sequence number for each LSA type in ChronoSync added
Actions #4

Updated by Ashlesh Gawande over 7 years ago

  • Related to Task #2375: Jenkins fails build during OpenSSL linking added
Actions #5

Updated by Ashlesh Gawande over 7 years ago

Will need to remove openssl dependency after this is completed.

Actions #6

Updated by Ashlesh Gawande over 7 years ago

NLSR maintains its own sequence numbers (https://redmine.named-data.net/projects/nlsr/wiki/Handles_synchronization_logic_of_NLSR_LSDB_updates).

Chronosync does not to allow applications to set sequence numbers and maintains its own sequence numbers.

Making Chronosync a dependency is very simple and straightforward if a small API change can be made in Chronosync to allow setting of sequence numbers in publishData methods.

Apart from benefits mentioned in description we can rid NLSR of two dependencies: openssl and protobuf.

Actions #7

Updated by Ashlesh Gawande about 7 years ago

  • Blocked by Bug #3990: ERROR: Interest size exceeds maximum limit on exclude interest for large topologies added
Actions #8

Updated by Ashlesh Gawande almost 7 years ago

  • Blocked by Feature #4032: Allow applications to set sequence number added
Actions #9

Updated by Ashlesh Gawande almost 7 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to Ashlesh Gawande
  • Target version changed from v0.5.0 to v0.4.0
  • % Done changed from 0 to 80
Actions #10

Updated by Ashlesh Gawande almost 7 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 80 to 100
Actions #11

Updated by Ashlesh Gawande almost 7 years ago

Need to remove nsync from tests-integrated/wscript and also from tests/wscript.

Also need to update NLSR developer's guide.

Need to update https://github.com/named-data/NLSR/blob/master/COPYING.md

Also rename method onNSyncUpdate.

Version doesn't seem correct: https://github.com/named-data/NLSR/blob/3e105a0493ee6c204226cfc16ae6ba6c3e52b059/wscript#L72

Actions #12

Updated by Ashlesh Gawande almost 7 years ago

  • Status changed from Feedback to Closed

Will update the dev guide, if necessary, after: https://gerrit.named-data.net/#/c/3943/

Actions #13

Updated by Ashlesh Gawande about 6 years ago

  • Related to Bug #4513: Need to use a fixed session name for ChronoSync sockets added
Actions

Also available in: Atom PDF