basic plan for two-week atomic images

[Dennis Gilmore]

On Friday, June 12, 2015 10:00:43 AM Adam Miller wrote:
> On Wed, May 27, 2015 at 11:37 AM, Adam Miller
> 
> <maxamillion at fedoraproject.org> wrote:
> > On Thu, May 21, 2015 at 4:46 PM, Matthew Miller
> > 
> > <mattdm at fedoraproject.org> wrote:
> >> On Thu, May 21, 2015 at 04:14:51PM -0500, Dennis Gilmore wrote:
> >>> > 1. F22 trees built nightly (already happening)
> >>> 
> >>> there is new atomic trees built as part of the package updates
> >>> process managed by bodhi.
> >> 
> >> Cool.
> >> 
> >>> > 2. Images built from those nightly (I think right now only rawhide?)
> >>> 
> >>> once f22 is final only rawhide.
> >> 
> >> What would it take to make those happen post-release?
> > 
> > If we could get a clearly defined list of what these items are I would
> > be happy to work towards getting them done. I just don't know how that
> > all needs to fit into current processes right now. This is definitely
> > something I'd like to at least have outlined before the Rel-Eng FAD[0]
> > so maybe some progress could be made before then and/or during.
> > 
> > I do have an open pull request to enable two week ISO composes with
> > the rel-eng scripts but it's still being reviewed and iterated on[1].
> > 
> > I also submitted a patch to the pungi 4 dev branch to enable atomic
> > ISOs[2] be built as a koji task once we migrate to pungi4 and can take
> > advantage of that capability.
> > 
> >>> > 3. Images go through automated tests, automatically (tunir; not fully
> >>> > 
> >>> >    automatic yet, right?)
> >>> 
> >>> there is zero automated testing available, but we really need it, afaik
> >>> it is all manual
> >> 
> >> See <https://fedoraproject.org/wiki/Changes/tunir>. Plus glorious
> >> Taskotron future, I'm sure. :)
> > 
> > I'm not sure where in the phases this should fit, it seems like a
> > giant forklift of work to me given that the base Fedora distro that
> > Atomic is going to be pulling it's bits from doesn't even have this
> > functionality. Am I mistaken or possibly missing something? (Please
> > correct me if I am)
> > 
> >>> > 4. Every two weeks, latest image to pass those tests gets linked
> >>> > 
> >>> >    on atomic.fpo, again all automatically (NEEDS DESIGN AND CODE)
> >>> >    
> >>> >     - probably need a manual override
> >>> >     - page will present these images with appropriate setting of
> >>> >     
> >>> >       expectations ("fedora qa not to blame for anything here").
> >>> >     
> >>> >     - need something to happen if there aren't any that pass for
> >>> >     
> >>> >       two weeks, which should not happen I hope, but, y'know)
> >>> >       
> >>> >         * automatic message about image being out of date
> >>> >         * next successful image automatically posted? Or do we
> >>> >         
> >>> >           skip two weeks?
> >>> >     
> >>> >     - also needs: commitment to follow and fix if things break
> >>> 
> >>> We need people to test, and a process to move things through stages.
> >>> build all the images, etc. a location to put things, i,e lots of
> >>> things
> 
> tl;dr - Two week Atomic builds is currently blocked but we're working on it.
> 
> I wanted to follow up on this particular point. Recently at the Fedora
> Activity Day for Release Engineering[0] we started to dig into the
> Pungi4 code that was recently released into the wild. The unfortunate
> data point is that nothing works right now, we are chewing through it
> the best we can but this is all new code to almost everyone on the
> team (myself included). The test cases currently pass entirely on the
> set of dummy rpms that are fed to the tests but as soon as we open the
> flood gates of real Fedora content this fails in new and exciting
> ways. These runs take over an hour per test so I'm going to focus on
> how to trim that down so we're iterating on a few hundred packages in
> a compose instead of 10s of thousands. It's high on my personal
> priority list to have this resolved so that we can enable Fedora
> Atomic as well as be more flexible with other things. On a similar
> note, the koji run-root plugin is making it's way to production soon
> (already in stage and testing is looking good) so I have high hopes
> there. These two things combined will enable the Atomic builds as well
> as eventually enabling the pxe-to-live stuff.
> 
> I'm not sure how much people actually care about this since I never
> got a response to my previous email. However, I did at least want to
> follow up with a status update because this is something I have a
> personal interest in as I'm a big fan of Atomic and really want to
> make sure it succeeds.
> 

My plan was to extend the current updates script that makes docker base images 
and cloud images to make the atomic installer also

we will only use the pungi4 code in f23 on

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.fedoraproject.org/pipermail/cloud/attachments/20150612/453e337b/attachment-0001.sig>