except the creator now start out as frozen, to save lots of time
when setting up the elabinelab. To thaw:

myboss> wap tbacct -u thaw <user>

The -u option says to ignore the current status, and set the status to
what it should be. This should eventually be the default operation so
that this script is independent of the web interface.

elabinelab, and then thawing as needed.

Added speed-test-run, a client which fetches manifests for every sliver in a slice and runs speed-test on each node.

Merge branch 'mapflashbranch' of git-public.flux.utah.edu:/flux/git/users/mstrum/emulab-devel into mapflashbranch

Conflicts:
	protogeni/demo/src/Console.as
	protogeni/demo/src/MenuSliceCreate.as
	protogeni/demo/src/MenuSliceDetail.as

are not created during the swapin. This should save a bunch of time
when the project has lots of users. Even admin users are frozen, so if
you are an admin and need to log in:

realboss> sudo ssh innerboss
innerboss> sudo -u elabman tbacct thaw <user>

Hmm, might have to first change the status in the users table to
'active'

that not all accounts are created, saving time. If a frozen user
is then thawed, the account is created.

of the lans, so that vinterfaces work correctly.
Grab a new copy of the manifest after sliver start since in CM version
two, that is when the vlantags are set.
Clean up print statements and lower chattiness.

Clean up sliver action stuff, and add stop and restart.

debugging tool.

Bug fix to UpdateManifest(); need to pluck the vlantag out of the
linked lan (the underlying vlan when its an encapsulated link).

The component managers are those which have reported having a sliver to the SA.

when they are released (SHUTDOWN) since these proxy nodes do not
go though a typical state transition.

When schema file names were changed, these constants weren't. Didn't matter as long as the contents of the schema didn't change.