February 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #426: Run dracut on atomic upgrades
by William Brown 07 Mar '18

07 Mar '18

firstyear reported a new issue against the project: `atomic-wg` that you are following: `` When you install a new rpm-ostree (ie upgrade) dracut should be run. This is to capture settings relevant to the hardware from files such as /etc/crypttab (discard via luks) or modprobe.d. Today, it would appear manually running dracut has no effect (?). This would be a great addition as it would then automate and allow hardware corrections for kernel modules - for me I have a macbook pro that requires quirks set to the sdhci card, but on atomic I need to modprobe -r/modprobe after restart to make them apply. Thanks, `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/426

3 8

[atomic-wg] Issue #413: use python-docker instead of python-docker-py
by Tomas Tomecek 06 Mar '18

06 Mar '18

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` I opened this page: https://fedoraproject.org/wiki/CI/Tests/stat I was quite shocked, that python-docker-py is on the list. We have renamed the package to python-docker after the big API changes happened in version 2. Right now I'm trying to get rid of python-docker-py. Would it be possible to include python-docker in Atomic Host compose instead of python-docker-py? The package is probably pulled by atomic CLI, but the fact is that on rawhide atomic RPM requires python3-docker: ``` $ rpm -q --requires atomic | grep docker python3-docker >= 1.7.2 ``` RHEL and CentOS still include python-docker-py because no one requested the newest upstream release yet. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/413

4 15

[atomic-wg] Issue #403: Minimal OSTree/ISO image initiative
by Josh Berkus 06 Mar '18

06 Mar '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Currently, the main user story for Fedora Atomic Host is as a container infrastructure web host. The OStree ref and ISOs we maintain work well for this user story, and it leads to certain decisions like keeping docker and atomic CLI in the base image (see https://pagure.io/atomic-wg/issue/360) However, there is a user story we are not satisfying, which is the user who wants a truly minimal install, and is more interested in being able to compose her own ostrees and atomic updates than she is in container orchestration. This is an important user story because we already have demand for it, especially from the IoT sector. The steps to pursue this would be: 1. work with users to refine and specify the requirements for a "minimal" edition 2. identify and recruit contributors to assist with building it 3. create and publicize new minimal ref and associated tools Based on my conversations at conferences, the main requests are these: * reduce the size of the base ostree by stripping things out, preferably to less than 300MB installed. * auto-rollback on rpm-ostree upgrade reboot fail * a complete, well-documented toolchain for building and redistributing custom ostrees, based on either the minimal ref or "from scratch". * support for ARM32 (unlikely at best, but people have asked) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/403

6 9

[fedora-atomic] PR #107: Remove old python-docker-py library.
by Dusty Mabe 01 Mar '18

01 Mar '18

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` Remove old python-docker-py library. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/107

2 4

[atomic-wg] Issue #430: consider using quay.io container registry
by Dusty Mabe 01 Mar '18

01 Mar '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` In a few previous issues ([1](https://pagure.io/atomic-wg/issue/379) [2](https://pagure.io/atomic-wg/issue/381) [3](https://pagure.io/atomic-wg/issue/383) we had discussed our strategy regarding automated container builds in dockerhub. Now that we have friends with a hosted container registry we should consider pivoting and using quay.io instead. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/430

5 4

[atomic-wg] Issue #424: memcached and mariadb container not built for f27
by Clement Verna 01 Mar '18

01 Mar '18

cverna reported a new issue against the project: `atomic-wg` that you are following: `` The memcached and mariadb container were never built for f27. The last build for mariadb is mariadb-10.1-13.f26container and for memcached memcached-0-2.f26container_modular. Also memcached Dockerfile on the f27 is using the rawhide base image. https://src.fedoraproject.org/container/memcached/blob/f27/f/Dockerfile#_1 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/424

1 5

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

28 Feb '18

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… ================================================ #fedora-meeting-1: fedora_atomic_wg ================================================ Meeting started by miabbott_ at 16:32:04 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-28/fedora_atomic… . Meeting summary --------------- * roll call (miabbott_, 16:32:19) * previous meeting action items (miabbott_, 16:36:28) * opened ticket for VFAD: https://pagure.io/atomic-wg/issue/429 (dustymabe, 16:37:05) * quay.io discussion ticket: https://pagure.io/atomic-wg/issue/430 (dustymabe, 16:37:30) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host (miabbott_, 16:39:23) * archive unused github repos - https://pagure.io/atomic-wg/issue/428 (miabbott_, 16:41:46) * LINK: https://meetbot.fedoraproject.org/sresults/?group_id=fedora_atomic_wg&type=… (misc, 16:42:59) * reduce redundant mailing lists + irc channels - https://pagure.io/atomic-wg/issue/427 (miabbott_, 16:43:20) * ACTION: ashcrow to ping tomas about building f27/tools container (miabbott_, 16:46:17) * march 9th vFAD (dustymabe, 16:49:27) * LINK: https://pagure.io/atomic-wg/issue/429 (dustymabe, 16:49:38) * ACTION: sanja_ to help make/stick to an agenda for next week's VFAD (dustymabe, 16:58:20) * open floor (miabbott_, 16:59:10) * FAW content changes - https://pagure.io/workstation-ostree-config/pull-requests?status=0 (miabbott_, 17:00:43) * sayan got fedimg on stg (miabbott_, 17:02:13) * sayan started work on having fedimg to use qcow2 directly - https://github.com/fedora-infra/fedimg/issues/64 (miabbott_, 17:10:54) * LINK: https://pagure.io/atomic-wg/issues?status=all&search_pattern=fedimg (dustymabe, 17:11:15) * Moved the ownership of the pagure repo to dustymabe (kushal, 17:12:23) Meeting ended at 17:14:56 UTC. Action Items ------------ * davdunc to inform WG about AWS scan results of Fedora Atomic Host * ashcrow to ping tomas about building f27/tools container * sanja_ to help make/stick to an agenda for next week's VFAD Action Items, by person ----------------------- * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host * sanja * sanja_ to help make/stick to an agenda for next week's VFAD * sanja_ * sanja_ to help make/stick to an agenda for next week's VFAD * **UNASSIGNED** * ashcrow to ping tomas about building f27/tools container People Present (lines said) --------------------------- * miabbott_ (54) * dustymabe (51) * zodbot (27) * walters1 (16) * sayan (13) * sanja_ (7) * misc (7) * kushal (6) * sanja (6) * bowlofeggs (4) * lorbus (4) * davdunc (4) * jberkus_ (3) * jbrooks (3) * ksinny (1) * jligon (1) * dustymab1 (1) * jlebon (1) * giuseppe (1) * jberkus (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[fedora-atomic] PR #112: Add support for s390x
by Sinny Kumari 28 Feb '18

28 Feb '18

sinnykumari opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add support for s390x `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/112

2 1

[fedora-atomic] PR #111: Add support for s390x
by Sinny Kumari 28 Feb '18

28 Feb '18

sinnykumari opened a new pull-request against the project: `fedora-atomic` that you are following: `` Add support for s390x `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/111

4 4

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

27 Feb '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-02-28 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

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) February 2018