_____________________________
From: Gordan Bobic <[email protected]>
Sent: lørdag, marts 26, 2016 3:30 PM
Subject: Re: [RedSleeve-Users] ?==?utf-8?q? Raspberry Pi 3
To: <[email protected]>
> £600 here in UK from here:
> https://www.xcase.co.uk/gigabyte-server-boards/gigabyte-mp30-ar0-with-appliedmicror-x-gene1r-processor.html
>
Ouch, that is some money, after all.
>Which brings me to the next point. One of the big advantages of the
>MP30-AR0 is that it takes ECC RAM. That means we can have more
>confidence in the packages built on it. What I was hoping we could
>arrange is having a reproducible Koji docker container build (well, a
>method of making a rootfs with all the required configuration, making a
>docker image from a tarball is trivial). Then I could just put your
>docker Koji container on the new server, and make a few builder
>containers to do the actual building. This would still be a lot faster
>than using older machines with a single core and 512MB of RAM.
Sound like a good plan. Note that it is only the builders that needs so run on
ARM architecture. The main controller and the web frontend can run on any
architecture (read - cheaper x86_64)
>As an upshot, you wouldn't have to run anything - once you have put
>together a src.rpm, you could just throw the package at the koji
>container running here (my server will be running 24/7 anyway), and
>it'll take care of it.
True. I use and even better solution - well the same that Fedoraproject, CentOS
etc use. I have stored all .spec files in git and just pull the spec file from
git. So your koji and my koji can pull from the same git server. We could store
it all at GitHub. I just prefer to have a private git repository since there
could be stored sensitive data after all (NSA go.....)
>If you have instructions I could follow to create reproducible results
>running koji on an armv5tel machine so that I could containerize it on
>the new server, that would be quite awesome.
Sure, the documentation is (still) located at
http://www.saltbaek.dk/dokuwiki/There are still some bits and pieces missing -
for exampel i am so lazy i want a web gui for creating ssl user certificates
instead of i need to ssh into the machine for this.And i am missing git hook
script that starts rebuilding a package when git repo is updatedAlso a
verification script that checks that all packages in git have a build profile
in koji.Other than that it has been running for 3-4 weeks now 24/7 unless when
the builders crash - the Banana Pi M3 is the worst (do to poor design).
>Note that I don't mean to discourage you from running your own, I just
>think having it as a cetrally available resource for registered package
>maintainers would be beneficial. Having extra available builders won't
>hurt (even if an extra SheevaPlug or similar probably won't make a
>noticeable dent in the workload compared to the MP30). Sure, I dont get
>discouraged at all - i am not an old fashioned system administrator that lives
>in my own little kingdom ;)
But maybe I should offer running the sigul server. It would be good security
having the signing server apart from the build system - again this can run on
any type hardware/OS.
>I am not sure how that works, but we have had network TFTP boot
>capability in u-boot since forever so I am not entirely sure what PXE
>would bring to the table that we don't already have... Ok i have not tried
>that. And that must be the same as PXE. PXE code AFAIK does nothing other than
>load the network stack and boot on tftp. Same as the Anaconda installer can
>and I guess that feature is build into uboot. The most effective in a
>classroom would be booting from tftp insted of the teacher having to maintain
>many SD-cards.
>Anyway, which of the above machines would you like? GuruPlug has been
>claimed, the others are available.
I am currently on Easter vacation but i am back tomorrow evening and then i
will have the answer on that. But anything easy to configure with 1gb RAM,
wifi/ethernet build-in and if possible SATA interface :)
Btw - can i get [email protected] as an alias/forward to
[email protected]
BRBjarne
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
