GitLab

need to get setup and should not be messed with.

That's where the GPO want UUIDs to go.  (And it's where we put them now,
though we didn't before.)  We still look for UUIDs in other places, because
we're not ready to break backward compatibility with old certificates yet.

This is necessary to comply with GENI AM API v3.

This is necessary to comply with GENI AM API v3.

(just like we do when using shared nodes).

last vlan since on a procurve, a port has to be in *some* vlan.
So, when down to the last one, add it to the default vlan and
then do the removal. This comes up in syncVlansFromTables only.

with shared vlans, using the reserved table in a join does not
get the ones we need.

If debugging is on, this will be evident based on the debugging messages...

NOTE: currently only for FreeBSD 7.3 installs because that is the only
set of boss/ops/fs packages I have built so far!

This mostly involved minor changes to event agents. Too often we were
passing a pointer to a "long" to *get_int32, which on a 64-bit x86 OS would
fill the wrong half of a 64-bit variable. There was also one instance of
TCL code that had to be tweaked to account for 32- vs 64-bit.

These changes also required regeneration of SWIG stubs and an ugly change
to the SWIG generated code to use va_copy rather than direct assignment in
a couple of places.

Also related to SWIG is ensuring that the components that go into the
perl/python stub .so files are built with PIC. The amd64 linker requires
this.

The meta-ports had to be changed to reflect that linuxthreads and
ulsshxmlrpcpp don't work on amd64. The former had little effect as we
had mostly eliminated uses of linuxthreads already. The one thing that
did change was that we do not build nfstrace on amd64 (and we don't
currently use this anyway). Removing ulsshxmlrpcpp required switching
to the new event scheduler (event/new_sched) that Ryan did awhile back.
Note that it is only "new" in the sense that it uses a standard XMLRPC
package, there should be no functional differences. However, to be safe
we only use new_sched as the standard scheduler on 64-bit server installs.

Finally, added support to elabinelab setup to do a 64-bit server install.
Just specify FBSD73-64-STD as the boss/ops/fs osid and rc.mkelab should
do the rest.

That is pretty much it other than some random nits here and there.

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'

missing.

Fix a weird problem where the failure to start up the "crude" listener
got reflected as a failure of the latency test. This was happening on
Fedora 15 because we could not run crude at elevated priority.

Part of the fix is to wait a second after starting a listener and then
make sure it is running. In the case of such an early failure of "crude",
we then try again without elevated priority.

Now accept a range of addresses from first-last, instead of base+mask.
That way, arbitrary ranges can be speficied (address blocks are no
longer limited to aligned powers of two).

We were using "short" and "int" in the data struct passed between client
and server. Note that we still need to address the big/little endian thing.

Hardwire the sort type for a few columns that cause guessType grief.

Remove the insertion of blank-rows-as-spacers in a table. They don't
sort well. Leigh got rid of most of these a while back.

The former ensures that we get the same behavior as when the same
sorted output is produced using "order by" in mysql. I added a
sortable_alpha_cs that we can use for a column should we discover
a case where we really want a case-sensitive sort.

The latter ensures that a user can at least manually do a multi-column
sort (e.g., the equiv of "order by state,eid" when displaying experiments
by clicking on the eid column and then on the state column).

This is needed due to the odd way in which we use sorttable.
In normal use, sorttable.init would be called via the DOMContentLoaded
event hook and this would invoke makeSortable() to do the DOM magic
necessary to ensure all tables marked sortable are make sortable.

But due to our use of AJAX-y dynamic content loading, this won't work
(or so I am told!) So we generate our own call to makeSortable(mytable)
when we produce any sortable table "mytable". But if init() has not been
called before that first call to makeSortable, the DATE_RE regex will
not be initialized and strange things happen in guessType and consequently,
in the sort functions themselves.