(Add tracker bug and fix change name typo) |
m (→Owner: added my name) |
||
| Line 7: | Line 7: | ||
== Owner == | == Owner == | ||
* Name: [[User:mattdm| Matthew Miller]], [[User:sgallagh| Stephen Gallagher]] | * Name: [[User:mattdm| Matthew Miller]], [[User:sgallagh| Stephen Gallagher]], [[User:Kushal| Kushal Das]] | ||
* Email: mattdm at fedoraproject, sgallagh at redhat.com | * Email: mattdm at fedoraproject, sgallagh at redhat.com, kushal@fedoraproject.org | ||
* 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) | ||
Revision as of 16:15, 10 October 2014
Convert Fedora Cloud Image to Fedora Server ("Adopt Your Cattle")
Summary
We provide a smooth path so a Cloud Base Image can be turned into Fedora Server. Fedora Cloud images are designed to be run and managed as scale-out undifferentiated "cattle", while Fedora Server is intended for more "pet-like" individually-managed servers.
(See this presentation if you aren't familiar with the pets-vs-cattle cloud computing metaphor.)
Owner
- Name: Matthew Miller, Stephen Gallagher, Kushal Das
- Email: mattdm at fedoraproject, sgallagh at redhat.com, kushal@fedoraproject.org
- Release notes owner:
- Product: Cloud and Server
- Responsible WG: Cloud
Current status
Detailed Description
This is code to be written - it will be a simple script which will take a generic Fedora Cloud Base Image and turn it into Fedora Server.
Benefit to Fedora
This helps address some of the blurry lines between the Cloud and Server products. It gives an easy path for someone who wants to run a traditional server in a public or private cloud environment to get there from images we provide. And, if someone's intended-to-be-cattle server starts developing a personality, this gives a way to deal with that.
Scope
- Proposal owners:
Will work with Cloud and Server SIG members to develop the script and documentation and policies around it.
- Other developers: N/A
- Release engineering: N/A
- Policies and guidelines: N/A
Upgrade/compatibility impact
Systems migrated to Fedora Server in this way should be upgradeable via the normal processes recommended for Fedora Server upgrades, subject to the inherent limitations of cloud providers (e.g., no interactive console access).
How To Test
- Launch a Fedora Cloud Base Image
- Run the conversion script
- Treat resulting system as Fedora Server
User Experience
No previous functionality exists. New user experience should be simple and command-line based.
Dependencies
Existence of Fedora Cloud and Fedora Server.
Contingency Plan
- Contingency mechanism: Functionality will not exist
- Contingency deadline: beta freeze
- Blocks release? No
- Blocks product? No
Documentation
Documentation will be written but needs to match code which does not exist yet.
Release Notes
Adopt Your Cattle! Fedora Cloud is aimed at providing scale-out, largely undifferentiated compute resources. If you want to turn a cloud node into Fedora Server, we have a method for doing so. Read documentation at ...