Campus Factory Install RC

This is a pre-release. It is not officially supported. The underlying technology, BoSCO? is still in development. The RC's may not work with all versions of bosco. If you find any bugs, email campusgrids@fnal.gov

About This Document

This document is the instructions to install the 1.0 Release Candidate. For the production release (0.4.X), see the CampusFactoryInstall.

Both BoSCO? and the Campus Factory are changing. As BoSCO? changes, so will the Campus Factory.

Requirements

  • A node with a public IP address.
    • Really, the node only needs to be reachable by the cluster worker nodes.

Procedure

Install BoSCO?

  1. Download the Campus Factory version of BoSCO? (soon to be THE bosco version)
    [user@client ~]$ wget http://glidein.unl.edu/~dweitzel/release_dir.tar.gz 
  2. Untar the release
    [user@client ~]$ tar xzf release_dir.tar.gz 
    [user@client ~]$ cd release_dir/ 
  3. Install bosco:
    [user@client ~]$ ./bosco_install 
  4. Source the setup scripts
    [user@client ~]$ source $HOME/bosco/bosco_setenv 
  5. Start bosco:
    [user@client ~]$ bosco_start 
  6. Add clusters to the bosco install. cluster_type is either pbs, lsf, sge, or condor
    [user@client ~]$ bosco_cluster -a user@host.edu cluster_type  

condor_config after condor instillation

condor_config will be automatically set to point to your condor configuration file- no additional steps need to be taken.

source to setup condor environment variables at root directory

souce /home/user/bosco/bosco_setenv must be run each time you log in, or this may be placed in login scripts

Validation of Success

The best way to validate the success of a running Campus Factory is to submit a job to be executed.

The test job, test.condor:

universe = vanilla
output = out
error = err
executable = /bin/sleep
arguments = 10
log = logfile
should_transfer_files = YES
when_to_transfer_output = ON_EXIT
queue 1

Submit the job:

[user@client ~]$ condor_submit test.condor

Debugging

The campus factory logs are located in the condor log directory. Which is located at
[user@client ~]$ condor_config_val LOG 

The file name is campus_factory.log.

Multi-User BOSCO

For multi-user BOSCO, special care must be given to enable multiple users to use the same bosco condor instance.

First, you must install the BOSCO instance just as before in the above instructions. Second, you install a system wide condor instance. Only the BOSCO instance will run, but it will run as root.

We will assume that BOSCO was installed as user bosco for the sake of this guide.

  1. As the bosco user, stop bosco:
    [user@client ~]$ bosco_stop 
  2. As the bosco user, edit $HOME/bosco/local.HOST/config/condor_config.factory. Modify the ENVIRONMENT to include bosco's home directory, and add the USERID line.
    CAMPUSFACTORY_ENVIRONMENT = "PYTHONPATH=$(LIBEXEC)/campus_factory/python-lib CAMPUSFACTORY_DIR=$(LIBEXEC)/campus_factory _campusfactory_GLIDEIN_DIRECTORY=$CAMPUSFACTORY_DIR/share/glidein_jobs HOME=/home/bosco"
    CAMPUSFACTORY_USERID = bosco
    
  3. As root, change ownership of the password file and start the bosco instance of condor:
    [root@client ~]$ source ~bosco/bosco/bosco_setenv
    [root@client ~]$ chown root: `condor_config_val SEC_PASSWORD_FILE`
    [root@client ~]$ bosco_start
  4. As root, install Condor into a global directory. For example, you may install the Condor RPM. Do not start this instance of Condor.
  5. Now, as any user, you may run the test job given in Validation of Success

Topic revision: r21 - 07 Feb 2017 - 20:01:29 - BrianBockelman
Hello, TWikiGuest!
Register

 
TWIKI.NET

TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..