per-experiment instantiation with aggregate data like the number of
swapins, the dates and the like. The other part is the per
swapin/modify stats. These are number of pnodes, links, lans,
etc. Long term, I think we want more precise swapin stats, and with
experiment modify in the mix, we need to have multiple stat records
per experiment, but do not need to duplicate all the stuff in the
other table just mentioned.

To reduce the amount the table size, we cross reference the tables by
index only instead of with pid,eid and the like. We use exptidx to
link experiments, experiment_stats, and the new experiment_resources
table. experiment_resources and stats are linked by another index in
the resources table, which indicates which is the current resource
row. On a modify, a new resource record is created, and the stats
record updated to point to the new (latest) resource record.

Web Changes: Improve showstats and showexpstats. Make them user
accessible so that mere users can see stats for themselves and for
their projects. No ability for mere users (PIs) to look at another
person's stats. Generally, these two pages need more work, but now
they are more useful. I added Show Stats to the user info and project
info pages to display per-usr/proj stats. Add more info in the
showstats display, but the showexpstats display is still not pretty
printed; just the raw tables.

Rename a few fields, add some indexes, and otherwise make some minor
changes that are sure to annoy everyone.

per-OS. Also, moved the functionality to check for this into libdb,
so we can call it from other places (like the batch daemon.)

we can create emulated links that use the veth device instead of an IP
alias. Without linux support, mere users would not get to choose this
option since it will only work between FreeBSD boxes with veth
support.

Unlike the interfaces table, veth interfaces come and go with
experiment swapin and swapout, with assignment to be done in
assign_wrapper. However, each veth maps to a real interface on a node,
as defined in the interfaces table, and the cross link is the "iface"
slot. There is a "mac" address since veth devices need a MAC, but I'm
not sure how that will be assigned yet. I am letting the DB do the
allocation of veth ids by making it an auto_increment field, and a
dual key of (node_id, veth_id). So, the DB will assign increasing
values per node_id, not globally to the table. Very slick.

swap_exitcode (last error), idle_swaps (a count), batch (a flag to
indicate a batch experiment).

Add a operational log. Okay, its not actually a log, but a table that
will grow forever until it consumes the earth. Its a small table
though, so it will take a few years. Its cross indexed with the
experiment_stats table, so by massaging this table along with the
stats table, we can get a good picture of what was running on the
testbed when, and how many resources it was using. Sorry, not a log
file, but we can easily generate a log file from tbe table if the Boss
really wants one. The table entry averages 28 bytes.

Move stats to their own main menu item (admin mode only). Remove from
the showexp_list page since that was bogus.

initstats.pl to fill in the tables as best as possible. Mostly a
hack job since we need Mac's scripts to go over the logs and really
fill in the info.

as they primary key instead of the node_id, so that the latter can be
easily changed. Also added a timestamp the the new_nodes column.

been auto-discovered, but are waiting for the testbed admins to
'approve' them. They don't need nearly as much information as the
real nodes and interfaces tables.

who gets root on widearea nodes, inside and outside of jail. Kinda
brute force; might need to make this more flexible at some point,
perhaps with a node/user mapping table for widearearoot (root outside
the jail), and a widearea_trust slot to the group_membership table
(root inside a jail), but this will do for now since its handled
entirely inside of tmcd.

I was originally using local_root to determine root access inside the
jail, but we need to more finely control who gets root on widearea
nodes. Outside the jail, only tbadmin got jail, and thats definitely
too restrictive!

- Added 'Country' to users table
- Changed "Zip" to "ZIP/Postal Code"
- Reformatted Postal Address Forms

Changed sitevariables table to use 'varchar(255)' for
name column instead of 'text'.
Made name column primary key.

This is pretty much a comment field for now;
NULL is a safe value, but if a node is a RON node
"ron:" followed by the name of the node in the ron
hosts table (in the external-to-emulab ron db) is
the preferred value. (This may facilitate automatic
db synchronization later.)

Changed widearea_nodeinfo address columns to tinytext,
to make them consistent with users table.

Added 'sitevariables' table.

This is the table prompted by Mac's email yesterday, which
can contain site-specific configuration options.

'default' _must_ be set for each row, and will be used if
'value' is NULL.

'description' _should_ be set for each row.

The table doesn't have a primary key, but is indexed to
32 characters on the "name" column, so it should be plenty efficient.

libdb functions and web interface forthcoming...

finally! These have been in the DB for a long time, but never used.
As Eric pointed out, its easier to get realistic address info from
people if we provide the right forms. The downside is that all current
users will have to adjust their info the next time they edit their
info. Thats okay. I thought about forcing all users to do it the next
time they log in, but I figured people would scream.

Instructions for adding 'webnews' table.

only pid, to pid/gid like most other things in the testbed. Also add a
"global" slot to denote images that are globally available to all
projects (system images). The older "shared" attribute is now used to
denote images that are shared within a project (available to all
subgroups in the project). The migration path for existing DBs is
given in the migrate file. Be sure to run those commands on an
existing testbed or things will break!

www/newimageid, www/newimageid_ez: A bunch of changes for
shared/global attributes. Added a group menu to the form so users can
create images in subgroups. Beefed up the Java code that constructs
the path name to use the gid, shared, and global attributes of the
form to give the user the best possible path that we can. Improved the
pathname checking code so that we do not allow just any old path in
case the user elects to disregard the path we carefully constructed
for them. Also check the proj/group membership, and setup defaults for
users that have permission in just one pid/gid to create images.

libdb.in: Changed permission check in TBImageIDAccessCheck() to
reflect shared/global attribute changes.

os_load: Get rid of test that checked path of the image. The path
checking is done in the web interface anyway, so why duplicate in 4
places. Other minor changes reflecting shared->global name change.
Also note that images can come from the group directory now.

create_image: Get rid of test that checked path of the image. The path
checking is done in the web interface anyway, so why duplicate in 4
places. Also note that images can come from the group directory now.

www/dbdefs: Changed permission check in TBImageIDAccessCheck() to
reflect shared/global attribute changes.

www/showimageid_list, www/showstuff: Minor global/shared attribute
changes.

www/menu: Change osids/imageids pointer to point to the image list,
not the osid list. This is more reasonable for mere users who have
access to the EZ form, and thus never really need to concern
themselves with osids.

www/editimageid: Add proper pathname checking. There were no checks at
all before!

Bad idea. Use an auto_incrementing idx field instead.

by assign_wrapper to help control emulated links. When set for an
emulated link, assign uses the BW spec for mapping the links (onto
phys links) but does not insert a linkdelay to traffic shape it
(unless the link is shaped in some other manner, like a delay or plr,
in which case a linkdelay is inserted, but with no bw cap). This might
be temporary syntax, expecially if we cannot make emulated links work
right!

of emulated and linkdelays on a per-link/lan basis (although you
cannot make a lan emulated at this time).

	tb-set-link-uselinkdelay $link0 1
	tb-set-lan-uselinkdelay $lan0 1
	tb-set-link-emulated $link0 1

Added slots to the virt_lans table, used in assign_wrapper to control
these features on a per link/lan basis. Note, the global options are
still available to prefer/force linkdelays for an entire experiment.
When setting uselinkdelays on a per link/basis, if the link would not
otherwise be shaped, you are requesting that a linkdelay be inserted
anyway (in otherwords, its the equiv of tb-set-forcelinkdelays on an
individual basis).

to a specific one, for the purposes of mapping things like FBSD-STD to
FBSD47-STD (the current OSID to use). This is technically more correct
than what os_setup used to do, which was map FBSD-STD to whatever
FreeBSD OSID was currently on the disk. Now it maps to a specific one,
and if that is not loaded, it sets up a reload.

existing DB to bring it into compliance with the changes. Its
a text file, but please put in actual sql commands or script.
Mark each change with the CVS revision number of the corresponding
change in database-create.sql.