Changes in 3d198a6: Merge branch 'master' of https://bitbucket.org/sbgrid/corepublicwiki

				bch2-wu-springer-hur.md
			
          @@ -23,6 +23,9 @@ The Linux computers share authentication and data directories and can only be ac

           The systems named venus, mercury, and mars have GPUs installed and are used for data processing. These systems can be accessed remotely.

           Please note that your home directories are only visible to your labmates and PI by default. Permissions vary depending on the nature of the directory or files in question. PIs can request modifications to file permissions to suit the lab's needs.

          +# Wu Lab Software

          +Cryosparc is installed on Venus.  Cryosparc is installed and running on Venus. It is accessible via a web interface, please email [help@sbgrid.org](mailto:help@sbgrid.org) to ask how to access it.

          +

           # Data Backups

           Full and incremental backups are made of SBGrid file servers, including your home and data directories. These backups are usually kept for three months. If you need a file restored, please contact us at [help@sbgrid.org](mailto:help@sbgrid.org).

				faq-data-collection-at-ne-cat.md
			
          @@ -10,7 +10,7 @@ collection time at [NE-CAT](http://necat.chem.cornell.edu/

           Please work with your local liaisons to learn more about the procedure and

           follow up our instructions very carefully.

          -* DFCI: [Sacha Uljon](mailto:Sacha_Uljon@dfci.harvard.edu?subject=NE-CAT)  

          +* DFCI: [David Heppner](mailto:heppner@crystal.harvard.edu?subject=NE-CAT)  

           * Harvard: [John Janetzko](mailto:j.janetzko@gmail.com?subject=NE-CAT)  

           * Harrison Laboratory and Children's Hospital: [Kevin McCarthy](mailto:mccarthy@crystal.harvard.edu?subject=NE-CAT)

				faq-setting-up-passwordless-ssh.md
			
          @@ -1,19 +1,25 @@

           # Setting up password-less ssh

          - * NOTE: All sbgrid bound Servers and Workstations require 'pub' key to be ***uploaded***: See Below

          + * ***NOTE***: All SBGrid bound Servers and Workstations on the SBGrid network in the Longwood area require 'pub' key to be ***uploaded*** to our. authentication servers. Please follow the steps named "Generate SSH Keys" and "For Systems on the SBGrid network at Longwood" below.

          +

          + Off Quad systems (at MCB, HU, Tufts, Genzyme) please following the steps named "Generate SSH Keys" and "For Off-Quad SBGrid Systems" below.

          +### Generate SSH Keys

          +

             1. Generate ssh key-pair for local workstation: `ssh-keygen -t rsa` ; accept default options and hit return when prompted for passphrase.

          -  2. Copy public key (`~/.ssh/id_rsa.pub`) to remote system: `scp ~/.ssh/id_rsa.pub remotesys:~/` If this is the first connection to the remote system, type `yes` to accept the remote system key.

          -  3. Login to remote system, configure remote system to trust public key:

          +

          +#### For Off-Quad SBGrid Systems

          +  1. Copy public key (`~/.ssh/id_rsa.pub`) to remote system: `scp ~/.ssh/id_rsa.pub remotesys:~/` If this is the first connection to the remote system, type `yes` to accept the remote system key.

          +  2. Login to remote system, configure remote system to trust public key:

              * `ssh remotesys`

              * create ~/.ssh if it doesn't exist: `mkdir ~/.ssh`

              * `cat ~/id_rsa.pub >> ~/.ssh/authorized_keys`

              * `chmod 700 ~/.ssh`

              * `chmod 640 ~/.ssh/authorized_keys`

          -  1. Logout of remote system, and repeat login to check that everything works correctly. If so, `~/id_rsa.pub` can be removed from the remote system.

          +  3. Logout of remote system, and repeat login to check that everything works correctly. If so, `~/id_rsa.pub` can be removed from the remote system.

          -###For SBGrid Systems

          -There is no need for ~/.ssh/authorized_keys, the file is ignored on all our linux systems. The 'pub' key ***must*** be uploaded to our authentication servers. These examples assume you copied the pub key over, you can also copy and paste the entire contents of the .pub file between systems.

          +###For Systems on the SBGrid network at Longwood

          +There is no need for ~/.ssh/authorized_keys, the file is ignored on all our linux systems on the SBGrid network at Longwood. The 'pub' key ***must*** be uploaded to our authentication servers. These examples assume you copied the pub key to your Linux home directory, you can also copy and paste the entire contents of the .pub file between systems.

           You will need to run these commands on **crystal.harvard.edu**. If you are a Consortium member use shell.sbgrid.org.

				hu1-gaudet-dsouza.md
			
          @@ -44,6 +44,7 @@ Snapshots of the Linux filesystems are taken every hour and kept for 24 hours on

           and up to 12 months. Data is also replicated to a secondary server. If you need a file restored, please contact [help@sbgrid.org](mailto:help@sbgrid.org).

           # Software

          +

           ## NMRViewJ for D’Souza Lab

           To use nmrviewj you need the NMRViewj configuration files that Victoria created.

...	...	@@ -10,7 +10,7 @@ collection time at [NE-CAT](http://necat.chem.cornell.edu/
10	10	Please work with your local liaisons to learn more about the procedure and
11	11	follow up our instructions very carefully.
12	12
13		-* DFCI: [Sacha Uljon](mailto:Sacha_Uljon@dfci.harvard.edu?subject=NE-CAT)
	13	+* DFCI: [David Heppner](mailto:heppner@crystal.harvard.edu?subject=NE-CAT)
14	14	* Harvard: [John Janetzko](mailto:j.janetzko@gmail.com?subject=NE-CAT)
15	15	* Harrison Laboratory and Children's Hospital: [Kevin McCarthy](mailto:mccarthy@crystal.harvard.edu?subject=NE-CAT)
16	16

...	...	@@ -44,6 +44,7 @@ Snapshots of the Linux filesystems are taken every hour and kept for 24 hours on
44	44	and up to 12 months. Data is also replicated to a secondary server. If you need a file restored, please contact [help@sbgrid.org](mailto:help@sbgrid.org).
45	45
46	46	# Software
	47	+
47	48	## NMRViewJ for D’Souza Lab
48	49	To use nmrviewj you need the NMRViewj configuration files that Victoria created.
49	50

...	...	@@ -23,6 +23,9 @@ The Linux computers share authentication and data directories and can only be ac
23	23	The systems named venus, mercury, and mars have GPUs installed and are used for data processing. These systems can be accessed remotely.
24	24	Please note that your home directories are only visible to your labmates and PI by default. Permissions vary depending on the nature of the directory or files in question. PIs can request modifications to file permissions to suit the lab's needs.
25	25
	26	+# Wu Lab Software
	27	+Cryosparc is installed on Venus. Cryosparc is installed and running on Venus. It is accessible via a web interface, please email [help@sbgrid.org](mailto:help@sbgrid.org) to ask how to access it.
	28	+
26	29
27	30	# Data Backups
28	31	Full and incremental backups are made of SBGrid file servers, including your home and data directories. These backups are usually kept for three months. If you need a file restored, please contact us at [help@sbgrid.org](mailto:help@sbgrid.org).

...	...	@@ -1,19 +1,25 @@
1	1	# Setting up password-less ssh
2		- * NOTE: All sbgrid bound Servers and Workstations require 'pub' key to be *uploaded*: See Below
	2	+ * *NOTE: All SBGrid bound Servers and Workstations on the SBGrid network in the Longwood area require 'pub' key to be uploaded* to our. authentication servers. Please follow the steps named "Generate SSH Keys" and "For Systems on the SBGrid network at Longwood" below.
	3	+
	4	+ Off Quad systems (at MCB, HU, Tufts, Genzyme) please following the steps named "Generate SSH Keys" and "For Off-Quad SBGrid Systems" below.
3	5
	6	+### Generate SSH Keys
	7	+
4	8	1. Generate ssh key-pair for local workstation: `ssh-keygen -t rsa` ; accept default options and hit return when prompted for passphrase.
5		- 2. Copy public key (`~/.ssh/id_rsa.pub`) to remote system: `scp ~/.ssh/id_rsa.pub remotesys:~/` If this is the first connection to the remote system, type `yes` to accept the remote system key.
6		- 3. Login to remote system, configure remote system to trust public key:
	9	+
	10	+#### For Off-Quad SBGrid Systems
	11	+ 1. Copy public key (`~/.ssh/id_rsa.pub`) to remote system: `scp ~/.ssh/id_rsa.pub remotesys:~/` If this is the first connection to the remote system, type `yes` to accept the remote system key.
	12	+ 2. Login to remote system, configure remote system to trust public key:
7	13
8	14	* `ssh remotesys`
9	15	* create ~/.ssh if it doesn't exist: `mkdir ~/.ssh`
10	16	* `cat ~/id_rsa.pub >> ~/.ssh/authorized_keys`
11	17	* `chmod 700 ~/.ssh`
12	18	* `chmod 640 ~/.ssh/authorized_keys`
13		- 1. Logout of remote system, and repeat login to check that everything works correctly. If so, `~/id_rsa.pub` can be removed from the remote system.
	19	+ 3. Logout of remote system, and repeat login to check that everything works correctly. If so, `~/id_rsa.pub` can be removed from the remote system.
14	20
15		-###For SBGrid Systems
16		-There is no need for ~/.ssh/authorized_keys, the file is ignored on all our linux systems. The 'pub' key *must* be uploaded to our authentication servers. These examples assume you copied the pub key over, you can also copy and paste the entire contents of the .pub file between systems.
	21	+###For Systems on the SBGrid network at Longwood
	22	+There is no need for ~/.ssh/authorized_keys, the file is ignored on all our linux systems on the SBGrid network at Longwood. The 'pub' key *must* be uploaded to our authentication servers. These examples assume you copied the pub key to your Linux home directory, you can also copy and paste the entire contents of the .pub file between systems.
17	23
18	24	You will need to run these commands on crystal.harvard.edu. If you are a Consortium member use shell.sbgrid.org.
19	25