March 2020 - IoT - Fedora Mailing-Lists

by Chris Murphy

Hi, This is a systemd generator for setting up swap on zram. If a configuration file, /etc/systemd/zram-generator.conf, does not exist, nothing happens. If it does exist, a zram device is created, swap-create(a)zram0.service is created and started, which does mkswap and swapon using the same systemd logic found with either GPT swap autodiscovery (using partition type GUID) and /dev/urandom based swap. https://github.com/systemd/zram-generator This has been packaged in Fedora as 'zram-generator'. While zram package works fine and I see no problems with it, I'm liking the idea of converging on zram-generator, to use existing logic, maintenance and bug fixing. It's also an example of a generator made in Rust. I've found a few issues, reported upstream, but I don't think any of them negatively impact IoT. https://github.com/systemd/zram-generator/issues There's maybe a 50/50 chance we'll get this going in Workstation for Fedora 32 in lieu of a conventional swap partition (pretty much what IoT has been doing from the start, correct?). But I expect to propose it as a system-wide change for Fedora 33. The idea is to make the generator available system wide; and then we can discuss whether to: 1. enable it by default, by including a one size fits all configuration; which any edition/spin can opt-out by either deleting the configuration file or substituting it with their own 2. not enable it by default, by not including a configuration file; which any edition/spin can opt-in by including their own configuration file 3. what might possibly make sense as the most universal on size fits all configuration Based on the anaconda zram setup; the zram package setup; brief discussion upstream, and my own testing, I've arrived at: Create a zram device the same size as RAM (i.e. 1:1 ratio), with a cap of 2G or 4G. The rationale is, upstream says a zram device twice that of RAM is sane because expected compression ratio is 2:1. But going above that really makes no sense. Therefore a 1:1 ratio is conservative enough, but it's also reasonable to go with 1:2 (1/2 that of RAM, for the zram device size), depending on what IoT folks experience has been thus far. The ratio will affect small RAM devices more then workstations and servers, which I expect will pretty much always be subject to the cap. But if this isn't what upstream zram folks want to do, then it's not a big deal to just have a use case specific configuration files.

3 years, 10 months

2
3
0 / 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting

by pbrobinson＠fedoraproject.org

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-04-01 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting

by pbrobinson＠fedoraproject.org

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-04-01 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9245/

4 years

1
0
0 / 0

Voting now open for IoT edition name

by Ben Cotton

Voting is now open via the Elections app[1] for the IoT Edition's name. See the wiki[2] for a full timeline and an explanation behind the names. Voting will end at 2359 UTC on Wednesday 25 March. [1] https://elections.fedoraproject.org/about/iot_name [2] https://fedoraproject.org/wiki/IoT/Name -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

4 years

3
3
0 / 0

Fedora IoT Working Group Meeting Minutes 2020-03-25

by Paul Whalen

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 14:00:07 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2020-03-25/fedora_iot_wo... . Meeting summary --------------- * roll call (pwhalen, 14:00:08) * 1) ==== Working Group process and admin ==== (pwhalen, 14:02:36) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 14:02:36) * voting still open for the name (pbrobinson, 14:03:47) * LINK: https://elections.fedoraproject.org/vote/iot_name (pbrobinson, 14:03:50) * 2) ==== Fedora 31 status ==== (pwhalen, 14:06:59) * Latest compose available for testing (pwhalen, 14:06:59) * LINK: https://kojipkgs.fedoraproject.org/compose//iot/Fedora-IoT-31-20200321.0/ (pwhalen, 14:06:59) * No issues reported in F31. (pwhalen, 14:09:52) * 3) ==== Fedora 32 status ==== (pwhalen, 14:10:49) * Latest compose available for testing (pwhalen, 14:10:49) * LINK: https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-32-20200324.0/c... (pwhalen, 14:11:04) * we have an online provisioning tool now for F-32 https://provision.fedoraproject.org/ (pbrobinson, 14:11:42) * Test results for the latest nominated compose: https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT/Fedora-IoT-32-20200322.1 (pwhalen, 14:12:09) * Fedora 32 Final Freeze 2020-04-07 (pwhalen, 14:29:42) * Fedora 32 Final release date 2020-04-21 (pwhalen, 14:30:04) * Test day scheduled for April 8th. (pwhalen, 14:36:23) * 4) ==== Open Floor ==== (pwhalen, 14:37:26) Meeting ended at 14:40:09 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (57) * pbrobinson (25) * coremodule (11) * zodbot (9) * tdawson (8) * lorbus (7) * dressedfez (1) * bcotton (0) * puiterwijk (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting

by pbrobinson＠fedoraproject.org

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-03-25 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting

by pbrobinson＠fedoraproject.org

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2020-03-25 from 14:00:00 to 15:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9245/

4 years

1
0
0 / 0

Fedora IoT Working Group Meeting Minutes 2020-03-11

by Paul Whalen

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 14:00:15 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2020-03-11/fedora_iot_wo... . Meeting summary --------------- * roll call (pwhalen, 14:00:16) * 1) ==== Working Group process and admin ==== (pwhalen, 14:03:13) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 14:03:13) * LINK: https://fedoraproject.org/wiki/IoT/Name (pbrobinson, 14:04:42) * LINK: https://communityblog.fedoraproject.org/help-us-name-the-fedora-iot-edition/ (pbrobinson, 14:04:56) * the deadline for submitting name suggestions is Sunday 15 March (bcotton, 14:05:09) * 2) ==== Fedora 31 status ==== (pwhalen, 14:11:20) * Latest compose available for testing (pwhalen, 14:11:20) * LINK: https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-31-20200223.0/c... (pwhalen, 14:11:20) * No issues reported in Fedora 31. (pwhalen, 14:13:22) * 3) ==== Fedora 32 status ==== (pwhalen, 14:14:17) * Latest compose available for testing (pwhalen, 14:14:17) * LINK: https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-32-20200310.0/c... (pwhalen, 14:14:17) * LINK: https://fedoraproject.org/wiki/Releases/32/ReleaseBlocking (bcotton, 14:15:23) * Pull fails with: Image architecture mismatch: image uses "aarch64", expecting "arm64" (pwhalen, 14:30:44) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1793927 (pwhalen, 14:30:51) * 4) ==== Open Floor ==== (pwhalen, 14:34:59) Meeting ended at 14:37:20 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (40) * bcotton (16) * pbrobinson (13) * zodbot (9) * tdawson (6) * coremodule (2) * puiterwijk (2) * jsmith (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

4 years, 1 month

1
0
0 / 0

Fedora IoT Working Group Meeting Minutes 2020-03-18

by Paul Whalen

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 14:04:03 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2020-03-18/fedora_iot_wo... . Meeting summary --------------- * roll call (pwhalen, 14:04:03) * 1) ==== Working Group process and admin ==== (pwhalen, 14:06:42) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 14:06:42) * voting is open for the name (pbrobinson, 14:07:47) * LINK: https://elections.fedoraproject.org/about/iot_name (pbrobinson, 14:07:50) * Voting will end at 2359 UTC on Wednesday 25 March. (pwhalen, 14:10:54) * 2) ==== Fedora 31 status ==== (pwhalen, 14:12:29) * Expect a new F31 compose this week with 5.5.10 which will include some intel wifi fixes. (pwhalen, 14:13:56) * 3) ==== Fedora 32 status ==== (pwhalen, 14:14:15) * Fedora 32 Beta shipped yesterday (March 17th). (pwhalen, 14:15:09) * Fedora 32 IoT Beta compose - https://kojipkgs.fedoraproject.org/compose//iot/Fedora-IoT-32-20200314.0/ (pwhalen, 14:15:42) * Testing F32 Beta IoT compose - https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT/Fedora-IoT-32-20200314.0 (pwhalen, 14:16:33) * LINK: https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT/Fedora-IoT-32-20200314.0 (pwhalen, 14:22:11) * 4) ==== Fedora 33 Status ==== (pwhalen, 14:31:36) * Nothing of note for Fedora 33. (pwhalen, 14:33:26) * 5) ==== Open Floor ==== (pwhalen, 14:33:53) * please start to thing about F-33 features (pbrobinson, 14:36:56) Meeting ended at 14:37:32 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (40) * pbrobinson (25) * zodbot (7) * bcotton (2) * tdawson (2) * puiterwijk (2) * coremodule (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

4 years, 1 month

1
0
0 / 0

Re: Emerging editions, Fedora 32 Beta, and bureaucracy

by Kamil Paral

On Tue, Mar 17, 2020 at 10:11 PM Mohan Boddu <mboddu(a)bhujji.com> wrote: > Peter and I talked about it a while ago about merging IoT into regular > Fedora composes. But we never got to that point. I am not sure whats > their plan moving forward. My idea is to merge them together and keep > their composes as it is for their testing. > Hey Mohan! If IoT folks don't reply to this particular issue in a few days, can we simply assume merging the composes is the best way forward for everyone and just do it? :) I see only benefits. This all seems like a communication issue to me, nobody wants to kick the ball and move things forward, and everyone else is stalled. Thanks!

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

IoT March 2020