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.

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

Publisher should create and populate torrents and their hashes. #19

Closed
linux-modder opened this issue May 10, 2018 · 0 comments
Closed

Comments

@linux-modder
Copy link

On the old infra our torrent script would create a series of torrents (one per ISO, minus source),

Using the k8s infra and then attempting to create the torrents from the non-k8s infra where final images are served from the path variations make for a failure of torrent generation.

The k8s infra should add as an operation of the publisher job the following (with relevant path changes)

repodir=/srv/Livecds/$2
for spin in CINN KDE LXDE LXQT MATE SOAS WORK XFCE; do
#for spin in CINN LXDE LXQT WORK SOAS XFCE; do
#for spin in SECURITY ; do 
#for spin in SOAS ; do
hash=$(grep $spin $repodir/CHECKSUM512-$2)
    transmission-create -c "ISO SHA512SUM: ${hash} " -s 2048 -p -t http://respins.fedorainfracloud.org:6969/announce -o $repodir/F$1-${spin}-x86_64-$2.torrent $repodir/F$1-${spin}-x86_64-$2.iso
    chmod +r $repodir/*.torrent

    echo "update opentracker whitelist for ${spin}"
    transmission-show $repodir/F$1-${spin}-x86_64-$2.torrent | awk '/Hash/{print $2 " - "}' >> $repodir/buildfile
    echo F$1-${spin}-x86_64-$2.iso >> $repodir/buildfile

These torrents and thier hashes (which are what presently fails when created on non k8s infra) are what is feed to the SIGs whitelisted tracker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants