GitLab

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.

has the correct new_ tables in it.

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...

New 'blog-like news system.
Should make it easier to keep up with news updates!
Since:
  1. Doesn't require editing news.html in the CVS tree and
     recopying it/reinstalling just to add a news item.
  2. Doesn't involve editing menu.php3,
     since the modified date and "new" icon is automatic now.
  3. Looks nicer.

Also, it is based off the db, so other sites can have other news,
which they can maintain independently.

There are of course, neat features that have been suggested that
could go with this, such as message updates and automatic
mailing list mailings of news, but those don't exist yet...

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.

default SNMP community string (from configure) for individual
switch stacks.

Stored in $TB/www/thumbs/,
with filenames generated by hashing random data with experiment name.
(Stored in vis_experiments table in db.)

params to the entry, so that two pipes are built, one to the lan
and one from the lan. For duplex links, these params are ignored since
there is only one pipe (to the switch).

loaded on at once. The idea is to use this for things like rtLinux
that require a per-machine license. This mechanism is circumventable,
(for example, by simply making a second image), so it's mainly to
prevent experimenters from accidentally violating the license.

file with a tb- command and used in assign_wrapper to *force* link
delays when a delay would not otherwise be inserted. This avoids the
problem of trying to figure out when the user has set a queue param
that requires a delay. Kludgy, I know.

file with a tb- command and used in assign_wrapper to use link delays
instead of delay nodes. Default is zero, of course.

* Add vnode0,vnode1 slots to the delays table. This will allow us to
  match ipfw pipes to nodes after swapin, hopefully allowing us to
  control the delays for lans in addition to duplex links.

* Add IPaliases to interfaces table. Used in assign_wrapper when
  constructing "emulated" links, which will share a link via the use
  of aliases on the interface. This is a comma separated list of IP
  addresses (no, I refuse to make this a separate table!).

* Add virtnode_capacity slot to node_types, defaults to zero. This is
  used in ptopgen for determining how many virtnodes fit on a real
  node. I have not thought this through completely, but it allows me
  to make progress on other fronts.

* Add linkdelays delays, which sorta resembles the delays table, only
  this table stores oneway delays links, to be set up on the endpoints
  of a link or lan. Also, instead of being based on ipfw bridge rules,
  it is based on IP address/mask rules. At some point this table may
  merge witk the delays table, but will take time to work out the
  details and I do not want to mess up existing experiments by
  changing the delays table! Anyway, a duplex link gets one of these
  for each endpoint (a xmit ipfw rule). To mimic our lan setup, lan
  links get two, an xmit *and* a recv rule. My hope is that link
  delays will look just like normal delays (a packet leaving a node
  for a lan will get the outgoing delay, and a packet arriving gets
  the incoming delay).

VLAN domain. This means that we have to create and delete VLANs on
all switches, instead of just the 'leader'. This behavior is
controlled through the new single_domain column in the
switch_stack_types table.

node_id,phys_nodeid to help keepalive stuff. Unfortuantely, this
one doesn't seem to be making much of a difference.

Also, add a pid,eid key to resrved to ehlp queries that want to
find nodes assigned to a certain project, for example.