From Fedora Project Wiki
(Fix proposal owner scope)
(Change Announced on 2015-01-21)
Line 150: Line 150:
-->
-->


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAnnounced]]
<!-- 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 13:41, 21 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

  • 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)

Release Notes