Commit faaef37d authored by Jay Lepreau's avatar Jay Lepreau

"ops" node -> "users" host.

parent 0624d144
......@@ -36,17 +36,17 @@ probably be the project leader.
Within a week, say, you will receive email from the testbed admin
folks, either approving or denying your project.
You will then be able to really use the testbed: you will be able
to perform various functions through the Web interface and a Unix
login on the ops node.
to perform various functions through the Web interface and through
a Unix login account.
<p>
People working on the project
(students, staff, etc.) will request permission from the project
leader, also via the web interface, to <em>join</em> the project.
These requests can precede project approval; they will be queued.
Once project members have been authorized by the leader, they can log onto the
testbed ops node to start an experiment, reserving and
configuring nodes as necessary.
Once project members have been authorized by the leader, they can use
the Web interface and their Unix login to start and run experiments,
reserve and configure nodes, etc.
<!--
More detailed information on this
......@@ -133,8 +133,8 @@ reserving a set of nodes, which leads to automatic creation of Unix
accounts on those nodes for all members in your project. You will be
able to use ssh to log into those machines.
<p>
You will also receive an account on the operations machine
"ops.emulab.net", and from there will be able to access the test
You will also receive an account on the users' master host
"users.emulab.net", and from there will be able to access the test
nodes' serial line consoles via 'tip' as well as access console log
files.
</p>
......@@ -147,14 +147,14 @@ homepage</a>, or in the
<a href="http://www.cs.utah.edu/flux/testbed/doc/">testbed
documentation</a>. After checking those, you may
<a href="mailto:testbed-ops@flux.cs.utah.edu">
send e-mail to Testbed Ops</a>(testbed-ops@flux.cs.utah.edu).
send e-mail to testbed-ops@flux.cs.utah.edu</a>.
</p>
</ul>
<hr>
<address>testbed-www@flux.cs.utah.edu<br>
Last modified on Oct 31, 2000</address>
Last modified on Mar 10, 2001</address>
</body>
</html>
......@@ -73,7 +73,7 @@ accountability for their behavior.
<!-- <a href = "security.html"> -->
Each project gets a unique Unix group and its own protected subtree on
the ops node. That subtree is NFS-exported only to that group's
the users' master host. That subtree is NFS-exported only to that project's
assigned test machines. We don't currently protect against spoofing
on the control network, so there are vulnerabilities. The test networks
are fully separated between experiments by way of VLANs.
......@@ -81,14 +81,14 @@ are fully separated between experiments by way of VLANs.
<h3>How to contact Testbed Ops</h3>
For questions or problems, send email to
For questions or problems
<a href="mailto:testbed-ops@flux.cs.utah.edu">
Testbed Ops (testbed-ops@flux.cs.utah.edu)</a>.
send email to testbed-ops@flux.cs.utah.edu</a>.
<p>
<hr>
<address>testbed-www@flux.cs.utah.edu<br>
Last modified on Oct 31, 2000</address>
Last modified on Mar 10, 2001</address>
</body>
</html>
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment