1 / 67

Making Omelets Without Breaking Eggs: Adding Enterprise Features to Condor

Making Omelets Without Breaking Eggs: Adding Enterprise Features to Condor. Jason Stowe. condor_q. 1.0 Community 2.0 Condor += Hooks 3.0 Conversations with Miron 4.0 Configuration w/Pipes 5.0 Progress to date. Condor Community. com·mu·ni·ty.

stellam
Download Presentation

Making Omelets Without Breaking Eggs: Adding Enterprise Features to Condor

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. Making Omelets Without Breaking Eggs:Adding Enterprise Features to Condor Jason Stowe

  2. condor_q 1.0 Community 2.0 Condor += Hooks 3.0 Conversations with Miron 4.0 Configuration w/Pipes 5.0 Progress to date

  3. Condor Community

  4. com·mu·ni·ty

  5. A group of people living … under the same government.

  6. A group of people having common interests: the scientific community

  7. … Sharing, participation, and fellowship.

  8. Community = People

  9. Prior work Condor for movies: 1000+ CPUs (Linux/OSX)70+ TB storage Active Community member

  10. Currently:Cycle ComputingCondor Advice, Software & Enterprise SupportWindows/Linux/OSX

  11. Now work on bigger projects with people I sat with @ CondorWeek2005…

  12. Robert Nordlund, HartfordLife Cutting-edge commercial user

  13. X000’s server VMs, X0000’s workstationsTBs storage,Vast IT resources

  14. Commercial Users =sub-community

  15. Share common interests… and resources

  16. - Windows (&Linux/Solaris) - Commercial DB (Oracle) - Large Storage Capacity - Network Infrastructure - Available Tools: JMS, Web clusters, DNS

  17. How to Leverage Enterprise tools for Business Requirements -Disaster Recovery/etc.

  18. Bob Nordlund’s idea: Condor += Hooks

  19. Configuration:Contribute hooks to Condor, no workarounds (like extra daemons used in past)

  20. How do we get this done?

  21. How do we make an omelet,without breaking community eggs?

  22. A Conversation with Miron

  23. Funding

  24. Text Here

  25. Text Here

  26. Couldn’t industry provide funding for a team of people?

  27. Objectivity/Independence

  28. Condor is Attractive:Open, Innovative, Community

  29. Problem with Large Enterprise Funding Contracts

  30. = Dependence and Potential Conflict of Interest

  31. Needs of the many must outweigh the needs of the few or the one.

  32. What is the optimal way from Miron/Wisconsin’s perspective?

  33. Proposed Solution Wisconsin Responsible for: • Architectural Decisions – Final approval for features • Code Review/Integration • Release Planning • Maintenance

  34. Proposed Solution Integrator Responsible for: • Wisconsin – Build & Test, architecture feedback, development, code review, testing, and integration • Enterprise – requirements, scheduling, & support Enterprise funds feature addition

  35. Proposed Solution

  36. For the new feature:Wisconsin is Architect/MaintainerIntegrator is Developer/QA

  37. Intellectual Property

  38. Sharing, participation, and fellowship.

  39. One Unified Condor

  40. IP for Condor Code changes must be donated back to Condor

  41. Plan the work. Work the plan.We got started…

  42. HartfordLife = EnterpriseCycle = IntegratorWisconsin = Governing/Architect

  43. Bob and I called someone we sat next to @CondorWeek 2005

  44. Ian Chesal, AlteraWritten Innovative Middleware, Priority Scheduling and Quill (yay!)

  45. Share common interests…

More Related