February 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #420: driver blacklisting issue
by Olivier De Jonckere 26 Feb '18

26 Feb '18

olivierdj reported a new issue against the project: `atomic-wg` that you are following: `` Hello, I deploy in an Openstack cloud a kubernetes solution with Magnum (container orchestration service for Openstack) and gpu aware nodes/containers machine learning. As long as cuda 9.0 is available for fedora 25 only, and magnum doesn't support fedora 27, I naturally chose a fedora 25 atomic image for my cluster nodes. But I had a kernel panic with the nouveau driver on the fedora 25 guests, tried to disabling it, and never succeed. I tried again with a Fedora 27 atomic image and was able to disable nouveau without any problem. What is wrong with blacklisting on fedora 25 atomic? As long Openstack magnum and Nvidia cuda doesn't provide fedora 27 support I can't just switch to fedora 27. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/420

2 3

2wk atomic release candidate: 20180117
by Dusty Mabe 26 Feb '18

26 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Tomorrow we will attempt to release the 20180226 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180225.0 updates run: Version: 27.93 Commit(x86_64): da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 Commit(aarch64): 6607b02ff08bd0f0fc488772b398c25de28345a0bda0508ef45b433b91839ccd Commit(ppc64le): 848b618bd36e8b03bbcedf2d9ff881450440d8434f62cdb80006d3e899ebaa28 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018022… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018022… The AMIs are here: Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-2) ami-5840c920 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-1) ami-202d2640 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-east-1) ami-068b627b hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (sa-east-1) ami-dbd79fb7 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-west-1) ami-273f455e hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-central-1) ami-3d1e7352 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-2) ami-4b844229 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-1) ami-ab541cd7 hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-northeast-1) ami-2b1e594d hvm standard Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-2) ami-dd4fc6a5 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-west-1) ami-242d2644 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (us-east-1) ami-2b8d6456 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (sa-east-1) ami-86d59dea hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-west-1) ami-983a40e1 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (eu-central-1) ami-911c71fe hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-2) ami-4884422a hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-southeast-1) ami-cd551db1 hvm gp2 Fedora-Atomic-27-20180226.0.x86_64 EC2 (ap-northeast-1) ami-ed1d5a8b hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: b25bde0109441817f912ece57ca1fc39efc60e6cef4a7a23ad9de51b1f36b742 ostree diff commit new: da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 Upgraded: bash 4.4.12-13.fc27 -> 4.4.19-1.fc27 ca-certificates 2017.2.20-1.0.fc27 -> 2018.2.22-1.0.fc27 container-selinux 2:2.44-1.fc27 -> 2:2.48-1.fc27 coreutils 8.27-19.fc27 -> 8.27-20.fc27 coreutils-common 8.27-19.fc27 -> 8.27-20.fc27 findutils 1:4.6.0-14.fc27 -> 1:4.6.0-16.fc27 freetype 2.8-7.fc27 -> 2.8-8.fc27 glusterfs 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-client-xlators 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-fuse 3.12.5-1.fc27 -> 3.12.6-2.fc27 glusterfs-libs 3.12.5-1.fc27 -> 3.12.6-2.fc27 gnutls 3.5.17-1.fc27 -> 3.5.18-2.fc27 grub2-common 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-efi-x64 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-pc 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-pc-modules 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools-extra 1:2.02-19.fc27 -> 1:2.02-22.fc27 grub2-tools-minimal 1:2.02-19.fc27 -> 1:2.02-22.fc27 ima-evm-utils 1.0-2.fc27 -> 1.0-3.fc27 iproute 4.14.1-4.fc27 -> 4.15.0-1.fc27 iproute-tc 4.14.1-4.fc27 -> 4.15.0-1.fc27 kernel 4.14.18-300.fc27 -> 4.15.4-300.fc27 kernel-core 4.14.18-300.fc27 -> 4.15.4-300.fc27 kernel-modules 4.14.18-300.fc27 -> 4.15.4-300.fc27 krb5-libs 1.15.2-4.fc27 -> 1.15.2-7.fc27 ostree 2018.1-1.fc27 -> 2018.2-1.fc27 ostree-grub2 2018.1-1.fc27 -> 2018.2-1.fc27 ostree-libs 2018.1-1.fc27 -> 2018.2-1.fc27 python2 2.7.14-6.fc27 -> 2.7.14-7.fc27 python2-libs 2.7.14-6.fc27 -> 2.7.14-7.fc27 python3 3.6.4-7.fc27 -> 3.6.4-8.fc27 python3-libs 3.6.4-7.fc27 -> 3.6.4-8.fc27 rpm-ostree 2018.1-2.fc27 -> 2018.3-1.fc27 rpm-ostree-libs 2018.1-2.fc27 -> 2018.3-1.fc27 skopeo 0.1.27-1.git93876ac.fc27 -> 0.1.28-1.git0270e56.fc27 skopeo-containers 0.1.27-1.git93876ac.fc27 -> 0.1.28-1.git0270e56.fc27 strace 4.20-1.fc27 -> 4.21-1.fc27 vim-minimal 2:8.0.1478-1.fc27 -> 2:8.0.1527-1.fc27 Removed: compat-openssl10-1:1.0.2m-1.fc27.x86_64 We have a new kernel (4.15), ostree [1] , and rpm-ostree [2]. Happy testing! Dusty [1] https://github.com/ostreedev/ostree/releases/tag/v2018.2 [2] https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.3 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqURtMACgkQMwLb1zlS 5nHizw/9HLx/gXpFlkikQzo5+wmJ0ONUUZmu7SBSePlR6UUYUdLlCLsxwUOzWGg5 it4cW7oOwOldMipLH0eaYoTgWgKJfCM0PVRS2blsZ/gNaDvD7Qq/4LJ2RlAQaixY ZwBFivuKGlUggMYEtW0N7kC2K1BDnkxinmtH+/uRQYJ5ftbMRGxK5kjAzbFHt45d GYPvpL+bd5pQZ8+Kq3O7T9axpkdCJx1UK0ljZ+anoRYYYpK9OZvWE7UgOFudgC6I r6Trh6PyEVNVZj/nozpzgwZCWrli+yQ2lHnS9wpcrc6/2qz6X4sn/PMs6FWPnwIA j0mDsoHE7h6NFeFFlLy7E3P4aun3KC3rg+8CIsauqQ5eDHsp5EQ4FDOXtY/u8plA TxDDVbgtVDTtSD2iUCiS5jpk53tfBKaZ3e7GD/XmLN2FFnn1ifG1O1FNJwarcWR7 MGSajIxn06/krcdRdiHLH8lS0gvQmPrUQMqQSvyDjVxqRoITJcEdwDGIQd4MtUj8 UpM1EFfk9fcQp47d1xgk89qGDdLfTX2AC9/k9O2KrI8sBaZ0oi6eWJtYdN9S+rtp qfmQLiLB/0HYaWuJjYLbQFAnEk0kuRVxsrcpnoC70zI7hJRknVXDtlf+SeVg7VpL icnKp/kHsXV8KNN/gNL6Uq1RgjJX92DS/KkDnWB95XNvaMGu1jw= =Xia2 -----END PGP SIGNATURE-----

1 0

[fedora-atomic] Issue #110: Request to review release blocking deliverables of F28
by Jan Kurik 26 Feb '18

26 Feb '18

jkurik reported a new issue against the project: `fedora-atomic` that you are following: `` I would like to ask for a review of Release blocking deliverables [1] for F28 release delivered by Atomic (Cloud) WG. Please let me know in case of missing images, or in case the "blocking" status has changed since the last release. [1] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking#Cloud `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/issue/110

2 1

Fedora Atomic WG Meeting Minutes 2018-02-21
by Micah Abbott 21 Feb '18

21 Feb '18

suimmary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by miabbott at 16:30:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-21/fedora_atomic… . Meeting summary --------------- * roll call (miabbott, 16:31:44) * previous meeting action items (miabbott, 16:35:17) * ACTION: dustymabe to schedule february VFAD a CFP for proposed topics (dustymabe, 16:36:25) * working with dockerhub members and new members and will give/revoke access (dustymabe, 16:36:53) * AWS scans of Fedora Atomic Host still pending completion (miabbott, 16:39:48) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host (miabbott, 16:40:19) * riot/irc tutorial is written, will be published when new web site is announced (miabbott, 16:43:17) * ACTION: sanja to create ticket about elminating redundancy in mailing lists + irc channels (miabbott, 16:45:49) * ACTION: sanja to create ticket about archiving unused projectatomic github repos (miabbott, 16:46:09) * ACTION: misc to open ticket on the irc bot (miabbott, 16:49:00) * Design Meetings over Video (miabbott, 16:49:03) * LINK: https://pagure.io/atomic-wg/issue/418 (miabbott, 16:49:05) * Identify users for docker hub auto builds for system containers (miabbott, 16:52:54) * LINK: https://pagure.io/atomic-wg/issue/379 (miabbott, 16:52:56) * open floor (miabbott, 16:54:46) * ACTION: ashcrow to ping tomas about building f27/tools container (miabbott, 17:04:41) * ACTION: dusty to open ticket to start discussion about quay.io (dustymabe, 17:08:14) * LINK: https://pagure.io/fedora-comps/pull-request/220 (walters1, 17:09:55) * LINK: https://pagure.io/workstation-ostree-config/pull-request/70 (walters1, 17:10:03) * LINK: https://pagure.io/workstation-ostree-config/pull-request/64 (walters1, 17:10:39) * vote on new project atomic logo on mailing list or twitter (miabbott, 17:11:37) * LINK: https://twitter.com/projectatomic/status/965689983490195456 (miabbott, 17:11:41) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:11:46) * recent changes affecting fedora atomic workstation (miabbott, 17:13:19) * LINK: https://pagure.io/fedora-comps/pull-request/220 (miabbott, 17:13:22) * LINK: https://pagure.io/workstation-ostree-config/pull-request/70 (miabbott, 17:13:25) * LINK: https://pagure.io/workstation-ostree-config/pull-request/64 (miabbott, 17:13:32) * first Fedora Atomic Workstation SIG meeting was held on Monday Feb 19 (miabbott, 17:15:02) * LINK: https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG/Notes (miabbott, 17:15:03) * jessfraz working on something that could overlap with buildah (miabbott, 17:17:04) * LINK: https://twitter.com/jessfraz/status/966057711552094209 (miabbott, 17:17:09) * LINK: https://github.com/cyphar/orca-build (miabbott, 17:18:07) * LINK: https://getfedora.org/en/atomic/ this looks like a logo to me. (sanja, 17:19:20) * please contribute content to the new web site (miabbott, 17:26:08) * LINK: https://github.com/projectatomic/atomic-site-new (miabbott, 17:26:10) * tools container PR from action item (ashcrow, 17:29:11) * LINK: https://src.fedoraproject.org/container/tools/pull-request/2 (ashcrow, 17:29:23) * LINK: http://new.projectatomic.io/ (sanja, 17:32:25) Meeting ended at 17:32:36 UTC. Action Items ------------ * dustymabe to schedule february VFAD a CFP for proposed topics * davdunc to inform WG about AWS scan results of Fedora Atomic Host * sanja to create ticket about elminating redundancy in mailing lists + irc channels * sanja to create ticket about archiving unused projectatomic github repos * misc to open ticket on the irc bot * ashcrow to ping tomas about building f27/tools container * dusty to open ticket to start discussion about quay.io Action Items, by person ----------------------- * ashcrow * ashcrow to ping tomas about building f27/tools container * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host * dustymabe * dustymabe to schedule february VFAD a CFP for proposed topics * sanja * sanja to create ticket about elminating redundancy in mailing lists + irc channels * sanja to create ticket about archiving unused projectatomic github repos * **UNASSIGNED** * misc to open ticket on the irc bot * dusty to open ticket to start discussion about quay.io People Present (lines said) --------------------------- * miabbott (87) * sanja (75) * dustymabe (54) * ashcrow (32) * lorbus (26) * zodbot (20) * jbrooks (19) * walters1 (11) * giuseppe (7) * walters (6) * davdunc (4) * rubao|laptop (2) * jlebon (1) * sayan (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #379: Identify users for docker hub auto builds for system containers
by Steve Milner 21 Feb '18

21 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` As part of the work to start github->docker hub autobuilds for system containers we will need a GitHub which will give link to a docker hub account. Are there specific accounts already available which would make sense to reuse? Do we need to create accounts specific to auto building for both GitHub and docker hub? I tend to believe we should avoid a specific human account tied to this but instead use a service account. Reference: https://docs.docker.com/docker-hub/builds/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/379

3 8

[fedora-atomic] PR #108: Branching F28 from rawhide
by Mohan Boddu 20 Feb '18

20 Feb '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Branching F28 from rawhide `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/108

2 1

[fedora-atomic] PR #109: Setup for Rawhide being Fedora 29
by Mohan Boddu 20 Feb '18

20 Feb '18

mohanboddu opened a new pull-request against the project: `fedora-atomic` that you are following: `` Setup for Rawhide being Fedora 29 `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/109

2 1

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 20 Feb '18

20 Feb '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-02-21 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net 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/6952/

1 0

[atomic-wg] Issue #425: Enable serial consoles in images
by William Brown 19 Feb '18

19 Feb '18

firstyear reported a new issue against the project: `atomic-wg` that you are following: `` It would be useful to have serial consoles as an option for centos/fedora atomic images in parallel to the current video consoles. This would open up options for installation of atomic on embedded and other systems that tend to use serial consoles. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/425

1 0

[atomic-wg] Issue #419: lua in glibc rpm breaks package layering in rawhide
by Dusty Mabe 19 Feb '18

19 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` @pwhalen reported an issue when trying to upgrade a rawhide system that has package layering: ``` [root@rpiii ~]# rpm-ostree upgrade 1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds Checking out tree 25b4bbe... done Enabled rpm-md repositories: rawhide rpm-md repo 'rawhide' (cached); generated: 2018-02-04 09:02:29 Importing metadata [=============] 100% Resolving dependencies... done Applying 9 overlays Building filesystem (9/9) [=============] 100% Running pre scripts... [ 2074.161675] fuse init (API version 7.26) 1 done Running post scripts... error: Executing %transfiletriggerin for glibc: Package 'glibc' has (currently) unsupported <lua> script in '%transfiletriggerin' ``` This is because glibc [added a lua scriptlet](https://src.fedoraproject.org/rpms/glibc/c/6ff958f2aae58ce8d9199… which we currently [don't support](https://github.com/projectatomic/rpm-ostree/issues/749) We'll need to try to get that switched out so people can package layer in rawhide (and in f28). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/419

2 5

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) February 2018