Summary:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-05/fedora_atomic…
17-07-05-17.00.html
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by yzhang at 17:00:21 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-1/2017-07-05/fedora_atom…
.
Meeting summary
---------------
* Roll Call (yzhang, 17:00:35)
* Action items from last meeting (yzhang, 17:02:49)
* ACTION: maxamillion roshi to come up with guidelines for meeting
quorum for the atomic working group (yzhang, 17:03:52)
* ACTION: dustymabe to propose a VFAD for wiki and docs discussion
(dustymabe, 17:04:09)
* ACTION: maxamillion to look at logs from last meeting and add
summary of our discussion to ticket
https://pagure.io/atomic-wg/issue/284 (yzhang, 17:05:29)
* Make fedora-minimal base image generally available (yzhang, 17:06:25)
* LINK: https://pagure.io/atomic-wg/issue/290 (yzhang, 17:06:31)
* ACTION: maxamillion to release the fedora-minimal base image with
next container release: https://pagure.io/atomic-wg/issue/290
(yzhang, 17:13:30)
* Atomic Host images omit many common locales that all other flavors
include (yzhang, 17:14:31)
* LINK: https://pagure.io/atomic-wg/issue/282 (yzhang, 17:14:37)
* Figure out comprehensive strategy for atomic host container storage
(yzhang, 17:28:01)
* LINK: https://pagure.io/atomic-wg/issue/281 (yzhang, 17:28:06)
* fedimg: don't use 'builder' instance for uploading AMIs (yzhang,
17:28:57)
* LINK: https://pagure.io/atomic-wg/issue/269 (yzhang, 17:29:03)
* open floor (yzhang, 17:33:34)
* kubernetes sig (dustymabe, 17:35:17)
* LINK: https://pagure.io/atomic-wg/issue/287 (dustymabe, 17:35:48)
* ACTION: dustymabe to update the kubernetes thread with tracking
options: https://pagure.io/atomic-wg/issue/287 (yzhang, 17:42:01)
* cloud/atomic confusion (dustymabe, 17:42:32)
* ACTION: dustymabe to open a ticket for cloud/atomic confusion
(yzhang, 17:44:49)
* open floor (dustymabe, 17:46:43)
* please update the ticket and say what talks were accepted for flock
https://pagure.io/atomic-wg/issue/279 (dustymabe, 17:50:36)
* LINK:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org…
(dustymabe, 17:52:58)
* stef from the fedora CI efforts has a proposal for actually
delivering atomic host from a CI pipeline:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org…
please review that - he's going to discuss it with us next week at
this meeting (dustymabe, 17:53:40)
Meeting ended at 17:56:46 UTC.
Action Items
------------
* maxamillion roshi to come up with guidelines for meeting quorum for
the atomic working group
* dustymabe to propose a VFAD for wiki and docs discussion
* maxamillion to look at logs from last meeting and add summary of our
discussion to ticket https://pagure.io/atomic-wg/issue/284
* maxamillion to release the fedora-minimal base image with next
container release: https://pagure.io/atomic-wg/issue/290
* dustymabe to update the kubernetes thread with tracking options:
https://pagure.io/atomic-wg/issue/287
* dustymabe to open a ticket for cloud/atomic confusion
Action Items, by person
-----------------------
* dustymabe
* dustymabe to propose a VFAD for wiki and docs discussion
* dustymabe to update the kubernetes thread with tracking options:
https://pagure.io/atomic-wg/issue/287
* dustymabe to open a ticket for cloud/atomic confusion
* maxamillion
* maxamillion roshi to come up with guidelines for meeting quorum for
the atomic working group
* maxamillion to look at logs from last meeting and add summary of our
discussion to ticket https://pagure.io/atomic-wg/issue/284
* maxamillion to release the fedora-minimal base image with next
container release: https://pagure.io/atomic-wg/issue/290
* roshi
* maxamillion roshi to come up with guidelines for meeting quorum for
the atomic working group
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* yzhang (103)
* dustymabe (93)
* maxamillion (34)
* roshi (28)
* zodbot (17)
* kushal (12)
* jbrooks (11)
* sayan (6)
* ksinny (5)
* walters (5)
* miabbott (2)
* jlebon (2)
* imcleod (1)
* deuscapturus (1)
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
we hit [an issue](https://pagure.io/releng/issue/6761) yesterday because fedimg failed upload all of our AMIs for that day's build of FAH.
This is most likely due to the fact that we use a builder instance to pull the cloud disk image and then create the EBS. Bringing up the builder instance can fail (commodity hardware in EC2) and thus can lead to situations like this. It would be much better if we don't use a builder instance.
This is being worked on in https://github.com/fedora-infra/fedimg/issues/42.
This ticket will track that work that is 'two weeks away' from completion.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/269
Hey guys,
A bunch of us (myself, Pingou, Ari, Dusty, Colin, and others) have been
talking about the idea of delivering Atomic Host via a CI/CD pipeline.
The plan would be to provide continuous integration testing feedback to
folks working on packages in Atomic Host and bringing together its compose.
In addition the composed QCow2, OSTree, and AMI artifacts that are
integrated would be the same ones delivered to users, rather than being
recomposed in a different way.
I've written something up that explains things further:
https://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Delive…
I'd like to discuss this in the meeting today. Do we have time?
Cheers,
Stef
strigazi reported a new issue against the project: `atomic-wg` that you are following:
``
In this issue we will try to track the work we are doing to modify our templates in openstack/magnum to deploy kubernetes (etcd, flannel) in system containers.
At the moment, we run
1. etcd, flannel, kubelet and kube-apiserver from the binaries includes in fedora-atomic
2. kube-proxy, kube-scheduler, kube-controller-manager as static pods
3. core-dns, kubernetes-dashboard as deployments
The goal is to run all components of 1. in system containers and be able to change version easily and get the newest faster. We will investigate if there are benefits to run 2. as system-containers too.
We (magnum and atomic-wg) could leverage magnum to test the newest packages of kube/etcd/flannel. Magnum's CI will run soon on CICO [1].
Magnum's configuration scripts:
http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common/t…
[1] https://bugs.centos.org/view.php?id=13192
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/292
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-07-05 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/