From Fedora Project Wiki
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 62: | Line 62: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
[https://github.com/Rorosha/testCloud testCloud] was created because manually booting a cloud image locally can be a pain. It handles downloading the image, spoofing cloud-init metadata as well as | [https://github.com/Rorosha/testCloud testCloud] was created because manually booting a cloud image locally can be a pain. It handles downloading the image, spoofing cloud-init metadata as well as providing an ssh_config to easily connect to the booted instance. What was usually several different steps to get an image to boot locally is now just one: | ||
python testCloud.py <url for qcow2 image> | python testCloud.py <url for qcow2 image> | ||
It currently supports both the Fedora Cloud Base as well as the Atomic host image. | It currently supports both the Fedora Cloud Base as well as the Atomic host image. | ||
'''Note:''' ''testCloud will likely change names in the near future.'' | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Provides a simple means for Fedora users and developers to easily: | |||
* Learn about Cloud (if you don't have access to a cloud provider) | |||
* Test Fedora Cloud releases | |||
* Locally test your cloud application | |||
* Lowers the barrier to get involved with Fedora cloud efforts | |||
<!-- 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?--> | <!-- 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?--> | ||
== Scope == | == Scope == | ||
* Proposal owners:[[User:Roshi]], [[User:Kushal]] | * Proposal owners:[[User:Roshi | Mike Ruckman]], [[User:Kushal | Kushal Das]] | ||
<!-- 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?--> | <!-- 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?--> | ||
| Line 125: | Line 130: | ||
<!-- 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. --> | <!-- 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: | * Contingency mechanism: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * 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? --> | <!-- 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), | * Blocks release? N/A (not a System Wide Change), No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? N/A <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
Latest revision as of 23:58, 20 January 2015
Local Test Cloud
Summary
testCloud is a small tool to download and boot cloud images locally.
Owner
- Name: Mike Ruckman
- Email: roshi@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 22
- Last updated: (2014-01-20)
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
testCloud was created because manually booting a cloud image locally can be a pain. It handles downloading the image, spoofing cloud-init metadata as well as providing an ssh_config to easily connect to the booted instance. What was usually several different steps to get an image to boot locally is now just one:
python testCloud.py <url for qcow2 image>
It currently supports both the Fedora Cloud Base as well as the Atomic host image.
Note: testCloud will likely change names in the near future.
Benefit to Fedora
Provides a simple means for Fedora users and developers to easily:
- Learn about Cloud (if you don't have access to a cloud provider)
- Test Fedora Cloud releases
- Locally test your cloud application
- Lowers the barrier to get involved with Fedora cloud efforts
Scope
- Proposal owners: Mike Ruckman, Kushal Das
- 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
N/A (not a System Wide Change)
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: 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), No
- Blocks product? N/A
Documentation
N/A (not a System Wide Change)