1 / 23

The Condor “RoadMap” Condor Week 2003

The Condor “RoadMap” Condor Week 2003. Todd Tannenbaum Department of Computer Sciences University of Wisconsin-Madison http://www.cs.wisc.edu/condor condor-admin@cs.wisc.edu. Overview. Impact of the new license What to expect over the next year(*) Research thrusts Software Release plans

binta
Download Presentation

The Condor “RoadMap” Condor Week 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. The Condor “RoadMap”Condor Week 2003 Todd Tannenbaum Department of Computer Sciences University of Wisconsin-Madison http://www.cs.wisc.edu/condor condor-admin@cs.wisc.edu

  2. Overview • Impact of the new license • What to expect over the next year(*) • Research thrusts • Software Release plans * Must-Forget-Disclaimer-Clause Rigorously Enforced

  3. License Change:Old License “Condor Internal Use License” • Right to install & use Condor at your organization • Can create derivative works, but… • May not redistribute • Long and complex • “Draconian” clauses

  4. License Change:New License “Condor Public License” Changed Feb 03 – Permits: • Installation and use • Reproduction • Modification • Redistribution • All with or without modification • In source and binary forms ! • Very similar to Globus License

  5. Open Source, but…WHERE’S THE BEEF^H^H SOURCE?!? • Readying the code • Making code base “self-contained” • Expect public source releases in summer • Note: License already changed!

  6. How much support we can give open source contributors is an open question. Some Strategies...

  7. Contribution Strategies • Bug fixes, no problem… • Significant Enhancements • Layer logic on top of Condor whenever possible • If changes are required to core Condor, open a dialog w/ the Condor Teambefore starting to work on your implementation

  8. Sending Contributions to Condor • Send us: • Source • Documentation • Testing strategy utilized • License issues; contribution must be • Licensed to the Condor Project, or • Assigned to the Condor Project, or • In the public domain w/ a compatible license • NOTE: GPL is not a compatible license!

  9. Issues: Open Source to Open Community • Discussion List • Online Source Code Repository • Do not need to wait for developer releases • RUST (or bugzilla?) move to online • Better developer documentation

  10. Release Schedule • Current Developer Release on the web: Condor v6.5.1 • What we have in-house: Condor v6.5.3 • Condor v6.5.3 is our next stable release candidate, and is in “code freeze”. • Condor v6.6.0 is ~4 weeks away.

  11. What’s New in Condor v6.6? • Covered by Zach. • What’s coming down the road in the next developer series? Already heard about: • “Self-contained” open source friendly build process • Closer integration w/ NMI / VDT build and test process • HawkEye • COD improvements

  12. Already heard about, cont. • Grid Shell • Generic “wrapper” for grid jobs • Monitor resource utilization of job • Monitor progress and completion status of job • Online I/O access independent of grid middleware • Perhaps some FTSH components

  13. Already heard about, cont. • Condor-G • MyProxy integration • Job Policy Expressions • Improved (easier) GlideIn • New Job Types • GT3 (OGSA), Oracle, NorduGrid

  14. What’s Next?Future Directions • Increased integration of data management and other Condor Project technology into the Condor HTC Software • And collaborator data management technology: • SRM • IBP • SAM • GridFTP • SRB • NeST • PFS • Stork • Diskrouter • FTSH • ByPass • NMI/VDT • HawkEye • GCB • Condor-G

  15. What’s Next? Big Item: More focus on being a service provider than just an end-user tool • XML representations of user logs, ClassAds, accounting info, etc. • Developer APIs / libraries • DRMAA • (Distributed Resource Management Application API) • SOAP access to services • Grid Service (OGSI)

  16. Distributed Resource Management Application API • Specification for the submission and control of jobs to one or more DRM systems • An API : not a protocol • Scope • Does: job submission, monitoring, control, final status • Does not: file staging, reservations, security, … • Proposed specification announced at GGF 7 • Committee co-chaired by Intel and Sun

  17. SOAP/Grid Service condor_schedd Cedar Web Service: SOAP HTTPS OGSI: SOAP HTTPG

  18. More what’s next… • Condor on Windows • Pass user credential to the execution site • Run the job as the user • Complete Shared Filesystem Support • Remote System Calls • No relink required • Note: Remote I/O Socket is already available • Assist with ACL management • Weds: Condor on Win32 BoF • Ports • “Clipped”  Full • Clipped means everything except the STANDARD universe

  19. Ports available Now (v6.6) • Full : • Linux RedHat 6.x, 7.x [x86] • HPUX 10.20 • Tru64 4.x • Solaris 2.6,2.7,2.8,2.9 [SPARC] • IRIX 6.5 • “Clipped” • Linux RedHat 8.0 [x86] • Linux SUSE and RH 7.2 [IA64] • Tru64 5.1 • HPUX 11.11 • Windows NT/2K/XP • Max OS X

  20. Ports in the Hopper • Full versions of everything clipped • And: • RedHat 9 [x86 and IA64] • AIX 5.1 “clipped” • HPUX 11.11 [PA2.0 and IA64] “clipped”

  21. More what’s next… • New version of ClassAds into Condor • Conditionals !! • if/then/else • Aggregates (lists, nested classads) • Built-in functions • String operations, pattern matching, time operators, unit conversions • Clean implementations in C++ and Java • ClassAd collections • Just this + open source changes may become ver 6.8.0.

  22. Thank you!

More Related