You can look at the error code to figure out if it will ever be
possible to map this experiment onto the testbed.

log, and to look at the summary page when the problem is not enough
free nodes!

CD, and for extra robstness.

the getbandwidth() call on them (which finds the closest matching
physical interface speed).

This is in addition to the normal bandwidth, and the difference is
that the estimated bandwidth is not enforced. It's just fed to assign
for mapping decisions. The idea is to allow for more efficient
packings by doing non-conservative bandwidth allocation.

Not documented yet, because it might change a little after I made it
work properly with asymmetric links.

addresses of the interfaces used so that its easier to set the
accesspoint using link_config and tevc. It would be nice if we did the
mapping for the user (from lan0-node1 to MAC) but that would require
changes to the scheduler to look inside events, and I do not want to
got there yet.

agent was created for each link,link-vnode in a link/lan only when
that link has a delay/linkdelay. Well, with the link-agent that will
be used on wireless lans, lets just stick those agents into the table
for all links/lans in the experiment; its harmless. Might revisit this
at some point.

with parsing assign's output.

the conglomerate link object, not the real link, for the reversed
flag.

makes link conglomerates.

we might be combining links that go in different directions. Keep
track of which direction a link points, and reverse the interfaces
when we print it out, if it's going the opposit direction than the
other links in the conglomerate.

new directive for your NS file: tb-use-physnaming(1) which means that
if you have a line like this:

	set pc6 [$ns node]

and pc6 is an actual name of a physical node, then do an implicit
"fixnode" to pc6. In other words, pc6 is the name of the node in your
NS file (virtual topo) *and* will be fixed to the real pc6. Needless
to say, if pc6 is allocated when you go to swapin, you lose.

Add a new function, factor_out_fixednodes, that takes a set of nodes
and a reference to another coarsening function. Seperately coarsens
the fixed nodes and passes the non-fixed nodes to the other coarsener.

Intended for debugging, and to use used with assign's pre-check
feature to catch experiments that will never be mappable.

currently available to only people with stud=1 status in the DB.

* www/tbauth.php3: Add a STUDLY() function to check that bit.

* www/linktest.php3: New page to run linktest on the fly. The level
  defaults to the current level in the experiments table, but you can
  override that via the form on the page.

* www/showexp.php3: Add link to aforementioned page. STUDLY() only.

* www/beginexp_form.php3: Add an option (selection) to set the linktest
  level for create/swapin. Defaults to 0 (no linktest). STUDLY() only.

* www/editexp.php3: Add an option to edit the default linktest level
  for an experiment. STUDLY() only.

* tbsetup/batchexp.in and tbsetup/swapexp.in: Add code to optionally run
  the linktest, sending email if it fails (exists with non-zero status).
  Failure does not affect the swapin.

In the ptop file, put the specific protocol (ie. 80211a) on the link
line.

In the ptop file, there is now only one fake airswitch. It can take
on all wireless types. We now only print one link line for each
physical wireless interface - it has the maximum bandwidth supported
by the interface, and is able to take on any protocol supported by the
interface.

match what ptopgen puts into to ptop file.

parsing code (for simplistic xml we spit from the parser).

and ptopgen.

Add link typing to assign. Each virtual link is given a single type.
Each physical link is given one or more types. A virtual link will
only be mapped to a physical link which can satisfy its type. In both
the top and ptop files, the link types are now mandatory, and they
fall at the end of the mandatory link arguments.

This differers from the 'regular' type system in two ways. First, a
plink is not constrained to filling only one type at a time. If we are
using emulated links, a plink could satisfy, say, an 'ethernet' link
and an 'fxp' link at the same time. This seems to more naturally match
the way we'll use link types.  Second, there are no counts assoicated
with link types, as there are for node types. ie. a link is not an
'ethernet:1' link, it's an 'ethernet' link. Presumably, when
multiplexing virtual links onto a physical one, it's bandwidth that's
the factor that limits the multiplexing.

The link type is now tak...

1. "make clean" will just remove stuff built in the process of a regular build
2. "make distclean" will also clean out configure generated files.

This is how it was always supposed to be, there was just some bitrot.

of their file server (aero)

Extend DISABLE_NAMED_SETUP: when set, we don't set a nodes hostname to
<name>.<eid>.<pid>.<domain> since that won't resolve.  Just stick with
pc<XXX>.<domain> in those cases.  The various sethostname* scripts are
now .in so that they get preprocessed to check for the option.

assign exits (exit codes).

* in assign_wrapper, no longer return any status from assign to the
  caller. This was pointless. Instead, return 0 on success, 1 on
  controlled error, and -1 on uncontrolled error (die() called
  someplace). Add in CANRECOVER bit whenever the wrapper exits, even
  if uncontrolled, by putting in an END block to catch the die. This
  should prevent certain cases where a swapmod error would be flagged
  as not recoverable.

* Remove most of the assign output processing since we no longer
  return its codes. Still print a portion of it to the log though.

* Change call to fatal() in assign_wrapper; do not pass an exitcode
  since in every case it was the same damn thing!

* Change tbswap to no longer carry assign_wrapper exit code to its
  exit.

* Change the batch daemon to treat all errors as continuable (keep
  batch queued) unless exit code is -1. We will need to revisit this a
  bit perhaps, when Rob adds precheck code.

major but it now works.

well known name so you can control it via the usual event mechanisms
(ns "at" and tevc). Previously, its name came from an internal
counter, and because the routine that creates the program object is
not at "toplevel", the parser would not rename the object. I'm sure
someone who understands this cruft could do better!

Anyway, now they are named as ${vname}_startcmd.

moment if its not "ethernet" its marked as wireless. We will need some
extra info if we ever branch out into non-ethernet, non-wireless lans.
Might also want to record what kind of wireless lans at some point?

links.

* ptopgen:

   1. Change to using interface_capabilities table to get the default
      speed for an interface type.

   2. The wrinkle is that an interface can have multiple speeds,
      depending on the protocol that is requested. In the wireless case the
      table looks like:

	| type             | capkey            | capval               |
	+------------------+-------------------+----------------------+
	| ath              | protocols         | 80211a,80211b,80211g |
	| ath              | 80211a_defspeed   | 54000                |
	| ath              | 80211b_defspeed   | 11000                |
	| ath              | 80211g_defspeed   | 54000                |

   3. We use the above info to tell us the default speed for links, based
      on the particular protocol.

   4. And lastly, create "air" switches for each of 80211a, 80211b, 80211g,
      and specify links from the switches to the nodes that have interfaces
      that support those protocols. At the moment, there is a hardwired
      list of 80211a, 80211b, 80211g in ptopgen, so create 3 new air
      switches and links from each of the nodes to each of the switches.
      Rob says that assign can handle this just fine (using the same
      interface on a node to connect to three different air switches, at
      different speeds).

* assign_wrapper:

   1. First off, I had to increase the bogousity factor of how we determine
      that a delay node is required (requires_delay() routine) on a link or
      lan. Using the interface_capabilities table, I determine the default
      speed for each protocol on each interface type.

   2. When calling requires_delay() I now the pass the lan so that we can
      get the "protocol" of the link/lan and use that to find the default
      speed. The main reason for all this crud is that if a user specifies
      a bandwidth of 54Mb on a wired ethernet, we want to make sure we
      insert a delay node, but not if the user is using 80211g. As it was,
      delay nodes would be skipped cause there are now nodes with
      interfaces that support those speeds. This change also allows to know
      that a delay node should be inserted on a wireless link, if we ever
      wanted to do something as silly as that!

   3. Okay, so now onto the actual wireless support!  Whenever the protocol
      for a lan is not "ethernet" spit out links to fake lan nodes, sorta
      like we used to do with ethernet lans before Rob made all those great
      changes to assign. So, a lan with protocol 80211a will get fake links
      to the 80211a air switch that ptopgen spits out (see above).  We
      currently bypass all delay node processing on wireless lans, and in
      fact we avoid most post-processing (after assign) of wireless lans
      (no vlans, veths, etc). At some point we can bring certain things
      back in (like emulated links) but that will be some time! See
      comments above about ptopgen.

   4. Added a section to copy over the virt_lan_settings and
      virt_lan_member_settings to the interface_settings table, for each
      node's interfaces in the mapped experiment. I also make up the ssid
      for the lan, and add the protocol to the settings so that the client
      side knows what it is supposed to do. I also set the acesspoint since
      that requires MAC addresses, and this is easiest place to get and set
      the MAC (all of the nodes in a lan need to know the MAC of the node
      acting as the access point). In the virtual topology, the accesspoint
      is specified as a node name.

* tbsetup/ns2ir:

   1. Add tb-set-lan-protocol(lan, protocol) to set the protocol to one of
      ethernet, 80211a, 80211b, 80211g. Defaults to ethernet.

   2. Add tb-set-lan-accesspoint(lan, accesspoint) to set the name of the
      access point for a lan. Obviously this makes sense for only wireless
      links; ignored for wired links.

   3. Add tb-set-lan-setting(lan, setting, value) to specify a setting that
      applies to the entire lan. At present, these are ignored for wired
      lans. Both setting and value are strings.

   4. Add tb-set-node-lan-setting(lan, node, setting, value) to specify a
      setting that applies to a particular node in a lan. At present, these
      are ignored for wired lans. Both setting and value are strings.

there is not default imageid, so it can generate an error!

down when invoked from the RPC server.

probably not the final form for this stuff, but is fine for initial
development of wireless support.

	tb-set-protocol $lan0 "80211g"
	tb-set-lan-accesspoint $lan0 $nodew1

statement.