The trouble with torrents

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



So, Fedora 29 Beta is out the door and mostly that went very smoothly as
always. With one exception: torrents.

Right now we are (were) using the last opensource version of
'bittorrent' python client to seed our torrents. However, I noticed
yesterday that it is no longer working. It's not just one bug, but a
number of them judging by the different tracebacks it's spewing.

As a stopgap to get Beta happy I installed and ran rtorrent on torrent01
in a tmux session to seed our beta torrents, but thats a curses app
thats not automateable.

So, we really need to figure a way forward here.

1. Get permission from Council/FESCo to drop torrents (To make that case
we need to show some graphs that not many people are using torrents
anymore).

2. Move our torrents to amazon cloudfront. This should be doable, but
means we are using a non free service so it would make me sad.

3. Try and find a open source seeding app that is manageable from
ansible/config files. (Good luck, they are all old, or gui only, etc).

4. Just use rtorrent in tmux to seed everything and have to manually
start/stop it when you add/remove any.

5. Some other clever idea someone has.

We can discuss this in meeting tomorrow, but I figured I would start a
thread here too.

kevin


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux