Go to the NASA 
                        Website TetrUSS:       
			 USM3D; Skip Navigation
TetrUSS Software Components Application Gallery Supported Platforms Request TetrUSS TetrUSS Team Publications Test Cases Links
Home
Introduction
Overview
Boundary Conditions
Input Files
Running USM3D
Using AeroDB
Test Cases
Utilities
Ongoing / Future Work
FAQs
References

USING the NAS AeroDB Job Manager

Setting up an AeroDB Account

STEP 1: Preliminary setup actions
a. Send email to Ed Tejnil (tejnil@nas.nasa.gov)
- requesting to be added to AeroDB for usm3ddb.
- Also request AeroDB username and password for database and web portal.
b. call NAS (650-604-4444) and request, that his default login shell be changed to
"tcsh" on all NAS systems.
c. Bookmark the AeroDB web portal at the following URL:
https://www.nas.nasa.gov/cgi-bin/AeroDB/src/aerodb_sec.cgi


STEP 2: Set up AeroDB Job Launcher on NAS Columbia
a. Add the following to your NAS Columbia .cshrc file and then update via 'source .cshrc'
- alias psaerodb 'ps -aedf | grep AERO'
- alias jlaerodb 'perl /u/tejnil/AeroDB/src/AERODB_JL.pl'

b. Start job launcher (user types bold words below). For example:

% jlaerodb

... starting AERODB_JL

... SSHSCP_OPT (env) using ssh/scp option

Enter DB connect info (return=<default>):

db_driver <DBI:mysql>:
db_name <climate>: usm3ddb
db_hostname <angel.ipg.nasa.gov>:
db_port <3306>:
db_user <dbuser>: get from Neal Frink
db_password: ******* <--- database password (get from Neal Frink)

c. Place job launcher into background by 1) hit ctrl_z, then 2) type 'bg'

d. Job launcher should then stay running in the background even after logging off.
You can check to see that job launcher is running by typing 'psaerodb' at anytime. (See "Troubleshooting" if problems occur).


STEP 3: Set up NAS account for using SSH without a password if you don't have it already
a. Generate dsa/rsa public (.pub) and private keys (empty passphrase):
id_dsa, id_dsa.pub, id_rsa, id_rsa.pub.

% ssh-keygen -t dsa -N ""
% ssh-keygen -t rsa -N ""

b. Generate authorized keys file:

% cd ~/.ssh
% cat id_{d,r}sa.pub >! authorized_keys

c. Generate: known_hosts file (~/.ssh directory):

% ssh -o StrictHostKeyChecking=ask [machine].nas.nasa.gov
% ssh -o StrictHostKeyChecking=ask [machine]
% ls -l ~/.ssh
-rw------- 1 tejnil g16005 852 Jul 19 14:12 authorized_keys
-rw------- 1 tejnil g16005 668 Jul 19 14:11 id_dsa
-rw------- 1 tejnil g16005 616 Jul 19 14:11 id_dsa.pub
-rw------- 1 tejnil g16005 887 Jul 19 14:11 id_rsa
-rw------- 1 tejnil g16005 236 Jul 19 14:11 id_rsa.pub
-rw-r--r-- 1 tejnil g16005 2972 Jul 19 15:02 known_hosts

d. Broadcast rsa/dsa public/private keys (~/.ssh directory) and
authorized_keys to each machine you want to use:

% scp ~/.ssh/id_{d,r}sa* ~/.ssh/authorized_keys [machine]:\~/.ssh/.

e. Access machine w/o a password

% ssh [machine].nas.nasa.gov uptime
% ssh [machine] uptime


NASA Official Responsible For Content: Dr. Neal T. Frink
Site Curator: The TetrUSS Team
Last Updated: October 31, 2006

Feedback on Langley Products and Services