Commit 55052e6a authored by Jay Lepreau's avatar Jay Lepreau

Reality treatment, mostly concerning wide-area resources, but also

some software versions.  Shrink the emulab cluster picture so it's
not so dominant and therefore inconsistent with the broad story.
*** NOT TESTED ***
parent 52461b9b
......@@ -5,7 +5,7 @@
-->
<center>
<h1>
Hardware Overview
Hardware Overview, "Emulab Classic"
</h1>
</center>
......
......@@ -13,52 +13,78 @@ PAGEHEADER("Home");
?>
<p><em>Netbed</em>, an outgrowth of <em>Emulab</em>, provides
integrated access to three disparate experimental environments:
simulated, emulated, and wide-area network testbeds. Netbed strives
to preserve the control and ease of use of simulation, without
sacrificing the realism of emulation and live network experimentation.
</p>
<p>
Welcome to Emulab. Emulab (sometimes called the Utah Network Testbed)
is a new and unique type of experimental environment: a
universally-available "Internet Emulator" which provides a
new balance between control and realism. Several hundred
machines, combined with secure, user-friendly web-based tools, and driven
by <it>ns</it>-compatible scripts, allow you
to remotely reserve, configure and control machines and links down to
the hardware level:
packet loss, latency, bandwidth, packet ordering,
buffer space all can be user-defined. Even the operating system disk
contents can be securely and fully replaced with custom images.
Netbed unifies all three environments under a common user interface,
and integrates the three into a common framework. This framework
provides abstractions, services, and namespaces common to all, such as
allocation and naming of nodes and links. By mapping the abstractions
into domain-specific mechanisms and internal names, Netbed masks much
of the heterogeneity of the three approaches.
</p>
<p> <em>Wide-area resources</em>: Netbed currently includes
approximately 32 nodes geographically distributed across approximately
25 sites, largely the machines in the "MIT distributed testbed."
Experimenters with a valid research use can get non-root shell access
to these shared nodes, with ssh keys and other aspects automatically
managed by Netbed. Secure shared filesystem access is coming soon via
SFS.
</p>
<p>
The Testbed currently features high-speed Cisco switches connecting,
with over 5 miles of cabling, 168 core nodes (PCs) and 160 edge nodes
(Compaq DNARD Sharks). The core nodes can be
used as edge nodes, simulated routers, traffic-shaping nodes, or
traffic generators. During an experiment's time slots, the experiment
(and associated researchers) get exclusive use of the assigned
machines, including root access if desired. Until we finish designing
and building smarter scheduling and state-saving software, and obtain
the disk space, scheduling is manual and done at coarse granularity
(days).
<em>"Emulab Classic,"</em> a key part of Netbed, is a universally-available
time- and space-shared network emulator which achieves new levels of
ease of use.
Several hundred
PCs in racks, combined with secure, user-friendly web-based tools, and driven
by <it>ns</it>-compatible scripts or a Java GUI, allow you
to remotely configure and control machines and links down to
the hardware level. Packet loss, latency, bandwidth, queue sizes--
all can be user-defined. Even the OS disk
contents can be fully and securely replaced with custom images by any experimenter;
Netbed can load ten or a hundred disks in 2.5 minutes total.
</p>
<p> Utah's local installation currently features high-speed Cisco
switches connecting 5 100Mbit interfaces on each of 168 PCs. The
<a href = "http://www.uky.emulab.net">University of Kentucky</a>'s installation
contains 48 similarly networked PCs.
The PC nodes can be used as
edge nodes running arbitrary programs, simulated routers,
traffic-shaping nodes, or traffic generators. While an "experiment"
is running, the experiment (and its associated researchers) get
exclusive use of the assigned machines, including root access. </p>
<p>
We provide some default software (e.g. Redhat Linux and FreeBSD on the PCs,
NetBSD on the Sharks) that many users want. The basic software
configuration on your nodes includes accounts for project members,
root access, DNS service, compilers and linkers. But fundamentally,
the software you run on it, including all bits on the disks, is
replaceable and up to you. The same applies to the network's
We provide default OS software (Redhat Linux 7.1 and FreeBSD 4.5);
the default configuration on your nodes includes accounts for project members,
root access, DNS service, and standard compilers, linkers, and editors.
Fundamentally, however,
all the software you run on it, including all bits on the disks, is
replaceable and entirely your choice. The same applies to the network's
characteristics, including its topology: configurable by users.
</p>
<br /><br />
<a href='pix/side-crop-big.jpg'>
<img src='pix/side-crop-small.jpg' align=right /></a>
<img src='pix/side-crop-smaller.jpg' align=right /></a>
<h3>Links to help you get started:</h3>
<ul>
<li><b><a href = "docwrapper.php3?docname=auth.html">
Authorization Scheme, Policy, and "How To Get Started"</a></b>
<li><b><a href = "docwrapper.php3?docname=hardware.html">
Hardware Overview</a></b>
<li><b><a href = "docwrapper.php3?docname=software.html">
Software Overview</a></b>
Overview of Installed Software</a></b>
<li><b><a href = "docwrapper.php3?docname=hardware.html">
Hardware Overview, "Emulab Classic"</a></b>
<li><b><a href = "docwrapper.php3?docname=security.html">
Security Issues</a></b>
<li><b><a href = "docwrapper.php3?docname=policies.html">
......@@ -72,4 +98,3 @@ characteristics, including its topology: configurable by users.
PAGEFOOTER();
?>
......@@ -71,7 +71,7 @@ function WRITESIDEBAR() {
<tr><td class="menuheader"><b>Information</b></td></tr>
<?php
WRITESIDEBARBUTTON("Home", $TBDOCBASE, "index.php3");
WRITESIDEBARBUTTON_ABS("Kentucky Emulab", $TBDOCBASE,
WRITESIDEBARBUTTON_ABS("Univ. Kentucky Emulab", $TBDOCBASE,
"http://www.uky.emulab.net");
WRITESIDEBARBUTTON_NEW("Join Netbed (CD)",
......@@ -82,7 +82,7 @@ function WRITESIDEBAR() {
WRITESIDEBARBUTTON("Documentation", $TBDOCBASE, "doc.php3");
WRITESIDEBARBUTTON_NEW("Papers", $TBDOCBASE, "pubs.php3");
WRITESIDEBARBUTTON("People", $TBDOCBASE, "people.php3");
WRITESIDEBARBUTTON("The Gallery", $TBDOCBASE, "gallery/gallery.php3");
WRITESIDEBARBUTTON("Photo Gallery", $TBDOCBASE, "gallery/gallery.php3");
WRITESIDEBARBUTTON("Projects on Emulab", $TBDOCBASE,
"projectlist.php3");
WRITESIDEBARLASTBUTTON("Sponsors", $TBDOCBASE,
......@@ -426,7 +426,7 @@ function PAGEFOOTER() {
</tr><tr>
<td class="contentbody">
<center><font size=-1>
[&nbsp;<a href="http://www.cs.utah.edu/flux"
[&nbsp;<a href="http://www.cs.utah.edu/flux/"
>The&nbsp;Flux&nbsp;Research&nbsp;Group</a>&nbsp;]
[&nbsp;<a href="http://www.cs.utah.edu/"
>School&nbsp;of&nbsp;Computing</a>&nbsp;]
......@@ -436,10 +436,7 @@ function PAGEFOOTER() {
<br>
<!-- begin copyright -->
<font size=-2>
&copy; 2000-2002
<a href="http://www.utah.edu/">University of Utah</a>
and the
<a href="http://www.cs.utah.edu/flux/">Flux Group</a>.
&copy; 2000-2002 The University of Utah.
<a href="<?php echo "$TBDOCBASE"; ?>/docwrapper.php3?docname=copyright.html">
All rights reserved.</a>
</font>
......@@ -541,4 +538,4 @@ function SUBMENUEND() {
<?php
}
?>
\ No newline at end of file
?>
......@@ -10,6 +10,9 @@
Most any legitimate research/experimental use is allowed, including
use by companies. Of course, when demand exceeds supply we will have
to assign priorities to projects, but the hardware base will be expanding.
Due to limited resources and other issues, we currently allow only
research use of the wide-area nodes; educational and development use
are not permitted.
</p>
<h2>Acceptable Use, Allocation Priority, Reporting, Governance, Disclaimer</h2>
<p>
......
......@@ -5,15 +5,19 @@
-->
<center>
<h1>
Software Overview
Overview of Installed Software
</h1>
</center>
<ul>
<li><b>Wide-area nodes</b>: FreeBSD 4.6 with additions for robustness
and for participation in the wide area testbed.
<p>
<li><b>boss.emulab.net</b>: Master node, database, web server, name server, trusted disk-image server
<p>
Also known as <b>www.emulab.net</b>.
Runs FreeBSD 4.3-RELEASE. This is the master machine for the testbed
Also known as <b>www.netbed.org</b>.
Runs FreeBSD 4.5-RELEASE. This is the master machine for the testbed
software. Runs all the critical software components and thus is not
directly accessible by testbed users. Moderates (via the database)
access to node power cycling and disk-image loading as well as providing
......@@ -23,7 +27,7 @@
<li><b>users.emulab.net</b>: Control node, NFS server, test node serial line server and console access point
<p>
Also known as <b>ops.emulab.net</b>.
Runs FreeBSD 4.3-RELEASE. This is the main server machine for users
Runs FreeBSD 4.5-RELEASE. This is the main server machine for users
of the testbed and is where home directories and all project files
live. While most of the testbed configuration process is done via
the Web interface, a few things must be done while logged into
......@@ -32,14 +36,16 @@
files will already have this directory in your path.
<p>
This is also our "serial-line console" server. Experimenters can access
This is also one of Emulab's "serial-line console" servers. Experimenters can access
the console of any testbed node (using <code>tip</code>) from here.
Console output of all nodes is also logged here.
<h3>Machines used only for ``Emulab Classic'':</h3>
<p>
<li><b>tipserv1.emulab.net</b>: additional test node serial line server
<p>
Runs FreeBSD 4.3-RELEASE.
Runs FreeBSD 4.5-RELEASE.
Provides physical serial line ports for additional testbed nodes.
Not directly accessible by testbed users, hosted serial lines are
accessed by users via a proxy agent on users.emulab.net.
......@@ -84,7 +90,8 @@
and only read-only access is allowed without the password.
<p>
<li><b>sh[1-20]-[1-8].emulab.net</b>: testbed <a href="hardware.html#tbshark">Shark</a> nodes
<li><em>(Currently unavailable)</em><br>
<b>sh[1-20]-[1-8].emulab.net</b>: testbed <a href="hardware.html#tbshark">Shark</a> nodes
<p>
The Sharks run NetBSD by default, with the filesystems provided via
NFS. You may also boot your own OSKit kernels. At this time, no support
......
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