Condor Glidein: Condor Daemons On-The-Fly

1
Condor GlideinCondor Daemons On-The-Fly
2
Why Glidein?

• You have access to a cluster running some other
  batch system.
• You want Condor features, such as
• queue management
• matchmaking
• checkpoint migration

3
What Does Glidein Do?

• Installation and setup of Condor.
• May be done remotely.
• Launching Condor.
• Through Condor-G submission to Globus.
• Or you run the startup script however you like.

4
Condor Startd in Flight
5
Example

• condor_glidein some.gatekeeper.edu
• Eventually, a remote node appears in your Condor
  pool.
• condor_status
• Name OpSys Arch State Activity
  LoadAv Mem ActvtyTime
• 3412_at_somewhere.edu LINUX INTEL Unclaimed Idle
  0.01 500 0000501

6
But it didnt work!?

• Some glidein gotchas
• Use condor_glidein from version 6.7.3
• Must allow glideins to join your pool.Check
  HOST_ALLOW settings.
• Must have inbound/outbound connectivity.(Stay
  tuned for availability of GCB, though.)
• Jobs will probably need to use Condor file
  staging or remote i/o.

7
Glidein Lifespan

• Glidein nodes automatically go away when there is
  no work for them to do.
• Use idletime to customize.
• Use runtime to set upper age limit.

8
Glidein Security

• No authentication of daemons by default.
• May enable GSI authentication using -gsi options.
  
• Default is to only run jobs from the user who
  submitted glidein.
• May use anybody to open access to anyone in the
  Condor pool.

9
Who Runs Glidein?

• Anyone, but
• Admin must allow glideins to join pool.
• For greater freedom, create separate glidein
  pool.
• Glideins join personal Condor pool.
• Use flocking to submit jobs to this personal pool
  plus any others.

10
Can I Configure It More?

• Yes. Generate default configuration and edit it.
• condor_glidein genconfig genstartup
• condor_glidein useconfig X usestartup X
• Use forcesetup to overwrite existing
  installation.

11
Development Status

• Condor 6.7 series glidein features
• Support for easy GSI setup.
• Hassle-free access to tarballs.
• Greater flexibility to operate in other (e.g.
  non-Globus) environments.
• General hardening for life in the wild.

12
Future Directions

• Integration with GCB so Firewalls are less
  problematic.
• Glidein schedds.
• Heirarchical queue management ala Condor-C.
• Glidein management.
• On-demand expansion of Glidein pool.
• See Edward Walkers GridShell work.

13
Any Questions?

• Ask me now...
• Or email condor-users_at_cs.wisc.edu.
• Check the Glidein documentation at
  http//www.cs.wisc.edu/condor/glidein
• Thanks!