put special characters in them.

a bootstrapping problem - this script is required to install into the
main tree, but of course, the testbed libraries are no there the first
time!

interface to the backend. mkproj now looks at the pcremote_ok set
and makes the proper calls to grantnodetype. This reduces the amount
of hardwired goo in the web interface.

Still, there is a bit of hardwired stuff in mkproj. At present we do
not form a relationship between a phys node type and the types we
assign to the virtual nodes. Thats is, nothing says that a pcplabphys
implies the right to use pcplabinet, etc. With only 3 remote phys
types, I just hardwired it into mkproj calling grantnodetype with type
pcplab (the class for the virtnodes) for pcplabphys. Same for pcron
and pcwa, (both get pcvwa). Ultimately we need a better type system.
In general the type system is pretty screwy.

Grant permission to use types/class of nodes. If given a specific
"type", then grant permission to use just that type. If its a class, then
permission to use all of the types in that class, the class itself, and any
aux nodetypes for the type/class (node_types_auxtypes table).

For example:

	wap grantnodetype -p testbed pc2000
	wap grantnodetype -p testbed pcvm
	wap grantnodetype -p testbed pcplab

Also added webnsgen as a frontend for web pages that need to call
nsgen.

and a template. The idea is that it's a general tool for generating
NS files for standard topologies (ie. LANs), filling in some
user-supplied values. Has some features that are useful for NS files,
like default values and skipping or commenting out sections if values
for variables are not given.

Could probably use some better error checking on the the XML file.

Does not yet get installed.

state machine (state). All of the stuff that was previously handled by
using batchstate is now embedded into the one state machine. Of
course, these mostly overlapped, so its not that much of a change,
except that we also redid the machine, adding more states (for
example, modify phases are now explicit. To get a picture of the
actual state machine, on boss:

		stategraph -o newstates EXPTSTATE
		gv newstates.ps

Things to note:

* The "batchstate" slot of the experiments table is now used solely to
  provide a lock for batch daemon. A secondary change will be to
  change the slot name to something more appropriate, but it can
  happen anytime after this new stuff is installed.

* I have left expt_locked for now, but another later change will be to remove
  expt_locked, and change it to active_busy or some such new state name in
  the state machine. I have removed most uses of expt_locked, except those
  that were necessary until there is a new state to replace it.

* These new changes are an implementation of the new state machine,
  but I have not done anything fancy. Most of the code is the same as
  it was before.

* I suspect that there are races with the batch daemon now, but they
  are going to be rare, and the end result is probably that a
  cancelation is delayed a little bit.

the new interfaces.

change.

node - copies source, etc. from NFS to avoid mountd problems, and
copies results back when finished.

a correct final reading.

When inserting new interface entries, set the role appropriately,
based on control_iface setting in the node_types table.

that jails do.  sshtb can now handle vnodeid's, and must be given a
vnodeid if it's a Plab node, because the username will differ
depending on this.

forget to do them all!

Handle interfaces we didn't find on the switch.

Use newnode_reboot to reboot nodes, since they won't yet be at their
'permanent' IP addresses.

Changed my mind again on what state the new nodes should be put into
once they've been created. Now, they go into emulab-ops/hwdown, and
boot into the FreeBSD MFS. This way, the admins have a chance to look
at them before they loose them on the world, and they're booted into
something that runs SSH, so we don't lose control over nodes that
don't have power controllers (which newnode doesn't currently handle,
anyway.)

Also, needs to be able to run sudo (as the admin) so that it can
restart dhcpd.

one that lists and allows operations on a number of nodes at once, and
another that allows editing of an individual node.

Split much of the functionality of newnodecheckin.php into a new
library, so it can get re-called from newnodes_list.php3 later.

Move where we look for MACs on the switches - instead of doing in in
newnode, call it from newnodecheckin.php - this provides the admins
more feedback as to what's going on, and allows them to call it again
later or put the information in by hand.

Allow base experiment to be changed when the experiment is swapped
out. That is, change virt_lans only. Eventually use this from the web
interface so that we can present a page to edit the traffic shaping
parameters on non-active experiments as well as active experiments.

them in the real nodes/interfaces/wires tables.

Not yet well tested! (So, they don't get installed yet)

Script and datafile to ensure consistency of off-site sitevariable
definitions-- A lot like schemadiff.

database-fill was inappropriate, since you don't want sitevars
from the main site to overwrite remote sitevars.

Needs to be integrated into install process, probably in the
same way as schemadiff.

bogus email to tbops, but rather spits the error directly to the
user.

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!

 - fix bad indenting to a uniform 4 spaces (before was 2, 4 and 8 mixed)
 - Move ping-for-isup functionality into a separate script
 - Make sure every transition triggered by stated (directly or indirectly)
   sends an event, instead of taking shortcuts.

This called for a new script, eventping, which just pings until the node
is pingable, then sends an ISUP event. Stated runs this in the background
where necessary, and nothing else should run it.

Adding eventping meant modifying configure and the utils makefile, too.

using the new assign, and captures Leigh's linkdelays work.

history).

When an image is created successfully, a message stating this fact is printed
to the log.

More importantly, I fixed a bug in the NFS slack factor logic which resulted
in create_image waiting forever for progress to be made.

Modified the timeout logic in create_image to track the image creation progress
(size) rather than simply waiting a certain amount of time.  Also changed the
code to report progress at regularly spaced intervals (adjustable), and
to indicate when the timeout timer has been activated, or halted due to
progress.  The changes also include an NFS cache slack factor, which makes
the effective non-progress timeout equal to the sum of the slack time, plus
the non-progress time (currently 3 + 5 = 8 minutes).

Some changes were made to the error and cleanup logic to help revert the
state of the DB and node as much as possible (node is not rebooted if the
DB state cannot first be reverted) prior to exit.