< Changes
m (Change accepted by FESCo in today's meeting) |
mNo edit summary |
||
| Line 32: | Line 32: | ||
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: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1619451 #1619451] | ||
== Detailed Description == | == Detailed Description == | ||
Revision as of 21:13, 20 August 2018
Cloud Provider Image Updates
Summary
Provide monthly updates to cloud provider images.
Owner
- SIG: Cloud
- Primary Contact: Joe Doss
- Email: joe@solidadmin.com
- Release notes owner:
- Product: Cloud
- Responsible WG: Cloud SIG
Current status
Detailed Description
Fedora Cloud images are not updated after the initial release of the most current Fedora version. This can leave outstanding issues with the images that can impact the user experience long after they have been addressed by package updates. Providing updated Cloud images across all supported cloud providers on a monthly basis post release will ensure end users are getting the best Fedora Cloud experience possible.
Benefit to Fedora
Update Cloud images will provide a better end user experience as it will ensure it is up to date with the most current packages. This gives users faster Fedora Cloud provisioning times and a secure out of the box Cloud instance.
Scope
- Proposal owners:
Cloud SIG
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: 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
- Outstanding bugs post release will no longer be present in images.
- Improved provisioning times as the initial dnf update will be quicker.
- Improved base image security.
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? N/A This is an internal process change.
Documentation
N/A (not a System Wide Change)