October 2017 - Atomic Working Group (ARCHIVED)

[atomic-wg] Issue #343: automatically extend root filesystem to all available disk space for cloud images
by Dusty Mabe 06 Oct '17

06 Oct '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Since we moved to a new model where we are only using overlay2 on top of the root filesystem (default), we need to automatically extend the root filesystem to fill up the root VG by default, unless the user modifies docker-storage-setup config file and tells us to do otherwise. I opened a [PR](https://github.com/projectatomic/container-storage-setup/pull/258) for this functionality to be added to container-storage-setup. The new version of that rpm is in updates-testing. We'll update the kickstarts to properly take advantage of this soon. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/343

1 3

[atomic-wg] Issue #217: Move python container image from Fedora-Dockerfiles GitHub into DistGit
by Tomas Tomecek 06 Oct '17

06 Oct '17

ttomecek added a new comment to an issue you are following: `` @torsava is from @hhorak's team and could yield some updates `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/217

1 0

2wk atomic release candidate: 20171003
by Dusty Mabe 05 Oct '17

05 Oct '17

Tomorrow we will attempt to release the 20171003 images. These images contain the following ostree version/commit: 26.141 541abd650d1ffb3929e2ba8114436a0b04ee41da76a691af669dd037589a1421 The atomic host VM images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-2017100… The ISO image is here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-2017100… The AMIs are here: Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-northeast-1) ami-a8f627ce hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-southeast-1) ami-6296ea01 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-southeast-2) ami-b7a340d5 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (eu-central-1) ami-0a43f165 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (eu-west-1) ami-ca11c5b3 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (sa-east-1) ami-547a0538 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-east-1) ami-da25dea0 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-west-1) ami-e090a080 hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-west-2) ami-75a55f0d hvm standard Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-northeast-1) ami-25f92843 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-southeast-1) ami-4a97eb29 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (ap-southeast-2) ami-37a24155 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (eu-central-1) ami-f65def99 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (eu-west-1) ami-3917c340 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (sa-east-1) ami-237c034f hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-east-1) ami-9027dcea hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-west-1) ami-f8af9f98 hvm gp2 Fedora-Atomic-26-20171003.0.x86_64 EC2 (us-west-2) ami-14a45e6c hvm gp2 The diff between this and the previous released version is: ostree diff commit old: 98088cb6ed2a4b3f7e4e7bf6d34f9e137c296bc43640b4c1967631f22fe1802f ostree diff commit new: 541abd650d1ffb3929e2ba8114436a0b04ee41da76a691af669dd037589a1421 Upgraded: audit 2.7.7-1.fc26.x86_64 -> 2.7.8-1.fc26.x86_64 audit-libs 2.7.7-1.fc26.x86_64 -> 2.7.8-1.fc26.x86_64 audit-libs-python 2.7.7-1.fc26.x86_64 -> 2.7.8-1.fc26.x86_64 audit-libs-python3 2.7.7-1.fc26.x86_64 -> 2.7.8-1.fc26.x86_64 boost-iostreams 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 boost-program-options 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 boost-random 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 boost-regex 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 boost-system 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 boost-thread 1.63.0-7.fc26.x86_64 -> 1.63.0-8.fc26.x86_64 cockpit-bridge 150-1.fc26.x86_64 -> 151-1.fc26.x86_64 cockpit-docker 150-1.fc26.x86_64 -> 151-1.fc26.x86_64 cockpit-networkmanager 150-1.fc26.noarch -> 151-1.fc26.noarch cockpit-ostree 150-1.fc26.x86_64 -> 151-1.fc26.x86_64 cockpit-system 150-1.fc26.noarch -> 151-1.fc26.noarch container-selinux 2:2.22-1.fc26.noarch -> 2:2.24-1.fc26.noarch dbus 1:1.11.16-1.fc26.x86_64 -> 1:1.11.18-1.fc26.x86_64 dbus-libs 1:1.11.16-1.fc26.x86_64 -> 1:1.11.18-1.fc26.x86_64 etcd 3.1.3-1.fc26.x86_64 -> 3.1.9-1.fc26.x86_64 gsettings-desktop-schemas 3.24.0-1.fc26.x86_64 -> 3.24.1-1.fc26.x86_64 kernel 4.12.13-300.fc26.x86_64 -> 4.12.14-300.fc26.x86_64 kernel-core 4.12.13-300.fc26.x86_64 -> 4.12.14-300.fc26.x86_64 kernel-modules 4.12.13-300.fc26.x86_64 -> 4.12.14-300.fc26.x86_64 libblkid 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 libfdisk 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 libmount 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 libpkgconf 1.3.8-1.fc26.x86_64 -> 1.3.9-1.fc26.x86_64 libreport-filesystem 2.9.1-2.fc26.x86_64 -> 2.9.1-3.fc26.x86_64 libsmartcols 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 libsolv 0.6.29-1.fc26.x86_64 -> 0.6.29-2.fc26.x86_64 libssh2 1.8.0-2.fc26.x86_64 -> 1.8.0-5.fc26.x86_64 libsss_idmap 1.15.3-3.fc26.x86_64 -> 1.15.3-4.fc26.x86_64 libsss_nss_idmap 1.15.3-3.fc26.x86_64 -> 1.15.3-4.fc26.x86_64 libsss_sudo 1.15.3-3.fc26.x86_64 -> 1.15.3-4.fc26.x86_64 libuuid 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 linux-firmware 20170828-76.gitb78acc9.fc26.noarch -> 20170828-77.gitb78acc9.fc26.noarch nss 3.32.0-1.1.fc26.x86_64 -> 3.32.1-1.0.fc26.x86_64 nss-sysinit 3.32.0-1.1.fc26.x86_64 -> 3.32.1-1.0.fc26.x86_64 nss-tools 3.32.0-1.1.fc26.x86_64 -> 3.32.1-1.0.fc26.x86_64 oci-register-machine 0-3.10.gitcbf1b8f.fc26.x86_64 -> 0-5.11.gitcd1e331.fc26.x86_64 ostree 2017.10-2.fc26.x86_64 -> 2017.11-1.fc26.x86_64 ostree-grub2 2017.10-2.fc26.x86_64 -> 2017.11-1.fc26.x86_64 ostree-libs 2017.10-2.fc26.x86_64 -> 2017.11-1.fc26.x86_64 pkgconf 1.3.8-1.fc26.x86_64 -> 1.3.9-1.fc26.x86_64 pkgconf-m4 1.3.8-1.fc26.noarch -> 1.3.9-1.fc26.noarch pkgconf-pkg-config 1.3.8-1.fc26.x86_64 -> 1.3.9-1.fc26.x86_64 python2-pyOpenSSL 16.2.0-5.fc26.noarch -> 16.2.0-6.fc26.noarch python3 3.6.2-5.fc26.x86_64 -> 3.6.2-7.fc26.x86_64 python3-docker 2.5.1-1.fc26.noarch -> 2.5.1-2.fc26.noarch python3-libs 3.6.2-5.fc26.x86_64 -> 3.6.2-7.fc26.x86_64 python3-pyOpenSSL 16.2.0-5.fc26.noarch -> 16.2.0-6.fc26.noarch python3-sssdconfig 1.15.3-3.fc26.noarch -> 1.15.3-4.fc26.noarch selinux-policy 3.13.1-260.8.fc26.noarch -> 3.13.1-260.10.fc26.noarch selinux-policy-targeted 3.13.1-260.8.fc26.noarch -> 3.13.1-260.10.fc26.noarch sssd-client 1.15.3-3.fc26.x86_64 -> 1.15.3-4.fc26.x86_64 system-python 3.6.2-5.fc26.x86_64 -> 3.6.2-7.fc26.x86_64 system-python-libs 3.6.2-5.fc26.x86_64 -> 3.6.2-7.fc26.x86_64 util-linux 2.30.1-1.fc26.x86_64 -> 2.30.2-1.fc26.x86_64 Removed: compat-openssl10-1:1.0.2j-9.fc26.x86_64 Added: libsoup-2.58.2-1.fc26.x86_64 A new kernel and new version of ostree are the most notable changes. Dusty

2 5

[atomic-wg] Issue #335: Fedora-Atomic-26 odd networking behavior
by Dimitris Theoharis 05 Oct '17

05 Oct '17

dimtheo reported a new issue against the project: `atomic-wg` that you are following: `` hello using this image Fedora-Atomic-26-20170821.0.x86_64.qcow2 with magnum to deploy a kube cluster , i found out some issues with networking and im not sure if there is something wrong with the image or not. first of all if i just create a single instance using the above image and i ssh into it , networking is fine and fast as it should be. The problems begin when i use that image with magnum to deploy a cluster then the networking become so slow to the point where its useless. It takes 25 min to docker pull even the smallest images from docker hub , it will take 10 seconds to let you ssh from one minion to another etc . I can verify there are no networking problems in the openstack cloud and all other instances outside of kubernetes have no such problems . there is plenty of ram and disk space available as well in the master and 2 minions as well so i would like to ask if someone else has experienced a similar issue ? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/335

3 10

[atomic-wg] Issue #325: atomic host two week release emails don't make it to the atomic-devel list
by Michael Scherer 05 Oct '17

05 Oct '17

misc added a new comment to an issue you are following: `` Ok so I did open a ticket with our IT and will handle information gathering, etc, etc. I can't promise a miracle (and for tracking purpose, our internal ticket number is "INC0617469") `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/325

1 0

[atomic-wg] Issue #325: atomic host two week release emails don't make it to the atomic-devel list
by Dusty Mabe 05 Oct '17

05 Oct '17

dustymabe added a new comment to an issue you are following: `` Update from Patrick: ``` 11:15:29 dustymabe | hey puiterwijk - the 2 week atomic release emails still don't seem to be making it to the atomic-devel mailing list 11:16:41 <-- | miminar (miminar@nat/redhat/x-vlxfkiszhbgukohj) has quit (Ping timeout: 240 seconds) 11:16:52 puiterwijk | dustymabe: at this moment, there's nothing I can do about that, since the projectatomic.io mailservers are actively refusing | our connection 11:17:43 --> | crose (~crose(a)132.237.154.126) has joined #atomic 11:17:59 dustymabe | puiterwijk: question: did we get farther this time? i.e. was there a dns problem before (now fixed) and now there is a | connection refused problem? 11:18:12 puiterwijk | dustymabe: yes, we got much farther. There was no DNS issues 11:18:28 dustymabe | puiterwijk: thanks, can you update the issue with that information? 11:18:31 puiterwijk | Oct 5 13:25:08 bastion01 postfix/smtp[6427]: 5486361F01C4: to=<atomic-devel(a)projectatomic.io>, relay=none, delay=38278, | delays=38275/3/0.08/0, dsn=4.4.1, status=deferred (connect to mx2.redhat.com[10.11.203.6]:25: Connection refused) 11:18:43 dustymabe | i can try to resolve it with misc 11:19:00 puiterwijk | misc can't help with that. You'll need RHIT 11:19:33 dustymabe | sure - but I need someone to handle talking to RHIT, I believe 11:19:45 puiterwijk | dustymabe: servicenow :) 11:20:24 dustymabe | so no one in OSAS is at least somewhat responsible for the lists? 11:20:38 dustymabe | i would have assumed misc 11:20:49 puiterwijk | Nope, nobody ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/325

1 0

[atomic-wg] Issue #325: atomic host two week release emails don't make it to the atomic-devel list
by Dusty Mabe 05 Oct '17

05 Oct '17

dustymabe added a new comment to an issue you are following: `` still not working - the release announcement did not make it to the list but [my reply](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-October/msg00023.html) did. Here is the thread view: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-Oct… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/325

1 0

[atomic-wg] Issue #333: removing gluster/ceph rpms from base atomic host
by Dusty Mabe 05 Oct '17

05 Oct '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` These were removed as part of the [remove of kube](https://pagure.io/fedora-atomic/c/7d50906d91097f6eef4af91a6f693b98c57a9b91?branch=master). They were originally added [here](https://pagure.io/fedora-atomic/c/a1f7373f66d10150349aa7e1869c22ad9ebb78c8?branch=master) as a result of [this BZ](https://bugzilla.redhat.com/show_bug.cgi?id=1303546) We need to determine if tools like openshift-ansible depend on them being in the host for gluster storage to work or if it all works inside containers for them. A longer term approach would be to get package layering support in an ansible module so that we could worry about stuff like this less. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/333

5 17

[atomic-wg] Issue #344: Fix Atomic meeting location in Fedocal
by Justin W. Flory 05 Oct '17

05 Oct '17

jflory7 reported a new issue against the project: `atomic-wg` that you are following: `` # Summary The [current Atomic meeting](https://apps.fedoraproject.org/calendar/meeting/6370/) location is set to `fedora-meeting-1@freenode` instead of `fedora-meeting-1(a)irc.freenode.net`, putting it on its own calendar separate from other meetings in #fedora-meeting-1. # Quick fix Since @dustymabe created the event, I think he is the only one able to edit it. It should be easy enough to edit the location for all meetings. Since this is the only event set to this location, the accidental duplicate calendar should be erased after the Atomic meeting is updated. I brought this up in #atomic just now, but it was late and I think most people were already off for the night, and I knew I'd never remember after tonight, so a ticket seemed the best bet. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/344

2 5

Fedora Atomic WG Meeting Minutes 2017-10-04
by Dusty Mabe 04 Oct '17

04 Oct '17

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-04/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-04/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 17:02:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-04/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 17:02:15) * this weeks 26 atomic host release (dustymabe, 17:07:55) * we had one user report an issue with this weeks 26 atomic host candidate https://pagure.io/atomic-wg/issue/345 (dustymabe, 17:08:22) * plan to go ahead and release F26AH today and investigate minnowboard issues and report back upstream. (dustymabe, 17:13:16) * fedora 27 blocker/important bugs (dustymabe, 17:13:46) * LINK: https://pagure.io/atomic-wg/issue/331 (dustymabe, 17:13:51) * we are tracking issues related to Fedora 27 Atomic Host in this issue: https://pagure.io/atomic-wg/issue/331 (dustymabe, 17:14:29) * LINK: https://pagure.io/atomic-wg/issue/343 (dustymabe, 17:15:16) * LINK: https://fedoramagazine.org/fedora-27-atomic-cloud-test-day/ (dustymabe, 17:16:34) * test day report for f27 atomic host (dustymabe, 17:17:19) * LINK: http://testdays.fedorainfracloud.org/events/27 (dustymabe, 17:18:00) * how ready are we for fedora 27? (dustymabe, 17:21:01) * LINK: https://pagure.io/releng/issue/6984 (dustymabe, 17:23:56) * LINK: https://www.projectatomic.io/blog/2017/06/future-plans-for-fedora-atomic-re… (jbrooks, 17:25:11) * ACTION: dustymabe to update the rolling release plan with info about f27ah (dustymabe, 17:32:37) * ACTION: jberkus to identify and create issue with list of blog posts we want around f27 release time (dustymabe, 17:33:46) * ACTION: jbrooks to go through remove-kube items and update (jbrooks, 17:34:34) * ACTION: strigazi to do some testing around upgrades from f26 to f27 with kubernetes (dustymabe, 17:35:19) * previous meeting action items (dustymabe, 17:35:33) * ACTION: jbrooks to email fedora-devel with issue of needed deps for asciibinder container in fedora proper (dustymabe, 17:40:32) * ACTION: jberkus to follow up on partial container images from Flock (dustymabe, 17:44:08) * open floor (dustymabe, 17:44:11) * ACTION: dustymabe to open ticket to consider changing meeting time of atomic wg meeting (dustymabe, 17:56:28) Meeting ended at 17:58:23 UTC. Action Items ------------ * dustymabe to update the rolling release plan with info about f27ah * jberkus to identify and create issue with list of blog posts we want around f27 release time * jbrooks to go through remove-kube items and update * strigazi to do some testing around upgrades from f26 to f27 with kubernetes * jbrooks to email fedora-devel with issue of needed deps for asciibinder container in fedora proper * jberkus to follow up on partial container images from Flock * dustymabe to open ticket to consider changing meeting time of atomic wg meeting Action Items, by person ----------------------- * dustymabe * dustymabe to update the rolling release plan with info about f27ah * dustymabe to open ticket to consider changing meeting time of atomic wg meeting * jberkus * jberkus to identify and create issue with list of blog posts we want around f27 release time * jberkus to follow up on partial container images from Flock * jbrooks * jbrooks to go through remove-kube items and update * jbrooks to email fedora-devel with issue of needed deps for asciibinder container in fedora proper * strigazi * strigazi to do some testing around upgrades from f26 to f27 with kubernetes * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (137) * jberkus (40) * jbrooks (34) * strigazi (26) * zodbot (14) * ksinny (5) * miabbott (3) * davdunc (2) * kushal (1) * sayan (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) October 2017