In the previous post we discussed the comforts of computing right from “home”, i.e. the place where you develop source code, job submission scripts, parameter files, executable binaries, log files, data files and datasets large and small, with potentially external library dependencies. Keeping work on the remote systems in synch with work on the local system can be a challenge. Our team at UChicago and the Open Science Grid has been addressing this.
The “Campus Connect Client” is in beta-mode, but ready for early adopters to try out. In the plot, the heavy-side step function shows the moment at which OSG was added to a user’s local campus submission from the Palmetto cluster at Clemson University.
Work Courtesy Lincoln Bryant
The following information is from the OSG Support Helpdesk authored by David Champion OSG Group @UChicago.
The Campus Connect Client is a bridge from a campus to OSG’s national grid infrastructure. OSG is a national distributed high-throughput system, not a traditional high performance supercomputer located in a single data center. The Campus Connect Client is a set of tools for linking a campus research computing cluster to a CI Connect instance. Users of a campus facility can submit jobs into the Open Science Grid without leaving their institutional working environment.
Campus Connect Client provides:
Experienced HTCondor users may prefer to use OSG Connect’s login server directly. But many campus researchers already have a comfortable home on their local computational resource, and no need to interact directly with HTCondor. Campus Connect Client targets these users, making it easy to extend local resources with the full national grid.
OSG works with resource providers to set up Campus Connect Client access at the system level. If the package or module is already installed at your site, you can start using it today. If not, we can work with your site operations team to provide it, or you can install it for yourself.