Commit ac509c4d authored by Robert Ricci's avatar Robert Ricci

Write about public IP addresses

parent 3e12ce6a
......@@ -78,7 +78,41 @@ manipulate RSpecs directly.
@section[#:tag "public-ip-access"]{Public IP Access}
@(under-construction)
@future-work["planned-dynamic-public-ip"]
@(tb) treats publicly-routable IP addresses as an allocatable resource.
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
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
@seclink["experiments"]{experiment}, and @tt{proj} is the
@seclink["projects"]{project} that the experiment belongs to. This name is
predictable regardless of the physical nodes assigned.
By default, @seclink["virtual-machines"]{virtual machines} are @italic{not}
given public IP addresses; basic remote access is provided through an @tt{ssh}
server running on a non-standard port, using the physical host's IP address.
This port can be discovered through the @seclink["rspecs"]{manifest} of an
instantiated experiment, or on the ``list view'' of the experiment page.
If a public IP address is required for a virtual machine (for example, to
host a webserver on it), a public address can be requested on a per-VM basis.
If using @seclink["jacks"]{the Jacks GUI}, each VM has a checkbox to request
a public address. If using @seclink["geni-lib"]{python scripts and
@tt{geni-lib}}, setting the @tt{routable_control_ip} property of a node
accomplishes the same effect.
Different clusters will have different numbers of public addresses available
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
addresses}.
@section[#:tag "markdown"]{Markdown}
......
......@@ -150,3 +150,11 @@ will develop interfaces to expose, explore, and export this information.
temperature). @(tb) will provide both logged and real-time access to this
data for experimenters.
}
@section[#:tag "planned-dynamic-public-ip"]{Dynamic Public IP Addresses}
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
be assigned one of these addresses. An open question is how we will be able
to tell which DHCP requests belong to which experiment.
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