mothership branch. Yes, this is going to annoy someone.

of the Utah clusters.

for emulab-ops and testbed for some testing.

option to the mapper, which passes along a -G option to ptopgen when
it should remove all 10G links.

are updated (this is a temporary hack until I change how accounts are
updated on the geni path).

1. Do not allow guest users to use anything but the APT cluster. We had
   talked about this a while back, and today it caused a problem:

2. Because a guest tried to use the Mothership (cause of a URN in the
   profile), we had GeniUser lookup confusion. We store guest users in the
   geni-sa geni_users table, but because PROTOGENI_LOCALUSER=1, we end up
   creating a nonlocal account on the Geni path, and that conflicts.
   Changed how we do lookups.

Status 204 (RC_NO_CONTENT) is actually the correct one, since we are not
retuning any content, but apparently gitlab is (no longer?) smart enough
to recoginze all 2xx codes as being okay, and seens to want to see 200

via the Geni API, which have hard to guess project names).

	boss> wap perl prereserve emulab.net:testbed 1

At the remote cluster, you prepend the domain of the SA (for the portal,
that is emulab.net) to the project name at the portal.  prereserve will
find the correct project, assuming at least one experiment has ever been
created on the remote cluster. If not, then this trivial little hack will
not work.

Useful when executing a bunch of these in a row.

This is useful for the new r430s where the control net location varies
depending on how many 1Gb experimental interfaces the node has.

shellinaboxd daemon and/or the wrapper is doing something strange that
makes apache unhappy.

all the time, so bail on that and fallback to reporting errors solely
though the spew log(s).

gone at the remote cluster.

* A new Start Linktest button is in the bottom right of the topology tab.

* When started, we create a new tab to display the linktest output
  (currently the unmodified output from Classic emulab linktest). The state
  of the experiment is change to linktest to prevent further action on the
  experiment, except of course for stop linktest.

* When linktest is running, there is a Stop Linktest button in the upper
  collapse panel. This will stop linktest in its tracks, but the tabs
  remain. When you kill a linktest tab while linktest is running, linktest
  continues running, you have to use the Stop button.

* I have added a small help document to the templates directory that the
  user is shown when they click on the ? mark in the linktest modal.
  Written in markdown format, it is a culling of text from the Emulab wiki
  linktest page.

Caveats:

* Because of polling, there is a short (5-15 seconds) delay before the
  experiment is returned to the ready state. Not much to do about this in a
  polling world. Wouldn't callbacks be nice?

* Linktest can be used on a multisite topology, although cross site links
  cannot be tested at this point. Links/Lans that are contained entirely to
  one site or the other are testable though. We build a new tab for each
  site to spew the linktest output.