Please add AMI image to AWS Seoul region
by ms@sentience.rocks
Dear Matthew Miller,
I see you commented about AWS Seoul region about a year ago. But we still don't have fedora cloud AMI listed in Seoul region..
If this issue was forgotten because no one ever used fedora (docker) cloud image in Seoul region, well, here I am .. ^_^ ~
For now i am using copied AMI from us west, but it would be really nice if we have natively? listed offical fedora image..
Thank you !!
7 years, 2 months
Fedora 26: Request for review of Release Blocking Deliverables
by Jan Kurik
Hi Atomic/Cloud team,
as we are moving forward with Fedora 26 I would like to make sure we
have all the deliverables, which might or might not be blocking for
the release, identified on time. As such, I would like to ask you to
review the list of deliverables the Atomic/Cloud team delivers for
Fedora 26 release. The list is available on
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
.
In case you find any discrepancy in the list, feel free to correct it
or let me know and I will correct it then.
Thanks for your help and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
7 years, 2 months
Fedora Cloud DevConf Workshop
by Adam Miller
Hello all,
During the last Fedora Cloud/Atomic WG meeting jberkus brought up
the idea of having a workshop at DevConf to tackle some Layered Image
items which we, at the time, seemed in agreement on. Josh and I were
talking on irc today and I wanted to make a proposal to the list and
find out what others thought.
Meeting Time: 14:00 (localtime at DevConf)
Meeting Location: TBD
Virtual-Meeting Location: #fedora-cloud
Work-Tracking (we should make cards for tasks):
https://taiga.fedorainfracloud.org/project/maxamillion-fedora-layered-ima...
Work to accomplish:
7 years, 2 months
Cloud Meeting Minutes 2017-01-11
by Jason Brooks
summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atom...
full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atom...
===================================
#fedora-meeting-1: fedora_atomic_wg
===================================
Meeting started by jbrooks at 17:00:12 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atom...
.
Meeting summary
---------------
* roll call (jbrooks, 17:00:19)
* action items from last meeting (jbrooks, 17:02:09)
* ACTION: dustymabe walters jberkus to discuss overlayfs partitioning
issue (jbrooks, 17:09:17)
* ACTION: jbrooks to update compose your own doc (jbrooks, 17:14:49)
* ACTION: jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches (jbrooks, 17:15:12)
* LINK: https://pagure.io/atomic-wg/issue/180 (jbrooks, 17:16:02)
* ACTION: all comment on PRD draft to discuss next week (jbrooks,
17:22:48)
* ACTION: dustymabe to start ticket to discuss virtual fads (jbrooks,
17:35:59)
* November 21 ISO is not bootable on UEFI (jbrooks, 17:36:55)
* LINK: https://pagure.io/atomic-wg/issue/185 (jbrooks, 17:37:03)
* LINK: https://pagure.io/atomic-wg/issue/192 (dustymabe, 17:38:19)
* Ship fedora-motd in F24 atomic image (jbrooks, 17:42:31)
* LINK: https://pagure.io/atomic-wg/issue/160 (jbrooks, 17:42:36)
* Proposed website changes for Cloud Base → Atomic Host switch
(jbrooks, 17:43:29)
* LINK: https://pagure.io/atomic-wg/issue/158 (jbrooks, 17:43:34)
* design, deploy and document Fedora OpenShift Playground (FOSP)
(jbrooks, 17:45:36)
* LINK: https://pagure.io/atomic-wg/issue/153 (jbrooks, 17:46:26)
* open floor (jbrooks, 17:47:30)
* LINK:
https://kojipkgs.fedoraproject.org/atomic/25/refs/heads/fedora-atomic/25/...
(jbrooks, 17:58:11)
Meeting ended at 18:01:17 UTC.
Action Items
------------
* dustymabe walters jberkus to discuss overlayfs partitioning issue
* jbrooks to update compose your own doc
* jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* all comment on PRD draft to discuss next week
* dustymabe to start ticket to discuss virtual fads
Action Items, by person
-----------------------
* dustymabe
* dustymabe walters jberkus to discuss overlayfs partitioning issue
* jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* dustymabe to start ticket to discuss virtual fads
* jberkus
* dustymabe walters jberkus to discuss overlayfs partitioning issue
* jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* jbrooks
* jbrooks to update compose your own doc
* jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* **UNASSIGNED**
* all comment on PRD draft to discuss next week
People Present (lines said)
---------------------------
* jbrooks (103)
* dustymabe (58)
* maxamillion (42)
* jberkus (36)
* kushal (26)
* zodbot (18)
* sayan (13)
* misc (7)
* roshi (7)
* trishnag (4)
* scollier (3)
* bowlofeggs (2)
* dgilmore (2)
* puiterwijk (1)
* coremodule (1)
Generated by `MeetBot`_ 0.1.4
7 years, 2 months
Proposal: require DESCRIPTION, USAGE label for images
by Josh Berkus
Folks,
Looking at the new FDLIBS, I'm noticing that there's not a narrative
description of the image required or provided anywhere that I can find.
Clearly one is needed for users. So, here's a proposal:
New Required LABELs:
USAGE: single command line giving usage example
for invoking the container; will be "N/A" for
some containers.
DESCRIPTION: Narrative description incuding:
* What service/software it provides
* What specific purpose it fulfills, if required
* Notes on how to use it, if not covered by USAGE,
such as how to supply configuration files
* Depedencies on other images (e.g. "requires a database")
* Links to documentation for the Software, if any
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
7 years, 2 months