Line 58: | Line 58: | ||
tbd | tbd | ||
=== Release === | |||
=== Docs === | === Docs === | ||
Line 65: | Line 67: | ||
=== Marketing === | === Marketing === | ||
* Impact on Cloud | * Impact on Cloud | ||
== Benefit to Fedora == | == Benefit to Fedora == |
Revision as of 20:28, 16 June 2015
Two Week Atomic
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. 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
tbd
Release
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)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)