February 2018 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #409: no rawhide atomic workstation ostree composes for a month
by Pete Walter 18 Feb '18

18 Feb '18

pwalter reported a new issue against the project: `atomic-wg` that you are following: `` There's an up to date F27 atomic workstation repo at https://dl.fedoraproject.org/pub/ostree/27 , but it seems to be only for F27 and doesn't have any rawhide content. dustymabe pointed me to the older https://kojipkgs.fedoraproject.org/compose/ostree/rawhide/ repo, which however hasn't been updated for a month now. According to https://kojipkgs.fedoraproject.org/compose/ostree/rawhide/refs/heads/fedora… the last timestamp is 2017-12-18 09:27 dustymabe said on irc that rawhide composes must have been failing and asked me to file this ticket. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/409

5 11

[atomic-wg] Issue #411: release: find way to inspect created artifacts to make sure they have correct ostree version
by Dusty Mabe 16 Feb '18

16 Feb '18

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` As part of a FAH release we go through each architecture to make sure that the qcow that was created has the same ostree version # across them all. This is to prevent us from doing a release with artifacts that have mismatched ostree versions. It would be nice for us to automate this discovery so we don't have to do it by hand. Some options are: - leverage out test systems to report ostree version/commit in the results - somehow get pungi/koji/imagefactory to report the ostree version/commit that was used when creating the image (might be able to do this with icicle) - pull down the images with some script and use guestfish/libguestfs to verify. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/411

3 3

[atomic-wg] Issue #423: Failed to start Create Volatile Files and Directories on ppc64le
by J McVicker 15 Feb '18

15 Feb '18

tux808 reported a new issue against the project: `atomic-wg` that you are following: `` Performed default install Fedora-Atomic-ostree 27-20180212.2 for ppc64le & x86_64 platforms. Both installed successfully, but first-boot on ppc64le edition fails with systemd error: Failed to start Create Volatile Files and Directories.. then dropped into emergency dracut:/# prompt. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/423

2 4

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

14 Feb '18

=================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by miabbott at 16:31:01 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-14/fedora_atomic… . Meeting summary --------------- * roll call (miabbott, 16:31:18) * previous meeting action items (miabbott, 16:35:34) * dusty created ticket for evaluating podman in a few months (dustymabe, 16:36:08) * LINK: https://pagure.io/atomic-wg/issue/422 (dustymabe, 16:36:11) * LINK: https://pagure.io/atomic-wg/issue/421 (dustymabe, 16:37:24) * LINK: https://pagure.io/atomic-wg/issue/421 (miabbott, 16:37:27) * Design Meetings over Video (miabbott, 16:38:55) * LINK: https://pagure.io/atomic-wg/issue/418 (miabbott, 16:39:16) * ACTION: dustymabe to schedule february VFAD a CFP for proposed topics (dustymabe, 16:40:31) * Identify users for docker hub auto builds for system containers (miabbott, 16:41:33) * LINK: https://pagure.io/atomic-wg/issue/379 (miabbott, 16:41:40) * ACTION: dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership (dustymabe, 16:51:48) * open floor (miabbott, 16:55:28) * update on AWS Marketplace: FAH 27.72 is making the way through preliminary scans. (miabbott, 16:57:53) * LINK: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/using-cloud-i… (jdoss, 16:58:38) * ACTION: davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 (miabbott, 17:04:48) * waiting on input from mattdm about publishing Fedora images to Azure (miabbott, 17:07:03) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (dustymabe, 17:09:08) * a list of common problems affecting users: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (dustymabe, 17:10:00) * common problems users are hitting with Atomic Host/Workstation (miabbott, 17:10:10) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:10:11) * submit ideas for docs/guides/faqs on projectatomic site (miabbott, 17:12:44) * LINK: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-Feb… (miabbott, 17:12:46) * LINK: https://github.com/projectatomic/atomic-site-new/tree/master/ideas (miabbott, 17:12:54) * the first Atomic Workstation SIG meeting will be on Monday 02/19 (dustymabe, 17:14:05) * LINK: https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG/Agenda (dustymabe, 17:14:12) * ACTION: sanja to create ticket on eliminating redundant mailing lists + irc channels (miabbott, 17:20:21) * ACTION: sanja to create irc tutorial to onboard newcomers from slack, etc (miabbott, 17:23:00) * ACTION: misc to open ticket on the irc bot (miabbott, 17:27:22) * LINK: https://fedoramagazine.org/3-fedora-videos-devconf-cz-2018/ (dustymabe, 17:29:09) * new Project Atomic site (miabbott, 17:29:22) * LINK: http://new.projectatomic.io/ (miabbott, 17:29:27) Meeting ended at 17:33:47 UTC. Action Items ------------ * dustymabe to schedule february VFAD a CFP for proposed topics * dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership * davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 * sanja to create ticket on eliminating redundant mailing lists + irc channels * sanja to create irc tutorial to onboard newcomers from slack, etc * misc to open ticket on the irc bot Action Items, by person ----------------------- * davdunc * davdunc to inform WG about AWS scan results of Fedora Atomic Host 27.72 * dustymabe * dustymabe to schedule february VFAD a CFP for proposed topics * misc * misc to open ticket on the irc bot * sanja * sanja to create ticket on eliminating redundant mailing lists + irc channels * sanja to create irc tutorial to onboard newcomers from slack, etc * **UNASSIGNED** * dusty to send email to existing members of PA docker hub org and proposed new members to solidify membership People Present (lines said) --------------------------- * dustymabe (93) * miabbott (78) * sanja (66) * ashcrow (37) * zodbot (28) * misc (18) * walters (17) * jbrooks (15) * davdunc (10) * jdoss (7) * giuseppe (7) * lorbus (6) * mclasen (5) * jlebon (4) * rubao (3) * imcleod (1) * strigazi (1) * ksinny (1) * gscrivano (0) * smilner (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

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

13 Feb '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-02-14 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 #388: Add Fedora AMIs to govcloud region.
by David Duncan 08 Feb '18

08 Feb '18

davdunc reported a new issue against the project: `atomic-wg` that you are following: `` There are currently no Fedora images in the AWS govcloud region. To publish images in the govcloud, we must follow the ITAR guidelines. The AWS GovCloud (United States) region supports United States International Traffic in Arms Regulations (ITAR) compliance. International Traffic in Arms Regulations (ITAR) controls the export of defense-related articles and states that no non-US person can have physical or logical access to the articles stored in the ITAR environment. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/388

2 2

[atomic-wg] Issue #394: Write up on using other docker versions on Atomic Host
by Steve Milner 07 Feb '18

07 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` We need to have documentation showing how to use other docker versions on Atomic Host in the event the admin wishes to use an alternate docker runtime. References: - https://jebpages.com/2017/11/08/install-docker-ce-on-fedora-atomic-host-if-… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/394

4 12

Fedora Atomic WG Meeting Minutes 2018-02-07
by Dusty Mabe 07 Feb '18

07 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:31:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-02-07/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:31:48) * previous meeting action items (dustymabe, 16:35:47) * cri-o/podman in Atomic Host (dustymabe, 16:36:54) * LINK: https://pagure.io/atomic-wg/issue/407 (dustymabe, 16:37:10) * LINK: https://medium.com/cri-o/introducing-kpod-f06109b96374 (ashcrow, 16:42:31) * LINK: https://bodhi.fedoraproject.org/updates/FEDORA-2018-665045691d (miabbott, 16:46:27) * dwalsh | podman is just showing up in Fedora now, https://bodhi.fedoraproject.org/updates/FEDORA-2018-665045691d (dustymabe, 16:47:36) * ACTION: dustymabe to create new ticket for evaluating podman in a few months (dustymabe, 16:56:20) * Design Meetings over Video (dustymabe, 17:02:00) * LINK: https://pagure.io/atomic-wg/issue/418 (dustymabe, 17:02:08) * LINK: https://pagure.io/atomic-wg/blob/master/f/README.md (dustymabe, 17:06:47) * we'll try to have a few VFADs over the coming months to work through some design discussions surround system containers and also atomic host (dustymabe, 17:08:59) * open floor (dustymabe, 17:13:04) * submit ideas for new docs - https://github.com/projectatomic/atomic-site-new/tree/master/ideas (miabbott, 17:15:51) * we did an interview with linux unplugged to talk about fedora atomic host/workstation http://www.jupiterbroadcasting.com/122172/atomic-neon-kool-aid-lup-235/ (dustymabe, 17:15:56) * LINK: http://www.jupiterbroadcasting.com/122172/atomic-neon-kool-aid-lup-235/ (dustymabe, 17:16:02) * you can try out jigdo with Fedora Atomic Host Continuous - https://pagure.io/fedora-atomic-host-continuous (miabbott, 17:16:24) * devconf.us CFP is open (dustymabe, 17:16:56) * ACTION: sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks (dustymabe, 17:18:16) * LINK: http://www.projectatomic.io/blog/2018/02/fedora-atomic-workstation/ (dustymabe, 17:24:53) * LINK: http://www.projectatomic.io/blog/2018/02/fedora-atomic-workstation/ (dustymabe, 17:24:58) Meeting ended at 17:28:28 UTC. Action Items - ------------ * dustymabe to create new ticket for evaluating podman in a few months * sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks Action Items, by person - ----------------------- * dustymabe * dustymabe to create new ticket for evaluating podman in a few months * sanja * sanja to create ticket in atomic-wg pagure for coordinating devconf.us talks * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (156) * sanja (38) * ashcrow (36) * zodbot (34) * dwalsh (22) * miabbott (13) * jbrooks (12) * walters (10) * mrguitar (9) * lorbus (8) * misc (6) * davdunc (6) * giuseppe (5) * sayan (4) * clcollins (3) * jligon (2) * jlebon (2) * rubao|laptop (2) * puiterwijk (1) * strigazi (1) * gs (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlp7USUACgkQMwLb1zlS 5nHmrBAAzpjoRd0BueqplwcbKJSoUhYYGDoVwZLIHbo/bzoM5PpyYrx5BOfKOKGM CnSGeOUtgl/bK5dwerFnlKh3FebWSVMlIVwP82oSlZj9GLeAChnH3krgZF6t+bSf biXu5t/0EdZgEBvNUSxIdZqN/MRwk2Ut9NOuIsucfjTkQxRDpiyI1RfRgnl29OCO ZlT2U8DdOepG0CY+KgFtRE8xUpazaoq4pROCmjbFl4ZTfVEUr84NbMOn609Mq2FW pU0fMFer01sT6VMBYwDswFA/vSCrSyCn/Z09dpazgmYMjoJcF1mNNK3FZs5gAfBZ k/DNxkxqdmHiJRO70DmghbPVv9NNS0bidcR+1LhlnGvp7yLeYGF7RkA7Xo+gTDmb rSmber12JZ0Uh20vBUdK1RH0pvyifRhODuJuqmdGjlKh+mvW2tkXPTN6cgeaih0U TxL0/vPfxvWDheK9Nm65+PNrbY1bgKz4AKBdlOExfC8YOSWbRVosCvLfMX5wZe6g J1gFfyYNxbdtpW4x+toJwsEijoskpg2Zx/WVzXF/VppMEU5FPp80MiJManS9o//p mRoOhBCylPx6TK7FreXaysqoNbIIHUO82m99qzR1svP3F9CuvWbeLn1wEbHPRk7W X88542kxo59zu1WTBr4iidvFQSK1K4jA9uw7kaJnPHP/RolcB/0= =OftR -----END PGP SIGNATURE-----

1 0

[atomic-wg] Issue #407: cri-o in Atomic Host
by Steve Milner 07 Feb '18

07 Feb '18

smilner reported a new issue against the project: `atomic-wg` that you are following: `` In [this ticket](https://pagure.io/atomic-wg/issue/360) is was decided to continue to keep ``docker`` in the base. However, we want to make sure that people have the option to use ``cri-o`` as their container runtime if they would like to do so (and possibly other runtimes in the future). For consistency it would seem ``cri-o`` should be added to base as well but this would increase the size. However, we already have system containers for both ``cri-o`` and ``docker``. How can we provide a good ``cri-o`` experience for our Atomic Host user base keeping in mind that ``docker`` will be part of the base already? /cc @dwalsh @mpatel `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/407

3 7

Fedora Atomic Workstation questions
by Elad Alfassa 07 Feb '18

07 Feb '18

Hi all, I have some questions regarding Fedora Atomic Workstation: 1) How do 3rd party repositories (such as ones providing nonfree drivers, which obviously can't be containerized) work with rpm-ostree? If our end goal is for users to be able to use Fedora Atomic Workstation for every usecase they use Fedora Workstation for today, we need a plan for this. One possible solution (which isn't exactly the most clean one, but it might work) is to allow /usr/local to be writable, and allow it to be managed with package management tools such as dnf. This will also be useful for legacy software which people still need to use, but can't be containerized easily. 3) I understand the benefit of containerizing my workstation. However, I'm not sure everything I do can be done in a container. For example, if I want to hack on a system-level DBus service. What's the proposed workflow for this? keep in mind I don't want to just make temporary changes that'll disappear after a reboot, because I want to be able to use my service even if it never finds its way into Fedora proper (since it probably won't). Am I supposed to create a container and expose DBus (and other system stuff my service might need) to the container? And what if I want to hack on the container runtime itself? :) 4) If I have a container for development, this means that I have to have two copies of coreutils, openssh, and most system libraries/utilities. One copy, the "host", is updated by rpm-ostree. But what about the copy on the container? I'll have to remember to manually rebuild it on every update, or manually run "dnf update" in the container, which is not ideal (i'll probably forget, and end up running insecure/buggy software). Would it be possible to build a container based on the host filesystem in such a way that all basic system libraries and utilities are accessible directly (not as a copy) for the container? Alternatively, would some mechanism for automatic re-building of the container images after every ostree update is done can be created? 5) Do we expect every developer using Fedora to write their own Dockerfile / Buildah script for their development environment? I think that's a bit too much overhead and we need to at least have a utility to automatically generate these based on some common configurations, and the usage might look something like create_dev_container --langauges=rust,python,c --additional-packages=ffmpeg I like the idea of Atomic Workstation, and I want it to become our default offering one day, but I think that before we get there we have to figure out this kind of stuff. (Maybe you already did and I just missed the documentation?) Thanks, -- -Elad.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) February 2018