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
On 09/17/2015 10:54 AM, Adam Miller wrote:
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).
Sorry for the slow reply. I've been really focused on content generator work lately.
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.
This is an interesting idea. I think it might be too far for 2.0, but I'll have a look at some of these tools.
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?
Not yet, but soon.
On Mon, Sep 28, 2015 at 12:18 PM, Mike McLean mikem@redhat.com wrote:
On 09/17/2015 10:54 AM, Adam Miller wrote:
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).
Sorry for the slow reply. I've been really focused on content generator work lately.
No worries, that's great news though. I'm looking forward to content generators. :)
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.
This is an interesting idea. I think it might be too far for 2.0, but I'll have a look at some of these tools.
No worries, just wanted to throw it out there.
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?
Not yet, but soon.
Awesome, thanks!
-AdamM
koji-devel mailing list koji-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/koji-devel
koji-devel@lists.fedorahosted.org
-
Adam Miller -
Mike McLean