Commit 2d567a6d authored by Gary Wong's avatar Gary Wong

Document the geni-lib dynamic IP address pool extension.

parent 9c86bbbb
......@@ -78,8 +78,6 @@ manipulate RSpecs directly.
@section[#:tag "public-ip-access"]{Public IP Access}
@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
......@@ -108,11 +106,21 @@ 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 dynamic public
addresses}.
@subsection[#:tag "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 also allow profiles to request
a pool of dynamic addresses; VMs brought up by the user can then run DHCP to
be assigned one of these addresses.
Profiles using @seclink["geni-lib"]{python scripts and @tt{geni-lib}} can
request dynamic IP address pools by constructing an @tt{AddressPool} object
(defined in the @tt{geni.rspec.igext} module), as in the following example:
@code-sample["geni-lib-dynamic-ip-pool.py"]
The addresses assigned to the pool are found in the experiment
@seclink["rspecs"]{manifest}.
@section[#:tag "markdown"]{Markdown}
......
# Request a pool of 3 dynamic IP addresses
pool = AddressPool( "poolname", 3 )
rspec.addResource( pool )
......@@ -151,10 +151,3 @@ will develop interfaces to expose, explore, and export this information.
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 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.
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