|Line 47:||Line 47:|
Latest revision as of 13:15, 28 July 2009
- 1 Condor Feature
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Optional Feature Packages
- 1.8 Test Plan
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 Contingency Plan
- 1.12 Documentation
- 1.13 Release Notes
Introduce the Condor system into Fedora.
- Name: Matthew Farrellee
- Targeted release: Fedora 8
- Last updated: 27 July 2009
- Percentage of completion: 100%
Condor is a specialized workload management system for compute-intensive jobs. Like other full-featured batch systems, Condor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their serial or parallel jobs to Condor, Condor places them into a queue, chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion.
Benefit to Fedora
Fedora systems will be able to simply join and create Condor pools, of which there are thousands worldwide.
The condor package to be included in Fedora. Including management packages and feature packages built on top of Condor.
Optional Feature Packages
The EC2 Enhanced feature allows for near seamless translation of standard universe Condor jobs to condor EC2 jobs in the grid universe. For all intents and purposes, the job runs as any standard universe job except the execution of the job occurs on an Amazon EC2 AMI instance.
Low-Latency Scheduling provides a means for bypassing condor's normal scheduling process and instead submit work directly to an execute node using the AMQP protocol.
Test on all Fedora architectures. (PASS)
This is not directly visible to typical users. The condor package provides a set of services that can be used to construct and join Condor pools. The typical user will be an administrator.
- gsoap (already in Fedora)
- classads (already in Fedora)
Find in upstream manual.