From Fedora Project Wiki
(Moving to F23 as requested in the tracking bug)
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Infobox_group
| name = Local Test Cloud
| image = [[File:Test_cloud_logo_thumb.jpg]]
| caption = [[Cloud Virtualization]]
}}




Line 26: Line 31:
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->


[https://github.com/Rorosha/testCloud testCloud] is a small tool to download and boot cloud images locally.
[https://github.com/Rorosha/testcloud testcloud] is a small tool to download and boot cloud images locally.


== Owner ==
== Owner ==
Line 44: Line 49:
* Responsible WG:
* Responsible WG:
-->
-->
==Installation==
See the [[Local Test Cloud Installation Guide]] for instructions on installation.


== Current status ==
== Current status ==
Line 62: Line 71:
<!-- 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 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:
[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>


It currently supports both the Fedora Cloud Base as well as the Atomic host image.
  testcloud instance create <name of instance> -u <url for qcow2 image>


'''Note:''' ''testCloud will likely change names in the near future.''
It currently supports only the Fedora Cloud Base image, and work is ongoing to support the Atomic host image.  


== Benefit to Fedora ==
== Benefit to Fedora ==

Latest revision as of 20:48, 10 May 2016

Local Test Cloud
Cloud Virtualization



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:

Installation

See the Local Test Cloud Installation Guide for instructions on installation.

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:

 testcloud instance create <name of instance> -u <url for qcow2 image>

It currently supports only the Fedora Cloud Base image, and work is ongoing to support the Atomic host image.

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