|
|
| Line 1: |
Line 1: |
| {{admon/important | Comments and Explanations | MOSTLY EMPTY DRAFT ''}}
| |
|
| |
|
| |
| = Adopt-Your-Cattle = | | = Adopt-Your-Cattle = |
|
| |
|
| Line 9: |
Line 6: |
| == Owner == | | == Owner == |
| * Name: [[User:mattdm| Matthew Miller]], [[User:sgallagh| Stephen Gallagher]] | | * Name: [[User:mattdm| Matthew Miller]], [[User:sgallagh| Stephen Gallagher]] |
| <!-- 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: mattdm at fedoraproject, sgallagh at redhat.com | | * Email: mattdm at fedoraproject, sgallagh at redhat.com |
| * 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> --> |
| Line 32: |
Line 28: |
|
| |
|
| == 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. -->
| | 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 == | | == Benefit to Fedora == |
| <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
| | 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 == | | == 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:
| | Will work with Cloud and Server SIG members to develop the script and documentation and policies around it. |
| <!-- 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: N/A |
| <!-- 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: N/A |
| <!-- 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: N/A |
| <!-- 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 -->
| | 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). |
| 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.
| | 1. Launch a Fedora Cloud Base Image |
| | 2. Run the conversion script |
| | 3. Treat resulting system as Fedora Server |
|
| |
|
| A good "how to test" should answer these four questions:
| | == User Experience == |
|
| |
|
| 0. What special hardware / data / etc. is needed (if any)?
| | No previous functionality exists. New user experience should be simple and command-line based. |
| 1. How do I prepare my system to test this change? What packages
| | |
| need to be installed, config files edited, etc.?
| | == Dependencies == |
| 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 -->
| | Existence of Fedora Cloud and Fedora Server. |
| N/A (not a System Wide Change)
| |
|
| |
|
| == User Experience ==
| |
| <!-- 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 == | | == Contingency Plan == |
| <!-- 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)? -->
| |
|
| |
|
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| N/A (not a System Wide Change)
| |
|
| |
|
| == Contingency Plan ==
| | * Contingency mechanism: Functionality will not exist |
| <!-- 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 deadline: beta freeze |
| * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | * Blocks release? No |
| <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
| | * Blocks product? No |
| * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |
| <!-- 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. -->
| |
|
| |
|
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| | Documentation will be written but needs to match code which does not exist yet. |
| 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/ -->
| |
| <!-- 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.
| | 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 ... |
| -->
| |
|
| |
|
| [[Category:ChangePageIncomplete]] | | [[Category:ChangePageIncomplete]] |
Adopt-Your-Cattle
Summary
We provide a smooth path so a Cloud Base Image can be turned into Fedora Server.
Owner
- Name: Matthew Miller, Stephen Gallagher
- Email: mattdm at fedoraproject, sgallagh at redhat.com
- Release notes owner:
- Product: Cloud and Server
- Responsible WG: Cloud
Current status
- Targeted release: Fedora 21
- Last updated: 2014-04-04
- Tracker bug: <will be assigned by the Wrangler>
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
Will work with Cloud and Server SIG members to develop the script and documentation and policies around it.
- 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
1. Launch a Fedora Cloud Base Image
2. Run the conversion script
3. 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 ...
