Use p2p to distribute just built ISO between test servers
It looks as great idea to use p2p protocols for distribution purposes.
Researching such way shows the following:
- opentracker as tracker https:/
- aria2 for downloading an ISO
- Transmission daemon for seeding
- custom control applications written in python
Blueprint information
- Status:
- Complete
- Approver:
- Igor Shishkin
- Priority:
- Low
- Drafter:
- Igor Shishkin
- Direction:
- Approved
- Assignee:
- Igor Shishkin
- Definition:
- Approved
- Series goal:
- Accepted for 4.0.x
- Implementation:
-
Implemented
- Milestone target:
-
4.0
- Started by
- Igor Shishkin
- Completed by
- Mike Scherbakov
Related branches
Related bugs
Sprints
Whiteboard
It should be better to use transmission-daemon on clients to download ISO with custom python scripts controls when downloading is complete to return status to jenkins while transmission-daemon starts seeding file to other nodes.
This asynchronous behaviour look much better then using aria2c because it needs to detach when downloading is complete what brings other nodes to lose peers.
Application to start seeding to peers https:/
Server side is already implemented. Jenkins ISO building job is already start initial seed for every ISO. On this week is planned to start downloading with torrents.
mihgen - Igor, what's the current status on this? Do you still need any infrastructure? Please write email announcing this feature when it's ready.
No, it's almost ready, server starts seed is already working and accepts new ISO. I waiting for release to setup jenkins to download these ISO's over p2p.
Yesterday Jenkins jobs for 4.0 building was updated to generate .torrent files and set link to them in build description.
