cloud June 2017

cloud@lists.fedoraproject.org

19 participants
83 discussions

[atomic-wg] Issue #193 `Please add Atomic Host and Fedora Cloud Base to AWS Asia Pacific (Seoul) Region`
by Pagure 30 Jun '17

30 Jun '17

mattdm reported a new issue against the project: `atomic-wg` that you are following: `` This [opened in January](https://aws.amazon.com/blogs/aws/now-open-aws-asia-pacific-seoul-r… and we missed it. (If we were in the Amazon Marketplace, this would happen automatically. Oh well.) See request on mailing list [here](https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproje… Also, once available, don't forget to ask the web team to update the launch pages. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/193

2 5

[atomic-wg] Issue #186 `switch to overlay2`
by Pagure 30 Jun '17

30 Jun '17

walters reported a new issue against the project: `atomic-wg` that you are following: `` <vgoyal> walters: so there are two options. One is changing default to overlay2, which is common across all variants <vgoyal> walters: another new option is specifying where the storage from overlayfs comes from. Does it come from root filesystem or from free space in volume group <vgoyal> for atomic, rootfs is just 3G and if we overlayfs uses rootfs, then it will fill up pretty fast. <vgoyal> so we created a new option in dss, DOCKER_ROOT_VOLUME <vgoyal> if one specifies DOCKER_ROOT_VOLUME=yes, then dss looks for free space in volume group and creates a logical volume, makes a file system on this and mounts on /var/lib/docker/ <vgoyal> now when docker starts, it will put all images and containers in the new volume ( and not logical volume backing rootfs) <vgoyal> given workstation rootfs uses all free space, workstation will not require this by default. <vgoyal> but server and atomic leave free space in volume group and by default that can be used for docker. (like devicemapper graph driver) <vgoyal> so DOCKER_ROOT_VOLUME=yes is required only for server and atomic variants only (and not workstation one) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/186

2 67

[atomic-wg] Issue #283: please include documentation for run label inside Fedora container guidelines
by Tomas Tomecek 30 Jun '17

30 Jun '17

ttomecek reported a new issue against the project: `atomic-wg` that you are following: `` ``` run: a command line to invoke the container, suitable for use by the Atomic CLI, including placeholders and the embedded atomic-run code. Must successfully execute on a suitable Fedora Atomic system. Required if "usage" is not present. Example for the Cockpit container: run="/usr/bin/docker run -d --privileged --pid=host -v /:/host IMAGE /container/atomic-run --local-ssh" ``` I wish it contained information from the [`atomic-run manpage`](https://github.com/projectatomic/atomic/blob/master/docs/atomic-r…. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/283

2 2

[atomic-wg] Issue #276: Set architecture label in the base container image
by Honza Horak 29 Jun '17

29 Jun '17

hhorak reported a new issue against the project: `atomic-wg` that you are following: `` I believe that setting the architecture label in every layered Dockerfile is not necessary, it might be even problematic once we'll have containers on non-intel platforms, because then we'd need to either maintain more copies of Dockerfiles with different architecture labels or remove it later (when we'll have more layered Dockerfiles to maintain at that point). So, I'd like to propose to set the architecture label in the container base image, so it is inherited in the layered images and we don't need to hard-code it there. Then, setting architecture label should be made prohibited (or obsolete) in https://fedoraproject.org/wiki/Container:Guidelines. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276

3 4

Atomic WG Meeting Minutes 2017-06-28
by Dusty Mabe 28 Jun '17

28 Jun '17

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 17:01:17 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-28/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 17:01:23) * list of people to ping for meetings (dustymabe, 17:07:04) * LINK: https://pagure.io/atomic-wg/pull-request/288# (dustymabe, 17:07:13) * previous meeting action items (dustymabe, 17:10:51) * ACTION: dustymabe to propose a VFAD for wiki and docs discussion (dustymabe, 17:11:39) * LINK: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2… (dustymabe, 17:14:22) * ACTION: maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:14:52) * PRD has been approved (gholms, 17:16:04) * Matching Fedora Server's PRD format was helpful (gholms, 17:16:39) * LINK: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting (dustymabe, 17:17:12) * ACTION: jberkus to create new issues, specs for docs.projectatomic.io publication (dustymabe, 17:18:55) * clarify policy on atomic host support for older Fedora "number" releases (dustymabe, 17:20:07) * https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:20:11) * the fedora magazine post has landed https://fedoramagazine.org/upcoming-fedora-atomic-lifecycle-changes/ (dustymabe, 17:20:31) * fedimg: don't use 'builder' instance for uploading AMIs (dustymabe, 17:22:54) * LINK: https://pagure.io/atomic-wg/issue/269 (dustymabe, 17:23:00) * this will most likely wait until after fedora 26 release because we are now in freeze (dustymabe, 17:23:29) * Set architecture label in the base container image (dustymabe, 17:26:28) * LINK: https://pagure.io/atomic-wg/issue/276 (dustymabe, 17:26:35) * Figure out comprehensive strategy for atomic host container storage (dustymabe, 17:28:45) * LINK: https://pagure.io/atomic-wg/issue/281 (dustymabe, 17:29:07) * AGREED: changing fedora 27 and beyond to default to overlayfs on the root partition will help us simplify our storage setup and align better with other fedora variants. This seems like a reasonable change to make assuming that overlayfs proves stable for the f26 cycle. (dustymabe, 17:41:27) * Atomic Host images omit many common locales that all other flavors include (dustymabe, 17:41:38) * LINK: https://pagure.io/atomic-wg/issue/282 (dustymabe, 17:41:45) * ACTION: maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group (dustymabe, 17:44:14) * Identify group of people interested in maintaining kubernetes (dustymabe, 17:44:56) * LINK: https://pagure.io/atomic-wg/issue/287 (dustymabe, 17:45:14) * open floor (dustymabe, 17:49:50) * Work continues on fixing EC2 image visibility, as copied images need their permissions changed (gholms, 17:53:06) * if you haven't yet tried out minishift, you should check it out https://www.openshift.org/minishift/ (dustymabe, 17:54:15) Meeting ended at 17:58:46 UTC. Action Items ------------ * 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 * jberkus to create new issues, specs for docs.projectatomic.io publication * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group Action Items, by person ----------------------- * dustymabe * dustymabe to propose a VFAD for wiki and docs discussion * jberkus * jberkus to create new issues, specs for docs.projectatomic.io publication * maxamillion * maxamillion to look at logs from last meeting and add summary of our discussion to ticket https://pagure.io/atomic-wg/issue/284 * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * roshi * maxamillion roshi to come up with guidelines for meeting quorum for the atomic working group * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * dustymabe (156) * roshi (24) * maxamillion (24) * gholms (22) * zodbot (20) * jberkus (18) * kushal (13) * yzhang (12) * sayan (11) * gbraad_ (9) * suiwenfeng (7) * DimGR (7) * walters (2) * miabbott (1) * rubao (1) * nzwulfin (1) * jzb (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Atomic WG Meeting Minutes 2017-06-21
by Dusty Mabe 28 Jun '17

28 Jun '17

summary: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2… full log: https://meetbot.fedoraproject.org/teams/fedora_atomic_wg/fedora_atomic_wg.2… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 17:03:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-06-21/fedora_atomic… . Meeting summary --------------- * roll call (dustymabe, 17:03:28) * Fedora OSBS RFE: install go-md2man to buildroot image (dustymabe, 17:06:20) * LINK: https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:06:28) * LINK: https://pagure.io/atomic-wg/issue/256 (dustymabe, 17:10:56) * LINK: https://pagure.io/atomic-wg/issue/256#comment-436537 (dustymabe, 17:11:31) * ACTION: maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 (dustymabe, 17:17:11) * action items from last meeting (dustymabe, 17:17:28) * ACTION: dustymabe to propose a VFAD for wiki and docs discussion (dustymabe, 17:18:18) * ACTION: jberkus to update wg on final approval of PRD (dustymabe, 17:18:38) * ACTION: jberkus to create new issues, specs for docs.projectatomic.io publication (dustymabe, 17:18:48) * dustymabe did create the SIG page for the wiki https://fedoraproject.org/wiki/Atomic_WG (dustymabe, 17:19:39) * maxamillion updated the container guidelines to enforce ENV and label for https://pagure.io/atomic-wg/issue/277 (dustymabe, 17:19:57) * Atomic Host images omit many common locales that all other flavors include (dustymabe, 17:21:12) * LINK: https://pagure.io/atomic-wg/issue/282 (dustymabe, 17:21:20) * talk/workshop proposals for Flock (dustymabe, 17:23:36) * LINK: https://pagure.io/atomic-wg/issue/279 (dustymabe, 17:23:40) * Set architecture label in the base container image (dustymabe, 17:25:34) * LINK: https://pagure.io/atomic-wg/issue/276 (dustymabe, 17:25:42) * fedimg: don't use 'builder' instance for uploading AMIs (dustymabe, 17:37:29) * LINK: https://pagure.io/atomic-wg/issue/269 (dustymabe, 17:37:34) * clarify policy on atomic host support for older Fedora "number" releases (dustymabe, 17:38:39) * LINK: https://pagure.io/atomic-wg/issue/228 (dustymabe, 17:38:53) * open floor (dustymabe, 17:40:34) * testday went well, no notable issues found. Good work! (roshi, 17:43:28) Meeting ended at 17:50:02 UTC. Action Items ------------ * maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 * dustymabe to propose a VFAD for wiki and docs discussion * jberkus to update wg on final approval of PRD * jberkus to create new issues, specs for docs.projectatomic.io publication Action Items, by person ----------------------- * dustymabe * dustymabe to propose a VFAD for wiki and docs discussion * maxamillion * maxamillion to add summary to ticket https://pagure.io/atomic-wg/issue/284 * **UNASSIGNED** * jberkus to update wg on final approval of PRD * jberkus to create new issues, specs for docs.projectatomic.io publication People Present (lines said) --------------------------- * dustymabe (112) * maxamillion (34) * roshi (22) * zodbot (16) * jbrooks (6) * jds2001 (5) * sayan (2) * dgilmore (2) * miabbott (1) * nirik (1) * mnguyen (1) * rubao (1) * ksinny (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #289: Investigating the possibility to have an Atomic Host LiveCD
by Gerard Braad (吉拉德) 28 Jun '17

28 Jun '17

gbraad reported a new issue against the project: `atomic-wg` that you are following: `` At the moment we run a CentOS-based livecd to run our VM environment, but we would really like to target an Atomic Host. I have been looking into generating an image using the kickstart at https://github.com/gbraad/minishift-atomic-iso/. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/289

1 0

[atomic-wg] Issue #228 `clarify policy on atomic host support for older Fedora "number" releases`
by Dusty Mabe 28 Jun '17

28 Jun '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` After talking with people from the fedora community and from the atomic WG it has become clear that there is a lot of confusion on our policy for support for N-1 releases of Fedora Atomic Host. First off some terminology: **support**: means that we test and release new 2 week releases for this number release (i.e. we currently test/release new two week releases of Fedora 25 Atomic Host). **N-1**: currently is Fedora 24 Atomic Host **life support**: means that we still push out OSTree updates for the OSTree that backs this number release, but we don't create new image releases and we don't formally test it. Currently we have been offering **support** for the current (N) release of Fedora and **life support** for the previous (N-1) release of Fedora. In the future I'd like to formalize our **support** policy and stop providing **life support** for previous releases once it is no longer a current release. There are a couple of reasons for this: - The level of effort going into N-1 is very minimal and I wouldn't want someone running that to get a false sense of security from it. - If N-1 breaks in releng for whatever reason, spending time on N-1 is not a high priority and I'd like to not have to fix it if it breaks. For F26 I'd like to formally state this policy of **support**ing only the N release. We can also **life support** the N-1 for an agreed upon time period after the N release (30to60 days or something) to allow for transition. Note: There is also some discussion about making Fedora Atomic a rolling release. That is outside the scope of this ticket. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/228

5 18

[atomic-wg] Issue #266: rpmostree_compose Ansible module
by Trishna Guha 28 Jun '17

28 Jun '17

trishnag reported a new issue against the project: `atomic-wg` that you are following: `` As for Ansible module for atomic host we have `atomic_host` and `atomic_image` modules written. The plan/purpose of this ticket is to have rpm-ostree modules get done for Ansible as well. We can perhaps have all the `rpm-ostree` options as Ansible modules so that we really do not need to execute rpm-ostree commands as part of `shell`/`command` modules in Ansible. I wrote `rpmostree compose` Ansible module: https://github.com/ansible/ansible/pull/23209. Can anyone volunteer to review the PR? Bringing in @dustymabe @jberkus @walters @jlebon here. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/266

2 1

Announce: Fedora Layered Image Release
by Adam Miller 27 Jun '17

27 Jun '17

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud June 2017