It has been dead for a long time and I am tired of seeing the message.

so that it can be called from the PG code.

This commit is intended to makes the license status of Emulab and
ProtoGENI source files more clear.  It replaces license symbols like
"EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
blocks that contain actual license statements.

This change was driven by the fact that today, most people acquire and
track Emulab and ProtoGENI sources via git.

Before the Emulab source code was kept in git, the Flux Research Group
at the University of Utah would roll distributions by making tar
files.  As part of that process, the Flux Group would replace the
license symbols in the source files with actual license statements.

When the Flux Group moved to git, people outside of the group started
to see the source files with the "unexpanded" symbols.  This meant
that people acquired source files without actual license statements in
them.  All the relevant files had Utah *copyright* statements in them,
but without the expanded *license* statements, the licensing status of
the source files was unclear.

This commit is intended to clear up that confusion.

Most Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the Affero GNU General Public License, version 3
(AGPLv3).

Most Utah-copyrighted files related to ProtoGENI are distributed under
the terms of the GENI Public License, which is a BSD-like open-source
license.

Some Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the GNU Lesser General Public License, version 2.1
(LGPL).

We thought we had it on all this time, but we have been enabling "xntpd"
in /etc/rc.conf, but it has been "ntpd" since about FreeBSD 5.

Boss/ops/fs: reboot them together after setup rather than serially.

Nodes: leave them in PXEWAIT throughout the setup, until after boss has
been rebooted.  At that point we send them the new bootinfo RESTART command
telling pxeboot to re-DHCP and use the new info obtained (next-server) to
contact a potentially new boss node.  This is a quick way to switch a node
in PXEWAIT from talking to the outer boss to talking to the inner one.

A significant number of rinky-dink changes were needed to do this, primarily
adding a new state, PXELIMBO, where nodes can be sent to sit until they are
restarted.  It turns out, just putting them in an existing state such as
PXEWAKEUP or SHUTDOWN wouldn't work, as they tend to timeout or otherwise
reboot.

resolution. Less confusing now.

Ongoing changes to make better use of the node objects and methods.

deleted, they still remain in the user table with a status of
"archived", but since all the queries in the system now use uid_idx
instead of uid, it is safe to reuse a uid since they are no longer
ambiguous. 

The reason for not deleting users from the users table is so that the
stats records can refer to the original record (who was that person
named "mike"). This is very handy and worth the additional effort it
has taken.

There is no way to ressurect a user, but it would not be hard to add.

land in hwdown.

Currently, if a node fails to boot in os_setup and the node is running
a system image, it is moved into hwdown. 99% of the time this is
wasted work; the node did not fail for hardware reasons, but for some
other reason that is transient.

The new approach is to move the node into another holding experiment,
emulab-ops/hwcheckup. The daemon watches that experiment, and nodes
that land in it are freshly reloaded with the default image and
rebooted. If the node reboots okay after reload, it is released back
into the free pool. If it fails any part of the reload/reboot, it is
officially moved into hwdown.

Another possible use; if you have a suspect node, you go wiggle some
hardware, and instead of releasing it into the free pool, you move it
into hwcheckup, to see if it reloads/reboots. If not, it lands in
hwdown again. Then you break out the hammer.

Most of the changes in Node.pm, libdb.pm, and os_setup are
organizational changes to make the code cleaner.

because we (vnode_setup) needs to go out to the nodes and run vnodesetup
to trigger the reload, but os_setup needs to setup the reload.  So for
now, os_setup sets up the reload but does not wait nor reboot the vnode;
vnode_setup does that like normal.  Probably there are going to be timeout
problems, but it's good enough for my needs right now.

the tb-set-node-os command with a second optional argument; if that is
present, the first arg is the child OS and the second is the parent OS.
We add some new features in ptopgen (OS-parentOSname-childOSname) based
off a new table that maps which child OSes can run on which parents, and
the right desires get added to match.  We setup the reloads in os_setup
along with the parents.  Also needed a new opmode, RELOAD-PCVM, to handle
all this.

For now, users only have to specify that their images can run on pcvms, a
special hack for which type the images can run on.  This makes sense in
general since there is no point conditionalizing childOS loading on
hardware type at the moment, but rather on parentOS.  Hopefully this stuff
wiill mostly work on shared nodes too, although we'll have to be more
aggressive on the client side garbage collecting old frisbee'd images for
long-lived shared hosts.

I only made these changes in libvtop, so assign_wrapper folks are left in
the dark.

Currently, the client side supports frisbee.  Only in openvz for now, and
this probably breaks libvnode_xen.pm.  Also in here are some openvz
improvements, like ability to sniff out which network is the public
control net, and which is the fake virtual control net.

node or virthost.

Enough information is logged so that, at any point in time,
it is possible to tell what images are being used.  After
collecting some stats for a while I hope to use this data to
evaluate various strategies for preloading disks with images
other than the default.

Although not its primary purpose, enough information is
collection to be able to get a snapshot of node usage at any
point in time.  This includes what nodes are being used and by
who, as in which experiments and thus which projects.

NOTE: For a while you might see a few of these warnings,
  *** WARNING: os_setup:
  ***   could not find previous state (rsrcidx=484084) in image_history
  ***   table, won't be able to determine newly allocated nodes
if someone does a swapmod to an experiment that was swapped in
before this commit was installed.  This is because os_setup uses
previous information in the table to determine newly allocated
nodes.  This warning can safely be ignored in this case, and should
go away over time.

Currently nodereboot in libreboot essentially ignores the waittime
arg because it forks and calls node_reboot to do the real work, but
doesn't pass on the waittime to it.  Fix this by adding a "-W"
option to node_reboot in order to specify the waittime.

Use this to extend the waittime for a PLC node to come up from 6 minutes to 10.

rather than "USER@boss.emulab.net".  The reason they where from
USER@boss.emulab.net is because they the script was being run as USER.
I just added the "From:" header to the email.

after reboot in first swapmod, so it would be dealloc'd in the second
swapmod).

plabslice, but still sorta behave like one. Mostly fixing up some
special cases and using a different waittime calculation.

thankless job but someone has to do it. I'm expecting to finish by the
time Bush 43 leaves office.

statements.

Parallelize the setup of plab vnodes alongside the loading of local
physical nodes.  We fork vnode_setup to operate on the plab vnodes just
before firing off local reload/reboot/reconfig operations.  The status
of the plab vnode setup setup is checked just before firing off vnode_setup
for any local vnodes.  The ISUP wait for plab vnodes continues to fall
within the same stage as wating for local vnodes.  New arguments have been
added to vnode_setup to tell it to only operate on specific vnode types.
'-j' for local jail nodes, and '-p' for plab nodes.  If neither are
specified, the default is to operate on all types.

Avoid counting planetlab vnodes twice.

  tbreport errors & context.

- Modified fatal() in swapexp, batchexp, and tbprerun, and die_noretry()
  in os_setup to pass hash parameter to tblog functions.

- Added tbreport errror & context information for select errors in
  swapexp, tbswap, assign_wrapper2, snmpit_lib, snmpit, batchexp,
  assign_wrapper, os_setup, parse-ns, & tbprerun.

- Added assign error parser in assign_wrapper2.

- Added parse.tcl error parser in parse-ns.

- Added severity constants for tbreport in libtblog_simple.

- Added tbreport() function & context table mappging for reporting
  discrete error types to libtblog.

Small bug fixes in cleanup in os_setup summary code.

Fix syntax error.

swapexp: The previous commit, witch added a message about the recovery
action when a swap-modify failed to the top of the email, did not
catch all of the possible cases.  Added the case when the experiment is
not swapped in.

os_setup: Refactored/rewrote os_setup error summary code.  Distinguish
the case when nodes fail to properly load the os and when the don't
boot after loading the os.

Don't use "no warnings 'uninitialized'" since that is a perl 5.6+ feature
and some are still using an ancient version of perl.

length => $length in os_setup!

Fixed bug in summary of failed nodes when there are more than can fit on a line.

Various tblog changes:

Added message about recovery action when a swap-modify failed to the
top of the email.

Fine tuned os_setup summary error.  Added (possible partial) list of
nodes that fail; if a large number fail only show as many that will
fit on a single line.  Other tweaks.

Flagged assign_wrapper errors of an Invalid OS as user errors.

table, into a new table called node_type_attributes, which is intended
to be a more extensible way of describing nodes.

The only things left in the node_types table will be type,class and the
various isXXX boolean flags, since we use those in numerous joins all over
the system (ie: when discriminating amongst nodes).

For the most part, all of that other stuff is rarely used, or used in
contexts where the information is needed, but not for type descrimination.
Still, it made for a lot of queries to change!

Along the way I added a NodeType library module that represents the type
info as a perl object. I also beefed up the existing Node module, and
started using it in more places. I also added an Interfaces module, but I
have not done much with that yet.

I have not yet removed all the slots from the node_types table; I plan to
run the new code for a few days and then remove the slots.

Example using the new NodeType object:

	use NodeType;

	my $typeinfo = NodeType->Lookup($type);

        if ($typeinfo->control_interface(\$control_iface) ||
            !$control_iface) {
  	    warn "No control interface for $type is defined in the DB!\n";
        }

or using the Node:

	use Node;

        my $nodeobject = Node->Lookup($node_id);
        my $imageable  = $nodeobject->NodeTypeInfo()->imageable();
or
        my $rebootable = $nodeobject->isrebootable();
or
        $nodeobject->NodeTypeAttribute("control_interface", \$control_iface);

Lots of way to accomplish the same thing, but the main point is that the
Node is able to override the NodeType (if it wants to), which I think is
necessary for flexibly describing one/two of a kind things like switches, etc.