[atomic-wg] Issue #186 `switch to overlay2`

dustymabe added a new comment to an issue you are following: `` > We are making docker-storage-setup more generic (to be usable by other > container runtime as well, apart from docker). So in an attempt to do that, > we are introducing new options. > EXTRA_VOLUME_NAME="docker-root-lv" >

[atomic-wg] Issue #186 `switch to overlay2`

dustymabe added a new comment to an issue you are following: `` > We are making docker-storage-setup more generic (to be usable by other > container runtime as well, apart from docker). So in an attempt to do that, > we are introducing new options. > EXTRA_VOLUME_NAME="docker-root-lv" >

[atomic-wg] Issue #185 `November 21 ISO is not bootable on UEFI`

jberkus added a new comment to an issue you are following: `` @dustymabe I tested this on one of the minnowboards, and it installed and booted fine. Note that, instead of allocating specific bytes for /boot, you can use this KS command: reqpart --add-boot `` To reply, visit the link below or

[atomic-wg] Issue #186 `switch to overlay2`

vgoyal added a new comment to an issue you are following: `` We are making docker-storage-setup more generic (to be usable by other container runtime as well, apart from docker). So in an attempt to do that, we are introducing new options. EXTRA_VOLUME_NAME="docker-root-lv"

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

mattdm added a new comment to an issue you are following: `` I think we can simplify the rules to 1. RootFS: 25% of disk space, with a minimum of 3GB and a maximum of 16GB 2. Docker Partition: maximum of 50% of total disk space 3. Leave anything else unallocated No need to specify a rule for

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

dustymabe added a new comment to an issue you are following: `` > > This should be easy to do with anaconda-based installs, but how would this > work with images? > > docker-storage-setup can do this for us. The images are only baked with an > atomicos VG and an atomicos/root LV.

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

dustymabe added a new comment to an issue you are following: `` > This should be easy to do with anaconda-based installs, but how would this > work with images? docker-storage-setup can do this for us. The images are only baked with an `atomicos` VG and an `atomicos/root` LV.

Re: [atomic-wg] Issue #196 `moving to docker 1.13 in Fedora 25`

On Jan 18, 2017 22:46, "Dusty Mabe" wrote: dustymabe added a new comment to an issue you are following: `` > I think we should get docker-1.13 into Rawhide right away. Yup, I'm going to build it there ASAP. agree on this point. The discussion was meant to target f25. ``

[atomic-wg] Issue #196 `moving to docker 1.13 in Fedora 25`

dustymabe added a new comment to an issue you are following: `` > I think we should get docker-1.13 into Rawhide right away. agree on this point. The discussion was meant to target f25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/196

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` Presumably we can do this by changing the default cloud-init? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197 ___ cloud mailing list --

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` That's a very good question! And AWS images is one of the biggest places we need to have good default behavior ... `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

mattdm added a new comment to an issue you are following: `` This should be easy to do with anaconda-based installs, but how would this work with images? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` The way it is now: Currently, the rootFS is sized at 3GB, fixed, and the Docker partition is 40% of the remaining space. This causes new users to run out of disk space if they do layering, ostree unlock,

[atomic-wg] Issue #186 `switch to overlay2`

dustymabe added a new comment to an issue you are following: `` OK I think we will settle on having an extra partition that is used as the root store for `/var/lib/docker` on Atomic Host (i.e. we will have `DOCKER_ROOT_VOLUME=yes` be the default) along with default to overlay2. We may revisit

[atomic-wg] Issue #196 `moving to docker 1.13 in Fedora 25`

dwalsh added a new comment to an issue you are following: `` I think we should get docker-1.13 into Rawhide right away. The problem with putting it into Fedora 25 is it has not been fully vetted with OpenShift and Kubernetes yet. I don't believe we should swap out the docker version their

[atomic-wg] Issue #196 `moving to docker 1.13 in Fedora 25`

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` In the meeting today @runcom brought up the topic of: - removing docker-latest in Fedora (mail thread on that

[atomic-wg] Issue #185 `November 21 ISO is not bootable on UEFI`

dustymabe added a new comment to an issue you are following: `` > VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV > succeeds, for both BIOS and UEFI firmware. Using default partitioning, the > required layout is created. Both installations completely startup, I can >

[atomic-wg] Issue #185 `November 21 ISO is not bootable on UEFI`

chrismurphy added a new comment to an issue you are following: `` VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV succeeds, for both BIOS and UEFI firmware. Using default partitioning, the required layout is created. Both installations completely startup, I can login,

[atomic-wg] Issue #185 `November 21 ISO is not bootable on UEFI`

dustymabe added a new comment to an issue you are following: `` First build is out that contains this fix. Please test: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170118.1/compose/Atomic/x86_64/iso/ Keep in mind you will need to have a /boot partition in order for this

Re: Hardware for FOSP

On 01/18/2017 12:57 PM, Michael Scherer wrote: > Hi, > > so as people asked me on irc, it seems there was a lack of communication > regarding the hardware for the FOSP project > (https://pagure.io/atomic-wg/issue/153). > > Due to internal changes (on top of regular changes) on the other side

Hardware for FOSP

Hi, so as people asked me on irc, it seems there was a lack of communication regarding the hardware for the FOSP project (https://pagure.io/atomic-wg/issue/153). Due to internal changes (on top of regular changes) on the other side of the RH firewall, the acquisition of the servers and the

Re: Fedora 2wk Atomic Blocker Bugs

On 01/17/2017 01:42 PM, Dusty Mabe wrote: > There are a few bugs that are blocking 2wk release. > > - one with the kernel that causes kube dns to not work > * https://bugzilla.redhat.com/show_bug.cgi?id=1414068 > - one with kube that causes selinux breakage > *

May miss today's meeting

Hello, I have got a bad fever from today evening. I may not be available in today's Atomic-wg meeting if I am not well. If I miss the meeting I'll make sure to go through the meeting logs tomorrow and will work on if I find a task for myself :). I was thinking to host today's meeting. But I'm

Re: About the recent failures of Atomic images on Autocloud

> On Wed, Jan 18, 2017 at 10:05:41AM +0530, Kushal Das wrote: > > Finally managed to isolate the issue. If we boot the image with only one > > CPU, the error comes up. If we boot with 2 or more CPU(s), no issues at > > all. Now the question is if we should make local testing on Autocloud > > with

Re: About the recent failures of Atomic images on Autocloud

On Wed, Jan 18, 2017 at 10:05:41AM +0530, Kushal Das wrote: > Finally managed to isolate the issue. If we boot the image with only one > CPU, the error comes up. If we boot with 2 or more CPU(s), no issues at > all. Now the question is if we should make local testing on Autocloud > with 2 CPU(s)