|Summary:||Host and Platform|
|Product:||[Fedora] Fedora||Reporter:||Jan Kurik <jkurik>|
|Component:||Changes Tracking||Assignee:||Petr Šabata <psabata>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Version:||27||CC:||gmarr, mattdm, psabata, sgallagh|
|Whiteboard:||ChangeAcceptedF27, SystemWideChange RejectedBlocker|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2017-10-30 16:59:04 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||1491023, 1493170|
Description Jan Kurik 2017-07-25 15:40:34 UTC
This is a tracking bug for Change: Host and Platform For more details, see: https://fedoraproject.org//wiki/Changes/Host_and_Platform Host and Platform is an evolution of the Base Runtime module concept introduced in Fedora 26 Boltron, splitting the minimal system further into independent modules allowing for greater flexibility when composing and maintaining the base system.
Comment 1 Jan Kurik 2017-08-10 06:18:17 UTC
On 2017-Aug-01, we have reached the Fedora 27 Change Checkpoint: Completion deadline (testable). At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well. Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness. Incomplete and non testable Changes will be reported to FESCo for 2017-Aug-11 meeting. Please set this bug to the MODIFIED state to indicate it is already in the testable state, or provide an update describing the current state of implementation for this Change. Thank you, Jan
Comment 2 Petr Šabata 2017-08-11 10:43:16 UTC
We have builds of Host & Platform modules ready. They're still being worked on -- polished, minimized (unbundling dynamic languages) and extended (more useful features) at the same time. But we have something :) There's also a compose that includes host, platform and shim, but it's currently defunct due to a robosignatory configuration problem. It's being fixed today (https://pagure.io/robosignatory/pull-request/15). Switching to MODIFIED.
Comment 3 Jan Kurik 2017-08-15 07:32:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Comment 4 Jan Kurik 2017-09-06 13:38:35 UTC
On 2017-Sep-05 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 27 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review. Thanks, Jan
Comment 5 Petr Šabata 2017-09-07 18:04:34 UTC
The content definition is still not 100% complete. Host & Platform currently pull in packages with broken deps; this needs to be ironed out. The H&P deliverables are/were blocked by several things: * signing issues (hopefully resolved as of today) * PDC not registering all module component builds (tracked) * incorrect variant of lorax in the buildroot, requiring packages we don't intend to ship via anaconda-gui (todo; hopefully we can reuse F26 templates) * possibly some packages missing (investigating; at least fedora-logos was added today) I will attend the FESCo meeting tomorrow.
Comment 6 Fedora Blocker Bugs Application 2017-10-19 17:05:06 UTC
Proposed as a Blocker for 27-server-beta by Fedora user mattdm using the blocker tracking app because: Host and Platform are by definition the fundamental building blocks.
Comment 7 Stephen Gallagher 2017-10-30 16:59:04 UTC
We have composes that are built from the host and platform modules (among others). I'm calling this one complete.
Comment 8 Geoffrey Marr 2017-10-30 20:01:48 UTC
Discussed during the 2017-10-30 blocker review meeting:  The decision to classify this bug as a RejectedBlocker was made as we don't really see that there's any utility in having a Change tracking bug as a release blocker, the release blocker process is about concrete functional bugs; any functional bug caused by the Change being incomplete should be evaluated as a blocker on its own merits.  https://meetbot.fedoraproject.org/fedora-blocker-review/2017-10-30/f27-blocker-review.2017-10-30-16.00.txt