BOSCO + Campus Factory

Checklist while implementing CF + Bosco integration

For the last several months, the campus infrastructure team has worked on software that will help users create a larger, more inclusive campus grid.  The goal largely has been to make the software easier to install and expand.

Integrating the Campus Factory (which is already used on many campuses) with Bosco has been a key goal for this effort.  Last week, I finally integrated the two (Beta Install Doc).  This will have many benefits for the user over both the current Campus Factory and current Bosco.

Feature	Campus Factory	Bosco v0	Campus Factory + Bosco
Installation	Large installation/configuration instructions. Install Condor and campus factory on every cluster.	Install on a central submit node. Configuration is handled automatically.
Adding Resources	Install Condor and the campus factory on every cluster. Configure to link to other submit and campus factory clusters.	Run the command bosco_cluster -add Installation and configuration handled auto-magically.
File Transfer	Using Condor file transfer, can transfer input and output.	Manually with scp by the user. No stderr or stdout from job.	Using Condor file transfer, can transfer input and output.
Job State	Accurate user job state.	Delayed user job state. No exit codes from the user jobs.	Accurate user job state.

As you can see from the above table, the combined Campus Factory + Bosco takes the best from both technologies.