April 2018 - Atomic Working Group (ARCHIVED)

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

10 Apr '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-04-11 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 #448: Ability to alter settings in modprobe.d and have them affect initrd
by William Brown 08 Apr '18

08 Apr '18

firstyear reported a new issue against the project: `atomic-wg` that you are following: `` My laptop requires settings for sdhci and i915. I would like to have these in ansible/version control and deployed to modprobe.d. However, atomic does not allow me to update the initrd correctly. It would be good if there was a way to generate the initrd for atomic images based on the content in the modprobe.d directory to allow customisation. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/448

2 3

[atomic-wg] Issue #249: The build system should provide an automatically populated VERSION label
by Dusty Mabe 06 Apr '18

06 Apr '18

dustymabe added a new comment to an issue you are following: `` Thanks @cverna ! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/249

1 0

[atomic-wg] Issue #249: The build system should provide an automatically populated VERSION label
by Clement Verna 06 Apr '18

06 Apr '18

cverna added a new comment to an issue you are following: `` I have open a ticket on koji-containerbuild[0] to discuss with the OSBS team how to implement this feature. [0] - https://github.com/release-engineering/koji-containerbuild/issues/95 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/249

1 0

[atomic-wg] Issue #249: The build system should provide an automatically populated VERSION label
by Clement Verna 06 Apr '18

06 Apr '18

The issue: `The build system should provide an automatically populated VERSION label` of project: `atomic-wg` has been assigned to `cverna` by cverna. https://pagure.io/atomic-wg/issue/249

1 0

Re: Fedora Atomic Community Meeting Minutes 2018-04-03
by Dusty Mabe 05 Apr '18

05 Apr '18

On 04/04/2018 05:29 PM, Laura Abbott wrote: > On 04/04/2018 02:08 PM, Dusty Mabe wrote: >>>> 2. I had to add a "custom" rpm to enable firmware for my laptop. Is there any work toward enabling /usr/local/lib/firmware to work? >>>> This document explains more.https://fy.blackhats.net.au/blog/html/2017/12/23/using_b43_firmware_on_fedora_atomic_workstation.html . Currently Fedora only accepts /lib/firmware Which of course is read only on atomic >> I'm not really sure why /usr/local/lib/firmware isn't used by Fedora. >> Maybe we can have someone from the kernel team comment. Added cc to >> Laura Abbott to see if she knows why. >> >> Dusty > > For why it's not used now, b43 has a license that's incompatible > (see https://fedoraproject.org/wiki/Firmware) and we haven't > gone out of our way to do anything with it. Yep. absolutely didn't expect you to answer why b43 wasn't included. Was more the /usr/local/lib/firmware question :) > > The kernel has this: > > /* direct firmware loading support */ > static char fw_path_para[256]; > static const char * const fw_path[] = { > fw_path_para, > "/lib/firmware/updates/" UTS_RELEASE, > "/lib/firmware/updates", > "/lib/firmware/" UTS_RELEASE, > "/lib/firmware" > }; > > /* > * Typical usage is that passing 'firmware_class.path=$CUSTOMIZED_PATH' > * from kernel command line because firmware_class is generally built in > * kernel instead of module. > */ > module_param_string(path, fw_path_para, sizeof(fw_path_para), 0644); > MODULE_PARM_DESC(path, "customized firmware image search path with a higher priority than default path"); > > > so /usr/local/firmware isn't in the default path but it looks like > you can provide your own path on the kernel command line and it > should work. I've never tried this myself but I'd test to see if > adding that works for you. Cool. So providing something like firmware_class.path=/usr/local/lib/firmware might work?? Will ask him to give that a shot. Dusty

1 0

Fedora Atomic Community Meeting Minutes 2018-04-03
by Sinny Kumari 04 Apr '18

04 Apr '18

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-04-03/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-04-03/fedora_atomic… ========================================== #fedora-meeting-1: fedora_atomic_community ========================================== Meeting started by ksinny at 05:00:56 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-04-03/fedora_atomic… . Meeting summary --------------- * Roll Call (ksinny, 05:01:12) * Introduction (ksinny, 05:07:47) * Questions (ksinny, 05:21:41) * ACTION: ksinny get answer for "Is there any plan to have a default flatpak repo eventually ? e.g. flathub, maybe on provided by fedora, etc" (ksinny, 05:36:59) * ACTION: ksinny get answer for is there any plans to have rpm-ostree handle package groups like DNF does? (ksinny, 05:37:50) * ACTION: ksinny get answer to "is there a plan to have a local RPM repo where I can put custom or downloaded rpms for installation with rpm-ostree ?" (ksinny, 05:47:41) * Atomic ML - https://fedoraproject.org/wiki/Atomic_WG#Mailing_List (ksinny, 05:51:44) * IRC channel - https://fedoraproject.org/wiki/Atomic_WG#IRC (ksinny, 05:51:59) * coordinate Project Atomic-related talks for devconf.in (ksinny, 05:52:43) * LINK: https://pagure.io/atomic-wg/issue/447 (ksinny, 05:52:51) * Open Floor (ksinny, 05:57:37) Meeting ended at 06:01:32 UTC. Action Items ------------ * ksinny get answer for "Is there any plan to have a default flatpak repo eventually ? e.g. flathub, maybe on provided by fedora, etc" * ksinny get answer for is there any plans to have rpm-ostree handle package groups like DNF does? * ksinny get answer to "is there a plan to have a local RPM repo where I can put custom or downloaded rpms for installation with rpm-ostree ?" Action Items, by person ----------------------- * ksinny * ksinny get answer for "Is there any plan to have a default flatpak repo eventually ? e.g. flathub, maybe on provided by fedora, etc" * ksinny get answer for is there any plans to have rpm-ostree handle package groups like DNF does? * ksinny get answer to "is there a plan to have a local RPM repo where I can put custom or downloaded rpms for installation with rpm-ostree ?" * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ksinny (70) * firstyear (68) * AdrianCeleste (41) * snarwade (16) * zodbot (11) * sayan (8) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

3 3

[atomic-wg] PR #451: Add kubeadm test link for Kubernetes test
by Sinny Kumari 04 Apr '18

04 Apr '18

sinnykumari opened a new pull-request against the project: `atomic-wg` that you are following: `` Add kubeadm test link for Kubernetes test `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/451

2 2

[atomic-wg] Issue #439: Container Release
by Clement Verna 04 Apr '18

04 Apr '18

cverna reported a new issue against the project: `atomic-wg` that you are following: `` The Fedora container release are quite difficult to get out, while the tooling might still need some work, I also feel that it is not really clear what we are expecting from the release. Following a discussion on atomic-devel, I propose the following : * Release containers that are based on the current stable fedora ( would be f27 currently) * Release containers that are based on the next stable fedora release (beta) ( would be f28 currently) with the idea to have these available for testing. This process would exclude rebuilding the f26 and rawhide based containers. Any feedback on this proposition ? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/439

5 11

Re: [atomic-devel] Fedora Atomic Community Meeting Minutes 2018-04-03
by Sinny Kumari 04 Apr '18

04 Apr '18

On Wed, Apr 4, 2018 at 2:59 AM, Sanja Bonic <sanja(a)redhat.com> wrote: > Thanks again for leading the meeting and thanks to everyone who > participated as well. :) > You are welcome :) > On Tue, Apr 3, 2018 at 2:36 PM, Matthias Clasen <mclasen(a)redhat.com> > wrote: > >> >> >> On Tue, Apr 3, 2018 at 8:13 AM Dusty Mabe <dusty(a)dustymabe.com> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA256 >>> >>> Thanks Sinny for running this!! I have some responses to the questions >>> below (and some suggestions) inline: >>> >>> On 04/03/2018 02:10 AM, Sinny Kumari wrote: >>> >>> > ========================================== >>> > #fedora-meeting-1: fedora_atomic_community >>> > ========================================== >>> >>> Might be good if we named this similar to our other meeting, but with >>> APAC in >>> the title: #startmeeting fedora_atomic_wg_apac. And then the Subject of >>> this >>> mail could be "Fedora Atomic WG APAC Meeting Minutes". >>> >>> >>> > Action Items >>> > ------------ >>> > * ksinny get answer for "Is there any plan to have a default flatpak >>> > repo eventually ? e.g. flathub, maybe on provided by fedora, etc" >>> >>> I think there is a plan to have a fedora flatpak repo (built from Fedora >>> RPMs) at some point in the future. For now flathub is the way to go. >>> >>> >>> >> Hey Sinny, >> >> yes, we need to have flatpaks enabled by default, eventually, since that >> is the >> preferred way to get desktop apps on an atomic workstation. >> >> We are working towards having flatpaks built from rpms inside fedora, >> which >> will give us a repository we can enable by default without problems. Most >> of >> the code for this has been written, it just takes some time to get it >> deployed >> in production. >> >> We also need the ability to have flatpaks preinstalled on an atomic >> workstation, >> so we can stop including things like firefox in the OS image and use a >> flatpak >> for that instead. >> >> I have created tickets for these issues here: >> https://pagure.io/fedora-atomic-workstation/issue >> >> Matthias >> > > -- http://sinny.io/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) April 2018