From Fedora Project Wiki
No edit summary
(work work work)
Line 1: Line 1:
{{admon/important | Comments and Explanations | MOSTLY EMPTY TEMPLATE AWAITING WORK}}
= (A)Periodic Updates to Images =
= (A)Periodic Updates to Images =


Line 7: Line 5:


== Owner ==
== Owner ==
<!--
* Name: Cloud WG collectively, [[User:mattdm| Matthew Miller]] as point of contact.
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
* Email: cloud at lists.fedoraproject, mattdm at fedoraproject
This should link to your home wiki page so we know who you are.
-->
* Name: [[User:FASAcountName| Your Name]]
<!-- 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.>
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* 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)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
Line 19: Line 12:
-->
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* Product: Cloud
* Responsible WG:
* Responsible WG: Cloud
-->
-->


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/21 | Fedora 21 ]]  
* Last updated: (DATE)
* Last updated: (DATE)
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 37: Line 30:


== Detailed Description ==
== 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. -->
 
We need to be able to produce official updates to the Fedora Cloud images. Initially, we plan to release these updates monthly, but also need the ability to release an out-of-cycle update in the event of a severe security issue.
 
This involves:
 
# policy for level of security issue required for out-of-cycle updates
# procedure for notification of security updates in images (as with rpm updates)
# automated QA (at least smoketests)
# documentation of QA expectations
# release engineering process
# mirroring of updated images
# updates to web site for new download links and EC2 AMI IDs.
 
Note that this will apply to the Cloud Base Image, the Docker Host Image, the Big Data Image, and the Docker Container Base Image. (The latter may need separate handling.)


== Benefit to Fedora ==
== Benefit to Fedora ==

Revision as of 18:57, 7 April 2014

(A)Periodic Updates to Images

Summary

We want to be able to release updated images not just at release time. Hope for a one-month regular cadence, plus emergency updates if needed.

Owner

  • Name: Cloud WG collectively, Matthew Miller as point of contact.
  • Email: cloud at lists.fedoraproject, mattdm at fedoraproject
  • Release notes owner:

Current status

  • Targeted release: Fedora 21
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

We need to be able to produce official updates to the Fedora Cloud images. Initially, we plan to release these updates monthly, but also need the ability to release an out-of-cycle update in the event of a severe security issue.

This involves:

  1. policy for level of security issue required for out-of-cycle updates
  2. procedure for notification of security updates in images (as with rpm updates)
  3. automated QA (at least smoketests)
  4. documentation of QA expectations
  5. release engineering process
  6. mirroring of updated images
  7. updates to web site for new download links and EC2 AMI IDs.

Note that this will apply to the Cloud Base Image, the Docker Host Image, the Big Data Image, and the Docker Container Base Image. (The latter may need separate handling.)

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)

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)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/(A)Periodic_Updates_to_Cloud_Images&oldid=375642"