Latest revision as of 18:06, 27 June 2014

Docker Container Image

Summary

This is Fedora running inside Docker. Currently, there are non-official images in the docker index, but we'd like them to really come out of release engineering.

Owner

Name: Lokesh Mandvekar / Dennis Gilmore
Email: lsm5@fedoraproject.org, dennis@ausil.us
Release notes owner:

Current status

Targeted release: Fedora 21
Last updated: 2014-04-07
Tracker bug: #1090890

Detailed Description

The public docker registry hosts many fedora images including an unprefixed (semi-official) image. However, this image doesn't have rel-eng approval which would be required for a fully official image.

The goal of this change is an unprefixed official image uploaded via Fedora rel-eng to Docker. Part of the change is to get rel-eng account/access in order to do the upload.

Benefit to Fedora

This will give docker/fedora users something trustworthy to build other stuff on. Will also give fedora an awesome presence on the docker index :)

Scope

Needs work in Koji to generate Docker base image reliably. There's conceptually two steps: first the tarball is generated, then it's imported. This change is still worthwhile even if the image isn't uploaded to the registry, as people could download it directly from Fedora and import it locally.

Proposal owners:

The proposal owner needs to build the image tarballs with the official kickstart scripts and make them available to docker's stackbrew repo, which is used by the Docker maintainers to build unprefixed images.

Release Engineering approval/intervention would be needed at some point (details still TBD)

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

Release engineering: Official Release Engineering image approval. Process still TBD.

Policies and guidelines: N/A (not a System Wide 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

Available here.

Release Notes

The Fedora image in the Docker index is now Fully Official! For details, see....

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+= Docker Container Image =
-<!-- Self Contained or System Wide Change Proposal?
-Use this guide to determine to which category your proposed change belongs to.
-Self Contained Changes are:
-* changes to isolated/leaf package without the impact on other packages/rest of the distribution
-* limited scope changes without the impact on other packages/rest of the distribution
-* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
-System Wide Changes are:
-* changes that does not fit Self Contained Changes category touching
-* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
-* changing system defaults
-For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
-improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
-We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
--->
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name <!-- The name of your change proposal --> =
 == Summary ==
-<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
+This is Fedora running inside Docker. Currently, there are non-official images in the docker index, but we'd like them to really come out of release engineering.
 == Owner ==
@@ Line 32: / Line 9: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:lsm5| Lokesh Mandvekar]] / [[User:ausil | Dennis Gilmore]]
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Email: lsm5@fedoraproject.org, dennis@ausil.us
 * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
@@ Line 45: / Line 22: @@
 == Current status ==
-* Targeted release: [[Releases/<number> | Fedora <number> ]]
+* Targeted release: [[Releases/21 | Fedora 21 ]]
-* Last updated: (DATE)
+* Last updated: 2014-04-07
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 Bugzilla states meaning as usual:
@@ Line 55: / Line 32: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1090890 #1090890]
 == Detailed Description ==
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+The [http://index.docker.io public docker registry] hosts many [https://index.docker.io/search?q=fedora fedora images] including an [https://index.docker.io/_/fedora/ unprefixed (semi-official) image]. However, this image doesn't have rel-eng approval which would be required for a fully official image.
+The goal of this change is an unprefixed official image uploaded via Fedora rel-eng to Docker.  Part of the change is to get rel-eng account/access in order to do the upload.
 == Benefit to Fedora ==
 <!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+This will give docker/fedora users something trustworthy to build other stuff on. Will also give fedora an awesome presence on the docker index :)
 == Scope ==
+Needs work in Koji to generate Docker base image reliably.  There's conceptually two steps: first the tarball is generated, then it's imported.  This change is still worthwhile even if the image isn't uploaded to the registry, as people could download it directly from Fedora and import it locally.
 <!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 * Proposal owners:
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+The proposal owner needs to build the image tarballs with the official kickstart scripts and make them available to docker's [https://github.com/dotcloud/stackbrew stackbrew] repo, which is used by the Docker maintainers to build unprefixed images.
+Release Engineering approval/intervention would be needed at some point (details still TBD)
 * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: Official Release Engineering image approval. Process still TBD.  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
@@ Line 126: / Line 113: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+Available [[Getting_started_with_docker | here]].
 == Release Notes ==
@@ Line 135: / Line 122: @@
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF21]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 144: / Line 131: @@
 [[Category:SelfContainedChange]]
 <!-- [[Category:SystemWideChange]] -->
+The Fedora image in the Docker index is now Fully Official! For details, see....

Search

Changes/Docker Container Image: Difference between revisions

Latest revision as of 18:06, 27 June 2014

Contents

Docker Container Image

Summary

Owner

Current status

Detailed Description

Benefit to Fedora

Scope

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes