1 / 24

Condor Team 2008

Condor Team 2008. Welcome to Condor Week #10 (year #25 for the project). Goodbye Grids Welcome Clouds! we survived grids, we are ready for clouds and prepare for what will follow. Subject: PS From: Ian Foster <foster@anl.gov> Date: Thu, 4 Dec 2008 19:40:28 -0600

trang
Download Presentation

Condor Team 2008

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. Condor Team 2008

  2. Welcome toCondor Week #10(year #25 for the project)

  3. Goodbye GridsWelcome Clouds!we survived grids, weare ready for clouds andprepare for what will follow

  4. Subject: PS From: Ian Foster <foster@anl.gov> Date: Thu, 4 Dec 2008 19:40:28 -0600 To: Miron Livny miron@cs.wisc.edu Miron: I visited CSIRO today and they told me that they are deploying a "desktop cloud." I asked them what "cloud software" they are using, and I was pleased to hear that they were using Condor. So Condor is officially cloud software, at least in Australia. I thought you'd like to know. Ian.

  5. Stay away from the hype and stick to theprincipals!

  6. High ThroughputComputingbecame a well established and widely used paradigm

  7. Condor-GGlide-ins Matchmakingcarry the load of EGEE and OSG

  8. Virtual Machinesfit our principals(they look like a job, they ‘come and go’, they checkpoint, they have many attributes, the can be matched, … )

  9. Innovation through widely adopted technologypartnerships with users in academia and industry, and IT providers

  10. The Condor Project – an Experiment in Experimental Computer Science NSF (CISE) 12/09

  11. Why am I here today? Because I believe that: • the Condor project is ‘different’, • we do not have many (any?) other such Computer Science projects, • it is important for the future of our science to have more (many?) such projects, • we can and should learn from what we have done so far what it takes to build and sustain such projects and • CISE can and should play a leadership role in changing the dynamics of our field so that more Computer Science departments will have such projects NSF (CISE) 12/09

  12. “Why are you leaving academia and taking a job in industry?”“I want to haveimpact!” NSF (CISE) 12/09

  13. In the words of Mike Carey “I left academia for industry because I was drawn to the idea of getting more direct access to real problems - from customers and challenges encountered while building commercial-grade software - because I felt like I was in somewhat of a mode of inventing and solving problems, at least w.r.t. some of the things I'd been working on.  Sure, that was leading to many written/submitted/accepted papers, but it was somehow less than satisfying after awhile.” NSF (CISE) 12/09

  14. It is all about Software I argue that ‘we’ do not know how • to develop, maintain, support and evolve (dependable) software, • to integrate software components into end-to-end (dependable) capabilities, • to evaluate the quality of software, • to estimate the cost (effort) related to software and • to treat software as infrastructure NSF (CISE) 12/09

  15. (my) terminology • Experiment - an act or operation for the purpose of discovering something unknown or of testing a principle, supposition, etc.: • Technology Adoption – to select a technology as a means to meet an ends of significant importance/value • Real users – individuals or groups who adopt (and use) a computing technology • Experimental Computer Science – advance the state of the art of computing (new frameworks, new technologies, new abstractions) through experiments that involve real users NSF (CISE) 12/09

  16. Two new Institutes on the UW Campus - MIR & WID 16

  17. The MIR Three-Plane Model 17

  18. Using Condor with Blackboard Sam Hoover IT Systems Architect Computer Systems and Operations CCIT, Clemson University shoover@clemson.edu

  19. Problem Statement Courses in Blackboard need to be archived Blackboard provides a batch archive script Over 6,200 courses are currently active The course list was split into equal numbers across 5 servers Archives took 60 hours to complete

  20. Implementing Condor with Blackboard Blackboard is a “heavy” Java Enterprise application We wanted to take advantage of the multiple cores per server Security is a requirement Performance of the application during processing MUST be maintained

  21. Sam Hoover: shoover@clemson.edu Sam Hoover: shoover@clemson.edu

  22. Benefits of using Condor with Blackboard Job scheduling ensures load balancing and enables higher throughput through use of all available hardware resources Post processing with DAGMan streamlines operation Jobs are suspended and resumed automatically to protect user performance Archive time has been reduced by 65% End of Semester “full” archive is now feasible

  23. Credits • Clemson could not have achieved this innovation without the contributions of the following people and groups: • Sam Hoover, CSO - Principal Innovator • Randy Martin and Matt Garrett, CSO • NSF CI-TEAM award (RENCI principal) • Sebastien Goasguen, School of Computing • Blackboard Operations Team (CCIT-wide representation)

  24. Thank you for building such a wonderful community

More Related