[fedora-atomic] PR #87: add back in gluster/ceph

miabbott commented on the pull-request: `add back in gluster/ceph` that you are following: `` LGTM `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/87 ___ cloud mailing list --

[fedora-atomic] PR #69: manifest: Add microcode_ctl

miabbott commented on the pull-request: `manifest: Add microcode_ctl` that you are following: `` LGTM `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/69 ___ cloud mailing list --

[atomic-wg] Issue #295: Start using new mailing list/IRC channel around f26 release time

miabbott added a new comment to an issue you are following: `` +1 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images

miabbott added a new comment to an issue you are following: `` Routed again from fedora-infrastructure to releng. New ticket at releng#6780 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/272 ___ cloud

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images

miabbott added a new comment to an issue you are following: `` Filed fedora-infrastructure#6047 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/272 ___ cloud mailing list -- cloud@lists.fedoraproject.org

[atomic-wg] Issue #264: 2WK Atomic Release Criteria

miabbott added a new comment to an issue you are following: `` > ADDITION: we should require that Atomic be able to run a system container. > @dwalsh, and you supply a good command-line for a system container which > should always run successfully? Using Atomic Run is OK. Added a section on

[atomic-wg] Issue #257 `atomic host tree in F26 does not boot properly`

miabbott added a new comment to an issue you are following: `` > what should it be? - should we open an issue upstream somewhere? F25 Atomic Host has: ``` $ grep passwd /etc/nsswitch.conf #passwd:db files nisplus nis passwd: files altfiles sss ``` `` To reply, visit the link below or

[atomic-wg] Issue #257 `atomic host tree in F26 does not boot properly`

miabbott added a new comment to an issue you are following: `` Booted the ISO via `virt-manager` and collected the output from the console using: `virsh console 16 | tee console.log` Formatting got a bit mangled, but I put the majority of it into this paste

Re: Meeting with Openstack magnum team today

On 02/23/2017 11:32 PM, Dusty Mabe wrote: Spent the day chatting with a bunch of Fedora Atomic users today. Some pain points that came out of todays discussions: - kubernetes versions * sometimes we have lagged behind upstream in Fedora and this has caused some pain. They are on

[atomic-wg] Issue #198 `move ostree ref to be "container-host"`

miabbott added a new comment to an issue you are following: `` Could we align with what RHEL and CentOS do? Or is there value in preserving the `container-host` nomenclature? RHEL uses the following branch: `rhel-atomic-host/7/x86_64/standard` CentOS uses this:

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

miabbott added a new comment to an issue you are following: `` I downloaded the Nov 21 ISO from here: https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20161121.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20161121.0.iso ...and wrote it to a USB key. Then successfully

Re: Separate Repository for Atomic Specific Fedora-Dockerfiles

On 09/08/2016 01:33 PM, Trishna Guha wrote: On Thu, Sep 8, 2016 at 8:10 PM, Josh Berkus > wrote: In what way are images created for atomic not runnable on regular Docker? Examples? Sure. [1] is the Dockerfile for running cockpit on atomic

Re: Fedora Atomic Host Two Week Release Announcement

For anyone interested in the package diffs between the last two week release (23.68) and the most recent (23.79), I've got you covered. The URL below contains the output from... # rpm-ostree db diff --format diff 51b12b199c 1a68c7b9c0 ...which are the commit IDs for 23.68 and 23.79

Re: Fedora Atomic Host Two Week Release Announcement

- Original Message - > From: "Dusty Mabe" > To: cloud@lists.fedoraproject.org > Sent: Saturday, February 13, 2016 9:23:53 AM > Subject: Re: Fedora Atomic Host Two Week Release Announcement > > > > On 02/12/2016 01:08 PM, Adam Miller wrote: > > On Fri, Feb 12, 2016

Re: [atomic-devel] Fedora Atomic Host Two Week Release Announcement

AFAICT, the link for the updated ISO from https://getfedora.org/en/cloud/download/atomic.html ...is working properly this morning. In case one of the mirrors isn't up to speed yet, the direct link is:

Re: Fedora 23 Cloud Atomic Developer Mode Preview

I tried devmode this afternoon and it worked very well. I discussed a few nits with jlebon on #atomic, but thought I would mention them here. - The generated root password can include similar characters l (letter L), 1 (number 1), O (upper-case letter O), 0 (number zero), etc. I got bit by

Re: Fedora Atomic Host Two Week Release Announcement

TL;DR - This email describes how to determine the changes between two releases via a number of 'ostree' and 'rpm-ostree' commands. Kind of hacky, but it works. I couldn't find an email about the previous two week release, so I had to kind of guess that it was released around Nov. 16. With