1. Thinking Outside the Nest Utilizing Enterprise Resources with Condor Bob Nordlund The Hartford Condor Week 2006

2. April 26, 2006Condor Week 20062 About The Hartford Founded in 1810 Quarter-trillion dollars under management Fortune 100 30,000 employees Happily using Condor for last 3 ½ years >3000 VM dedicated Condor pool >1000 VM workstation pool, and growing Almost entirely Windows

3. April 26, 2006Condor Week 20063 Objective Expose interfaces to Condor to facilitate the integration of enterprise resources.

4. April 26, 2006Condor Week 20064 Business Drivers Increasing Dependence on Condor Business Continuity Planning Survival Critical Mission Critical Business Essential Disaster Recovery Leverage Existing Infrastructure Investments Many tools in use that facilitate cross data center operation Don’t want to re-invent the wheel

5. April 26, 2006Condor Week 20065 Strategy Carefully identify hook locations Non-invasive Non-destabilizing Identify ‘big hitters’ Common need Phased approach Carefully piloted Identify implementers Create hooks in strategic locations in the Condor daemons to allow its out-of-the-box behaviors to be modified by custom code.

6. April 26, 2006Condor Week 20066 Example: Enterprise Configuration Management Utilize Centralized Storage (RDBMS on SAN) Scalable (>30,000 Computers) Highly Available (24x7x365) DR Capable (Multiple Data Centers) Support for Change Control/Versioning Reporting/Auditing (SOX) Manageable and Extensible Supportable (Standard Tools and Technologies)

7. April 26, 2006Condor Week 20067 Example (cont.): Enterprise Configuration Management (What we’d like to avoid…) Collector Negotiator Schedulers Execute Nodes condor_config

8. April 26, 2006Condor Week 20068 Example (cont.): Enterprise Configuration Management Oracle Redundant SAN-Connected Sun F15K WebLogic F5 Application Server Farm Multiple Datacenter Redundant Load Balancers Collector Negotiator Schedulers Execute Nodes HTTP JDBC Management Tools F5

9. April 26, 2006Condor Week 20069 Possible Hooks Job Events OnStart OnComplete OnFailure Ping Machine Events OnAppear OnDisappear OnClaimed Daemon Events OnCore (Should never happen) OnReconfig Data Storage GetConfig LogEvent External Queue

10. April 26, 2006Condor Week 200610 Bottom Line Condor should evolve towards a framework architecture exposing interfaces for non-core functionality and providing reference implementations for default behavior. This would enable a secondary source of innovation by allowing external parties to participate in extending Condor’s capabilities with no impact to the core.

11. April 26, 2006Condor Week 200611 Thank You