< Changes
(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:
- 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
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:
- 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
This replaces upgrading in the cloud context.
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)