GitLab

interfaces when configuring veth interfaces. Instead, tmcd now returns
actual configuration information for those interfaces, albeit slightly
modified to make it apparent what their role is. See revision 1.232 of
tmcd/tmcd.c for more information.

See initial revision for tbsetup/gentopfile for more details. Note
that a gzipped version of the file is also created by gentopofile, and
we try to get that first to cut down on the amount of data copied over
(the topomap is highly compressable).

Clean up subdir stuff to use the standard -subdir rules.

file derived from the topomap file (see initial log file gentopofile).
Actually, none of the code in this program is new; I just copied out
the guts of dohostnames() from tmcd, and replaced the DB queries with
reads from stdin to get exactly the same data. The idea is that
rc.hostnames on the node will generate the input from the topomap,
feed that into genhostsfile, and feef the output of that into the same
parsing code that is used to red the results from tmcd.

There are also two utility scripts that I used for testing:

	genfromdb pid eid | genhostsfile nodeid
	cat topomap | genfromtopo | genhostsfile nodeid

gentopofile.  Note that the call to "staticroutes -j" is still there
while we transition over; eventually the -j option (which created an
input file for ddijkstra) will be removed, since the client side
rc.routes will generate that file on the remote node using the topomap
generated by gentopofile.

file in the experiment tbdata directory. This topo file is intended to
be used on the node to generate inputs to dijkstra and genhostsfile,
so that routes and /etc/hosts can be generated on the node, rather
then in tmcd, where it creates a huge bottleneck during experiment
startup of very large experiments (many 100s of nodes). This topo file is
slightly more rational then just dumping DB rows like we do from the RPC
server. For example:

	# nodes: vname,links
	lonely,link0:10.1.1.2
	node-1,lan0:10.1.2.2 link0:10.1.1.3
	node-2,lan0:10.1.2.3
	node-3,lan0:10.1.2.4
	# lans: vname,mask,cost
	lan0,255.255.255.0,1
	link0,255.255.255.0,1

Usage: gentopofile [-n] pid eid

The file is written as "topomap" in the current directory.  Use the
-n (impotent) option to dump the topofile to stdout rather writing to
the file.

separately for now. This is in prepratation for computing hosts files
on the nodes instead of in tmcd.

found this regex on a web page someplace.

changes yet, so backing them out. Previous commit message is meaningless.

for physical interfaces underlying veth interfaces; The interfaces are
configured as part of regular ifconfig, rather then as a hack in veth
configuration.

Most of the info return is left blank, especially INET (ip address)
which indicates the special handling.

setting up an emulab in Malaysia.

pounding /user too much (via NFS of course).

(/usr/ports/devel/p5-Time-HiRes) to get higher resolution
gettimeofday() function that reports microseconds and seconds. Change
the output routine to append the microseconds to the original HH:MM:SS
timestamps that get printed.

from os_setup.

Needs to be backed out later.

the pnode rebooted, the file got multiple entries causing the generated
gated config to have syntax errors.

	- increase IP interrupt queue size from 50 to 128
	- turn on magic nfs-permission-denied-avoidance sysctl

the dijkstra program on the linkmap in the tbdata directory, and feed
those results into the pattern match loop as if the results came from
tmcd.

Obviouse problem; if we change the format that is returned from tmcd.

currently I run this all the time regardless of routertype or
use_ipassign flags, since its really quick. Will improve later.