110 likes | 123 Views
Thinking Outside the Nest Utilizing Enterprise Resources with Condor. Bob Nordlund The Hartford Condor Week 2006. About The Hartford. Founded in 1810 Quarter-trillion dollars under management Fortune 100 30,000 employees Happily using Condor for last 3 ½ years
E N D
Thinking Outside the NestUtilizing Enterprise Resources with Condor Bob Nordlund The Hartford Condor Week 2006
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 Condor Week 2006
Objective Expose interfaces to Condor to facilitate the integration of enterprise resources. Condor Week 2006
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 Condor Week 2006
Strategy Create hooks in strategic locations in the Condor daemons to allow its out-of-the-box behaviors to be modified by custom code. • Carefully identify hook locations • Non-invasive • Non-destabilizing • Identify ‘big hitters’ • Common need • Phased approach • Carefully piloted • Identify implementers Condor Week 2006
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) Condor Week 2006
Example (cont.):Enterprise Configuration Management (What we’d like to avoid…) Collector Negotiator Schedulers condor_config Execute Nodes Condor Week 2006
Example (cont.):Enterprise Configuration Management Management Tools Application Server Farm Multiple Datacenter Collector WebLogic HTTP JDBC HTTP Oracle Negotiator F5 WebLogic F5 Schedulers Redundant SAN-Connected Sun F15K WebLogic Redundant Load Balancers Execute Nodes Condor Week 2006
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 Condor Week 2006
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. Condor Week 2006
Thank You Condor Week 2006