< Features
m (→Current status) |
No edit summary |
||
| Line 38: | Line 38: | ||
<!-- 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 63: | Line 63: | ||
http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=INSTALL.txt | http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=INSTALL.txt | ||
I will endeavor to get this into an RPM asap. | |||
== 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)? --> | ||
Mostly we depend on getting the deltacloud driver upstream, but I don't think that will be too hard. | condor RPM | ||
deltacloud RPM | |||
condor-cloud RPM (yet to be made). | |||
Mostly we depend on getting the deltacloud driver upstream, but I don't think that will be too hard. I will get this started shortly. | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 81: | Line 86: | ||
== 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 | ||
Revision as of 18:43, 8 July 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-07-07
- Percentage of completion: 90%
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 to install the Condor package and then get the source from:
http://git.fedorahosted.org/git/?p=condor-cloud.git
There is an INSTALL document in the source, you can see it here:
http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=INSTALL.txt
I will endeavor to get this into an RPM asap.
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).
Mostly we depend on getting the deltacloud driver upstream, but I don't think that will be too hard. I will get this started shortly.
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 IaaS cloud implementation built behind deltacloud (http://deltacloud.org).