Create an overlay using the overlay manager specified.
Discover daemons available for creation of overlay using the overlay manager specified.
Obtain the status any of the overlays deployed and managed by the specified overlay manager.
Teardown an overlay deployed by the specified overlay manager.
Name of the new overlay. A suffix such as ".xbone.overlay" will be added automatically. If "use DNS" is checked below, the overlay name will also become part of the DNS names of your overlay nodes.
Select whether the overlay will use IPv4 or IPv6 tunnels.
If you check "use DNS", the overlay manager will assign DNS names in the OM's domain to the nodes of the new overlay. If unchecked, no DNS entries are created, and you will need to use IP addresses directly to reach overlay nodes.
If you check "use LDAP", the overlay manager will query hosts from LDAP server, those hosts will be used in the overly creation and node deamon discovery. Specify attribute-value pairs to narrow the search in the database (e.g., os=linux, kernel=bob). The node daemons must register first with appropriate attributes.
The overlay manager that will be used to deploy the overlay. It has
the format
Multicast search radius limiting the region in which the overlay manager will look for X-Bone hosts willing to participate in setting up the new overlay.
These topologies are available for new overlays:
![]() Linear |
![]() Ring |
![]() Star |
Dynamic routing support is experimental This option will determine whether to use Static Routing or Dynamic Routing within the overlay. Only dynamic routing with Zebra/Quagga are supported.
Application Deployment is still Experimental!
Automatically deploy and
start an application after the overlay has been set up. You need to
specify the complete URL of the deployment script, eg. http://,
file://, or (anonymous) ftp://.
Deployment of custom network is still
experimental! Specify the complete URL of a netlist file,
e.g. file://, or (anonymous) ftp://. The format is quite simple - a
series of host pairs separated by newlines. The names chosen for the
virtual hosts will those specified in the netlist. The checking for
pairs is strict, and lines that dont match the pair requirement will
be discarded.
$cat netlist.txt
apple banana
banana orange
orange apple
Number of hosts in the overlay. (Hosts are overlay nodes that do not route packets.)
Operating system requirements for the hosts. Only hosts of the checked operating systems will be picked for the new overlay.
Number of routers in the overlay.
Operating system requirements for the routers. Only routers of the checked operating systems will be picked for the new overlay.
IPsec authentication algorithm used to authenticate all overlay traffic.
IPsec encryption algorithm used to encrypt all overlay traffic.
Number of seconds to wait for discovery responses from resource daemons
Number of hops the discovery message should be multicast.
Properties of the links in the overlay. All links are identical.
Specify a list of hosts that must be used for the overlay creation. The host names must be separated by space, commas or newlines.