[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26
release time
by Dusty Mabe
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
6 years, 9 months
Minutes for meeting
by Josh Berkus
===================================
#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_atom...
.
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
6 years, 9 months
[atomic-wg] Issue #297: Disable deltarpms in the Fedora base docker image
by Matthew Miller
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
6 years, 9 months
[atomic-wg] Issue #281: Figure out comprehensive strategy for atomic host
container storage
by Dusty Mabe
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
6 years, 9 months