jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Article Title: Fedora 27 Atomic Feature Roundup
Deadline: October 30
Priority: Normal
Publication: Fedora Community Blog
This should be a round-up of the features in Fedora 27 Atomic, for a general audience that hasn't followed Atomic for the last 6 months. Should cover features from the talking points briefly and link off to other articles.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/356
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Title: Installing Kubernetes on Fedora 27 Atomic
Deadline: November 15
Publication: Project Atomic Blog, Docs
Priority: Low
This should be based on the F26 article from Jason Brooks, updated to show the correct options and terminal sessions for F27.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/357
walters opened a new pull-request against the project: `fedora-atomic` that you are following:
``
Use boot_location: new
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/102
walters reported a new issue against the project: `fedora-atomic` that you are following:
``
See https://github.com/projectatomic/rpm-ostree/pull/959#issuecomment-325780234
Right now we have:
```
[root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /boot|grep initramfs
-00600 0 0 52565370 7e6c941d0eefc5760917b300bade10e107d99c89fd0f627b7d9e1cf03068b9bd { [(b'security.selinux', b'system_u:object_r:boot_t:s0')] } /boot/initramfs-4.13.9-300.fc27.x86_64.img-850b4ded439b2151106725e7b522d8485d312c9ed80aee65c818c9f99c2c1701
[root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /usr/lib/ostree-boot|grep initramfs
-00600 0 0 52565370 79acadd126fcb5a02142119dfab6bd35fd5bfb46606adeab23f89cb04c4afc2a { [(b'security.selinux', b'system_u:object_r:lib_t:s0')] } /usr/lib/ostree-boot/initramfs-4.13.9-300.fc27.x86_64.img-850b4ded439b2151106725e7b522d8485d312c9ed80aee65c818c9f99c2c1701
[root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /usr/lib/modules|grep initramfs
-00600 0 0 52565370 f70d77da922263abc7e4f4e9fc92e178b051df8e10bd3105ebbb642ca5748f4b { [(b'security.selinux', b'system_u:object_r:modules_object_t:s0')] } /usr/lib/modules/4.13.9-300.fc27.x86_64/initramfs.img
```
Which means 3 physically distinct copies of the initramfs, and with `/boot` as its own partition, that brings it to 4. Using `boot_location: new` should bring us to 2 copies in the tree, and at that point I think we should change the SELinux policy to bring that to 1.
I still need to verify that everything works for Anaconda with that set.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/issue/94
walters opened a new pull-request against the project: `fedora-atomic` that you are following:
``
post: Strip glibc_post_upgrade.x86_64
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/101