Compute Element deployment notes

OS Setup

• We will need to get rid of osg-release, install osg-release 3.2, yum clean all. The clean all part is very important, otherwise we will get the 3.1 cache installed.
• Then, start following the Twiki. Certs and network config will stay on your way but go away quickly.
• To install Condor, review the local file in the puppet configuration (soon to get rid of it), add the package "osg-wn-client" to the condor module, just temporarily so the CE can get through, then comment it back after using it. At this point, if the certificate is the right one, condor will be working already and condor_q will confirm that it's fine * Then it becomes the tricky part. install osg-ce-condor and we will have to deal with the .ini files, my impression was :

-rw-r--r--. 1 root root   869 Apr 21 14:29 01-squid.ini  - same for the site
-rw-r--r--. 1 root root  1882 Apr 21 14:30 10-misc.ini  - same for the site
-rw-r--r--. 1 root root  2584 Feb 24 15:27 10-storage.ini - same for the site
-rw-r--r--. 1 root root  1688 Feb 24 15:27 15-managedfork.ini - same for the site (default?)
-rw-r--r--. 1 root root  1746 Apr 21 14:58 20-condor.ini - CE specific, look through
-rw-r--r--. 1 root root 11610 Apr 21 15:12 30-gip.ini - CE specific, look through
-rw-r--r--. 1 root root  1903 Apr 21 15:19 30-gratia.ini - same for the site
-rw-r--r--. 1 root root  1723 Feb 24 15:27 30-infoservices.ini - default
-rw-r--r--. 1 root root   339 Feb 24 15:27 40-localsettings.ini - default
-rw-r--r--. 1 root root  1442 Feb 24 15:27 40-network.ini - default
-rw-r--r--. 1 root root  2500 Apr 21 15:30 40-siteinfo.ini - CE specific, look through

In the future we should keep a tarball of these files (don't change a lot throughout releases) for each CE. if the hostname doesn't change almost nothing changes.

-- Main.samir - 2014-04-21