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 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
gscrivano reported a new issue against the project: `atomic-wg` that you are following:
``
I'd like to refer to an image in the registry without referring to the Fedora version that it is based on, so that it will be easier to track if an image was updated and get always the latest version.
For example, it could be a new namespace "latest" or "current" that points to the latest "f[1-9][0-9]+" one, as:
`registry.fedoraproject.org/latest -> registry.fedoraproject.org/f26`
With such a change I could do something like:
```
# atomic install --system registry.fedoraproject.org/latest/etcd
```
and keep using "atomic pull && atomic containers update etcd" to keep the container updated without worrying that the latest version will be in a different namespace at some point.
Another advantage of such change is that it will make easier to use images from the Fedora registry onto other systems (such as RHEL or CentOS) where it is not immediate to know what is last version of Fedora available and how to get the most updated version of an image.
This won't break current use cases, as the namespaced images will still exist.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/376
smilner reported a new issue against the project: `atomic-wg` that you are following:
``
When the group can not come to a 100% (or whatever percentage is deemed enough) consensus we could have an in chat +1/-1 vote called by the meeting leader. This could be for anything from continuing a discussion on a topic, to moving the conversation to pagure, to making a decision in the meeting. If the +1/-1 result ends in a positive integer then the proposal passes.
* +1, -1, +1, +1 = 2 == PASS
* +1, -1, +1, -1 = 0 == FAIL
* -1, -1, +1, -1 = -1 == FAIL
Calling a vote would be at the discretion of the meeting leader and should generally called when:
* A clear decision is required
* The conversation is not leading to a conclusion/actionable result
* A barometer of the room on a topic is needed
If an item **requires** an outcome yet the team is unable to agree on one via the voting process the issue would then be escalated to the proper Fedora committee/working group.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/377
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Article Title: Installing [Docker, Etcd, Flannel, something] In a System Container
Deadline: Dec 1
Publication: Project Atomic Blog
Priority: Nice To Have
This article would be intended to show off the improved system containers, atomic CLI and FLIBS system containers. In it, the writer would step through installing some piece of software other than Kubernetes which is available from FLIBS in a system container, such as an alternate version of Docker.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/359
walters opened a new pull-request against the project: `fedora-atomic` that you are following:
``
Add rpm-ostree jigdo spec
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/pull-request/93