Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support Bittorrent-like replication #6890

Closed
luisdavim opened this issue Feb 4, 2019 · 8 comments
Closed

Support Bittorrent-like replication #6890

luisdavim opened this issue Feb 4, 2019 · 8 comments
Assignees
@xaleeks
Labels
area/P2P-Distribution area/performance area/replication kind/requirement New feature or idea on top of harbor

Comments

@luisdavim
Copy link

If we have a lot of geographically distributed harbor instances it would be nice to have support for Bittorrent to synchronise images across them so that we could push an image to one of the instances and it would start seeding that image to the other instances, each instance that has that image becomes a seeder for it.
@ghost
Copy link

ghost commented Feb 8, 2019

There is work being done to integrate Dragonfly + Harbor (see this for more details). @steven-zou can provide some more context.

@luisdavim
Copy link
Author

That seems related to image pulling, not registry replication. Am I wrong?

@steven-zou
Copy link
Contributor

@luisdavim

Right, that integration covers the image distributions via P2P protocol. For pushing case, the Harbor image replication can help to geographically sync images among different registry instances on top of normal way. Not support p2p way yet. Do you have some good idea of supporting the p2p way in image replication?

@steven-zou steven-zou self-assigned this Feb 11, 2019
@luisdavim
Copy link
Author

The scenario that I'm thinking about is one where we'd have many k8s clusrters and an Harbor instance on each of them, I would like to be able to push my images to one central Harbor instance, that could be used as a torrent tracker and the other ones would sync using p2p.

@steven-zou
Copy link
Contributor

The scenario that I'm thinking about is one where we'd have many k8s clusrters and an Harbor instance on each of them, I would like to be able to push my images to one central Harbor instance, that could be used as a torrent tracker and the other ones would sync using p2p.

@luisdavim

The scenario you mentioned can be covered by the image replication feature of Harbor now. The replication feature is built on top of registry API, not by a P2P way.

For the P2P approach in the image sync/replication feature, do you have a good idea and are you willing to do some contributions on that feature?

@reasonerjt reasonerjt added the kind/requirement New feature or idea on top of harbor label Apr 11, 2019
@steven-zou steven-zou assigned xaleeks and unassigned steven-zou Aug 20, 2019
@steven-zou
Copy link
Contributor

Transfer all the requirements to @xaleeks for tracking.

@xaleeks
Copy link
Contributor

xaleeks commented Dec 6, 2019

@luisdavim reviving this, we are tackling it in the upcoming release and have several community members engaged. Ping us here if you are interested in discussing or contributing.

@xaleeks xaleeks changed the title Support Bittorrent replication Support Bittorrent-like replication Apr 22, 2020
@xaleeks
Copy link
Contributor

xaleeks commented May 26, 2020

we're tracking that work here #10875

@xaleeks xaleeks closed this as completed May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xaleeks xaleeks

Labels
area/P2P-Distribution area/performance area/replication kind/requirement New feature or idea on top of harbor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@luisdavim @reasonerjt @steven-zou @xaleeks