From Fedora Project Wiki
(Move to Fedora 22, see tracking bug for more details)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= (A)Periodic Updates to Images =
= (A)Periodic Updates to Cloud Images =


== Summary ==
== 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.
We want to be able to release updated cloud images not just at release time. Hope for a one-month regular cadence, plus emergency updates if needed.


== Owner ==
== Owner ==
* Name: Cloud WG collectively, [[User:mattdm| Matthew Miller]] as point of contact.
* Name: Cloud WG collectively, [[User:mattdm| Matthew Miller]] as point of contact.
* Email: cloud at lists.fedoraproject, mattdm at fedoraproject
* Email: cloud at lists.fedoraproject, mattdm at fedoraproject
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes owner: [[User:Pbokoc| Petr Bokoc]] pbokoc at redhat dot com
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product: Cloud
* Product: Cloud
* Responsible WG: Cloud
* Responsible WG: Cloud
-->


== Current status ==
== Current status ==
* Targeted release: [[Releases/21 | Fedora 21 ]]  
* Targeted release: [[Releases/22 | Fedora 22 ]]  
* Last updated: (DATE)
* Last updated: 2014-04-08
<!-- 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  
Bugzilla states meaning as usual:
Bugzilla states meaning as usual:
Line 27: Line 25:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
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=1091299 #1091299]


== Detailed Description ==
== Detailed Description ==
Line 44: Line 42:


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.)
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.)
Ultimately, we would like to produce updates whenever a package on the image or the kickstart file for the image changes. This is a step towards that goal.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 52: Line 52:


== Scope ==
== Scope ==
<!-- 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:
* Proposal owners: Create policies and procedures as outlined above. Will also assist with changes to release engineering.
<!-- 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?-->


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: Contributions welcome!
<!-- 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: Significant impact, obviously. Cloud WG will interact heavily with Release Engineering and work in concert.
<!-- 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. -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: No changes to existing policies.
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Users are expected to replace one image with the next.
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
The test of this feature is simply whether new images are available and functional.


A good "how to test" should answer these four questions:
Tests ''of'' the image are part of the feature proposal itself.


0. What special hardware / data / etc. is needed (if any)?
== User Experience ==
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== User Experience ==
Users will be able to select versioned images for download or launch in cloud providers. We may provide a simple web service for selecting images, (perhaps compatible with [https://launchpad.net/simplestreams simplestreams]).
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)  


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
No package dependencies but there are significant dependencies on release engineering.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: continue to do updates by hand
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: technically, first critical security update after F21 release, or first month after, whichever comes first.
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks release? no
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? no
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
TBD
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
Let's not make promises in the release notes.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangePageIncomplete]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->  
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->

Latest revision as of 13:16, 20 October 2014

(A)Periodic Updates to Cloud Images

Summary

We want to be able to release updated cloud 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: Petr Bokoc pbokoc at redhat dot com
  • Product: Cloud
  • Responsible WG: Cloud

Current status

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.)

Ultimately, we would like to produce updates whenever a package on the image or the kickstart file for the image changes. This is a step towards that goal.

Benefit to Fedora

When a massive security problem hits Fedora, we currently do image updates manually. Because this is exceptional, there is a lot to go wrong, and of course, things always go wrong at the worst possible times. The primary benefit of this change is to make image updates routine, so that when emergency update happens, we can handle it as if it were no big deal.

The actual updated images are, of course, a valuable secondary benefit. Since cloud images are usually short-lived, this allows new instances to be created without the overhead of applying several months' updates.

Scope

  • Proposal owners: Create policies and procedures as outlined above. Will also assist with changes to release engineering.
  • Other developers: Contributions welcome!
  • Release engineering: Significant impact, obviously. Cloud WG will interact heavily with Release Engineering and work in concert.
  • Policies and guidelines: No changes to existing policies.

Upgrade/compatibility impact

Users are expected to replace one image with the next.

How To Test

The test of this feature is simply whether new images are available and functional.

Tests of the image are part of the feature proposal itself.

User Experience

Users will be able to select versioned images for download or launch in cloud providers. We may provide a simple web service for selecting images, (perhaps compatible with simplestreams).

Dependencies

No package dependencies but there are significant dependencies on release engineering.

Contingency Plan

  • Contingency mechanism: continue to do updates by hand
  • Contingency deadline: technically, first critical security update after F21 release, or first month after, whichever comes first.
  • Blocks release? no
  • Blocks product? no

Documentation

TBD

Release Notes

Let's not make promises in the release notes.

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