(Add tracking bug) |
(Moving to F23 as requested in the tracking bug) |
||
| Line 46: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/23 | Fedora 23 ]] | ||
* Last updated: (2014-01-20) | * Last updated: (2014-01-20) | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 150: | Line 150: | ||
--> | --> | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Revision as of 15:29, 23 February 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
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 to implement proposed change
- 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)