F20 image building plan and decisions we need to make
I had planned to post this earlier in the week, but... well. Not a good
week. So here we go.
We'd like to get the the automatic service for uploading images to EC2 and
alt.fedoraproject.org) running, and ideally also anaconda-based image
generation. In order to do that, we need to decide and to do a number of
things:
1. We need a process for non-scratch builds of AMIs
a. We'll get the arch/name bug fixed, but in the meantime, I suggest we
go ahead with the uglier approach of creating a package in koji with the
arch in the name, as a temporary workaround.
b. We need to configure the expiration policy for these builds. I suggest
we choose three weeks for weekly builds, or one week for nightlies.
Alpha, Beta, and Final release images should be kept forever. If that
means we need different koji packages for the automatically-generated
weekly or nightly builds, let's do that.
2. We need a place to run the cron job that runs the scripted automatic builds
- and someone to put those scripts into that place
3. We need a system to run the uploader service -- ideally a new isolated
system for security, as this will need to hold EC2 credentials and have
write access to alt.fedoraproject.org.
4. We need to finalize the Oz/ImageFactory integration.
- timeline, work to be done?
- how to deal with possible oz bugs and fixes in production
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>