Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out today[2]. At this time the following Container Images are available in the Fedora

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out today[2]. At this time the following Container Images are available in the Fedora

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out today[2]. At this time the following Container Images are available in the Fedora

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

maxamillion added a new comment to an issue you are following: `` +1 to jberkus' proposal. :thumbsup: `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 ___ cloud mailing list --

[atomic-wg] Issue #297: Disable deltarpms in the Fedora base docker image

The issue: `Disable deltarpms in the Fedora base docker image` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/297 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send

[atomic-wg] Issue #215: Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit

The issue: `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been reset by maxamillion. https://pagure.io/atomic-wg/issue/215 ___ cloud mailing list -- cloud@lists.fedoraproject.org To

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

maxamillion added a new comment to an issue you are following: `` I'm +1 to this Also note, that I created `ato...@lists.fedoraproject.org` months ago and discussed it at one of the meetings but we never really moved over. It's there, it's just "inactive" because there's been zero email to it

[atomic-wg] Issue #284: Fedora OSBS RFE: install go-md2man to buildroot image

maxamillion added a new comment to an issue you are following: `` I meant to update this ticket, I'll get this out to the Infra as soon as we're out of Infrastructure Freeze. (Post Fedora 26 Release, so later this week) `` To reply, visit the link below or just reply to this email

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out today[2]. At this time the following Container Images are available in the Fedora

[atomic-wg] Issue #276: Set architecture label in the base container image

maxamillion added a new comment to an issue you are following: `` PR Submitted to imagefactory to add this functionality. https://github.com/redhat-imaging/imagefactory/pull/402 Once merged, we'll get the configurations in place with [pungi-fedora](https://pagure.io/pungi-fedora) `` To

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out yesterday[2]. At this time the following Container Images are available in the Fedora

[atomic-wg] Issue #276: Set architecture label in the base container image

maxamillion added a new comment to an issue you are following: `` Do you want this to be a LABEL or an ENV? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276 ___ cloud mailing list --

[atomic-wg] Issue #276: Set architecture label in the base container image

The issue: `Set architecture label in the base container image` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/276 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe

[atomic-wg] Issue #284: Fedora OSBS RFE: install go-md2man to buildroot image

The issue: `Fedora OSBS RFE: install go-md2man to buildroot image` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/284 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe

[atomic-wg] Issue #277: Enforce ENV usage as a requirement for release label

The status of the issue: `Enforce ENV usage as a requirement for release label` of project: `atomic-wg` has been updated to: Closed by maxamillion. https://pagure.io/atomic-wg/issue/277 ___ cloud mailing list -- cloud@lists.fedoraproject.org To

[atomic-wg] Issue #277: Enforce ENV usage as a requirement for release label

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

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release[2]. At this time the following Container Images are available in the Fedora Registry. Base Images:

Re: registry.fedoraproject.org/fedora:25 cannot install packages

On Fri, Jun 9, 2017 at 9:37 AM, Jonathan Lebon wrote: > Thanks Adam for the quick resolution. Would it be easy to > have an automated workflow to gate these updates on some > quick sanity tests? E.g. push to `:next` first, run some > tests, and then push to `:latest`? +1

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out earlier today[2]. At this time the following Container Images are available in the

[atomic-wg] Issue #277: Enforce ENV usage as a requirement for release label

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` Currently the [Container Guidelines on LABELS https://fedoraproject.org/wiki/Container:Guidelines#LABELS] *recommend* the use of `ENV` declarations for the `release` but it appears as though this

Re: Announce: Fedora Layered Image Release

On Tue, May 23, 2017 at 9:38 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Mon, May 15, 2017 at 03:45:32PM -0500, Adam Miller wrote: >> > >> > Is the infrastructure now ready for the respin? >> >> It appears the builds are still failing be

Re: Announce: Fedora Layered Image Release

On Mon, May 15, 2017 at 8:16 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Thu, May 11, 2017 at 10:04:19AM -0500, Dennis Gilmore wrote: >> El mié, 10-05-2017 a las 22:47 -0500, Adam Miller escribió: >> > On Tue, May 9, 2017 at 7:22 AM, Jan Pazdziora <jpazdz

Re: Announce: Fedora Layered Image Release

On Tue, May 9, 2017 at 7:22 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Mon, May 08, 2017 at 01:59:36PM -0500, Adam Miller wrote: >> On Thu, May 4, 2017 at 6:55 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: >> > On Thu, Apr 20, 2017 at 10:39:22PM -0500,

Re: Announce: Fedora Layered Image Release

On Thu, May 4, 2017 at 6:55 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote: >> Hello all, >> On behalf of the Fedora Atomic WG[0] and Fedora Release >> Engineering[1], I am pleased to announce the lat

Re: Announce: Fedora Layered Image Release

On Fri, Apr 28, 2017 at 2:39 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote: >> Hello all, >> On behalf of the Fedora Atomic WG[0] and Fedora Release >> Engineering[1], I am pleased to announce the lat

[atomic-wg] Issue #255: Consider creating redirection site for image Help Files

maxamillion added a new comment to an issue you are following: `` This is a request we would need to file with [Fedora Infrastructure](https://pagure.io/fedora-infrastructure) if it's something we actually want. No one in the WG has the capabilities to do this in an official capacity. `` To

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out yesterday[2]. At this time the following Container Images are available in the Fedora

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

maxamillion added a new comment to an issue you are following: `` What @jasonbrooks said. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/248 ___ cloud mailing list -- cloud@lists.fedoraproject.org To

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out yesterday[2]. At this time the following Container Images are available in the Fedora

[atomic-wg] Issue #249 `The build system should provide an automatically populated VERSION label`

The issue: `The build system should provide an automatically populated VERSION label` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/249 ___ cloud mailing list --

[atomic-wg] Issue #236 `container scratch build without a dist-git`

maxamillion added a new comment to an issue you are following: `` We can not currently, absolutely need to. I'll add this to the TODO list. Will update later with a Taiga card in the Fedora RelEng Tools space for context and on-going work. `` To reply, visit the link below or just reply to

Re: Updated Container Guidelines

On Thu, Feb 23, 2017 at 12:07 PM, Honza Horak wrote: > Hi Adam & co., > > I think the container guidelines should include a section about the Layered > Images used as a base for other Layered Builds. I've created an updated > draft that also fixes label names to use the

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the latest Fedora Layered Image Release. This follows the latest Atomic Host Release that came out yesterday[2]. At this time the following Container Images are available in the Fedora

Announce: Fedora Layered Image Release

Hello all, On behalf of the Fedora Atomic WG[0] and Fedora Release Engineering[1], I am pleased to announce the first ever Fedora Layered Image Release. Each Container Image is released with the following streams which aim to provide lifecycle management choices to our users: Name

Re: Ownership of the Cloud Base Image

On Wed, Feb 8, 2017 at 7:01 PM, Dusty Mabe wrote: > > After some discussions with mattdm and sgallagh about the cloud base > image and the server WG we have decided for now to leave the cloud > base image out of the server WG. Obviously it doesn't make sense to > have it stay

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`

The issue: `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/215 ___ cloud mailing list --

[atomic-wg] Issue #225 `Review Container Request for owncload (replacement of Fedora-Dockerfiles GitHub)`

maxamillion added a new comment to an issue you are following: `` Note that the Review Requiest in from jhogarth would replace the owncloud Dockerfile from GitHub. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/225

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

The issue: `Move registry container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been reset by maxamillion. https://pagure.io/atomic-wg/issue/219 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

The status of the issue: `Move registry container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been updated to: Closed by maxamillion. https://pagure.io/atomic-wg/issue/219 ___ cloud mailing list --

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

The issue: `Move registry container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion. https://pagure.io/atomic-wg/issue/219 ___ cloud mailing list --

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion added a new comment to an issue you are following: `` bowlofeggs has already started a review request for the registry: https://bugzilla.redhat.com/show_bug.cgi?id=1420568 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/219

[atomic-wg] Issue #213 `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit`

The status of the issue: `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit` of project: `atomic-wg` has been updated to: Closed as Duplicate by maxamillion. https://pagure.io/atomic-wg/issue/213 ___ cloud mailing

[atomic-wg] Issue #223 `Move container-best-practices container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/container-best-practices `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/223

[atomic-wg] Issue #222 `Move systemd-apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/222

[atomic-wg] Issue #220 `Move earthquake container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/earthquake `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/220

[atomic-wg] Issue #219 `Move registry container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/registry `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/219

[atomic-wg] Issue #218 `Move postgresql container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/postgresql `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/218

[atomic-wg] Issue #215 `Move redis httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/redis `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/215

[atomic-wg] Issue #213 `Move atpmic_scan_openscap container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/atomic_scan_openscap `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/213

[atomic-wg] Issue #214 `Move tools container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/tools `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/214

[atomic-wg] Issue #212 `Move qpid container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/qpid `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/212

[atomic-wg] Issue #211 `Move rabbitmq container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/rabbitmq `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/211

[atomic-wg] Issue #210 `Move systemd-systemd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/systemd/systemd `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/210

[atomic-wg] Issue #208 `Move mariadb container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/mariadb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/208

[atomic-wg] Issue #207 `Move couchdb container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/couchdb `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/207

[atomic-wg] Issue #206 `Move nginx container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/nginx `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/206

[atomic-wg] Issue #205 `Move memcached container image from Fedora-Dockerfiles GitHub into DistGit `

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/memcached `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/205

[atomic-wg] Issue #204 `Move ssh container image from Fedora-Dockerfiles GitHub into DistGit `

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/ssh `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/204

[atomic-wg] Issue #203 `Move apache httpd container image from Fedora-Dockerfiles GitHub into DistGit`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` https://github.com/fedora-cloud/Fedora-Dockerfiles/tree/master/apache `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/203

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

maxamillion 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? Sorry for lack of clarification, I

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` Currently the plan is to sync all container images from Fedora's Registry to the Docker Hub. Do we want to do this under the current [fedora namespace](https://hub.docker.com/u/fedora/) or create a new

[atomic-wg] Issue #201 `Planning for the first Atomic VFAD`

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` Following along with the [proposal that reached general consensus on the mailing

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

maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` The upstream OSBS development group has had to push out the deadlines for the automated rebuild work and Factory 2.0 isn't ready yet (it wasn't planned to be, but it is noted for posterity) which means

Re: Fedora Atomic WG Workflow Proposal

On Thu, Jan 12, 2017 at 12:02 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Wed, Jan 11, 2017 at 4:50 PM, Adam Miller > <maxamill...@fedoraproject.org> wrote: >> Hello all, >> Recently I attempted to start a mailing list thread that was the >>

Re: Fedora Atomic WG Workflow Proposal

On Wed, Jan 11, 2017 at 4:50 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > Hello all, > Recently I attempted to start a mailing list thread that was the > product of a discussion on IRC about putting together an Atomic WG > workshop sessi

Re: Fedora Atomic WG Workflow Proposal

On Thu, Jan 12, 2017 at 8:22 AM, Mike Ruckman <ro...@fedoraproject.org> wrote: > On Wed, 11 Jan 2017 16:50:03 -0600 > Adam Miller <maxamill...@fedoraproject.org> wrote: > > > >> >> Cards created should be units of work that can feasibly be >> accompl

Re: Fedora Atomic WG Workflow Proposal

On Wed, Jan 11, 2017 at 10:05 PM, Dusty Mabe <du...@dustymabe.com> wrote: > > > On 01/11/2017 05:50 PM, Adam Miller wrote: >> Hello all, >> Recently I attempted to start a mailing list thread that was the >> product of a discussion on IRC about putting together

Fedora Atomic WG Workflow Proposal

Hello all, Recently I attempted to start a mailing list thread that was the product of a discussion on IRC about putting together an Atomic WG workshop session[0] at DevConf[1]. This was then discussed during today's Atomic WG Meeting[2] where it was decided that we should make this Workshop

Re: Fedora Cloud DevConf Workshop

On Tue, Jan 10, 2017 at 12:55 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Tue, Jan 10, 2017 at 12:52 PM, Adam Miller > <maxamill...@fedoraproject.org> wrote: >> Hello all, >>During the last Fedora Cloud/Atomic WG meeting jberkus brought up &g

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

maxamillion added a new comment to an issue you are following: `` Proposal for Workshop to work on this stuff at DevConf sent to the mailing list -> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/WBTWBLOYWG66EDXJO2I4G3XY3X6EFAIF/ `` To reply, visit the link

Re: Proposal: require DESCRIPTION, USAGE label for images

On Tue, Jan 10, 2017 at 1:47 PM, Josh Berkus wrote: > On 01/10/2017 10:52 AM, Matthew Miller wrote: >> On Tue, Jan 10, 2017 at 10:44:03AM -0800, Josh Berkus wrote: On Tue, Jan 10, 2017 at 10:33:05AM -0800, Josh Berkus wrote: >> USAGE: single command line giving

Re: Fedora Cloud DevConf Workshop

On Tue, Jan 10, 2017 at 12:52 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > 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, s

Fedora Cloud DevConf Workshop

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

Re: Proposal: require DESCRIPTION, USAGE label for images

On Tue, Dec 13, 2016 at 3:24 PM, Josh Berkus wrote: > 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

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

On Tue, Dec 13, 2016 at 4:18 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko <ignate...@redhat.com> wrote: >> On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller >> <maxamill...@fedoraproject.org> wrote: >>>

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

On Thu, Dec 15, 2016 at 5:49 AM, Trishna Guha <trishnaguh...@gmail.com> wrote: > On Wed, Dec 14, 2016 at 1:06 AM, Adam Miller > <maxamill...@fedoraproject.org> wrote: >> Contributors will go through a simliar process as what they currently do >

Re: [DOC] Review Request for Fedora Atomic

On Fri, Dec 2, 2016 at 3:12 AM, Trishna Guha wrote: > Hi, > > As discussed in Fedora Cloud FAD 2016, We had decided to focus on > Documentation for Fedora Atomic working group. > > Our Documentation is live on [1]. This is the work done so far on > documentation. > We

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko <ignate...@redhat.com> wrote: > On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller > <maxamill...@fedoraproject.org> wrote: >> It is with great pleasure that the Fedora Project Announces the availability >> of the Fedora Docker

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

On Tue, Dec 13, 2016 at 2:45 PM, Dennis Gregorovic <dgre...@redhat.com> wrote: > > > On 12/13/2016 02:36 PM, Adam Miller wrote: >> It is with great pleasure that the Fedora Project Announces the availability >> of the Fedora Docker Layered Image Build Service[0

Announcement: Fedora Docker Layered Image Build Service is GO!

It is with great pleasure that the Fedora Project Announces the availability of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor Community! With this announcement we are opening availability of the Docker Layered Image Build Service for the Docker Layered Images[1] that

Re: Fedora Atomic Host Two Week Release Announcement

On Wed, Dec 7, 2016 at 3:31 PM, wrote: > > A new update of Fedora Cloud Atomic Host has been released and can be > downloaded at: > > Images can be found here: > > https://getfedora.org/en/cloud/download/atomic.html > > Respective signed CHECKSUM files can be found

Re: Docker Layered Image Naming and Tagging

On Thu, Oct 27, 2016 at 11:19 AM, Matthew Miller <mat...@fedoraproject.org> wrote: > On Thu, Oct 27, 2016 at 08:55:33AM -0500, Adam Miller wrote: >> The main thing that concern I have is that with modularity there is >> going to be a concept of "base runtime"

Re: Docker Layered Image Naming and Tagging

On Thu, Oct 27, 2016 at 8:55 AM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Wed, Oct 26, 2016 at 10:13 AM, Matthew Miller > <mat...@fedoraproject.org> wrote: >> On Tue, Oct 25, 2016 at 04:43:55PM -0500, Adam Miller wrote: >>> > I'm not sure we shoul

Re: Docker Layered Image Naming and Tagging

On Wed, Oct 26, 2016 at 10:13 AM, Matthew Miller <mat...@fedoraproject.org> wrote: > On Tue, Oct 25, 2016 at 04:43:55PM -0500, Adam Miller wrote: >> > I'm not sure we should put base distro and distro version as the >> > primary distinguisher. As a user, it's th

Re: Docker Layered Image Naming and Tagging

On Fri, Oct 21, 2016 at 11:10 AM, Matthew Miller <mat...@fedoraproject.org> wrote: > On Fri, Oct 21, 2016 at 10:06:41AM -0500, Adam Miller wrote: >> For layered images, we would follow something similar to: >> >> registry.fedoraproject

Re: [atomic-devel] Announcing Fedora Atomic "latest" download URLs

On Fri, Sep 30, 2016 at 11:57 AM, Josh Berkus <jber...@redhat.com> wrote: > On 09/30/2016 08:58 AM, Adam Miller wrote: >> On Thu, Sep 29, 2016 at 1:54 PM, Josh Berkus <jber...@redhat.com> wrote: >>> On 09/29/2016 08:18 AM, Adam Miller wrote: >>>> On b

No Two Week Atomic Release

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 are failing. We will try again for a release next Two Week window. Thank you, -AdamM

Re: Cloud and Server Q

On Tue, Oct 4, 2016 at 6:21 AM, Kushal Das wrote: > On 30/09/16, Josh Berkus wrote: >> On 09/30/2016 02:01 PM, Josh Boyer wrote: >> >> > 16:44:56 Cloud base image is the only blocking deliverable. >> > 16:44:59 Atomic is not. >> > >> > I realize this WG is in the middle of

Re: Cloud and Server Q

On Fri, Sep 30, 2016 at 8:35 AM, Matthew Miller wrote: > On Thu, Sep 29, 2016 at 04:16:15PM -0700, Adam Williamson wrote: >> > think QA clearly understands what cloud image(s) are release blocking, >> > as previously they were just the non-atomic images. >> Which images

Re: Cloud and Server Q

On Fri, Sep 30, 2016 at 8:35 AM, Matthew Miller wrote: > On Thu, Sep 29, 2016 at 04:16:15PM -0700, Adam Williamson wrote: >> > think QA clearly understands what cloud image(s) are release blocking, >> > as previously they were just the non-atomic images. >> Which images

Re: Docker Layered Image Naming and Tagging

On Thu, Sep 29, 2016 at 6:45 PM, Josh Berkus <jber...@redhat.com> wrote: > On 09/29/2016 03:03 PM, Adam Miller wrote: >> Hello all, >> I was recently discussing some items around docker layered image >> release process in the future with Randy (bowlofeggs)

Re: [atomic-devel] Announcing Fedora Atomic "latest" download URLs

On Thu, Sep 29, 2016 at 1:54 PM, Josh Berkus <jber...@redhat.com> wrote: > On 09/29/2016 08:18 AM, Adam Miller wrote: >> On behalf of the Fedora Cloud Working Group, I am happy to >> announce that we now have a persistent point of download for users who >> wou

Docker Layered Image Naming and Tagging

Hello all, I was recently discussing some items around docker layered image release process in the future with Randy (bowlofeggs) and Patrick (puiterwijk). As a side effect of our discussion there were two questions I wanted to ask of the Cloud WG: 1) Do we want to maintain docker images for

Announcing Fedora Atomic "latest" download URLs

Hello all, On behalf of the Fedora Cloud Working Group, I am happy to announce that we now have a persistent point of download for users who would like to simply reference a single URL for scripting purposes or otherwise. There is also a companion set of URLs that provide the image name that

Re: Fedora Atomic Host Two Week Release Announcement

On Wed, Sep 21, 2016 at 3:47 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Wed, Sep 21, 2016 at 12:53 PM, Adam Miller > <maxamill...@fedoraproject.org> wrote: >> On Wed, Sep 21, 2016 at 12:26 PM, Chris Murphy <li...@colorremedies.com> >> wrot

Re: Fedora Atomic Host Two Week Release Announcement

On Wed, Sep 21, 2016 at 12:53 PM, Adam Miller <maxamill...@fedoraproject.org> wrote: > On Wed, Sep 21, 2016 at 12:26 PM, Chris Murphy <li...@colorremedies.com> > wrote: >> This notification still seems broken. That page says: >> >> The latest two week bui

Re: Fedora Atomic Host Two Week Release Announcement

On Wed, Sep 21, 2016 at 12:26 PM, Chris Murphy wrote: > This notification still seems broken. That page says: > > The latest two week build did not meet our testing criteria. The > images available are from over 22 days ago. Check the Project Atomic > blog for updates and

Re: overlayfs for AFTER Fedora 25

On Wed, Sep 14, 2016 at 2: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

No Two Week Atomic Host this cycle

Hello all, There have not been any composes that have passed all AutoCloud Tests this Two-Week cycle and we will therefore be deferring release until the next cycle. The main blocker bug is being worked on[0]. Thank you, -AdamM [0] - https://bugzilla.redhat.com/show_bug.cgi?id=1353688

Re: Proposal to test AMIs using Autocloud

On Thu, Sep 1, 2016 at 9:22 AM, Sayan Chowdhury wrote: > Hi, > > I am planning to move the testing functionality to test AMIs from > fedimg to Autocloud. Right now, the fedimg just runs the /bin/true > command to test if the AMIs is proper or not. Therefore, I am

  1   2   >