GitLab

of the archive.

Hopefully fix bug in die_noretry which causes an experment to incorretly
report an error as:
  Can't locate object method "tberror" via package "No image can be found
  for arms-bb-mysql on pc29!" at /usr/testbed/libexec/os_setup line 41.
  (os_setup)

font, font size, etc as the main menus.

The non-main style (devel trees) is a little broken; style files are
really a pain, or maybe its just our style files that are impossible
to understand. Or maybe I'm just a dope.

Avoid starting an intermediate shell when executing commands.

Clean out unreferenced signatures

Move the definition of the header to defs.php3 so that it's not
duplicated.

archived to long term storage.

Helpful for debugging things like linktest.

This is strictly information right now; it is not worth trying to make
linktest calculate the expected loss for a red or gred link, but at
least the error report will indicate it.

Also add a linktest version tag and send that to the output log.

This is strictly information right now; it is not worth trying to make
linktest calculate the expected loss for a red or gred link, but at
least the error report will indicate it.

help readers identifiy new items.

Also, fix the webMaster and managingEditor elements - I was using the
name of the defs variable, not the name of the PHP variable...

First cut at a daemon that does regular checkups of the testbed
hardware/software.

	* configure, configure.in: Add tbsetup/checkup directory.

	* db/audit.in: Add a listing of stuck checkups.

	* install/boss-install.in: Add 'elabckup' user.

	* rc.d/3.testbed.sh.in: Startup the checkup_daemon.

	* sql/database-create.sql, sql/database-migrate.txt: Add the
	checkups tables.

	* tbsetup/GNUmakefile.in: Descend into the checkup directory.

	* tbsetup/checkup: The checkup daemon, man page, and
	  associated scripts.

	* tbsetup/ptopgen.in: Add a feature with a value of 0.9 to
	  prereserved nodes to keep them from being allocated unless
	  they're really wanted.

	* utils/firstuser.in: Add some other options so the script can be
	  used to create other pseudo users.

an inner emulab.

lost.  Since the exempt eid is always given when doing a swap in, the
prereserve wasn't doing anything.

if the user was in admin mode.

from RSS aggregators such as Firefox and Google Reader.

This came out of an idea discussed with Chris Alfeld and Jay.

with the mote powermonitor device.

scheduler can startup.

What ssh returns in the case of a timeout depends on timing, and since we
started using sshtb, even the check for a timeout return code wasn't working.

* The rest of the backend support for simplistic experiment duplication,
  either from an existing (current) experiment, or from a specific
  archive revision of a current or terminated experiment.

* Rework the swapmod code so that the archive is committed at the exact
  end of the swapout phase. This required adding (and moving) some code
  from swapexp to tbswap sine that is where the actual swapout/swapin
  happens during a swapmod

* Add a special directory called "archive" to the experiment
  directory, which is a place where users can store stuff they want
  saved away. This will eventually be a user defined set of
  directories, but this was good for getting the basic mechanism in
  place. Note that the when the contents of this directory are copied
  out for placement into the archive, it is an exact copy made with
  rsync.

* No longer "clean" the contents of the temporary store between
  commits of the archive. This was creating a lot of headaches, and
  was also causing the revision history to get messed up. The downside
  of this is that we have to be more careful to explicitly delete
  files that the user no longer uses. I have not solved all these
  issues yet, so in the meantime files will get left in the archive
  even if the user no longer references them.

This change displays the tags and pointers to the Archive matching
the experiment history and provides a "run" button to check out the
NS file from an earlier run and turn that into a new experiment. Still
very primitive.

If you specify an explicit firewall, you are implicitly assigned security
level 2 and you cannot explicitly specify the security level.  Likewise,
if you specify a security level, you cannot also specify a firewall.

The reason for this is that security level 1 (aka "Blue") now has a slightly
different meaning.  It is intended for protecting the inside from the outside
rather than visa-versa.  The only practical implication of this is that for
level 1, we don't do all the fancy power-off-boot-into-MFS-zapbootblock stuff
that we do for higher levels.

Anyway, I wanted to make sure that if you specify your own firewall, you
DO have to go through the full cleansing swapout since we can't trust a
firewall that the Average Joe sets up.

users only.

again.