_Sidebar.md
... ...
@@ -1,26 +1,26 @@
1
-[[start]]
1
+[start]
2 2
3 3
[an example](http://example.com/ "Title")
4 4
5 5
SBGrid Consortium Support for Users
6
-* [[Software Help]]
7
-* [[New Software Requests]]
8
-* [[Supported Operating Systems]]
9
-* [[Overriding Default Software Versions]]
10
-* [[Install The Software On Your Laptop]]
6
+* [Software Help](help.md)
7
+* [New Software Requests](requests.md)
8
+* [Supported Operating Systems](operatingsystems)
9
+* [Overriding Default Software Versions](overides.md)
10
+* [Install The Software On Your Laptop](laoptopinstall.md)
11 11
12 12
SBGrid Consortium Support for Site Administrators
13
-* [[Software Installation]]
14
-* [[Preparing Workstations to run the Software]]
15
-* [[Managing your Installation]]
16
-* [[Administrator Software Version Overrides]]
17
-* [[SBGrid CentOS/Fedora Mirrors]]
18
-* [[Admins Mailing List]]
13
+* [Software Installation](installation.md)
14
+* [Preparing Workstations to run the Software](workstations_setup.md)
15
+* [Managing your Installation](managing.md)
16
+* [Administrator Software Version Overrides](admin_overrides.md)
17
+* [SBGrid CentOS/Fedora Mirrors](mirrors.md)
18
+* [Admins Mailing List](mailinglist.md)
19 19
20 20
SBGrid Consortium Support for Developers
21
-* [[Resources for Developers]]
22
-* [[Build and Test Network]]
21
+* [Resources for Developers](developers.md)
22
+* [Build and Test Network](build.md)
23 23
24 24
Hardware Support Notes
25
-* [[Setup Stereo 3D]]
26
-* [[SBGrid Recommended Hardware]]
25
+* [SBGrid Recommended Hardware](hardware.md)
26
+* [Setup Stereo 3D](stereo.md)
admin_overrides.md
... ...
@@ -0,0 +1,32 @@
1
+====== Administrator Software Blacklist ======
2
+Site administrators can prevent the shell initialization files from configuring software on a host by creating an empty file at **/programs/local/conf/disabled-hosts/<hostname>**, where **<hostname>** is the output of the //hostname -s// command. This is useful for encouraging users not to run jobs on bastion hosts, file servers, etc.
3
+
4
+====== Administrator Software Version Overrides ======
5
+Most of the software titles installed in the SBGrid Suite have several versions available. Typically, we try to provide at least three versions of each software package, although very old or very new applications may have fewer versions.
6
+
7
+There are two methods for site admins to configure version overrides using files placed in a **/programs/local/conf/** directory.
8
+
9
+===== Site-wide Version Overrides =====
10
+A file named **site.conf** will be read when any SBGrid shell is initialized from the installation.
11
+
12
+===== Per-host Version Overrides =====
13
+A file named **<hostname.conf>**, where **<hostname>** is the output of the //hostname -s// command, will be read after the site.conf on the host matching that hostname.
14
+
15
+===== Precedence =====
16
+There are three files that will be examined for version overrides during shell initialization. In order from lowest to highest precedence:
17
+
18
+ * /programs/local/conf/site.conf
19
+ * /programs/local/conf/<hostname.conf>
20
+ * $HOME/.sbgrid.conf
21
+
22
+The overrides are reported during shell initialization:
23
+
24
+<code>
25
+ Configuration options in effect for this shell:
26
+ Variable Setting Configuration
27
+ SPIDER_L 18.10 site
28
+ CNS_L 1.21 machine
29
+ CCP4_L 6.1.2 personal
30
+</code>
31
+
32
+See [[Usage::Versions#Overriding Default Versions|this page]] for details on the override syntax.
0 33
\ No newline at end of file
help.md
... ...
@@ -0,0 +1,16 @@
1
+====== Software Help ======
2
+===== Getting Software Help =====
3
+
4
+If you are having a problem with software included in the SBGrid suite or think you've discovered an application bug, please use the [[http://sbgrid.org/bugs|SBGrid Software Bug Report]] to alert us to the problem. You can also email bugs@sbgrid.org with details on the problem, but the web form is the preferred method.
5
+
6
+If the problem with the software started after an update, you can configure your SBGrid environment to [[usage::versions|use an older version of the software]].
7
+
8
+===== New Software and Software Updates =====
9
+To request a new software package or an update to an existing package, please use the [[http://sbgrid.org/req|Software Update/Installation Request form]].
10
+
11
+We try to accommodate most requests for new software, but we do occasionally run into difficulties. Despite most of our software being free for academics, some developers insist that each lab download and install their own software. We are happy to provide developers with the list of SBGrid members that have access to their software, but that doesn't always satisfy their requirements.
12
+
13
+Even when things go smoothly, license requests and working out licensing details with developers can take some time, so please don't wait until the last minute before requesting software you anticipate you may need for your project.
14
+
15
+===== Newsletter =====
16
+SBGrid sends a monthly newsletter with information concerning software updates, upcoming webinars, talks and other items of interest to our community. The archive of previous newsletters is available online at the [[http://sbgrid.org/news/newsletters|SBGrid Newsletter Archive]].
0 17
\ No newline at end of file
installation_admin.md
... ...
@@ -0,0 +1,48 @@
1
+======Managing Your Software Installation======
2
+====='sbgrid-admin' Utility=====
3
+The //sbgrid-admin// utility used to install the software has a few other uses. There is a download link in the initial site set up email, and it is included in the installation itself at ///programs/share/sbgrid/bin/sbgrid-admin//. It includes built-in help:
4
+<code>
5
+ $ sbgrid-admin -h
6
+sbgrid-admin: a tool for administering an SBGrid Software suite installation
7
+
8
+Usage: sbgrid-admin [-chirstu]
9
+
10
+ -c Cron mode. Used for automated updates of the software suite.
11
+ -h Help message.
12
+ -i Install the software suite on this machine.
13
+ -p Print a launchd plist for updating the software on OS X machines.
14
+ -r Regenerate sh/csh shell configuration files.
15
+ -s Install the software branch for SGI IRIX.
16
+ -t Test the configuration file.
17
+ -u Force manual update of an existing installation.
18
+</code>
19
+
20
+The most commonly used option is //sbgrid-admin -u// to force a manual update. This will synchronize your local installation with the SBGrid master installation hosted at Harvard Medical School.
21
+
22
+The SBGrid software configuration files use both static and dynamically generated files. The main shell initialization files, **/programs/sbgrid.cshrc** and **/programs/sbgrid.shrc** are static files, but the operating-system specific configurations are dynamically generated and customized for the packages available at your site. //sbgrid-admin -r// will regenerate the branch-specific configuration files should you accidentally delete or alter them.
23
+
24
+===== Configuration Options =====
25
+The //sbgrid-admin// script has some additional configuration options to accommodate the installation requirements at different sites.
26
+
27
+The ~sbgrid/.sbgridrc configuration file for the //sbgrid-admin// script must contain a sitename and site key. All other configurations are optional.
28
+
29
+Options take the form of //OPTION_NAME="setting"//.
30
+
31
+|**Option**|**Example**|**Description**|
32
+|SB_SITENAME|sbgrid-bene|The site name for your installation provided by SBGrid|
33
+|SB_SITEKEY|xyxyxyxyxyxyxy|The installation key for your site provided by SBGrid|
34
+|INSTALL_TARGET|/nfs/programs|The installation directory for the software|
35
+|RSYNC_ARGS|"%%--%%port 8080"|Advanced arguments to rsync. Can be used to workaround blocked rsync ports.|
36
+|HTTP_PROXY|host.name:port|Proxy hostname and port for use by rsync and curl|
37
+|POST_UPDATE_SCRIPT|/absolute/path/to/script|Optional script to be run after a successful software update|
38
+|CRON_SCHEDULE|5 1 * * *|Set a custom cron schedule|
39
+\\
40
+
41
+===== Rsync Transaction Logging =====
42
+If you want a date-stamped log of all rsync downloads, deletions and updates, you can add a line like this to the ~sbgrid/.sbgridrc file:
43
+
44
+<code>
45
+RSYNC_ARGS="--log-file=$HOME/logs/sbgrid-admin-`date +%Y%m%d`.log"
46
+</code>
47
+
48
+This will create a date-stamped log file any time an actual change to the software tree happens. In general this should not be necessary, but for troubleshooting purposes it can be useful.
0 49
\ No newline at end of file
laptopinstall.md
... ...
@@ -0,0 +1,142 @@
1
+====== Copying the Software Installation ======
2
+If you run a machine that is frequently disconnected from the network, like a laptop, or don't want to set up an NFS-shared software installation, it is possible to install the software to the hard disk on your local machine.
3
+
4
+There are two scripts in the programs tree that can be used to create a copy of the software on your local hard disk. The ''sbgrid-laptop'' script allows you to select individual applications from the software distribution for installation on your laptop. By default only the latest version of the selected applications will be installed. The ''localsync'' script allows you to copy an entire operating system software branch to your local machine. This script can be used on laptops, but each branch is quite large in terms of disk space usage.
5
+
6
+======= Laptop Script ======
7
+You can create a customized local installation of the software using the ''sbgrid-laptop'' script located at ''/programs/share/bin/sbgrid-laptop''. This script requires you to have an SSH login to a computer that has access to an SBGrid software installation and will let you specify which packages you want to install.
8
+
9
+<code>
10
+sbgrid-laptop: a tool for creating a local installation of the
11
+ SBGrid software on a laptop.
12
+
13
+Usage: sbgrid-laptop [-ituv] [-e list|config]
14
+
15
+ -d Debug mode creates a log file for troubleshooting purposes.
16
+ -e [list|config]
17
+ Edit the software download list.
18
+ -i Initial set up and installation of the SBGrid software.
19
+ -s Re-run SSH key set up process.
20
+ -t Test your current configuration.
21
+ -u Update an existing installation using the current
22
+ configuration.
23
+ -v Verbose option for the file transfer.
24
+
25
+You need an SSH login to a machine with the SBGrid software installed
26
+to use this script. The script will create an SSH key and run an SSH
27
+agent process to handle authentication for the file transfers.
28
+</code>
29
+
30
+Copy the script the machine you want to install the software on, and then run it in install mode: ''./sbgrid-laptop -i''. Follow the prompts on the screen to create your configuration file, your software installation list and to enable logins using an SSH key for authentication.
31
+
32
+======= Sync Script ======
33
+There is a script in the programs tree that can be used to copy the appropriate branch from a shared installation to your laptop or workstation.
34
+
35
+Copy /programs/share/bin/localsync from the machine that has the software to your home directory on the standalone machine:
36
+
37
+<code>scp your.server.name:/programs/share/bin/localsync ~/</code>
38
+
39
+Then run the script like this:
40
+
41
+<code>
42
+chmod 755 ~/localsync
43
+~/localsync yourusername@your.server.name
44
+</code>
45
+
46
+The script will prompt you for your sudo (admin) password in order to create the programs directory, and then it will prompt you for your login password to the server that hosts your programs installation.
47
+
48
+Here is an example run on my workstation:
49
+
50
+<code>
51
+ $ ./localsync bene@developer.sbgrid.org
52
+Running 'sudo mkdir /programs && sudo chown bene /programs'
53
+[sudo] password for bene:
54
+Copying the software from the i386-mac branch on your server to your local
55
+hard disk. Enter your ssh login password below for bene@developer.sbgrid.org:
56
+
57
+receiving file list ...
58
+</code>
59
+
60
+This will copy the entire branch for your architecture to your local hard drive. For the OS X branch, this will use approximately 100 GB of disk space.
61
+
62
+You should use a network cable for the initial download, since the download is fairly large. Subsequent runs of the 'localsync' script are differential; they will only copy new or changed files, so they can be run over a wireless connection. The script can be run at any time to make your local installation match the installation on your local server.
63
+
64
+====== Sharing a Software Installation without NFS ======
65
+While we recommend that sites export their software installation via NFS to their workstations, it is possible to use rsync to copy the master installation to each workstation. This method has the drawback that it requires manual intervention on the part of the local sysadmin, and updates will not be instantaneous or simultaneous for all machines.
66
+
67
+On each client machine, you'll need an 'sbgrid' user. That user will have a passphraseless ssh key that lets it log into the machine that hosts your primary installation. Each client machine will have a cron job for that sbgrid user that runs at 2 AM that will sync the programs from the master installation to the client machine.
68
+
69
+Here is a basic command run down. 'server1' holds the programs installation and 'client1' is what will be connecting to it.
70
+
71
+ * Login as root/administrator on client1
72
+ * Create the 'sbgrid' user on client1
73
+ * Check the free space on /.
74
+ * If there's enough free space, set up the programs directory:
75
+<code>
76
+mkdir /programs
77
+chown -R sbgrid:sbgrid /programs
78
+</code>
79
+ * If there is not enough free space on the root volume, you'll need to find space on a local volume.
80
+
81
+ * Login as 'sbgrid' on client1.
82
+ * Create the passphraseless ssh key:
83
+<code>
84
+ssh-keygen -d
85
+</code>
86
+
87
+(hit enter to confirm default file location, no passphrase, etc)
88
+ * Copy the ssh key to server1:
89
+<code>
90
+cat ~/.ssh/id_dsa.pub | ssh server1 'cat - >> ~/.ssh/authorized_keys'
91
+</code>
92
+ * Copy the localsync script from server1 to client1. From client1:
93
+<code>
94
+scp sbgrid@server1:/programs/share/bin/localsync .
95
+</code>
96
+
97
+(May prompt to accept the host key. If you can't login without a password, the ssh key stuff above has failed, and you'll need to troubleshoot that.)
98
+</code>
99
+chmod 755 localsync
100
+./localsync sbgrid@server1
101
+</code>
102
+(This will take a while depending on the speed of the machines/network.)
103
+
104
+ * Test the installation:
105
+<code>
106
+tcsh
107
+source /programs/sbgrid.cshrc
108
+</code>
109
+ or
110
+<code>
111
+bash
112
+source /programs/sbgrid.shrc
113
+</code>
114
+
115
+(You should get a message like this: )
116
+<file>
117
+ Welcome to SBGrid!
118
+********************************************************************************
119
+ Your use of the applications contained in the /programs directory constitutes
120
+ acceptance of the terms of the SBGrid License Agreement included in the file
121
+ /programs/share/LICENSE. The applications distributed by SBGrid are licensed
122
+ exclusively to member laboratories of the SBGrid Consortium.
123
+
124
+ To hush this license message, run 'touch ~/.agree2sbgrid'.
125
+********************************************************************************
126
+ Please submit bug reports and help requests to: <bugs@sbgrid.org> or
127
+ <http://sbgrid.org/bugs>
128
+ This installation last updated: 20110411
129
+********************************************************************************
130
+ Total time to initialize: 1 second(s)
131
+</file>
132
+
133
+ * Add a cronjob for the updates. As the 'sbgrid' user on client1:
134
+<code>
135
+echo "0 2 * * * ~/localsync sbgrid@server1" | crontab
136
+</code>
137
+ * Check the cronjob:
138
+<code>
139
+crontab -l
140
+</code>
141
+
142
+You're done!
0 143
\ No newline at end of file
mailinglist.md
... ...
@@ -0,0 +1,2 @@
1
+====== Mailing List for Site Administrators ======
2
+We have a small mailing list for technical users and site administrators. Visit the [[https://cmcd.hms.harvard.edu/sympa/info/sbgrid-tech|SBGrid-tech mailing list]] page to sign up.
0 3
\ No newline at end of file
mirrors.md
... ...
@@ -0,0 +1,9 @@
1
+====== SBGrid Mirrors ======
2
+
3
+For the benefit of the local SBGrid community, we recommend the following to access frequently-used open source software. If you would like for us to add a mirror, please [[help@sbgrid.org|contact us]].
4
+
5
+\\
6
+
7
+^ Mirror Name ^^ Mirror URL ^
8
+|{{:software:centos_icon_60.png?nolink}}|[[http://www.centos.org|CentOS]]| [[http://mirrors.med.harvard.edu/centos/]]|
9
+|{{:software:sl6_logo.jpeg?nolink}}|[[http://www.scientificlinux.org/|Scientific Linux]]| [[http://mirrors.med.harvard.edu/scientificlinux/]]|
0 10
\ No newline at end of file
operatingsystems.md
... ...
@@ -0,0 +1,38 @@
1
+====== Supported Operating Systems ======
2
+The SBGrid Software Suite can run on Linux, OS X and IRIX machines.
3
+
4
+Last Update: 2014-02-04
5
+
6
+===== Linux =====
7
+We build and test software under 64-bit Red Hat 6. The majority of our Linux users are using the Red Hat/CentOS/Scientific Linux or Fedora distributions, but we also have labs using the software with Ubuntu, Debian and OpenSuSE. We don't explicitly test the software on these distributions, but it is known to work, and we will work to resolve problems reported by users of these Linux distributions.
8
+
9
+We officially support the two most recent releases of Red Hat/CentOS/Scientific Linux (currently 6 and 7) and the two most recent releases of Fedora Linux. At this time, only 64-bit versions of linux are fully supported. As of January 2015, we are no longer updating the 32-bit software branch, though we will work to resolve reported problems.
10
+
11
+Currently Supported:
12
+ * Red Hat Enterprise Linux 6.x and 7.x and the community supported versions: CentOS and Scientific Linux.
13
+ * Fedora releases actively supported by the Fedora community. Check https://fedoraproject.org/wiki/Releases for the current list.
14
+ * We are no longer building software for RHEL 5.x, but compatible applications will remain in the software tree. We will respond to support requests for these and we will resolve problems where possible. RHEL5 users may not receive the latest versions of software, but RHEL5 systems will continue to be functional and supported.
15
+\\
16
+
17
+===== OS X Intel =====
18
+We build and test the programs under the most four most recent OS X releases.
19
+
20
+Currently Supported:
21
+ * OS X Intel 10.7 - 10.10
22
+
23
+\\
24
+
25
+===== OS X PowerPC =====
26
+The OS X PowerPC branch is currently frozen. The applications are stable and work well on our PowerPC hardware, but they are not being updated.
27
+
28
+Currently Supported:
29
+ * OS X PowerPC 10.4 - 10.5
30
+\\
31
+
32
+===== IRIX =====
33
+The IRIX programs branch is currently frozen. The applications are stable and work well on our SGI hardware, but they are not being updated.
34
+
35
+Currently Supported:
36
+ * IRIX 6.5.26 + bugfix releases
37
+
38
+\\
0 39
\ No newline at end of file
workstation_setup.md
... ...
@@ -0,0 +1,88 @@
1
+
2
+===== General =====
3
+ * You should use a network installation for workstations and servers if at all possible. NFS, SMB and AFP all work for sharing a single installation among multiple machines. The decreased admin overhead, bandwidth and disk savings of sharing a single installation is a significant benefit.
4
+
5
+===== Linux =====
6
+ * All Linux machines need installations of a recent version (6.17+) of csh/tcsh. Red Hat Enterprise Linux 6 and other recent distributions usually have an up to date version. There are RPMs for Red Hat/CentOS/Scientific Linux 5.x in the software tree in the architecture specific directories:
7
+<code>
8
+/programs/i386-linux/system/RPMs
9
+/programs/x86_64-linux/system/RPMs
10
+</code>
11
+ * SELinux must be disabled.
12
+ * 64-bit machines need a number of 32-bit compatibility packages installed **even when using the 64-bit software branch**. This is due to a number of binary-only and legacy packages that are only available as 32-bit applications. Additional fonts for Tcl/Tk, Motif and Xview applications are also encouraged.
13
+
14
+Packages for RHEL 6, and 7 and compatible machines:
15
+<code>
16
+yum install glibc.i686 libgcc.i686 libX11.i686 libXaw.i686 libXext.i686 ncurses.i686 \
17
+ redhat-lsb.i686 xorg-x11-fonts-75dpi xorg-x11-fonts-100dpi xorg-x11-fonts-ISO8859-1-75dpi \
18
+ xorg-x11-fonts-ISO8859-1-100dpi xorg-x11-fonts-misc libXScrnSaver
19
+</code>
20
+
21
+ * The same 32-bit requirement applies for 64-bit Debian and Ubuntu machines. This is supported via the [[https://wiki.debian.org/Multiarch/HOWTO|Multiarch]] system. You'll need at least the following packages to run most of the software. Please email us if you discover we have left some out.
22
+<code>apt-get install libc6-i386 lsb tcsh gawk libjpeg62 curl libx11-6:i386 libxext6:i386</code>
23
+
24
+===== 3D Stereo on RHEL 7 systems with Gnome 3 =====
25
+
26
+Nvidia 3D stereo typically requires disabling the Composite extension in X.org. Unfortunately, this extension is required to run Gnome 3 and the gdm login mangager supplied as the default desktop in CentOS and many other linux distributions.
27
+
28
+As of version 337.19 of the nvidia driver, some Quadro configurations can operate with the composite extension enabled, but stereo functionality depends on a stereo-aware composite manager. The Composite manager in CentOS7 Gnome3 is not stereo aware and 3D stereo does not work by default.
29
+
30
+In order to use 3D stereo on Gnome3 systems, you can switch from Gnome3/gdm to MATE/lightdm.
31
+The MATE Desktop Environment is the continuation of GNOME 2 which is the default desktop in CentOS 5 and 6.
32
+
33
+To change to MATE on CentOS7 systems, first, install the Extra Packages for Enterprise Linux (EPEL) repo:
34
+<code>
35
+ yum install epel-release
36
+</code>
37
+
38
+Then install the nvidia drivers from epel
39
+<code>
40
+ yum install kmod-nvidia
41
+</code>
42
+
43
+You may find you need these packages as well
44
+<code>
45
+ yum install mesa-libGLU-9.0.0-4.el7.x86_64 libXScrnSaver-1.2.2-6.1.el7.x86_64
46
+</code>
47
+
48
+Next, install lightdm which doesn't require the composite extension.
49
+<code>
50
+ yum install lightdm
51
+</code>
52
+
53
+From there we do a couple of groupinstalls
54
+You may have these rpms installed already, but just for good measure
55
+<code>
56
+ yum group install "X Window System"
57
+</code>
58
+
59
+then
60
+<code>
61
+ yum groupinstall "MATE Desktop"
62
+</code>
63
+
64
+Toggle from gdm to lightdm in systemd using systemctl.
65
+To see what you are using as a 'display manager', check this link
66
+ <code>
67
+ls -l /etc/systemd/system/display-manager.service
68
+</code>
69
+
70
+This is likely pointing to gdm and should be changed to point to lightdm.
71
+You can change that with systemctl.
72
+<code>
73
+ systemctl disable gdm
74
+ systemctl enable lightdm
75
+</code>
76
+
77
+And then this will reload you changes, similar to changing runlevels with sysinitV
78
+<code>
79
+ systemctl isolate graphical.target
80
+</code>
81
+
82
+Make sure to select MATE from the drop menu as your graphical before you login.
83
+===== Mac OS X ======
84
+ * Prior to OS X 10.8, the stock X11 has better compatibility than the Xquartz development version available from MacOSForge. With the OS X 10.8 release, X11 is no longer included by Apple, and you'll need to install the latest Xquartz version offered on the MacOSForge site to run X11-based applications.
85
+
86
+===== Laptops ======
87
+ * You can create a local installation to take along with you.
88
+http://www.sbgrid.org/wiki/software/laptopinstall
0 89
\ No newline at end of file