We're interested in how sites are approaching long running/batch jobs.
In our environment, we allow users to submit long running batch jobs to
certain machines. These processes often involve computations over
large datasets with I/O to data storage. We need a way to ensure
that their batch jobs have access to the data storage without the
credential expiring.
We think this is a generic batch job problem to k4/k5 and/or AFS/DFS
services. What have people been doing in the k4/k5/AFS/DFS space to
deal with this problem?
Outside of keytabs. We're looking at creating a batch job wrapper
which requires the username/password of the user, obtains the
credential, and refreshes it for the duration of the process. Any
thoughts?
I will summarize the responses.
Daniel
--
Daniel D. Arrasjid Computing and Information Technology
Voice: (716) 645-6153 State University of New York at Buffalo
Fax: (716) 645-5972 301 Computing Center, Buffalo, NY 14260
E-Mail: [EMAIL PROTECTED] WWW: http://www.acsu.buffalo.edu/~daniel
PGP public key: http://www.acsu.buffalo.edu/~daniel/key.html
