GitLab

Quite simple actually. In ptopgen we add all persistent stores, which
are identified by having a non-zero lease_idx. To ensure they are only
matched up with the correct virt_blockstore, we add a feature "bs-lease-NN"
where NN is the unique lease index with weight 1.0.

In vtopgen, when a request is made to map a persistent store, we first
verify that the experiment pid matches that of the blockstore's lease
(this is a fer-now simple check which is actually redundant as we make
this check in the parser too) and ensure that the blockstore is not already
mapped (indicated by the blockstore_state entry having size==0) and then
we emit an entry with desire "bs-lease-NN" and weight 1.0.

Most of the file changes were actually to get the "preassign" flag to
vtopgen forwarded into the various libvtop modules so that I can check it
and not perform the permission/size check if it is set.

Also, multiple ports on the same contact node will now be consolidated into one stitch:node tag with multiple stitch:port children.

On shared nodes, look for the 'xen-host' or 'openvz-host' osfeatures when
determining sliver types.

dom0mem setting for the node, since that varies and reduces the
amount of guest memory available.

Utah has rewired some of the its pc3000s to a procurve, which supports
vlans > 1024. Since we do not have link features and desires, we need
to trick assign by using a different link type on the wire, in both
the ptop and vtop. The vtop looks for a vlan reserved tag greater then
1024, and changes the linktype to ethernet-highvlan. In ptopgen we
look for an attribute on the switch that says it can do highvlans, and
add that linktype for any wire attached it.

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

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.