Features/Condor Cloud

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Condor Cloud feature page)
 
(Updated percent complete.)
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
+
{{autolang|base=yes}}
 
+
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
+
 
+
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
+
 
+
 
+
 
<!-- 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 11: Line 5:
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
 
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
  
= Feature Name <!-- The name of your feature --> =
+
= Condor Cloud <!-- The name of your feature --> =
  
 
== 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 an IaaS cloud implementation using Condor and the Deltacloud API.
  
 
== Owner ==
 
== Owner ==
 
<!--This should link to your home wiki page so we know who you are-->
 
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:FASAcountName| Your Name]]
+
* Name: [[User:imain| Ian Main]]
  
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: <imain@redhat.com>
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/16 | Fedora 16 ]]  
* Last updated: (DATE)
+
* Last updated: 2011-11-01
* Percentage of completion: XX%
+
* 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 32: Line 28:
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- 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 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 ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 +
 +
Condor Cloud would give Fedora a relatively easy to setup, robust cloud IaaS solution.
  
 
== Scope ==
 
== Scope ==
 
<!-- 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 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 53: Line 55:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
 +
* 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 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 ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 +
 +
None necessary, revert to previous release behaviour.
  
 
== 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
  
 
== Release Notes ==
 
== 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 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 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/YourFeatureName]]  <!-- 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 -->
+
* 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: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