Hi Gordan.
RSEL Koji maintainer? No problem. I choose EPEL since I assumed that you
guys had the OS dist process in place and EPEL looked unmaintained
(which I guessed right :-D).
I suggest that I set up a ghost system to evaluate if it can be used.
You can then switch if you want.
The requirements you asking about is that the (Koji-Hub/Koji-Web) or the
Koji-client(build slaves).
https://fedoraproject.org/wiki/Koji#Koji_Components
I run the Hub/Web on the same CO6 x86_64, 1CPU, 2GB RAM, 16GB Disk.
Does not look overloaded.
I would prefer to document how to set up a RSEL Koji. Then the setup can
be installed anywhere - Cloud, Private Cloud or like me on a ESXi.
BR,
Bjarne
On 09-04-2015 16:39, Gordan Bobic wrote:
For me the deciding factor is that my entire set of build scripts
took me less than an hour to write. I gave up on Koji documentation
after about an hour because there just seemed to be far too many
moving parts involved.
Fancy becoming a RSEL Koji maintainer? What are the resource
requirements (CPU, RAM, disk)? I could easily enough spin
something up and get you ssh access to it (<= 512MB DreamPlug,
1GB -> 4GB I could probably get my Arndale OCTA or Cornfed
machine up and running next weekend (I've had them gathering
dust for a year, could rather do with the extra motivation to
get them up and running), or if you need more than that,
anything up to a fairly beefy x86-64 VM could be provided
easily enough.
Let me know if you're interested. Maybe it's time to switch
to Koji, if what you are saying is correct. Even if you could
just comprehensively document the installation process for the
wiki, it would be really useful.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
