August 2017 - Atomic Working Group (ARCHIVED)

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 22 Aug '17

22 Aug '17

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2017-08-23 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1@freenode The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6370/

1 0

[atomic-wg] Issue #323: Expand tagging for uploaded AMIs
by Paul W. Frields 22 Aug '17

22 Aug '17

pfrields reported a new issue against the project: `atomic-wg` that you are following: `` AWS supports arbitrary tagging for images (user can set a key:value pair and the keys don't seem to be restricted). Currently AFAICT from looking at the corpus of uploaded snapshots we are not using this feature at all. A few random AMIs seem to have a "name" key with a value that looks a lot like the released filename or ISO volume name, but that's just a handful (under a dozen out of almost 4,000 snapshots). We should be using tags to make it easier to sort and group these images to determine usage, reap them, etc. For example: origin: atomic, base, etc. release: 27, 28, etc. timing: prerelease, release phase: Beta, GA These are just strawmen. Other tags are fine. The key is to be able to effectively sort and discover information about classes of images, which is virtually impossible (at least through the AWS console) at the moment given they aren't delineated in any way. This seems like an "easyfix" from a code perspective, it's probably more work to decide on tagging itself. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/323

1 1

2wk atomic release candidate: 20170821
by Dusty Mabe 22 Aug '17

22 Aug '17

Tomorrow we will attempt to release the 20170821 images. These images contain the following ostree version/commit: 26.110 13ed0f241c9945fd5253689ccd081b5478e5841a71909020e719437bbeb74424 The atomic host VM images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-2017082… The ISO image is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-2017082… The AMIs are here: Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-northeast-1) ami-643bc902 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-southeast-1) ami-db0066b8 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-southeast-2) ami-e2c3d881 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (eu-central-1) ami-34fb505b hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (eu-west-1) ami-cef40bb7 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (sa-east-1) ami-3e037352 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-east-1) ami-61d3e81a hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-west-1) ami-ed7a4f8d hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-west-2) ami-4e1ef136 hvm gp2 Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-northeast-1) ami-a536c4c3 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-southeast-1) ami-7901671a hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (ap-southeast-2) ami-4bcdd628 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (eu-central-1) ami-8ffb50e0 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (eu-west-1) ami-02f20d7b hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (sa-east-1) ami-bc0272d0 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-east-1) ami-03dde678 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-west-1) ami-797a4f19 hvm standard Fedora-Atomic-26-20170821.0.x86_64 EC2 (us-west-2) ami-c61ff0be hvm standard The diff between this and the previous released version is: ostree diff commit old: f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6 ostree diff commit new: 13ed0f241c9945fd5253689ccd081b5478e5841a71909020e719437bbeb74424 Upgraded: bash 4.4.12-6.fc26.x86_64 -> 4.4.12-7.fc26.x86_64 boost-iostreams 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 boost-program-options 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 boost-random 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 boost-regex 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 boost-system 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 boost-thread 1.63.0-5.fc26.x86_64 -> 1.63.0-6.fc26.x86_64 curl 7.53.1-9.fc26.x86_64 -> 7.53.1-10.fc26.x86_64 docker 2:1.13.1-19.git27e468e.fc26.x86_64 -> 2:1.13.1-21.git27e468e.fc26.x86_64 docker-common 2:1.13.1-19.git27e468e.fc26.x86_64 -> 2:1.13.1-21.git27e468e.fc26.x86_64 docker-rhel-push-plugin 2:1.13.1-19.git27e468e.fc26.x86_64 -> 2:1.13.1-21.git27e468e.fc26.x86_64 dracut 044-183.fc26.x86_64 -> 046-2.git20170811.fc26.x86_64 dracut-config-generic 044-183.fc26.x86_64 -> 046-2.git20170811.fc26.x86_64 dracut-network 044-183.fc26.x86_64 -> 046-2.git20170811.fc26.x86_64 expat 2.2.1-1.fc26.x86_64 -> 2.2.3-1.fc26.x86_64 file 5.30-8.fc26.x86_64 -> 5.30-9.fc26.x86_64 file-libs 5.30-8.fc26.x86_64 -> 5.30-9.fc26.x86_64 glibc 2.25-7.fc26.x86_64 -> 2.25-8.fc26.x86_64 glibc-all-langpacks 2.25-7.fc26.x86_64 -> 2.25-8.fc26.x86_64 glibc-common 2.25-7.fc26.x86_64 -> 2.25-8.fc26.x86_64 glusterfs 3.10.4-2.fc26.x86_64 -> 3.10.5-1.fc26.x86_64 glusterfs-client-xlators 3.10.4-2.fc26.x86_64 -> 3.10.5-1.fc26.x86_64 glusterfs-fuse 3.10.4-2.fc26.x86_64 -> 3.10.5-1.fc26.x86_64 glusterfs-libs 3.10.4-2.fc26.x86_64 -> 3.10.5-1.fc26.x86_64 gnupg2 2.1.21-2.fc26.x86_64 -> 2.1.22-1.fc26.x86_64 gnupg2-smime 2.1.21-2.fc26.x86_64 -> 2.1.22-1.fc26.x86_64 kernel 4.11.11-300.fc26.x86_64 -> 4.12.5-300.fc26.x86_64 kernel-core 4.11.11-300.fc26.x86_64 -> 4.12.5-300.fc26.x86_64 kernel-modules 4.11.11-300.fc26.x86_64 -> 4.12.5-300.fc26.x86_64 krb5-libs 1.15.1-17.fc26.x86_64 -> 1.15.1-22.fc26.x86_64 libcrypt-nss 2.25-7.fc26.x86_64 -> 2.25-8.fc26.x86_64 libcurl 7.53.1-9.fc26.x86_64 -> 7.53.1-10.fc26.x86_64 oci-umount 2:1.13.1-19.git27e468e.fc26.x86_64 -> 2:1.13.1-21.git27e468e.fc26.x86_64 python-rhsm-certificates 1.19.4-1.fc26.x86_64 -> 1.20.1-1.fc26.x86_64 python2-cryptography 1.7.2-1.fc26.x86_64 -> 2.0.2-1.fc26.x86_64 python2-setuptools 36.2.0-1.fc26.noarch -> 36.2.0-2.fc26.noarch python3 3.6.2-1.fc26.x86_64 -> 3.6.2-5.fc26.x86_64 python3-cryptography 1.7.2-1.fc26.x86_64 -> 2.0.2-1.fc26.x86_64 python3-docker 2.4.2-1.fc26.noarch -> 2.4.2-3.fc26.noarch python3-libs 3.6.2-1.fc26.x86_64 -> 3.6.2-5.fc26.x86_64 python3-setuptools 36.2.0-1.fc26.noarch -> 36.2.0-2.fc26.noarch selinux-policy 3.13.1-260.3.fc26.noarch -> 3.13.1-260.4.fc26.noarch selinux-policy-targeted 3.13.1-260.3.fc26.noarch -> 3.13.1-260.4.fc26.noarch sqlite-libs 3.19.3-1.fc26.x86_64 -> 3.20.0-1.fc26.x86_64 system-python 3.6.2-1.fc26.x86_64 -> 3.6.2-5.fc26.x86_64 system-python-libs 3.6.2-1.fc26.x86_64 -> 3.6.2-5.fc26.x86_64 tmux 2.5-1.fc26.x86_64 -> 2.5-4.fc26.x86_64 vim-minimal 2:8.0.823-1.fc26.x86_64 -> 2:8.0.946-1.fc26.x86_64 Removed: python2-pyasn1-0.2.3-1.fc26.noarch python3-pyasn1-0.2.3-1.fc26.noarch Added: microcode_ctl-2:2.1-16.fc26.x86_64 python2-asn1crypto-0.22.0-4.fc26.noarch python3-asn1crypto-0.22.0-4.fc26.noarch A new kernel, selinux-policy and docker version are notable changes. Also we added microcode_ctl rpm that contains the latest cpu microcode technology (like updates for your processor). Dusty

1 0

[atomic-wg] Issue #321: Flock 2017 list of events from Atomic WG
by Dusty Mabe 22 Aug '17

22 Aug '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Please comment in this ticket for any talk, workshop, or discussion related to Atomic WG during Flock 2017. This will help us to make sure that we don't miss any important meeting. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/321

2 2

[atomic-wg] Issue #269: fedimg: don't use 'builder' instance for uploading AMIs
by Sayan Chowdhury 21 Aug '17

21 Aug '17

sayanchowdhury added a new comment to an issue you are following: `` Things are looking in dev, except for the fedmsg messages the the fedimg sends. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/269

1 0

[atomic-wg] Issue #322: [Test Day] Proposed Dates for F27 Atomic Test Day
by Sumantro Mukherjee 17 Aug '17

17 Aug '17

sumantrom reported a new issue against the project: `atomic-wg` that you are following: `` Hey , As you people might know, this is a shorter release cycle with a ton of major changes coming in. I wanted to know when you people are planning to holding a test day during this cycle. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/322

1 0

[atomic-wg] Issue #316: remove /var/run/nologin
by Aleksandar Kostadinov 17 Aug '17

17 Aug '17

akostadi reported a new issue against the project: `atomic-wg` that you are following: `` Please remove /var/run/nologin from fedora container image. If one installs SSHd inside, the file is preventing any connections. I was advised to move issue from bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1478984 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/316

4 11

Fedora Atomic WG Meeting Minutes 2017-08-16
by Dusty Mabe 16 Aug '17

16 Aug '17

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-16/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-16/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 17:00:09 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-08-16/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 17:00:13) * action items from last meeting (dustymabe, 17:02:50) * LINK: https://pagure.io/fedora-atomic/issue/72 (kushal, 17:03:41) * jberkus still working on moving kube issues to new kube-sig tracker (dustymabe, 17:03:43) * jbrooks updated 'remove-kube' issues and also moved them to the kube-sig tracker (dustymabe, 17:04:10) * jbrooks started investigating atomic host module (as a learning excercise). has made some progress, but no real results (dustymabe, 17:04:42) * kushal created https://pagure.io/fedora-atomic/issue/72 for us to plan our activities around flock (dustymabe, 17:05:30) * LINK: https://src.fedoraproject.org/modules/atomic (walters, 17:06:19) * contyk to present his POC so far for atomic host module (dustymabe, 17:06:40) * LINK: https://github.com/fedora-modularity/baseruntime-package-lists/blob/master/… (contyk, 17:10:04) * LINK: https://github.com/projectatomic/rpm-ostree/issues/744 (walters, 17:10:27) * LINK: https://src.fedoraproject.org/modules/atomic ? (dustymabe, 17:10:54) * contyk has a module definition for an atomic host module at https://src.fedoraproject.org/modules/atomic but many packages currently aren't building for various reasons in the module build system (dustymabe, 17:11:53) * ACTION: contyk to update the readme in https://src.fedoraproject.org/modules/atomic to point to other places where things are defined and explain why things are the way they are (dustymabe, 17:15:41) * open questions for the modularity team (dustymabe, 17:17:41) * LINK: https://blog.verbum.org/2012/10/13/building-everything-from-source-vs-self-… (walters, 17:19:03) * LINK: https://pagure.io/atomic-wg/issue/313 (dustymabe, 17:21:59) * ACTION: dustymabe walters jbrooks contyk to havea separate breakout on this topic (dustymabe, 17:36:56) * adding tuned to atomic host and btrfs-progs to atomic workstation (dustymabe, 17:37:42) * LINK: https://pagure.io/atomic-wg/issue/315 (dustymabe, 17:38:19) * LINK: https://pagure.io/atomic-wg/issue/319 (dustymabe, 17:38:33) * LINK: https://pagure.io/atomic-wg/issue/319#comment-458232 (walters, 17:42:15) * Flock 2017 list of events from Atomic WG (dustymabe, 17:43:04) * ACTION: jberkus to get with bexelbie to organize an atomic social for Flock (dustymabe, 17:46:54) * open floor (dustymabe, 17:48:20) Meeting ended at 17:54:26 UTC. Action Items ------------ * contyk to update the readme in https://src.fedoraproject.org/modules/atomic to point to other places where things are defined and explain why things are the way they are * dustymabe walters jbrooks contyk to havea separate breakout on this topic * jberkus to get with bexelbie to organize an atomic social for Flock Action Items, by person ----------------------- * contyk * contyk to update the readme in https://src.fedoraproject.org/modules/atomic to point to other places where things are defined and explain why things are the way they are * dustymabe walters jbrooks contyk to havea separate breakout on this topic * dustymabe * dustymabe walters jbrooks contyk to havea separate breakout on this topic * jberkus * jberkus to get with bexelbie to organize an atomic social for Flock * jbrooks * dustymabe walters jbrooks contyk to havea separate breakout on this topic * walters * dustymabe walters jbrooks contyk to havea separate breakout on this topic * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (105) * contyk (75) * walters (23) * jbrooks (22) * jberkus (16) * zodbot (14) * kushal (6) * ksinny (6) * jzb (4) * strigazi (3) * miabbott (2) * langdon (2) * yzhang (2) * roshi_ (1) * jlebon (1) * jwf (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #319: include btrfs-progs in ostrees
by Chris Murphy 16 Aug '17

16 Aug '17

chrismurphy reported a new issue against the project: `atomic-wg` that you are following: `` At least the workstation-ostree does not include btrfs-progs. `atomic host install btrfs-progs` does work but I think it should be included. (xfsprogs and e2fsprogs are included.) To support btrfs installations, it ought to be present at the time dracut runs so the tools can be baked into the initramfs. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/319

4 3

[atomic-wg] Issue #187: Remove-Kube: Make fully containerized install work
by Jason Brooks 16 Aug '17

16 Aug '17

The status of the issue: `Remove-Kube: Make fully containerized install work` of project: `atomic-wg` has been updated to: Closed as Duplicate by jasonbrooks. https://pagure.io/atomic-wg/issue/187

1 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) August 2017