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
===================================
#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
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
sinnykumari reported a new issue against the project: `atomic-wg` that you are following:
``
I am working on enabling Atomic Host CloudImages in Fedora 27 onward for multi-arches which includes aarch64 and ppc64le. Required changes has been made in Fedora config to enable qcow2 and raw images [Link - https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_361] .
It seems making above changes is not sufficient because we are seeing all related builds failing for both arches. One of the failed koji build link - https://koji.fedoraproject.org/koji/taskinfo?taskID=20304853
After debugging cause of failure (started with ppc64le), I see following two issues:
1. kickstart file used for building Atomic CloudImage has arch specific content at line https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_35 .
Possible solution
-----------------------
We can remove x86_64 mention with something generic like:
basearch=$(uname -i)
and replacing x86_64 with $basearch should fix this.
2. I see that in kickstart fedora-atomic.ks [ https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_27 ], we don't use autopart (used by all other variants' kickstart) to create partition. Instead of autopart, we create partitions manually by using part. This leads to anaconda text based installation failure with error message "storage configuration failed: failed to find a suitable stage1 device." on ppc64le [ https://kojipkgs.fedoraproject.org//work/tasks/4883/20304883/screenshot.ppm ]
It seems required PReP partition is not getting created for ppc64le arch.
If I add into kickstart file "part prepboot --fstype "PPC PReP Boot" --size=10" to create PReP partition on ppc64le, I get successful running AH CloudImage on ppc64le (tried locally) . But, this would again add-up arch-specific changes in kickstart file.
I would like to know your thoughts on getting them fixed in proper way.
Note: Debugging issue on aarch64 is still pending which might bring-up some additional concern.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/299
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-07-19 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/
walters reported a new issue against the project: `atomic-wg` that you are following:
``
In https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/
and https://pagure.io/atomic-wg/issue/228
we did some handwaving about releases that IMO was very vague :smile:
Now that 26 is out, every 25 AH will simply stop receiving updates without
admin intervention (either https://fedoraproject.org/wiki/Atomic_Host_upgrade
or `rpm-ostree rebase fedora-atomic/25/x86_64/updates/docker-host`).
I really think we need at least some grace period here. Also I'd like some
time to polish off end-of-life notification better. So I propose we add infrastructure
to continue promotion of /updates -> stable for the 25 ref for at least 2-3 releases.
However, we wouldn't release new media (cloud images, ISO) for 25.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/303
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
https://aws.amazon.com/blogs/aws/elastic-network-adapter-high-performance-n…
we support this in our kernel so we should probably enable it. We need to:
1 - enable it in fedimg and underlying tools if needed
2 - see if having it enabled on all AMIs affects being able to launch on certain instance types (we would like to be able to enable it on all AMIs and just have it be a no-op on instances that don't support it.
cc @sayanchowdhury
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/271
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We have system containers storing things in /var/lib/containers/storage. We have docker/moby containers storing things in /var/lib/docker. We might move to overlay2 on a single big root partition in the future, we might not.
We have discussed these topics in a few maililng list threads [[1](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2017-April/msg00031.html)] [[2]()] and also ran out of storage on atomic host before [[3](https://bugzilla.redhat.com/show_bug.cgi?id=1391725)]
Let's put some thought into this and try to figure out a proper strategy going forward.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/281