No edit summary |
No edit summary |
||
| Line 66: | Line 66: | ||
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. | ||
''testCloud will likely change names in the near future.'' | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Having an easy means to download and try the Fedora cloud images makes for easier testing and allows people without access to a cloud provider to check out the Fedora Cloud product. This allows for greater testing of our cloud images and easier means for people to learn about working in the cloud. | Having an easy means to download and try the Fedora cloud images makes for easier testing and allows people without access to a cloud provider to check out the Fedora Cloud product. This allows for greater testing of our cloud images and easier means for people to learn about working in the cloud. | ||
<!-- 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?--> | ||
Revision as of 23:28, 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 provides an ssh_config to easily connect to the booted instance. What was usually several different tasks to get an image to boot locally is now just:
python testCloud.py <url for qcow2 image>
It currently supports both the Fedora Cloud Base as well as the Atomic host image.
testCloud will likely change names in the near future.
Benefit to Fedora
Having an easy means to download and try the Fedora cloud images makes for easier testing and allows people without access to a cloud provider to check out the Fedora Cloud product. This allows for greater testing of our cloud images and easier means for people to learn about working in the cloud.
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: (What to do? Who will do it?) 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), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)