phracek added a new comment to an issue you are following:
``
Yes, issue can be closed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/205
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
This started as an [email](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-August/msg00002.html) to the atomic-devel list. Moving into a ticket for further discussion and tracking of experimentation of building Atomic Host out of a module. Summary of bullets from the email:
Here are some of the things we want to be able to do:
- 1 Have a rigorous definition (including specific versions, buildroot) of
what goes into an Atomic Host, including dependencies.
- 2 Triggering the CI/CD pipeline based on a change to definition
of what goes into Atomic Host.
- 3 A way to revert a package in the Atomic Host compose to an earlier version.
- 4 A place to store higher level tests along with rigorous definition
of Atomic Host, including them being versioned.
- 5 Landing multiple changes that need to land together to pass testing.
Out of that list we think we require that:
- 1R The definition of what is composed into Atomic Host artifacts should
include specific versions of packages, and all dependencies included.
- 2R The definition of what is composed in an Atomic Host should be stored
in a git repository so that changes can be detected easily. The
CI/CD pipeline can be triggered off of changes to this reposiroty.
- 3R A mechanism to make a future composed Atomic Host artifact, contain
an earlier (in RPM NVR parlance) version of a package.
- 4R The high level functional Atomic Host tests should live in the same
git repository with the rigorous definition of what goes into an Atomic
Host.
- 5R A mechanism to tell the CI Pipeline that multiple dist-git repository
changes (i.e. multiple changing RPMs) should be built and tested together.
Note - @walters also sent [an email](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproj… to a broader audience about modularity and Atomic Host that is worth a read.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/312
sdodson reported a new issue against the project: `atomic-wg` that you are following:
``
According to @dustymabe tuned is not currently installed on Fedora Atomic Host. OpenShift would like to make use of tuned profiles so we'd like to ensure that it's installed and enabled on atomic host.
We're not clear on the best way to deliver openshift specific tuned profiles to atomic host so we'd be interested in hearing if you have suggestions there. If nothing else is presented we'll likely drop them via our install playbooks.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/315