Making Omelets Without Breaking Eggs: Adding Enterprise Features to Condor

1
Making Omelets Without Breaking EggsAdding
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
(No Transcript)
5
community
6
A group of people living under the same
government.
7
A group of people having common interests the
scientific community
8
Sharing, participation, and fellowship.
9
(No Transcript)
10
Community People
11
(No Transcript)
12
Prior work Condor for movies 1000 CPUs
(Linux/OSX)70 TB storage Active Community
member
13
CurrentlyCycle ComputingCondor Advice,
Software Enterprise SupportWindows/Linux/OSX
14
Now work on bigger projects with people I sat
with _at_ CondorWeek2005
15
Robert Nordlund, HartfordLife Cutting-edge
commercial user
16
X000s server VMs, X0000s workstationsTBs
storage,Vast IT resources
17
Commercial Users sub-community
18
Share common interests and resources
19
- Windows (Linux/Solaris) - Commercial DB
(Oracle) - Large Storage Capacity - Network
Infrastructure - Available Tools JMS, Web
clusters, DNS
20
How to Leverage Enterprise tools for Business
Requirements -Disaster Recovery/etc.
21
Bob Nordlunds idea Condor Hooks
22
ConfigurationContribute hooks to Condor, no
workarounds (like extra daemons used in past)
23
How do we get this done?
24
How do we make an omelet,without breaking
community eggs?
25
A Conversation with Miron
26
Funding
27
Text Here
28
Text Here
29
(No Transcript)
30
Couldnt industry provide funding for a team of
people?
31
Objectivity/Independence
32
Condor is AttractiveOpen, Innovative, Community
33
Problem with Large Enterprise Funding Contracts
34
Dependence and Potential Conflict of Interest
35
(No Transcript)
36
Needs of the many must outweigh the needs of the
few or the one.
37
What is the optimal way from Miron/Wisconsins
perspective?
38
Proposed Solution

• Wisconsin Responsible for
• Architectural Decisions Final approval for
  features
• Code Review/Integration
• Release Planning
• Maintenance

39
Proposed Solution

• Integrator Responsible for
• Wisconsin Build Test, architecture feedback,
  development, code review, testing, and
  integration
• Enterprise requirements, scheduling, support
• Enterprise funds feature addition

40
Proposed Solution
41
For the new featureWisconsin is
Architect/MaintainerIntegrator is Developer/QA
42
Intellectual Property
43
Sharing, participation, and fellowship.
44
One Unified Condor
45
IP for Condor Code changes must be donated back
to Condor
46
Plan the work. Work the plan.We got started
47
HartfordLife EnterpriseCycle
IntegratorWisconsin Governing/Architect
48
Bob and I called someone we sat next to
_at_CondorWeek 2005
49
Ian Chesal, AlteraWritten Innovative Middleware,
Priority Scheduling and Quill (yay!)
50
Share common interests
51
Configuration w/Pipes (CWP)
52
CONDOR_CONFIG cat file
53
CONDOR_CONFIG default_fileLOCAL_CONDOR_CONFIG
getconfig http//address/(hostname)
54
Current Status
55
condor_status

• vm1_at_Hartfordlife CLAIMED BUSY
• vm1_at_CycleComputing CLAIMED BUSY
• vm1_at_cs.wisc.edu CLAIMED BUSY
• CWP Feature specification Done
• NMI Build Test Wrapping up
• CWP Implementation In progress
• Testing Code Review
• Integration Release

56
Condor_History
57
Community
58
Enterprise Community
59
Condor Hooks
60
Model for feature addition
61
if you are a Condor user
62
Need support with new functionality(Condor
Hooks)
63
Participate in the Community
64
Talk with Miron.Talk with me.
65
(Talk with everyone _at_CondorWeek 2006)
66
Help the community continue to work well for
everyone.
67
Thank you. Questions?jstowe_at_cyclecomputing.com