Prerequisites

The quick-start guide will assume that the user has certain accounts and has performed some standard setup procedures. The list of necessary accounts is:

1. CERN Nice
2. Fermilab LPC with lpcdarkqcd EOS group access
3. GitHub
4. CMS Connect (optional)

In addition, the user is expected to ...

1. be registered in the CMS VO
2. have a CERN grid certificate
3. have installed said certificate on whatever server from which they plan to submit jobs (i.e. CMS Connect). Direction on how to install a .p12 certificate file can be found in Section 5.1 of the CMS Offline WorkBook. If you are installing your certificate on CMS Connect (login-el7.uscms.org), then you can follow the directions in the CMS Connect Handbook.
4. have uploaded an ssh key from the working server (i.e. CMS Connect) to GitHub
5. make sure you have permission to write to the lpcdarkqcd FNAL EOS area. First, you will want to make sure you are a part of the lpcdarkqcd group. To do so, run the following command (from the LPC cluster):

   getent group | grep "lpcdarkqcd:" | grep -o `whoami`

   If you are not part of the lpcdarkqcd group, then you will need to make a request on the LPC Service Portal. Click on the "Modify Account on LPC Collaborative Group: Add/Remove Account to LPC Collaborative Group" link and fill out the form. Once you are added to the group, run the following command to make sure you have permission to write to the group area.

   crab checkwrite --site=T3_US_FNALLPC --lfn=/store/group/lpcdarkqcd

   If this does not run successfully, then you may have to make a request to map your grid certificate to FNAL. You can find directions on how to do this here.
6. install the call_host software (on whatever cluster will be used to submit jobs: cmslpc, CMS connect, etc.) as follows:

   cd ~/
   git clone https://github.com/FNALLPC/lpc-scripts

   then add the following line to your .bashrc:

   source ~/lpc-scripts/call_host.sh

   then log out and log back in.

People who have been working on CMS for a while will have most of this setup already. Everyone else should follow the applicable directions in the 'Account Procurement' section of the wiki.

There are some CMS Connect specific setup procedures:

1. Multi-factor authentication (MFA) is now required for ssh access. If you have not set this up yet: go to https://cms.ci-connect.net/, log in, go to "Profile" and follow the instructions in the bottom left. Wait 10-15 minutes for the server to update, and then make sure you can log in with the code.
2. Make sure the file ~/.ciconnect/defaultproject exists and that it contains the project associated to your institute. For instance, a person working at CU Boulder would list cms.org.colorado. An alternate project could be cms.org.connect. in some cases you may need to make the ~/.ciconnect folder.
3. Please add the following line in your .bashrc file:

   export X509_USER_PROXY=$HOME/tmp/x509up

   Then run the following commands:

   source ~/.bashrc
   mkdir ~/tmp
   voms-proxy-init -voms cms --valid 168:00