Changes between Version 3 and Version 4 of EARS

Timestamp:

Jul 19, 2013 4:58:57 PM (11 years ago)

Author:

jhickey

Comment:

--

EARS

@@ -1 @@
-= Getting Access to EARS =
+= Getting Access to EARS Overview =
 
-Access to the EARS cluster is filtered by a bastion host.  We figured the easiest way to provide secure access to users was to use SSH as a proxy from a bastion host.
+Access to the EARS cluster is filtered by a bastion host.  We figured the easiest way to provide secure access to users was to use SSH as a proxy from a bastion host.  Here is an overview of the steps.
+
+ * Get access to egate.deterlab.net which is the bastion host for the EARS testbed.
+ * Use egate.deterlab.net as a SOCKS proxy to access the web interface at https://www.ears.deterlab.net/
+ * Apply to your project on EARS.
+
+== Logging into EGATE, the bastion host ==
 
  * First, create a SSH key pair and email the public key, as an attachment, to us.  Also let us know what your preferred username is.
@@ -19 +25 @@
     }}}
 
-== Logging into users ==
 
-You can log into users.ears.deterlab.net from egate.  
 
-== Using the Proxy for the web interface ==
+== Using the Proxy for the EARS web interface ==
 
 
@@ -55 +59 @@
 
 * Now you should be able to access the web interface of the EARS cluster.
+
+== Accessing the Web Interface ==
+
+ * Once you have your proxy properly configured, you can access the web interface of the EARS cluster at [https://www.ears.deterlab.net https://www.ears.deterlab.net/] 
+
+ * If you are new to the EARS cluster, you will need to [https://www.ears.deterlab.net/joinproject.php Join an Existing Project]
+== Logging into users ==
+
+You can log into users.ears.deterlab.net from egate.  You will need to apply to a project and be approved before you can log into users since the EARS testbed is distinct from the ISI testbed.