Project

General

Profile

Actions

Task #1809

open

RepoSync

Added by Weiqi Shi over 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/29/2014
Due date:
% Done:

0%

Estimated time:

Description

Repo should be able to sync with each other. Currently the design is based on ChronoSync and is action based synchronization.

Actions #1

Updated by Weiqi Shi over 9 years ago

In current summit, repo sync will start when repo is set up. In next commit, a sync handle command should be invited to instruct repo to start or stop sync process.
Besides, in next commit, a new database to record the current sync status and sync tree should also be added. Otherwise, if a repo died and restart, it will forget all the others status and propagate its data to the synchronized group.

Actions #2

Updated by Junxiao Shi almost 8 years ago

As pointed out on operators mailing list, the lack of repo sync prevents the replication of NDN testbed certificates and makes UCLA router the single point of failure on the NDN testbed.

What's the plan on completing this task?

Actions #3

Updated by Junxiao Shi over 7 years ago

20160630 conference call discussed this issue.

The existing design is RepoSync: Combined Action-Based and Data-Based Synchronization Model in Named Data Network which needs to be reviewed.

One concern before any implementation is that, the existing repo-ng implementation is of poor code quality.
We should decide whether to add new feature onto it, or rewrite it from ground up before adding new features.

Actions #4

Updated by Junxiao Shi over 7 years ago

20160719 call states that rewriting repo-ng would not be helpful because no implementation can do much better under the same constraints.

Actions

Also available in: Atom PDF