Changes between Initial Version and Version 1 of Remote_Processing

Timestamp:

Aug 4, 2014, 1:23:19 PM (12 years ago)

Author:

watersc1

Comment:

--

Remote_Processing

@@ +1 @@
+= Setup/authentication =
+
+ 1. Step one is to see if your card works correctly.  Type in your Z
+number, and then use the card to generate a password for this webform:
+
+https://weblogin.lanl.gov/
+
+That should take you to a page that tells you you've logged in.  It
+should link to any needed training things (I think it did in the past,
+but I don't see anything for me there).
+
+In any case, if you can log in to weblogin, you should be able to log
+into Mustang.
+
+ 2. Log in as the ipplanl user with the same ssh key as the standard
+ipp user.  In the .ssh directory you'll find a config.watersc1 file.
+Construct one for yourself with your user name, and then modify the
+User entry in the config file.  Copy this config file (or its
+contents) to your personal (not ipplanl) ssh config.  The ipplanl
+instance is there for the lanl-czaring purpose, and the personal one
+for you to log in manually.
+
+Once you've made this ssh config change, you can now call:
+
+{{{
+ssh wtrw
+}}}
+This connects to the front end firewall computer.  It does not have a
+real shell, so you're limited to connecting onward to the Mustang
+frontend:
+
+{{{
+ssh mu-fe
+}}}
+
+ 3. You're now on one of the four front end nodes for Mustang, any of
+which works.  I've constructed a directory:
+
+{{{
+/turquoise/usr/projects/ps1/watersc1/user_template
+}}}
+Which contains the templates you should use for your .ipprc, .cshrc,
+and .ssh/config files.  The .ssh/config is the only one that needs
+editing, with my username/connection directory names changed.  Ensure
+that the connection directory exists, and that you can successfully
+ssh back to the cluster (as you; You'll likely need to generate/add
+keys).
+