Doing this required adding columns to the virt and physical blockstores
tables to mark the attributes that will be considered for mapping.
Unmarked entries just flow through to the client-side.

This commit also introduces filesystem support in the form of passing
through a mount point to the client-side.  It is left to the client to
decide what filesystem and fs options to use to setup the space, including
any logical volume aggregation required to support the request.

amount a physical has is stored in the node types table, and the
per-vm memory requirement is stored in the nodes table. ptopgen
adds up usage, and subtracts from the total for the ptop file.
The vtop number comes from a virt_node_attribute table, and we
pass this through to the client side. Note that this is less
important for openvz, more so for XEN.

In the NS file:

	tb-set-node-memory-size $node 1024

Number is in MBs. The mapper defaults this to 128 for openvz and 256
for xen. Maximum is hardwired to 256 and 512 respectively. Need to
think about a good way to configure this in.

In the node_attributes table, add an "allowed_projects" entry with
the value a comma separated list of project names that may use
this node.

I hope we don't have another way to do this; could not remember if we
did already!

Causes a lot of extra mail to the protogeni-errors list.

All incoming rspecs are now validated with rspeclint.
Multiple Create calls are now permitted.
Slivers now have URNs at allocation time.
Delete now returns a list of ex-slivers.
Advertisement now specifies an operational state machine.
Other minor fixes.

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

So what if your testbed has a control network but no experimental
network? In the past you were SOL, but with this commit you can now
create links and lans on the control network that look just like
an experimental network link/lan.

To make this work, ptopgen sports a new option (-C) that will put the
control network links and wires and switches into the ptop file.

libvtop generally operates as normal, but need to arrange for the
physical ports to be put into dual tag/trunk mode, where the native
vlan is the Control network. This is done with by setting attributes
on the lan table entry that indicate dual and what to use for the
native vlan. snmpit looks for these attributes.

There are a couple of places that use the stack name (Control or
Experiment) to determine if a vlan is control or experimental. This is
not longer truu, and so need to use an attribute in the lan table
entry. 

The last bit of the puzzle is that snmpit has to be careful when
disabling trunking on these ports. When this happens, all vlans are
cleard from the ports (by the device layer), including the Control
network itself, which would make the node unreachable. I had to add
some special cases to watch for that, and return the ports to the
control network.

To turn this on, create a ControlNetVlans and enable it. The mapper
looks for this and passes the -C argument to ptopgen.

Nothing special in the NS file, except you have to turn on vlan
encapsulation; tb-set-vlan-emulation vlan

No delay nodes, but linkdelays work okay. Works for openvz containers
as well.

Probe Cluster. The problem is that the IFB is a shared network that
every node attaches to, which can looks like an ethernet device that
can ifconfig'ed. In other words, one big lan.

But we still want the user to be able to create a lan so that they can
interact with it in thei NS file like any other network.

The NS syntax is:

	set lan2 [$ns make-lan "node1 node2 node3" * 0ms]
	tb-set-switch-fabric $lan2 "infiniband"

The switch fabric tells the backend to do IP assignment for the
specific global network. Yes, I tried to be a little but general
purpose. Lets see how this actually turns out.

This first commit treats the fabric as a single big lan on the same
subnet.

NOTE 1: Since the unroutable IP space is kinda small, but the Probe
Cluster is really big, we can easily run out of bits if we tried to do
assignment on virtual topos. Instead, fabrics get their IP allocation
at swapin time, and the allocations are deleted when the experiment is
swapped out. The rationale is that the number of swapped in
experiments is much much smaller then the number of possible topos
that can be loaded into the DB. Still might run out, but less likely.

The primary impact of above is that IP assignments can change from
one swap to another, but this is easy to deal with if the user is
scripting their experiment; the IP allocation is available via the
XMLRPC interface.

NOTE 2: The current code allocates from a single big network, which
makes it easy for users to mess each other up if they start doing
things by hand. Ultimately, we want each lan in each experinent to use
their own subnet, but that is going to take more work, so lets do it
in the second phase.

The definition of "network fabrics" is in the new network_fabrics
tables. As an example for probe:

	INSERT INTO `network_fabrics` set
		idx=NULL,
		name='ifband',
		created=now(),
		ipalloc=1, ipalloc_onenet=1,
		ipalloc_subnet='192.168.0.0',ipalloc_netmask='255.255.0.0'

'lifetime' structure still ambiguous.

determining the jailosid for "static" images like OPENVZ-STD. For
example:

	tb-set-hardware $n1 d710-vm
	tb-set-node-os $n1 OPENVZ-STD FEDORA15-64-OVZ-STD

The main point is that OPENVZ-STD is a placeholder with no associated
image. It exists to tell the mapper and osload what to do. This is
accomplished with nextosid. The new approach makes things consistent
with subos stuff.