F20 image building plan and decisions we need to make

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 12 Jul 2013 14:05:48 -0400
Matthew Miller <mattdm at fedoraproject.org> wrote:

> 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.
As I have said to you privately I don't find that acceptable. the fix
should be fairly trivial.

> 
>    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.

we just need to work out the right koji-gc policy to write. 
    
> 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

it needs to all be put into ansible and credentials in ansible-private
the host would likely be releng03.phx2.fedoraproject.org

> 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.
it would also be releng03.phx2.fedoraproject.org

> 4. We need to finalize the Oz/ImageFactory integration.
> 
>    - timeline, work to be done?

https://fedoraproject.org/wiki/Releases/20/Schedule
we are due to branch F20 on August 6th I would say that is the deadline,
that will give us time to test and fix any issues before Alpha Change
deadline of August 20th, the fedora 20 schedule is insanely tight
however you have had since we branched off f19 to work on things.

>    - how to deal with possible oz bugs and fixes in production

We deal with them as we hit them, its a bit hard to plan

Dennis 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlHgbe4ACgkQkSxm47BaWff1wACdFSwzkxOg2LcokOPJ3tKjz7Xc
YHIAoJ2Ew3YZbxKEdxzX8lcSQ8EoCqEC
=bUMf
-----END PGP SIGNATURE-----