July 2017 - cloud - Fedora mailing-lists

Python is missing in Fedora AWS AMIs
by Danishka Navin 29 Dec '22

29 Dec '22

Hi team, Is there any specific reason to drop python from Fedora AMIs in AWS? Regards, -- Danishka Navin http://danishkanavin.blogspot.com http://twitter.com/danishkanavin

6 5

firewalld in atomic host
by Dusty Mabe 01 Nov '17

01 Nov '17

NOTE: if you respond to this message please 'reply-all'. I'd like to discuss firewalld on atomic host. Recently I was trying to figure out the best way to explain to other users how to set firewall rules on atomic host. Usually I would say add your rules and then iptables-save, but on Atomic Host docker has added it's firewall rules in there dynamically so if you iptables-save you'll get a bunch of stuff that you don't want in your static configuration. There are ways around this; manually create your config file, or use iptables-save and then rip the docker stuff out. Either way it's a bit of a pain. I think firewalld would make this easier on the user. Not sure of the pro/con ratio though. Thoughts? Dusty

4 8

rawhide compoe - error: unlinkat: No such file or directory
by Dusty Mabe 03 Sep '17

03 Sep '17

Have we ever seen this before? Comes today's rawhide compose [1] DEBUG util.py:439: Committing: 100% DEBUG util.py:439: error: unlinkat: No such file or directory DEBUG util.py:439: Traceback (most recent call last): DEBUG util.py:439: File "/usr/bin/pungi-make-ostree", line 15, in <module> DEBUG util.py:439: ostree.main() DEBUG util.py:439: File "/usr/lib/python2.7/site-packages/pungi/ostree/__init__.py", line 89, in main DEBUG util.py:439: func() DEBUG util.py:439: File "/usr/lib/python2.7/site-packages/pungi/ostree/tree.py", line 99, in run DEBUG util.py:439: self._make_tree() DEBUG util.py:439: File "/usr/lib/python2.7/site-packages/pungi/ostree/tree.py", line 46, in _make_tree DEBUG util.py:439: shortcuts.run(cmd, show_cmd=True, stdout=True, logfile=log_file) DEBUG util.py:439: File "/usr/lib/python2.7/site-packages/kobo/shortcuts.py", line 335, in run DEBUG util.py:439: raise RuntimeError(err_msg) DEBUG util.py:439: RuntimeError: ERROR running command: rpm-ostree compose tree --repo=/mnt/koji/compose/atomic/rawhide/ --write-commitid-to=/mnt/koji/compose/rawhide/Fedora-Rawhide-20170622.n.0/logs/x86_64/Atomic/ostree-3/commitid.log --add-metadata-string=version=Rawhide.20170622.n.0 /mnt/koji/compose/rawhide/Fedora-Rawhide-20170622.n.0/work/ostree-3/config_repo/fedora-atomic-docker-host.json DEBUG util.py:577: Child return code was: 1 DEBUG util.py:188: kill orphans [1] - https://koji.fedoraproject.org/koji/taskinfo?taskID=20101234

2 4

[fedora-atomic] PR #69: manifest: Add microcode_ctl
by Colin Walters 18 Aug '17

18 Aug '17

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` manifest: Add microcode_ctl `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/69

2 3

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by dusty＠dustymabe.com 31 Jul '17

31 Jul '17

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2017-08-02 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

[fedora-atomic] PR #27: post: Work around LVM archival conflicting with ostree
by Colin Walters 27 Jul '17

27 Jul '17

walters commented on the pull-request: `post: Work around LVM archival conflicting with ostree` that you are following: `` Yeah, but the priority for me dropped way way down since for Fedora now we don't use devicemapper by default for Docker, and that makes LVM make backups way less often. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/27

1 0

[fedora-atomic] PR #27: post: Work around LVM archival conflicting with ostree
by Jonathan Lebon 27 Jul '17

27 Jul '17

jlebon commented on the pull-request: `post: Work around LVM archival conflicting with ostree` that you are following: `` Would be nice to see this happen still. I'm sorely reminded of it every time I run `ostree admin config-diff` and have to swim through the output. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/27

1 0

[cloud-sig] Issue #280: new meeting time for cloud sig
by Dusty Mabe 27 Jul '17

27 Jul '17

dustymabe reported a new issue against the project: `cloud-sig` that you are following: `` Now that the atomic working group has gained more identity separate from Fedora Cloud SIG, let's find a new time for a meeting. My initial thoughts are Monday at 15:00 UTC and maybe every other week. `` To reply, visit the link below or just reply to this email https://pagure.io/cloud-sig/issue/280

4 5

Atomic Host Docs VFAD on Friday information & preparation
by Josh Berkus 26 Jul '17

26 Jul '17

Folks: As scheduled, we will be having a Virtual Fedora Activity Day focused on the Atomic Host documentation this Friday, July 28th. The day starts at 13:30 UTC (9:30 EDT, 19:00 IST), with a video conference before we split up for work. The rest of the program may be found on this etherpad: http://etherpad.osuosl.org/fedora_atomic_docs_vfad Before you come to the VFAD, please read that document. If you have a chance beforehand -- or if you cannot make it to the VFAD at all -- please comment on the proposed documentation content in the etherpad. Make sure and put your name in for your color so we know whose comments belong to whom. (note to folks on the cloud@ mailing list: we will soon stop using this mailing list for Atomic stuff. please sign up for atomic-devel) -- -- Josh Berkus Project Atomic Red Hat OSAS

1 0

Fedora Atomic Host Two Week Release Announcement
by noreply＠fedoraproject.org 26 Jul '17

26 Jul '17

A new Fedora Atomic Host update is available via an OSTree commit: Commit: 3fd888c674c6d69907eabc665103341e01ebe3a04c3876af6cac673b0bf43662 Version: 25.122 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-201705… https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-201705… For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

2 2

Announce: Fedora Layered Image Release
by Adam Miller 25 Jul '17

25 Jul '17

1 0

Fedora Atomic Host Two Week Release Announcement
by noreply＠fedoraproject.org 25 Jul '17

25 Jul '17

A new Fedora Atomic Host update is available via an OSTree commit: Commit: 0715ce81064c30d34ed52ef811a3ad5e5d6a34da980bf35b19312489b32d9b83 Version: 26.91 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-26-201707… https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-26-201707… For direct download, the "latest" targets are always available here: https://getfedora.org/atomic_iso_latest https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest Filename fetching URLs are available here: https://getfedora.org/atomic_iso_latest_filename https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename For more information about the latest targets, please reference the Fedora Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_Links Do note that it can take some of the mirrors up to 12 hours to "check-in" at their own discretion. Thank you, Fedora Release Engineering

1 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by dusty＠dustymabe.com 24 Jul '17

24 Jul '17

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2017-07-26 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

Changing json file name in fedora-atomic git repo
by Dusty Mabe 24 Jul '17

24 Jul '17

We recently changed the ref for atomic host in Fedora 26 to be `atomic-host` rather than `docker-host`. Similarly we'd like to change the name of the file within the repo [1] from fedora-atomic-docker-host.json to fedora-atomic-host.json. If anyone is pulling from this repo and building trees please update your files to use the new filename for the master and f26 branches. We have temporarily left a symlink for compatibility. I'll be removing that in a week or two and updating this mail when that happens. Dusty [1] https://pagure.io/fedora-atomic/blob/70e320ccb557ffd7f1bb14d6a6f0748843dc3d…

1 1

[fedora-atomic] PR #68: f26: remove json file symlink
by Dusty Mabe 24 Jul '17

24 Jul '17

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` f26: remove json file symlink `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/68

2 2

[fedora-atomic] PR #67: remove json file symlink
by Dusty Mabe 24 Jul '17

24 Jul '17

dustymabe opened a new pull-request against the project: `fedora-atomic` that you are following: `` remove json file symlink `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/67

2 2

[cloud-sig] Issue #279: stop creating PV AMIs for cloud base image
by Dusty Mabe 24 Jul '17

24 Jul '17

dustymabe reported a new issue against the project: `cloud-sig` that you are following: `` We still create PV AMIs for cloud base images. Since we don't really test them I'd like to stop so they don't cause confusion. Any objections? `` To reply, visit the link below or just reply to this email https://pagure.io/cloud-sig/issue/279

2 2

Fedora-Atomic 26-20170720.0 compose check report
by Fedora compose checker 20 Jul '17

20 Jul '17

Missing expected images: Atomic vagrant-libvirt x86_64 Atomic raw-xz x86_64 Atomic vagrant-virtualbox x86_64 Atomic qcow2 x86_64 Passed openQA tests: 2/2 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

1 0

FYI - pagure.io/atomic-wg emails are now going to atomic@list.fp.o
by Dusty Mabe 19 Jul '17

19 Jul '17

They will no longer be sent to the cloud list. Please subscribe to the atomic list if you wish to receive them: https://lists.fedoraproject.org/admin/lists/atomic.lists.fedoraproject.org/

1 0

Fedora Atomic WG - Changes to IRC/Mailing list
by Dusty Mabe 19 Jul '17

19 Jul '17

TL;DR There is a new fedora atomic mailing list [1] and IRC channel [2], but the mailing list should only be used for automated messages and the IRC channel should be used only when something extremely Fedora specific (like releng bits) is being discussed. Otherwise please use the upstream project atomic mailing list [3] and IRC channel [4] for everything. The cloud* list and IRC channel should be no longer used for atomic specific discussions. In an attempt to minimize the confusion around the relationship between the Fedora Atomic Working Group and the Fedora Cloud SIG we have decided [5] to have a new mailing list [1] and irc channel [2] for Fedora Atomic. Since there is an upstream project atomic mailing list [3] and irc channel [4] already we have decided that the new fedora atomic mailing list and irc channels should be narrow in focus and actually push discussion towards the upstream project atomic mailing list and irc channel. This is mostly so we can get more people talking about the same problems in one place and have some cross pollination. The new communication model: Mailing Lists: * atomic(a)lists.fedoraproject.org This list is for all automated messages and cc'd on announcements. It is not a discussion list; discussions on it will be either (a) cc'd to atomic-devel or (b) redirected to a pagure issue as appropriate. * atomic-devel(a)projectatomic.io will be used for all mailing list discussions. IRC: * all discussions of general topics around Fedora Atomic, including contents, containerized kube, container reviews, ostree changes, etc, etc. will be on #atomic. * discussions and troubleshooting Fedora build pipeline/releng (bodhi, punji, etc.) for Atomic will be on the new channel #fedora-atomic. Content discussions which start there will get re-directed to #atomic. Please take this opportunity to subscribe to any new mailing lists and join any new irc channels you find appropriate. Dusty [1] https://lists.fedoraproject.org/admin/lists/atomic.lists.fedoraproject.org/ [2] #fedora-atomic) on freenode [3] https://lists.projectatomic.io/mailman/listinfo/atomic-devel [4] #atomic on freenode [5] https://pagure.io/atomic-wg/issue/295

1 0

[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time
by Dusty Mabe 19 Jul '17

19 Jul '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` There is plenty of confusion still to be had around the previous form of the cloud working group and what the atomic working group is today. This is compounded by the fact that we still use the cloud mailing list and the #fedora-cloud IRC channel. While it may be inconvenient for those of us that want to follow both the fedora cloud base image and the fedora atomic group, I think it would benefit users/contributors if we more clearly delineated between cloud and atomic. Let's discuss/vote on using #fedora-atomic on freenode as well as the atomic(a)lists.fedoraproject.org mailing list? Note - The cloud base image has not gone anywhere. It will still be managed by the cloud-sig http://pagure.io/cloud-sig. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295

13 35

Minutes for meeting
by Josh Berkus 19 Jul '17

19 Jul '17

=================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by jberkus at 17:01:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-19/fedora_atomic… . Meeting summary --------------- * Roll Call (jberkus, 17:01:49) * action items from last meeting (jberkus, 17:04:28) * open meeting tickets (jberkus, 17:05:47) * Ticket 295 Mailing lists and IRC (jberkus, 17:09:22) * LINK: https://pagure.io/atomic-wg/issue/295 (dustymabe, 17:09:50) * ACTION: : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra (jberkus, 17:22:27) * ACTION: : dustymabe to update IRC channel topics to reflect new scheme (jberkus, 17:23:15) * ACTION: ksinny to update wiki (jberkus, 17:23:29) * ACTION: dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings (dustymabe, 17:24:17) * ACTION: jberkus to write blog post for fedora magazine/pa.io on changes (jberkus, 17:24:22) * open floor (jberkus, 17:26:30) * LINK: https://pagure.io/atomic-wg/issue/303 (dustymabe, 17:27:33) * ACTION: dusty to put in place updating of last f25 ref automated via bodhi (dustymabe, 17:38:08) * ACTION: dustymabe to write blog post about last f25 updates (jberkus, 17:38:44) * ACTION: dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref (dustymabe, 17:38:52) * LINK: https://pagure.io/atomic-wg/issue/287 (strigazi, 17:39:21) * ACTION: dustymabe to create kubernetes-sig pagure repo and notify interested parties (dustymabe, 17:40:29) * ACTION: jberkus to re-create issues in new repo (jberkus, 17:41:44) * ACTION: kubernetes-sig to discuss version tagging for kube system containers (jberkus, 17:52:32) * LINK: https://pagure.io/atomic-wg/issue/294 (dustymabe, 17:53:52) * ACTION: dustymabe jberkus to write doc on docs vfad with all resources linked (jberkus, 17:59:10) Meeting ended at 18:00:56 UTC. Action Items ------------ * : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra * : dustymabe to update IRC channel topics to reflect new scheme * ksinny to update wiki * dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings * jberkus to write blog post for fedora magazine/pa.io on changes * dusty to put in place updating of last f25 ref automated via bodhi * dustymabe to write blog post about last f25 updates * dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref * dustymabe to create kubernetes-sig pagure repo and notify interested parties * jberkus to re-create issues in new repo * kubernetes-sig to discuss version tagging for kube system containers * dustymabe jberkus to write doc on docs vfad with all resources linked Action Items, by person ----------------------- * dustymabe * : dustymabe to update IRC channel topics to reflect new scheme * dustymabe to get a new fedora calendar entry for the Fedora Atomic Working Group meetings * dustymabe to write blog post about last f25 updates * dustymabe to create kubernetes-sig pagure repo and notify interested parties * dustymabe jberkus to write doc on docs vfad with all resources linked * jberkus * : jberkus to follow up with Fedora infra about moving pa.io MLs to Fedora infra * jberkus to write blog post for fedora magazine/pa.io on changes * jberkus to re-create issues in new repo * dustymabe jberkus to write doc on docs vfad with all resources linked * ksinny * ksinny to update wiki * **UNASSIGNED** * dusty to put in place updating of last f25 ref automated via bodhi * dusty to write a comprehensive blog post on updating f25->f26 and will include update about f25 updates ref * kubernetes-sig to discuss version tagging for kube system containers People Present (lines said) --------------------------- * jberkus (106) * dustymabe (96) * jbrooks (36) * maxamillion (32) * roshi (23) * gholms (16) * strigazi (14) * ksinny (12) * walters (12) * zodbot (11) * bowlofeggs (1) * scollier (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Josh Berkus Project Atomic Red Hat OSAS

1 0

[atomic-wg] Issue #304: Update to kubernetes 1.7.x
by Spyros Trigazis 19 Jul '17

19 Jul '17

strigazi reported a new issue against the project: `atomic-wg` that you are following: `` Follow the effort to update the kubernetes package to 1.7.x Thanks already @jchaloup for [1], [2] and [3] [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=919466 [2] http://pkgs.fedoraproject.org/cgit/rpms/kubernetes.git/commit/?id=9efe74b63… [3] https://bugzilla.redhat.com/show_bug.cgi?id=1471767 pinging: @dimtheo @jasonbrooks @jberkus @tstclair @sjenning @suiwenfeng fyi @dustymabe `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/304

3 6

[atomic-wg] Issue #297: Disable deltarpms in the Fedora base docker image
by Matthew Miller 19 Jul '17

19 Jul '17

mattdm reported a new issue against the project: `atomic-wg` that you are following: `` Because we do the nodocs and not all langs thing, the base docker image is missing files that prevent deltarpms from working on `dnf update`. This slows things down and wastes time when doing docker build. We could either tell people to turn this off every time in Dockerfiles, or we could disable it by default in the base image. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/297

3 2

FYI: rawhide ostrees not building because of dep issues
by Dusty Mabe 19 Jul '17

19 Jul '17

Bug is already filed against the correct component. This is just an FYI. https://bugzilla.redhat.com/show_bug.cgi?id=1472573

2 9

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud July 2017