Commit 9deb902d authored by Robert Ricci's avatar Robert Ricci

Spelling pass

parent c5853499
......@@ -23,7 +23,7 @@ data from previous users.
Disk images in @(tb) are typically created by starting with one of @(tb)'s
supplied images, customizing the contents, and taking a snapshot of the
resulting disk. The snapshotting process reboots the node, as it boots into an
MFS to ensure a quiesent disk. If you wish to bring in an image from outside
MFS to ensure a quiescent disk. If you wish to bring in an image from outside
of @(tb) or create a new one from scratch, please
@seclink["getting-help"]{contact us} for help; if this is a common request, we
may add features to make it easier.
......@@ -31,11 +31,11 @@ may add features to make it easier.
@(tb) has default disk image for each node type; after a node is freed by
one experimenter, it is re-loaded with the default image before being released
back into the free pool. As a result, profiles that use the default disk
images typically insantiate faster than those that use custom images, as no
images typically instantiate faster than those that use custom images, as no
disk loading occurs.
Frisbee loads disk images using a custom multicast protocol, so loading large
numbers of nodes typcially does not slow down the instantiation process
numbers of nodes typically does not slow down the instantiation process
much.
Images may be referred to in requests in three ways: by URN, by an unqualified
......@@ -48,7 +48,7 @@ the image into the profile. @(tb) will fetch your image on demand, and cache
it for some period of time for efficient distribution.
Images in @(tb) are versioned, and @(tb) records the provenance of images.
That is, when you create an image by snapshotting a disk that was previosuly
That is, when you create an image by snapshotting a disk that was previously
loaded with another image, @(tb) records which image was used as a base for
the new image, and stores only the blocks that differ between the two. Image
URLs and URNs can contain version numbers, in which case they refer to that
......@@ -86,7 +86,7 @@ By default, all @seclink["physical-machines"]{physical hosts} are given a
public IP address. This IP address is determined by the host, rather than the
experiment. There are two DNS names that point to this public address: a
static one that is the node's permanent hostname (such as
@tt{apt042.apt.emulab.net}), and a dynamic one that is assinged based on the
@tt{apt042.apt.emulab.net}), and a dynamic one that is assigned based on the
experiment; this one may look like @tt{<vname>.<exp>.<proj>.apt.emulab.net},
where @tt{<vname>} is the name assigned in the @seclink["rspecs"]{request
RSpec}, @tt{<eid>} is the name assigned to the
......@@ -111,7 +111,7 @@ for allocation in this manner.
Note that the above refers to VMs created by @(tb) itself; for @(tb) users who
wish to bring up their own virtual machines and wish to have public addresses
assigned to them, see our section on
@seclink["planned-dynamic-public-ip"]{planned support for dyamic public
@seclink["planned-dynamic-public-ip"]{planned support for dynamic public
addresses}.
@section[#:tag "markdown"]{Markdown}
......@@ -119,7 +119,7 @@ addresses}.
@(tb) supports
@hyperlink["http://daringfireball.net/projects/markdown/"]{Markdown}
in the major text fields in @seclink["rspecs"]{RSpecs}. Markdown is a simple
formatting syntax with a straighforward translation to basic HTML elements
formatting syntax with a straightforward translation to basic HTML elements
such as headers, lists, and pre-formatted text. You may find this useful in
the description and instructions attached to your profile.
......
......@@ -16,7 +16,7 @@
for notes regarding the status of the facility.}
@italic[(if (equal? doc-mode 'pdf)
(list "The HTML version of this manual is availble at " (hyperlink apt-doc-url apt-doc-url))
(list "The HTML version of this manual is available at " (hyperlink apt-doc-url apt-doc-url))
(list "This manual is also available as a " (hyperlink "http://docs.cloudlab.us/manual.pdf" "PDF")))]
......
......@@ -189,17 +189,17 @@ is to @seclink["getting-help"]{contact us}.
@section[#:tag "jacks"]{Creating a profile with a GUI}
@(tb) embeds the Jacks GUI for simple creation of small profiles. Jacks can
be accesed by clicking the ``topology'' button on the profile creation or
editing page. Jacks is designed to be simple, and to ensure that the topolgies
be accessed by clicking the ``topology'' button on the profile creation or
editing page. Jacks is designed to be simple, and to ensure that the topologies
drawn can be instantiated on the @seclink["hardware"]{hardware available}.
Thus, after making certain choices (such as picking an operating system image)
you may find that other choices (such as the node type) become limited.
@screenshot["jacks-blank.png"]
Jacks has a ``pallette'' on the left side, giving the set of node types
Jacks has a ``palette'' on the left side, giving the set of node types
(such as physical or virtual machines) that are available. Dragging a node
from this pallette onto the larger canvas area on the right adds it to
from this palette onto the larger canvas area on the right adds it to
the topology. To create a link between nodes, move the mouse near the first
node, and a small black line will appear. Click and drag to the second node
to complete the link. To create a LAN (multi-endpoint link), create a link
......@@ -212,7 +212,7 @@ To edit the properties of a node or link, select it by clicking on its icon
on the canvas. The panel on the left side will be replace by a property
editor that will allow you to to set the @seclink["disk-images"]{disk image}
for the node, set commands to be run when the node boots, etc. To unselect
the current node or link, and return to the pallette on the left, simply
the current node or link, and return to the palette on the left, simply
click a blank area of the canvas.
@section[#:tag "geni-lib"]{Describing a profile with python and @tt{geni-lib}}
......
......@@ -22,14 +22,14 @@
@clab-only{
@section[#:tag "cloudlab-utah"]{Utah/HP CloudLab Cluster}
The CloudLab cluster at the University of Utah is being built in patnership
The CloudLab cluster at the University of Utah is being built in partnership
with HP. The first phase of this cluster consists of 315 64-bit ARM
servers with 8 cores each, for a total of 2,520 cores. The servers are
built on HP's Moonshot platform using X-GENE system-on-chip designs from
Applied Micro. The cluster is hosted in the University of Utah's Downtown
Data Center in Salt Lake City.
More technitcal details can be found at @url[(@apturl "hardware.php#utah")]
More technical details can be found at @url[(@apturl "hardware.php#utah")]
@(nodetype "m400" 315
(list "CPU" "Eight 64-bit ARMv8 (Atlas/A57) cores at 2.4 GHz (APM X-GENE)")
......@@ -50,7 +50,7 @@
which has full bisection bandwidth internally.
We have plans to enable some users to allocate entire chassis; when
allocated in this mode, it will be possible to have complete adminstrator
allocated in this mode, it will be possible to have complete administrator
control over the switches in addition to the nodes.
}
......@@ -63,7 +63,7 @@
bisection bandwidth. It will have 525 TB of storage, including SSDs on
every node.
More technitcal details can be found at @url[(@apturl "hardware.php#wisconsin")]
More technical details can be found at @url[(@apturl "hardware.php#wisconsin")]
@(nodetype "ucs220m4" 90
(list "CPU" "Two Intel E5-2630 v3 8-core CPUs at 2.40 GHz (Haswell w/ EM64T)")
......@@ -96,7 +96,7 @@
}
@item{A 10 Gbps Ethernet @bold{``experiment network''}--each node has
@bold{two interfaces} on this network. Twleve leaf switches are
@bold{two interfaces} on this network. Twelve leaf switches are
Cisco Nexus C3172PQs, which have 48 10Gbps ports for the nodes and
six 40Gbps uplink ports. They are connected to six spine switches
(Cisco Nexus C3132Qs); each leaf has one 40Gbps link to each
......
......@@ -155,6 +155,6 @@ will develop interfaces to expose, explore, and export this information.
In some cases, users would like to create their own virtual machines, and would
like to give them public IP addresses. We plan to allow profiles to request
a pool of dyanmic addresses; VMs brought up by the user can then run DHCP to
a pool of dynamic addresses; VMs brought up by the user can then run DHCP to
be assigned one of these addresses. An open question is how we will be able
to tell which DHCP requests belong to which experiment.
......@@ -79,7 +79,7 @@ staff, or others who are relatively senior positions.
@screenshot["geni-portal-login.png"]
After you log in, you will asked to authorize the @(tb) portal to use
this account on your behalf. If your ceritifcate at your GENI aggregate
this account on your behalf. If your certificate at your GENI aggregate
has a passphrase on it, you may be asked to enter that passphrase; if not,
(as is the case with the GENI portal) you will simply see an ``authorize''
button as below:
......
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