GitLab

Actually, most of the changes here were just to generalize the "virtual
interface" state in the DB.  Other than the client-side scripts, there
is very little specific here specific to tagged VLANs.

In fact, you cannot specify "vlan" as a type yet as we haven't done the
snmpit support for setting up the switches.

For more info see bas:~mike/flux/doc/testbed-virtinterfaces.txt, which I
will integrate into the knowledge base and the Emulab doc at some point.

Each template has a datastore, which is really just a subdirectory that can
be populated with files, and committed to the subversion archive.  Note,
the datastore os specific to the template itself. The Template Archive link
on the Show Template page takes you to the subdirectory, which by
convention I am calling "datastore".

The directory actually lives in /proj/pid/exp/eid/TGUID-VERS ... but that
path is printed out for you on the archive page.

Anyway, put stuff in the datastore directory, and then commit the template
archive so there is a tag associated with it.

When an instance is created, a checkout of the datastore is placed in the
experiment directory (/proj/pid/eid/exp/template_datastore). The current
tag (from above) is stored with the instance so that we can later recreate
the enviroment for the instance, say for rerun.

Tarfiles and rpms in the datastore can be referenced as xxx://foo.rpm (in
your NS file).  tarfiles_setup transforms those when the instance is
swapped in, sorta like it does other URLs, only it does not actually fetch
them, just need to rewrite the paths so they reference datastore.

The program agent gets another environment variable so you can refer to the
datastore without hardwiring paths ($DATASTORE). Eventually I want to move
the checkout someplace else, but it was easy to drop it into the experiment
directory for now.

The adminon/off bit is now kept in the login table instead of the
users table so that you can be reddot on a per-browser (login) basis.

mess I created.

entries, but sheesh, they were screwed up! Hopefully fixed now.

the user has requested a per-experiment DB on ops (or wherever the DP
is). As you see, its an optional thing that will probably only be used
for templates.

* Rework metadata to be somewhat more general so that they can be used for
  things like parameter descriptions.

* My own little part of javascript hell ... add a highlight around the
  "current" template in the template graph. Sheesh!

* Add more tooltips (using the tooltip library). When you mouseover the
  metadata or descriptions, the formatted text is shown in a tooltip,
  which is handy when the valus is truncated cause its too long for the
  tables.

* setup some fields that parallel the
  elab-in-elab ones, for modifying the dhcpd.conf file.

* tb-set-node-plab-role to set a node as either 'plc' or 'node'
  used to set the DB role field above

show template page, to some primitive zoom code in the backend. It will
do for now.

Refactor "log" table to move some stuff into a new table.

are now reserved words mysql 5.X. Skip to the next entry ...

heavyweight queries in idlemail

node_types pxe_boot_path is going to be needed after all, so it has
made a triumphant return.

needed (reparsing of NS file with current bindings).

Mostly I decided that I made a huge mistake in using the exptidx as the
main cross index. I started to change that, which took a bunch of time.
Still more tables to fix up, but I think all of this code is gonna need
a major reorg once I am no longer under the gun to get it done.

an alternate "filename" for the dhcpd.conf file.  "Inner plabs" are likely
to need this (to boot pxelinux for emulating the plab boot CD).

dhcpd_makeconf picks up the DB field and sets the filename field accordingly.

nfree will invoke dhcpd_makeconf if any node being freed has a non-NULL
pxe_boot_path value, in order to reset it.

you can turn it on in your devel tree by setting the $EXPOSETEMPLATES
variable in www/defs.php3.in to 1. BE SURE NOT TO CHECK THAT CHANGE IN!

numbers off.  This should realign things...

Changed format of email sent to user on errors.  The error will now
appear instead of the generic message when I am confident it is
accurate.  The subject line will also change to reflect the cause of
an error.

Avoid sending mail to testbed-ops during failed swap related evenets
in some cases.  It will instead be sent to a new mailing list
testbed-errors.

Added a new row in the experiment info table "Last Error:" which
states the cause of the error, and links to a new page displaying the
error.

Made some assign/assign_wrapper errors more informative.

The error (as determined by tblog) is now stored in the database in a
more structured fashion.  This inlcudes adding a column for the session
(in the log table) to testbed_stats to link eash swap event with the
logs and possible the error.

Other changes to the database, see sql/database-migrate.txt

to commit it.

usage of the batch daemon on swapin.