Re: Vagrant mounting /var/lib/docker?

- Original Message - From: Joe Brockmeier j...@redhat.com To: Jason Brooks jbro...@redhat.com, Fedora Cloud SIG cloud@lists.fedoraproject.org Sent: Tuesday, March 17, 2015 12:19:32 PM Subject: Re: Vagrant mounting /var/lib/docker? On 03/17/2015 03:18 PM, Jason Brooks wrote: I

Re: Cloud SIG meeting minutes (2015-03-18)

Action Items * jzb help find scollier additional maintainer for dockerfiles On this item, I believe that the CentOS folks are interested in working together on Dockerfiles maintenance. Perhaps CentOS Dockerfiles and Fedora Dockerfiles could live together under Project

Re: Atomic 2 Week Proposal

- Original Message - From: Matthew Miller mat...@fedoraproject.org To: Fedora Cloud SIG cloud@lists.fedoraproject.org Sent: Wednesday, March 25, 2015 4:10:40 PM Subject: Atomic 2 Week Proposal On Wed, Mar 25, 2015 at 03:00:05PM -0400, Joe Brockmeier wrote:

Re: docker-storage-setup fails on F22 cloud image

- Original Message - From: Dusty Mabe du...@dustymabe.com To: cloud@lists.fedoraproject.org Sent: Wednesday, August 5, 2015 7:28:27 AM Subject: docker-storage-setup fails on F22 cloud image docker-storage-setup fails on our cloud image because there is no storage for it to

Re: [DISCUSS] Making Atomic the cloud edition

- Original Message - From: Matt Micene nzwul...@gmail.com To: Fedora Cloud SIG cloud@lists.fedoraproject.org Sent: Friday, August 21, 2015 6:49:18 AM Subject: Re: [DISCUSS] Making Atomic the cloud edition Given: jzb Given that a great deal of interesting work is going into

Re: [DISCUSS] Making Atomic the cloud edition

- Original Message - From: Joe Brockmeier j...@redhat.com To: Fedora Cloud SIG cloud@lists.fedoraproject.org Sent: Tuesday, August 18, 2015 3:54:16 PM Subject: [DISCUSS] Making Atomic the cloud edition Given that a great deal of interesting work is going into the Fedora Atomic

Re: RC* Atomic images are broken

- Original Message - > From: "Dusty Mabe" > To: cloud@lists.fedoraproject.org > Sent: Thursday, October 29, 2015 1:11:45 PM > Subject: Re: RC* Atomic images are broken > > On 10/28/2015 06:45 PM, Dusty Mabe wrote: > > We found out today that all RC images for

Re: Alternatives to cloud-init (was Re: [DISCUSS] Cloud and Server Workgroup relationship)

> > However another important point to make here is that "run a cloud image > locally > in libvirt on a workstation" is basically the use case for Vagrant - it does > things > like detecting the IP address so you can `vagrant ssh` etc. +1000 I'm trying to reproduce an issue in a

Re: [DISCUSS] Cloud and Server Workgroup relationship

- Original Message - > From: "Joe Brockmeier" > To: "Fedora Cloud SIG" , > ser...@lists.fedoraproject.org > Sent: Wednesday, October 28, 2015 11:43:27 AM > Subject: [DISCUSS] Cloud and Server Workgroup relationship > > Hi all, > >

Re: Atomic Host and the kernel

- Original Message - From: Josh Boyer jwbo...@fedoraproject.org To: Fedora Cloud SIG cloud@lists.fedoraproject.org Cc: Colin Walters walt...@redhat.com Sent: Wednesday, August 26, 2015 2:09:23 PM Subject: Atomic Host and the kernel Hi All, I'm emailing my questions on the

Re: F23 beta vagrant box issues

- Original Message - > From: "Dusty Mabe" > To: cloud@lists.fedoraproject.org > Sent: Tuesday, September 8, 2015 2:54:06 PM > Subject: F23 beta vagrant box issues > > We have had several people report issues with the F23 beta vagrant box > [1]. I see this in the

Re: Two-Week Atomic actual deliverables

- Original Message - > From: "Matthew Miller" > To: "Fedora Cloud SIG" > Sent: Friday, September 11, 2015 8:59:55 AM > Subject: Re: Two-Week Atomic actual deliverables > > On Thu, Sep 10, 2015 at 01:02:10PM -0400, Matthew Miller

Re: Mo's proposed fedora atomic logo

- Original Message - > From: "Matthew Miller" > To: "Fedora Cloud SIG" > Sent: Tuesday, September 15, 2015 11:23:54 AM > Subject: Mo's proposed fedora atomic logo > >

Re: 2 week Atomic Host release ready for testing

- Original Message - > From: "Joe Brockmeier" > To: cloud@lists.fedoraproject.org > Sent: Thursday, September 10, 2015 12:05:08 PM > Subject: Re: 2 week Atomic Host release ready for testing > > On 09/10/2015 02:21 PM, Michael McGrath wrote: > > Latest Atomic Host

Re: [DRAFT] Fedora 2 week Atomic Announcement

- Original Message - > From: "Joe Brockmeier" > To: "Fedora Cloud SIG" > Sent: Thursday, December 3, 2015 2:46:23 PM > Subject: [DRAFT] Fedora 2 week Atomic Announcement > > Hey all, > > Please take a look at this and let me know if

Re: [DRAFT] Fedora 2 week Atomic Announcement

- Original Message - > From: "Joe Brockmeier" <j...@redhat.com> > To: cloud@lists.fedoraproject.org > Sent: Friday, December 4, 2015 5:47:14 AM > Subject: Re: [DRAFT] Fedora 2 week Atomic Announcement > > On 12/03/2015 05:57 PM, Jason Brooks wrote:

Re: root on btrfs and lvmthinp for docker backing confusion

- Original Message - > From: "Chris Murphy" > To: "Fedora Cloud SIG" > Sent: Thursday, December 10, 2015 12:39:26 AM > Subject: root on btrfs and lvmthinp for docker backing confusion > > OK instead of hijacking some other

Re: [atomic-devel] Fedora 24 Based Two-Week Atomic Release Delayed - Feedback Requested

On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller wrote: > Hello all, > The original schedule for today's Fedora Two-Week Atomic Release > was going to include a cut-over of our back end Release Infrastructure > and AutoCloud automated QA environment to be compose

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

> > > > There is some history behind that. There is a bug report for it here: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1291860 > > Well sort of, it explains where the source for the package is coming from but > it doesn't really help me understand whether I should trust the package

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

On Wed, Jul 27, 2016 at 7:28 AM, Colin Walters wrote: > > > On Tue, Jul 26, 2016, at 04:59 PM, nore...@fedoraproject.org wrote: >> >> A new update of Fedora Cloud Atomic Host has been released and can be >> downloaded at: >> >> Images can be found here: >> >>

Minutes from 7/20

== #fedora-meeting-1: fedora_cloud_wg == Meeting started by jbrooks at 17:00:08 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-07-20/fedora_cloud_wg.2016-07-20-17.00.log.html . Meeting

[atomic-wg] Issue #188 `Remove-Kube: produce official containers with Kubernetes components`

jasonbrooks added a new comment to an issue you are following: `` I have the kube containers added to the layered build service, but I'm blocked until the build service allows for releasing containers -- my kube master components are based on a master image, and the node components are based on

[atomic-wg] Issue #187 `Remove-Kube: Make fully containerized install work`

The issue: `Remove-Kube: Make fully containerized install work` of project: `atomic-wg` has been assigned to `jasonbrooks` by jasonbrooks. https://pagure.io/atomic-wg/issue/187 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe

[atomic-wg] Issue #188 `Remove-Kube: produce official containers with Kubernetes components`

The issue: `Remove-Kube: produce official containers with Kubernetes components` of project: `atomic-wg` has been assigned to `jasonbrooks` by jasonbrooks. https://pagure.io/atomic-wg/issue/188 ___ cloud mailing list -- cloud@lists.fedoraproject.org

[atomic-wg] Issue #187 `Remove-Kube: Make fully containerized install work`

jasonbrooks added a new comment to an issue you are following: `` I'm working on this, currently debugging some flannel system container issues. My ansible scripts are here: https://github.com/jasonbrooks/contrib/tree/atomic-update. I'm testing w/ two node, one master clusters based on a

Re: Atomic Host: important updates in testing

On Tue, Feb 7, 2017 at 6:41 AM, Matthew Miller wrote: > On Tue, Feb 07, 2017 at 09:37:31AM -0500, Dusty Mabe wrote: >> Here is a summary of what is in updates-testing vs what is in updates: > [...] >> To rebase to the updates-testing tree just run: >> rpm-ostree rebase

[atomic-wg] Issue #200 `Planning for interim container releases: To rebuild or not rebuild?`

jasonbrooks added a new comment to an issue you are following: `` We should do what's needed to ensure that our images pick up the most recent rpms -- when you say rebuild all content, do you mean rebuild the rpms themselves, or rebuild all the images? `` To reply, visit the link below or just

[atomic-wg] Issue #187 `Remove-Kube: Make fully containerized install work`

jasonbrooks added a new comment to an issue you are following: `` RE the flannel issues I mentioned: https://github.com/projectatomic/atomic-system-containers/issues/28, fixed by https://github.com/projectatomic/atomic-system-containers/pull/29 `` To reply, visit the link below or just reply

[atomic-wg] Issue #187 `Remove-Kube: Make fully containerized install work`

jasonbrooks added a new comment to an issue you are following: `` Regular docker containers for the kube components (https://github.com/jasonbrooks/k8s-images/tree/f25), and system containers for flannel and etcd (https://github.com/projectatomic/atomic-system-containers). I'm not sure what

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

jasonbrooks added a new comment to an issue you are following: `` Will docker already be at 1.14 by the time f26 ships? I say it's better to test thoroughly in updates-testing and then push to stable when it's ready than flatly ban major docker updates within a Fedora release. `` To reply,

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

jasonbrooks added a new comment to an issue you are following: `` +1 to alignment w/ rhel/centos -- even if we some day have other refs, the "standard" atomic host is the container-hosting one. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/198

Re: Login Credentials for Fedora 25 AWS image

On Fri, Feb 17, 2017 at 1:24 PM, Michael Reilly wrote: > I am new to AWS and Fedora cloud images. I created an instance from the > Fedora 25 AWS image (HVM) Everything appears to have gone well. However > the AWS help indicates that to login I use ssh -i > root@ try

[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`

jasonbrooks added a new comment to an issue you are following: `` > @jasonbrooks. at least one other possible interpretation of "rolling" is that > we consume from rawhide and don't take Number release content. This would > prevent "large change" upgrades like when going from f24 to f25, but

[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`

jasonbrooks added a new comment to an issue you are following: `` > It feels weird to do semi-automatic rebases on the client side. Not saying > it's wrong. But we need to think a bit about how people manage automated > systems. > I guess my question here is - who wouldn't want a single

[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`

jasonbrooks added a new comment to an issue you are following: `` @dustymabe How about this: why should fedora do it differently than rhel? RHEL AH has had the same tree through all docker upgrades, through all kube upgrades, through half of kube being removed, across 7.1, 7.2, 7.3. They

[atomic-wg] Issue #228 `clarify policy on atomic host support for older Fedora "number" releases`

jasonbrooks added a new comment to an issue you are following: `` AFAICT, the thought is that rolling is a big disruptive thing, so we need to study it first. We are in fact not supporting N-1 now, so making that official isn't really a big deal. `` To reply, visit the link below or just reply

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

jasonbrooks added a new comment to an issue you are following: `` We should keep the major version number. It'll be useful for when we start "rolling." `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/229

[atomic-wg] Issue #231 `clarify meaning of "rolling" for future fedora atomic releases`

jasonbrooks reported a new issue against the project: `atomic-wg` that you are following: `` The Atomic WG has unofficially paid attention to only a single fedora atomic release at a time, specifically, the release based on the current latest stable Fedora release. There's a proposal to

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

jasonbrooks added a new comment to an issue you are following: `` Would there ever be more than one version per day? I don't see a problem w/ something like `25.17.0, 25.17.1, 25.17.2, 25.17.3` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/229

Re: Fedora Atomic WG Workflow Proposal

On Tue, Jan 17, 2017 at 6:21 AM, Adam Miller wrote: > On Thu, Jan 12, 2017 at 12:02 PM, Adam Miller > wrote: >> On Wed, Jan 11, 2017 at 4:50 PM, Adam Miller >> wrote: >>> Hello all, >>> Recently I

Re: overlayfs for AFTER Fedora 25

On Wed, Sep 14, 2016 at 12:14 PM, Dusty Mabe wrote: > > In the cloud meeting today I brought up overlayfs and F25. After > discussing with the engineers closer to the technology they recommend > waiting to move to overlayfs as the default in F26. > > I think this will work

Re: Fedora Cloud/Atomic Test Day

I was supposed to send out an ML msg about that but I haven't done it yet. How does Oct 11 sound? Jason On Sep 28, 2016 10:47, "Dusty Mabe" wrote: > Hey Jason, > > Did you ever make any progress on planning a test day for us for this > cycle? > > Dusty >

Re: No Two Week Atomic Release

On Thu, Oct 6, 2016 at 10:19 AM, Colin Walters wrote: > > > On Thu, Oct 6, 2016, at 09:21 AM, Adam Miller wrote: >> Hello all, >> I just wanted to post a quick update that there has not been a >> compose that passed all AutoCloud testing criteria for release in the >> past

Re: No Two Week Atomic Release

On Thu, Oct 6, 2016 at 6:21 AM, Adam Miller wrote: > Hello all, > I just wanted to post a quick update that there has not been a > compose that passed all AutoCloud testing criteria for release in the > past two weeks. It appears that the Vagrant libvirt images

Re: Cloud Atomic Server WGs

On Wed, Sep 21, 2016 at 12:56 PM, Chris Murphy wrote: > Couldn't make the Cloud meeting but just skimmed the log; > cross-posting to server@ list. > > How about combine Cloud and Server WGs into a new WG with three new sub > groups: > hardware, cloud, atomic? > > That

Re: Discussion on changing the name of Working Group

> I am also willing to volunteer for this. As the base image is moving to > server wg, and my work related to rel-eng testing side is stable, I can > refocus myself to the Fedora Atomic host in the same way I was doing > base image. Last few months were about jumping into too many things. I > hope

Re: Discussion on changing the name of Working Group

On Thu, Aug 25, 2016 at 11:43 AM, Dusty Mabe wrote: > > > On 08/24/2016 11:27 AM, Kushal Das wrote: >> Hi all, >> >> During Flock PRD discussion, a proposal was put up about changing the >> name of the WG to Atomic. We have few open questions from last week's >> meeting. I

Re: Fedora Cloud/Atomic Test Day

That'd be fine, or would Fri be better? On Sep 28, 2016 11:54, "Dusty Mabe" <du...@dustymabe.com> wrote: > > > On 09/28/2016 02:13 PM, Jason Brooks wrote: > > I was supposed to send out an ML msg about that but I haven't done it > yet. How does Oct 11 sound?

Re: Fedora Cloud/Atomic Test Day

On Sep 30, 2016 10:12, "Josh Berkus" wrote: > > All, > > Where are we with getting F25 Atomic to boot? If it doesn't boot, I > don't see any point in having a test day. > > Yeah, I was hoping doing it the week after next would give us time to get a testable image. > -- > --

Re: Fedora Cloud/Atomic Test Day

On Thu, Sep 29, 2016 at 10:38 PM, wrote: > Hey Jason > > Did you guys file a ticket for the test day? > If not , here's is where you can [ > https://fedorahosted.org/fedora-qa/report/11 ] > I'm going to file this ticket and write up a post about the test day, but I'm

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`

jasonbrooks added a new comment to an issue you are following: `` The dark text on purple around "atomic cli" is a little tough to read. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/158 ___ cloud

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`

jasonbrooks added a new comment to an issue you are following: `` > > There's a kube 1.4.5 in koji for fc26 > (http://koji.fedoraproject.org/koji/buildinfo?buildID=816481), and I've asked > Jan about making it available for fedora 25. > > Can you keep us in the loop here on the progress of

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`

jasonbrooks reported a new issue against the project: `atomic-wg` that you are following: `` We removed kubernetes, etcd, flannel, gluster and ceph from the atomic host for Fedora 25: https://pagure.io/fedora-atomic/c/219c9bb26426811a5f32188c59682ad70c3283e5?branch=f25 The idea is that these

Re: Blogs for F25 release

I summed up the state of kube on f25 in this issue: https://pagure.io/atomic-wg/issue/176 On Wed, Nov 9, 2016 at 11:45 PM, Josh Berkus wrote: > On 11/09/2016 09:43 AM, Dusty Mabe wrote: >> I believe we need to communicate a few things for F25: >> >> 1 - overlayfs - what it

Re: weird error with docker-storage-setup

On Fri, Oct 21, 2016 at 11:44 AM, Dusty Mabe wrote: > I haven't had time to really investigate but figured I would pass this along: > > > qcow: >

Re: Join Us for a Fedora 25 Test Day Next Week (October 24, 2016)

On Mon, Oct 24, 2016 at 4:44 AM, Kushal Das <m...@kushaldas.in> wrote: > On 19/10/16, Jason Brooks wrote: >> Want to help make Fedora Atomic Host even better? Join us next week >> for the Fedora Cloud Test Day, where we’ll be banging on the Atomic >> Host image for Fedor

Re: Join Us for a Fedora 25 Test Day Next Week (October 24, 2016)

On Mon, Oct 24, 2016 at 7:54 AM, Jason Brooks <jbro...@redhat.com> wrote: > On Mon, Oct 24, 2016 at 4:44 AM, Kushal Das <m...@kushaldas.in> wrote: >> On 19/10/16, Jason Brooks wrote: >>> Want to help make Fedora Atomic Host even better? Join us next week >>&g

[atomic-wg] Issue #177 `Disable interactive "cp" in fedora base image`

jasonbrooks added a new comment to an issue you are following: `` Right, I wonder if we can/should toss in some `unalias` commands into: https://pagure.io/fedora-kickstarts/blob/f25/f/fedora-docker-base.ks. `rm` and `mv` are also aliased to be interactive. CentOS has the same aliases. `` To

[atomic-wg] Issue #177 `Disable interactive "cp" in fedora base image`

jasonbrooks added a new comment to an issue you are following: `` It looks like you can ignote the alias w/ `\cp`. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/177 ___ cloud mailing list --

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`

jasonbrooks added a new comment to an issue you are following: `` We talked about enabling the network service, but we instead patched cloud-init to make NM work. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`

jasonbrooks added a new comment to an issue you are following: `` dist-git won't allow for pull requests, will it? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/180 ___ cloud mailing list --

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`

jasonbrooks added a new comment to an issue you are following: `` kube 1.4.5 for f25 in bodhi: https://bodhi.fedoraproject.org/updates/FEDORA-2016-fffea4b1c3 I've been working on getting it running in rpm-installed node pkgs / master pkgs in containers. Notes on that here:

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`

jasonbrooks added a new comment to an issue you are following: `` > 1) it requires package layering, which really pushes up the idea of having a > way for users to build their own OStree servers. What do you mean by that? Package layering doesn't require someone to build their own ostree

[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`

jasonbrooks added a new comment to an issue you are following: `` @pfrields That's it, thanks -- losing PRs is the main thing I'd miss about the current Fedora-Dockerfiles going away. It'll be awesome to have pagure fronting dist-git. `` To reply, visit the link below or just reply to this

Re: network not coming up on 20161011 FAH

On Tue, Oct 11, 2016 at 3:00 PM, Dusty Mabe wrote: > > > https://kojipkgs.fedoraproject.org//work/tasks/3677/16053677/Fedora-Cloud-Base-25-20161011.n.0.x86_64.qcow2 > > > seen on local kvm as well as on openstack newton: > > Cloud-init v. 0.7.7 running 'init' at Tue, 11 Oct

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe <du...@dustymabe.com> wrote: > > > On 12/12/2016 05:19 PM, Jason Brooks wrote: >> On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe <du...@dustymabe.com> wrote: >>> >>> After I get a bug[1] fixed and out the d

Re: Fedora 26 change: using overlayfs as default

On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe wrote: > > After I get a bug[1] fixed and out the door I'm going to publish > a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud > base to use overlay2 as the storage driver for docker. > > I'd like for everyone that

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`

jasonbrooks added a new comment to an issue you are following: `` Some updates: * the issue of fedora having an aged kube is resolved, v1.4.5 is in f25 stable * the issue of not being able to just `rpm-ostree install kubernetes` and proceed as if we never removed kube from the image is open.

Re: Prerequisites to removing Kube from base image

On Mon, Jan 9, 2017 at 1:21 PM, Josh Berkus wrote: > Atomic WG: > > I've filed four issues which I think represent the prerequisites to > making removal of the kubernetes binaries from the base Atomic image work. > > https://pagure.io/atomic-wg/issues?status=Open=remove-kube >

Cloud Meeting Minutes 2017-01-11

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atomic_wg.2017-01-11-17.00.html full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atomic_wg.2017-01-11-17.00.log.html === #fedora-meeting-1:

[atomic-wg] Issue #248 `Container Guidelines: Layered Images used as a base for other Layered Builds`

jasonbrooks added a new comment to an issue you are following: `` FYI, I have images like this now: http://pkgs.fedoraproject.org/cgit/docker/kubernetes-apiserver.git/tree/Dockerfile?h=f25 ``` FROM registry.fedoraproject.org/f25/kubernetes-master:latest ``` `` To reply, visit the link below or

Re: Meeting about rolling releases

On Fri, Mar 17, 2017 at 6:44 AM, Colin Walters wrote: > I can maybe attend this but I already have a lot of meetings today > and I'd like to write some code. > > My feelings on this are basically: > > 1) I wrote on an issue I can't find now, but I was basically suggesting: >

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

jasonbrooks added a new comment to an issue you are following: `` I made some edits (I made them in a google doc and sent you the link if you want that): === systemd-Based Containers === A systemd-based container runs systemd(/usr/bin/init) by default as its entrypoint. One or more services

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

jasonbrooks added a new comment to an issue you are following: `` How does this look? @dwalsh === systemd-Based Containers === A systemd-based container includes the systemd system and service manager as part of its image in order to run one or more systemd-managed services within a single

[atomic-wg] Issue #253: lower case vs Initial Cap in Labels

jasonbrooks added a new comment to an issue you are following: `` > I'm ok with com.redhat.component for long and short term. However if we > decide we need a org.fedoraproject.component then can we just go with > com.redhat.component in the short term so that we don't block? +1 `` To reply,

[atomic-wg] Issue #262: F26 Talking Points

jasonbrooks added a new comment to an issue you are following: `` These need some processing to suss out what's important, but f25 GA to current f26 is atomic 1.13.1 to 1.16.5: https://github.com/projectatomic/atomic/blob/master/CHANGELOG.md `` To reply, visit the link below or just reply to

Atomic WG Meeting Minutes 2017-04-05

#fedora-meeting-1: atomic_wg Meeting started by jbrooks at 17:01:22 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2017-04-05/atomic_wg.2017-04-05-17.01.log.html . Meeting summary ---

[atomic-wg] Issue #262: F26 Talking Points

jasonbrooks added a new comment to an issue you are following: `` With https://pagure.io/fedora-atomic/c/785b27dfeeeb6055af8b6581c247ca1412128dd6?branch=f25 did we actually start shipping more locales with atomic? That happened during 25 but after 25 first shipped. `` To reply, visit the link

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

jasonbrooks added a new comment to an issue you are following: `` The atomic-specific bits of each atomic host are very close. The questions relating to each, including things like enabling gpg sig verification or mirroring ostree content, generally apply to both centos and fedora atomic. You

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

jasonbrooks 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

[atomic-wg] Issue #304: Update to kubernetes 1.7.x

jasonbrooks added a new comment to an issue you are following: `` The kubernetes project maintains two releases at a time -- one way we might approach this is to keep the newer release in rawhide and the N-1 release in Fedora stable, and swap when a new upstream releases goes GA. As long as we

[atomic-wg] Issue #304: Update to kubernetes 1.7.x

jasonbrooks added a new comment to an issue you are following: `` Or, we could track the latest in Fedora stable and the alpha releases in rawhide -- that seems a bit more true to rawhide, and still worthwhile, but I can imagine people wanting to run the N-1 version, and we don't have a way of

[atomic-wg] Issue #228: clarify policy on atomic host support for older Fedora "number" releases

jasonbrooks added a new comment to an issue you are following: `` > Suggested revision: > > Due in part to this faster pace, the Fedora Atomic workgroup has always > focused its testing and integration efforts most directly on the latest > stable release, encouraging users of the older release

[atomic-wg] Issue #279: talk/workshop proposals for Flock

jasonbrooks added a new comment to an issue you are following: `` Discussing Kubernetes and Openshift Origin Deployment Options by @jasonbrooks and @yzhang When it comes to methods of deploying kubernetes and openshift origin clusters, the Fedora community faces an embarrassment of riches:

[atomic-wg] Issue #228: clarify policy on atomic host support for older Fedora "number" releases

jasonbrooks added a new comment to an issue you are following: `` PR for this blog post at: https://github.com/projectatomic/atomic-site/pull/434 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/228 ___

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

jasonbrooks 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/86 ___ cloud mailing list --

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

jasonbrooks 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 --