Added an optional subnode_of option to both advertisements and requests. Ptopgen now generates the subnode_of relationship in Geni mode.

last commit.

lumping the VLAN number in with the OID, leaving the field we expect
to contain the VLAN number blank. I'm not sure why this happens, but
I've seen it before, and I think that simply dealing with it is going
to be more successful than finding the root cause.

about "mib-2" and some others.  This is defined in SNMPv2-SMI which wasn't
in the list of MIB files and is needed by SNMPv2-MIB.  But, it probably
shouldn't need to be explicitly included, since there is an IMPORT of the
symbols in question at the beginning of SNMPv2-MIB.  But I added it to
the SNMP::addMibFiles() arguments anyway.

This came about because I was messing with PowerNet-MIB.txt to support the
7960 power controllers (we have an 8 year old version of that file).

Change location sitevars to general/default_* rather than protogeni/default_* as these may be more widely applicable than just Protogeni code.

its a delay node.

among all switches in a stack.  Does check to see if the required additional
perl modules are installed and will revert to standard behavior if not there.

Currently only looking up vlan numbers from all the switches in the stack
is actually parallelized; this alone results in a speed up by a factor of 5
on DETER.

Additional speedups could be gained if we assign all the vlan numbers for
vlans in snmpit -t at the time it is run thereby allowing us to
construct different vlans in different switches in an overlapping way.

We haven't implemented this yet on DETER awaiting synchronizing with the
mothership to make use of VLan->setVlanTag().

handle quieting backends in a different way - (to minimized changes
to nortel, foundry, and hp support), use perl "select" with one arg
to change default for "print" with no explicit fileglob.

print STDERR, STDOUT, still works; won't interfere with tblog() and friends.
will put parallization mods in a separate CVS change.

Clean up a couple of minor inconsistancies in the modules concerning
printing ports not in the wires table and make sure utterances like
"wap snmpit -i Nortel10 4/4" work properly.

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.

Changed flag output to attributes in ptop case to conform with Tarun's changes from a few months ago.

will get worked out better after the latest checkpoint :-).

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.

If in geni mode, do not print links from widearea nodes to the 'internet'. These will be printed based on interfaceroles anyhow.

ptopgen now emits 'role="experimental"' on interfaces. rspec-ad.rnc will now accept such advertisements.

The 'internet' node is defined and has a single interface called 'border' and is marked by the '<cloud />' element. All control interfaces with publicly routable IP addresses (not in one of the three private IP spaces) have a link to the 'internet'. Those interfaces now also contain a 'public_ipv4' attribute which contains their address. The modified schema validates this.

ptopgen now emits 'role="control"' on each control interface definition. The rspec now validates against it.

want to do.

virtual topology, get tickets, redeem tickets, map onto Emulab nodes.
Work in progress!

that the \w character class includes digits, and that regexps are (by
default) greedy from left to right...

Added a '-1' option which can be used to get the rspec of a single node. Note that this doesn't attempt to optimize away any database lookups.

This broke control net firewalls.

Make my best guess attempt at what the code should do; i.e., there are still
cases where we probably shouldn't allow such command lines.

that contain ports in the new VLAN: we might need to transit switches
'in the middle'.

I'm starting to think that the way we built up list of switches for
the commands is not the right thing to be doing - almost all of the
operations operate on whole stacks now, so we just have extra work to
do to convert stack names into switch names and back. Or, at the very
least, we need  a simpler way to compute (and store) the set of
switches that a VLAN has to transit.

'tables', 'reset', and 'synctables' commands. Rather than assuming all
VLANs live on the One True Experimental Net Stack (unless -S was given),
they all now check the database to see which stack they should be operating
on.

Changed how stack information is currently stored in the database. The
LAN attribute formerly known as 'stack' is now called 'class', and has
two valid values, 'Experimental' and 'Control'. The idea is to record
whether something is an experimental net or control net LAN, not which
specific stack it's on. The 'stack' column in the VLANs table now
records the actual stack_id on which the VLAN has been created.

This is all in support of testbeds that have multiple experimental-net
stacks, as Utah currently does.

have that information in the widearea_nodeinfo table.

found in the database, use the stack recorded there.

stack unless no ports are given. This allows it to be used on other
stacks without passing the -S option. There are probably other commands
that should get this treatment, but being conservative for now.

Also improved the debugging output from commands that complain about
multiple stacks.