#35 External need: Automatic Image Upload
Closed None Opened 5 years ago by mattdm.

'''Summary:''' Whenever an image is built, it is automatically uploaded to our cloud provider targets (EC2, etc.) and to the fedora ftp site (and possibly mirrors if we can convince mirror admins to drink from that firehose)

'''Importance:''' vital (current process where rel eng does it by hand will not scale)

'''Timeframe:''' whenever we can get it / this adds value whenever it happens

'''Fedora Sub-Project/SIG:''' Release Engineering, possibly Infrastructure for resources

'''Cloud SIG owner:''' TBD (note summer intern may help with that, if it is not too late)

Possibly we file this as a change. Also see previous intern's initial work: https://git.fedorahosted.org/cgit/cloud-image-service.git/

We need someone to help drive this, and to assist rel-eng and infrastructure in whatever they need.


Here's an (out of date) web page with an early version of the plan: https://fedoraproject.org/wiki/Features/FirstClassCloudImages/KojiPlan

Note, particularly, that in addition to uploading images, the plan needs some way of keeping track of which images were uploaded to each location, including build metadata (source, kickstart, some kinda label) and after-the-fact metadata (test results, labeling as release candidate or release, etc.).

Closing this ticket as part of trac clean up process. If you want to reopen, please reopen it after we move to pagure.io as atomic-wg.

Login to comment on this ticket.

Metadata