From Fedora Project Wiki
< Features
No edit summary |
(Updated percent complete.) |
||
| (17 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | |||
<!-- All fields on this form are required to be accepted by FESCo. | <!-- All fields on this form are required to be accepted by FESCo. | ||
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> | We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> | ||
| Line 8: | Line 9: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
Condor Cloud provides | Condor Cloud provides an IaaS cloud implementation using Condor and the Deltacloud API. | ||
== Owner == | == Owner == | ||
| Line 19: | Line 20: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/16 | Fedora 16 ]] | * Targeted release: [[Releases/16 | Fedora 16 ]] | ||
* Last updated: 2011- | * Last updated: 2011-11-01 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 27: | Line 29: | ||
<!-- 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. --> | ||
Condor Cloud provides | Condor Cloud provides an IaaS cloud implementation based on Condor using deltacloud (http://deltacloud.org) as the front end to control the cloud. It supports multiple hosts/nodes, caching of images on each node for quicker startup, and copy on write (COW) image files so the images do not need to be copied per-instance. It uses libvirt/KVM to launch instances on the hosts and is fairly configurable. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 37: | Line 39: | ||
<!-- What work do the developers 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 developers 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?--> | ||
The cloud itself is all up and running. The deltacloud driver would have to be merged with upstream | The cloud itself is all up and running. The deltacloud driver would have to be merged with upstream codebase. We will also need to create a package for the configuration and scripts needed to set up condor as the backend to deltacloud. | ||
== How To Test == | == How To Test == | ||
| Line 54: | Line 56: | ||
--> | --> | ||
You will need to | * You will need a bare metal machine, not a VM to run it on. | ||
* You will need to install the condor-cloud rpm. | |||
* Read and follow directions in /usr/share/doc/condor-cloud/fedora_install.txt. | |||
If you wish to set up other nodes you will need to install condor-cloud-node rpm on each machine and again follow instructions in /usr/share/doc/condor-cloud/fedora_install.txt. | |||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
This cloud could be used directly by end users | This cloud could be used directly by end users via the Deltacloud API. It can also be used as a backend for Aeolus, although there is some testing/integration work to be done on the Aeolus side. | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
* condor RPM | |||
* deltacloud RPM | |||
* condor-cloud RPM (yet to be made). | |||
condor-cloud RPM is now built. Deltacloud driver is in upstream and a release is pending very soon. | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 80: | Line 85: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
An in-progress design document: | |||
http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=DESIGN.txt | http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=DESIGN.txt | ||
| Line 88: | Line 93: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
Condor Cloud is an IaaS cloud implementation | Condor Cloud is an Infrastructure as a Service (IaaS) cloud implementation. It allows you to create as many VMs from an image or images as you wish, distributing them across a pool of configured hosts. The user interface is the Deltacloud API (http://deltacloud.org). The backend is implemented using Condor (http://www.cs.wisc.edu/condor/) which in turn starts VMs using libvirt and KVM. | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/Condor_Cloud]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
[[Category: | [[Category:FeatureAcceptedF16]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 19:09, 1 November 2011
Condor Cloud
Summary
Condor Cloud provides an IaaS cloud implementation using Condor and the Deltacloud API.
Owner
- Name: Ian Main
- Email: <imain@redhat.com>
Current status
- Targeted release: Fedora 16
- Last updated: 2011-11-01
- Percentage of completion: 100%
Detailed Description
Condor Cloud provides an IaaS cloud implementation based on Condor using deltacloud (http://deltacloud.org) as the front end to control the cloud. It supports multiple hosts/nodes, caching of images on each node for quicker startup, and copy on write (COW) image files so the images do not need to be copied per-instance. It uses libvirt/KVM to launch instances on the hosts and is fairly configurable.
Benefit to Fedora
Condor Cloud would give Fedora a relatively easy to setup, robust cloud IaaS solution.
Scope
The cloud itself is all up and running. The deltacloud driver would have to be merged with upstream codebase. We will also need to create a package for the configuration and scripts needed to set up condor as the backend to deltacloud.
How To Test
- You will need a bare metal machine, not a VM to run it on.
- You will need to install the condor-cloud rpm.
- Read and follow directions in /usr/share/doc/condor-cloud/fedora_install.txt.
If you wish to set up other nodes you will need to install condor-cloud-node rpm on each machine and again follow instructions in /usr/share/doc/condor-cloud/fedora_install.txt.
User Experience
This cloud could be used directly by end users via the Deltacloud API. It can also be used as a backend for Aeolus, although there is some testing/integration work to be done on the Aeolus side.
Dependencies
- condor RPM
- deltacloud RPM
- condor-cloud RPM (yet to be made).
condor-cloud RPM is now built. Deltacloud driver is in upstream and a release is pending very soon.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
An in-progress design document:
http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=DESIGN.txt
Release Notes
Condor Cloud is an Infrastructure as a Service (IaaS) cloud implementation. It allows you to create as many VMs from an image or images as you wish, distributing them across a pool of configured hosts. The user interface is the Deltacloud API (http://deltacloud.org). The backend is implemented using Condor (http://www.cs.wisc.edu/condor/) which in turn starts VMs using libvirt and KVM.