#6119: AtomicHost rel-eng integration

[Fedora Release Engineering]

#6119: AtomicHost rel-eng integration
-----------------------------+-----------------------
  Reporter:  walters         |      Owner:  rel-eng@…
      Type:  task            |     Status:  new
 Milestone:  Fedora 22 Beta  |  Component:  koji
Resolution:                  |   Keywords:  meeting
Blocked By:                  |   Blocking:
-----------------------------+-----------------------

Comment (by walters):

 I definitely understand the rationale behind pungi for mainline "installer
 + RPMs".  But for Atomic, the content is by nature *already* assembled,
 and the point of the scripts is to inject it into the installer itself so
 it can be installed offline.

 Now, I have had requests to provide the exact ostree commit that went into
 an installer image, and it makes a lot of sense to have visible.  If we're
 trying to achieve that there are the exact same package versions in the
 release content set, I could certainly see an argument that "pungi" would
 generate two installers and for the ostree one, start from the exact
 commit used for that compose, rather than "latest".

 On the other hand, you're talking about moving things into Koji with the
 argument that they can be asynchronous - but that is at odds with the
 concept of a gigantic release all containing one unified package set.

 At a high level, the way I'm thinking about things, particularly with
 discussion of the 2-4-6 for Atomic:
  - It's really important to share as much code as possible (hence using
 Anaconda, lorax, obviously RPMs, etc.).  I'm not opposed to Koji as well
 (though there's more to discuss there, such as the fact that koji today
 has no concept of dependencies between tasks, e.g. rpm -> tree -> [cloud
 image | pxetolive]).
  - On the other hand, one of the facets some competitors have is releasing
 a lot more frequently than every 6 months.  And matching this is
 definitely part of the goal of Atomic - releasing the host tree as well as
 the base image shouldn't (need to) block on GPG signing texlive.  (On the
 other other hand, some things included in Atomic have documentation built
 using TeX, so I know it's not that simple - but there's a reachable middle
 ground)

 Anyways so...bottom line then I guess is for Fedora 22 there will be an
 Atomic-specific installer, but not PXE-to-Live?  And the latter is blocked
 on a Koji task?

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6119#comment:12>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project