Thinking Outside the Nest

Utilizing Enterprise Resources with Condor

Bob Nordlund

The Hartford

Condor Week 2006

April 26, 2006 Condor Week 2006 2

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

April 26, 2006 Condor Week 2006 3

ObjectiveExpose interfaces to Condor to facilitate the integration of enterprise resources.

April 26, 2006 Condor Week 2006 4

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

April 26, 2006 Condor Week 2006 5

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.

April 26, 2006 Condor Week 2006 6

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)

April 26, 2006 Condor Week 2006 7

Example (cont.):Enterprise Configuration Management (What we’d like to avoid…)

CollectorCollector

NegotiatorNegotiator

SchedulersSchedulers

ExecuteNodes

ExecuteNodes

condor_config

April 26, 2006 Condor Week 2006 8

Example (cont.):Enterprise Configuration Management

OracleOracle

Redundant SAN-Connected

Sun F15K

WebLogicWebLogic

WebLogicWebLogic

WebLogicWebLogic

F5F5

Application Server FarmMultiple Datacenter

RedundantLoad Balancers

CollectorCollector

NegotiatorNegotiator

SchedulersSchedulers

ExecuteNodes

ExecuteNodes

HTTP

HTTPJDBC

ManagementTools

ManagementTools

F5F5

April 26, 2006 Condor Week 2006 9

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

April 26, 2006 Condor Week 2006 10

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.

April 26, 2006 Condor Week 2006 11

Thank You