Features/Condor Cloud

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m
(Updated percent complete.)
 
(10 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 19: Line 20:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/16 | Fedora 16 ]]  
 
* Targeted release: [[Releases/16 | Fedora 16 ]]  
* Last updated: 2011-07-11
+
* Last updated: 2011-11-01
* Percentage of completion: 90%
+
* Percentage of completion: 100%
  
  
Line 55: Line 56:
 
-->
 
-->
  
You will need to install the Condor package and then get the source from:
+
* You will need a bare metal machine, not a VM to run it on.
  
http://git.fedorahosted.org/git/?p=condor-cloud.git
+
* You will need to install the condor-cloud rpm.
  
There is an INSTALL document in the source, you can see it here:
+
* Read and follow directions in /usr/share/doc/condor-cloud/fedora_install.txt.
  
http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=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.
 
+
Once it is an RPM it will just be a matter of installing the deltacloud RPM (with condor cloud driver) and the condor-cloud rpm.  The latter will add configuration entries and scripts to allow you to set up condor as a cloud provider.
+
  
 
== User Experience ==
 
== User Experience ==
Line 73: Line 72:
 
<!-- 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
+
* condor RPM
deltacloud RPM
+
* deltacloud RPM
condor-cloud RPM (yet to be made).
+
* condor-cloud RPM (yet to be made).
  
Mostly we depend on getting the deltacloud driver upstream.  I have posted the git repo location to the list and am awaiting review for acceptance.  I have talked to David Lutterkort and it sounds like it will not be a problem.
+
condor-cloud RPM is now built.  Deltacloud driver is in upstream and a release is pending very soon.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 94: 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 built behind deltacloud (http://deltacloud.org).
+
 
 +
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 ==
Line 100: Line 100:
  
  
[[Category:FeaturePageIncomplete]]
+
[[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


Contents

[edit] Condor Cloud

[edit] Summary

Condor Cloud provides an IaaS cloud implementation using Condor and the Deltacloud API.

[edit] Owner

  • Email: <imain@redhat.com>

[edit] Current status

  • Targeted release: Fedora 16
  • Last updated: 2011-11-01
  • Percentage of completion: 100%


[edit] 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.

[edit] Benefit to Fedora

Condor Cloud would give Fedora a relatively easy to setup, robust cloud IaaS solution.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] Contingency Plan

None necessary, revert to previous release behaviour.

[edit] Documentation

An in-progress design document:

http://git.fedorahosted.org/git/?p=condor-cloud.git;a=blob_plain;f=DESIGN.txt

[edit] 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.

[edit] Comments and Discussion