dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We need a place for people to be able to report issues against the container base images. I'm thinking it should be under the *Fedora Container Images* product with a component matching the container base image names.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/370
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Until we get a tool to which submitters can submit automated tests, we should add a requirement to have a narrative test description for each container submission. This spares the reviewer from having to figure out how to test images for software he/she may be unfamiliar with.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/367
maxamillion reported a new issue against the project: `atomic-wg` that you are following:
``
In the Fedora RelEng Tools Backlog meeting, we were discussing various [AutoCloud tickets](https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-a…, which are all kind of in a state of flux since the future of AutoCloud is unknown. I would like to get an answer from the WG what the ongoing commitment is there and if these work items are things that RelEng should care about.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/361
The status of the issue: `bodhi creating ostrees using pungi` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/300
dustymabe added a new comment to an issue you are following:
``
Randy, Patrick and Adam were able to push this through in https://github.com/fedora-infra/bodhi/pull/1900. This is in stage now and will move to prod hopefully very soon. Closing this ticket.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/300
summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-18/fedora_atomic…
full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-18/fedora_atomic…
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by dustymabe at 17:02:33 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-18/fedora_atomic…
.
Meeting summary
---------------
* roll call (dustymabe, 17:02:35)
* previous meeting action items (dustymabe, 17:05:54)
* ACTION: jberkus to follow up on images from Flock container workshop
(dustymabe, 17:09:23)
* ACTION: jberkus to follow up on docs from Flock workshop
(dustymabe, 17:09:35)
* ACTION: jberkus to raise kube installation issues with openshift
installer team (dustymabe, 17:09:45)
* ACTION: dustymabe to update the rolling release plan with info about
f27ah (dustymabe, 17:11:21)
* LINK: https://pagure.io/atomic-wg/issue/349#comment-472028
(dustymabe, 17:11:54)
* ACTION: jbrooks to email fedora-devel with issue of needed deps for
asciibinder container (dustymabe, 17:13:32)
* ACTION: strigazi to do some testing around upgrades from f26 to f27
with kubernetes (dustymabe, 17:18:58)
* ACTION: davdunc to blog AWS MP availability of FAH/Cloud.
(dustymabe, 17:19:06)
* re-evaluate atomic working group meeting time (dustymabe, 17:19:35)
* LINK: https://pagure.io/atomic-wg/issue/346 (dustymabe, 17:19:41)
* ACTION: dustymabe to make new doodle with top 3 or 4 possible times
and have people re-vote (dustymabe, 17:23:57)
* The Future of AutoCloud (dustymabe, 17:24:46)
* LINK: https://pagure.io/atomic-wg/issue/361 (dustymabe, 17:24:52)
* LINK: https://upstreamfirst.fedorainfracloud.org/ (maxamillion,
17:30:09)
* LINK: https://apps.fedoraproject.org/autocloud/compose (dustymabe,
17:30:31)
* While autocloud has served us well in the past we don't have anyone
working on new features for it and if it were to need serious
maintainence we'd probably have trouble managing it. The Fedora CI
pipeline (from the Fedora CI objective) should provide feature
parity with Autocloud in the future and we should leverage that
pipeline as soon as it does. This can eventually become our
(dustymabe, 17:40:15)
* Decide strategy for including container runtimes in Atomic Host
(dustymabe, 17:43:09)
* LINK: https://pagure.io/atomic-wg/issue/360 (dustymabe, 17:43:15)
* LINK:
https://github.com/kubernetes-incubator/cri-o/blob/master/.travis.yml#L13
(walters, 17:47:50)
* open floor (dustymabe, 18:03:34)
Meeting ended at 18:05:50 UTC.
Action Items
------------
* jberkus to follow up on images from Flock container workshop
* jberkus to follow up on docs from Flock workshop
* jberkus to raise kube installation issues with openshift installer
team
* dustymabe to update the rolling release plan with info about f27ah
* jbrooks to email fedora-devel with issue of needed deps for
asciibinder container
* strigazi to do some testing around upgrades from f26 to f27 with
kubernetes
* davdunc to blog AWS MP availability of FAH/Cloud.
* dustymabe to make new doodle with top 3 or 4 possible times and have
people re-vote
Action Items, by person
-----------------------
* davdunc
* davdunc to blog AWS MP availability of FAH/Cloud.
* dustymabe
* dustymabe to update the rolling release plan with info about f27ah
* dustymabe to make new doodle with top 3 or 4 possible times and have
people re-vote
* jberkus
* jberkus to follow up on images from Flock container workshop
* jberkus to follow up on docs from Flock workshop
* jberkus to raise kube installation issues with openshift installer
team
* jbrooks
* jbrooks to email fedora-devel with issue of needed deps for
asciibinder container
* **UNASSIGNED**
* strigazi to do some testing around upgrades from f26 to f27 with
kubernetes
People Present (lines said)
---------------------------
* dustymabe (136)
* jberkus (39)
* jbrooks (28)
* dwalsh (24)
* maxamillion (20)
* ashcrow (15)
* walters (14)
* zodbot (13)
* tflink (8)
* ttomecek (3)
* davdunc (2)
* kushal (1)
* gholms (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
The status of the issue: `F26s will not provision on Azure` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/302
dustymabe added a new comment to an issue you are following:
``
:beers: - closing this ticket
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/302