Koji 2.0 Storage Suggestion and Request for Public Roadmap
Hello all,
There was a conversation about docker base image building today
that included folks from Fedora, CentOS and the Project Atomic teams
and we somehow got on the topic of static object storage. I can't
remember who actually proposed the idea originally but I *think* it
was either Colin Walters or Ian McLeod (if I've incorrectly assigned
credit/blame, apologies).
Anyhoo, the idea is to use a static object store back end such as
Swift/S3/CephRADOS/etc in place of a traditional filesystem (NFS) for
the storage of build artifacts in Koji 2. This would ultimately offer
a more easily scaled storage tier to Koji and also caters nicely to
the concept of immutable build artifacts. If it was made pluggable, it
would also offer a lot more options to koji admins on the storage
setup.
I was hoping for feedback on that, but I was also wanting to request a
public roadmap for Koji 2 (does one exist?). Is there a code
branch/repo somewhere where Koji 2 work is happening?
I look forward to feedback/discussion.
Thank you,
-AdamM