Two Week Atomic

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

Summary

Fedora Atomic Host is an implementation of the Project Atomic pattern for a specialized operating system for the deployment of containerized applications. For the past two Fedora releases, we've included an Atomic Host cloud image as a non-blocking deliverable. However, upstream Atomic is moving very fast — by the end of the alpha, beta, final stabilization cycle Fedora uses, the released artifact is basically obsolete. Additionally, the Project Atomic team at Red Hat would like to do their ongoing development work in the Fedora upstream, and the six-month release cycle does not lend itself to that.

This change moves Atomic away from the main Fedora 6-month distribution release, and instead to separate releases every two weeks on a new web site, http://atomic.fedoraproject.org/

Owner

Name: Matthew Miller
Email: mattdm@fedoraproject.org
cosigners wanted!
Release notes owner:

Current status

Targeted release: Fedora 23 (but actually ideally will start with F22, long before F23 release)
Last updated: 2015-06-16
Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Delivery

1. Move Atomic away from the main Fedora 6-month distribution release, including:

Removal from http://getfedora.org/
F23 atomic images won't be on the regular mirrors

2. Updated Fedora Atomic Host images produced every two weeks, and presented at:

New website at http://atomic.fedoraproject.org/
Images at http://alt.fedoraproject.org/pub/alt/fedora-atomic/

Image Production

1. Images will be produced nightly (See Release Engineering Ticket #6196.)

qcow2 / raw.xz
vagrant variant

2. These images will be built using Anaconda's ostree-target mode from a nightly tree built from the current Fedora release (i.e., currently Fedora 22) plus updates — this may include updates-testing.

will use current-release anaconda for this
may need a mechanism to include an updates.img

3. When the next Fedora release (e.g., F23) branches, those images will also start production (but may not be the target for release; see below)

Testing

Testing will be almost entirely automated and will not require extra resources from the QA team.

Whenever a new image is produced, a listener will receive the associated message on the Fedora message bus
a battery of tests will be automatically executed (initially using tunir (the goal is to migrate to Tasktron when that is ready)
test results will be fed back to fedmsg
and available on a dashboard somewhere

Of course, QA team expertise and help is always welcome
There should also be a mechanism for manually marking an image as failed even if it passes the automatic tests

Release

As with testing, the goal is for this process to be entirely automatic (after initial development, of course).

1. Every two weeks, a process will scan the fedmsg history for image builds which have passed the tests, and

publish to http://atomic.fedoraproject.org/

2. If no image passed the tests in the

Docs

tbd

Marketing

Impact on Cloud

Benefit to Fedora

Scope

Proposal owners:

Other developers: N/A (not a System Wide Change)

Release engineering: N/A (not a System Wide Change)

Policies and guidelines: N/A (not a System Wide Change)

Trademark approval: N/A (not needed for this Change)