GitLab

frisbee won't suck up for buffering).  Also check the kernel limit for
maximum datasize and take that into account.  (Related to this: I have
changed the frisbee MFS loader.conf file to set kern.maxdsiz=2000000000)

  SFS.

* Do not send SSH pubkeys to local nodes; the data is never used on
  local nodes, but along with SFS keys, comprises about 85% of the
  data we send back in the accounts request.

admin people allowed. Comment from script:

# * Initially we come in with just a nodeid. Display a page of little maps
#   and titles the user must select (a floor in a building) from. User clicks.
# * Next time through we have a building and floor defined in addition to the
#   the nodeid. We put up that big image with the current nodes on that floor.
#   We use the external floormap program to generate that image, but without
#   an imagemap. Instead, we use a form with an input type=image, which acts
#   as a big submit button; when the user clicks in the image, the browser
#   submits the form, but with the x,y coords added as form arguments.
# * We get all of the above arguments on the final click, including x,y. Verify
#   all the aguments, and then do the insert.
# * If user goes to reset the node location, form includes an additional submit
#   button that says to use the old coords. This allows us to change the contact
#   info for a node without actually changing the location.

Caveats:

* We do not describe buildings in the DB, and so we are currently hardwired
  to MEB for the building, and the images for each floor are still
  hardwired in the external script (vis/floormap.in) that creates the
  image. Needs to be dealt with before we can export this stuff.

* There is no way web interface to delete a location entry. That should be
  easy to deal with when needed, but in the meantime:

	delete from location_info where node_id='pcXXX'

* All nodes get a "Set Location Entry" on the shownode page menu; I leave
  it to admin people to not set the location for a non-wireless node; will
  fix later as needed.

* Coordinates are all in pixels. As Russ points out, this is (way) less
  then ideal, but certainly simple.

the fly, or use heigh/width specs in the img tag, but I hate how the
browser scales things. Short term solution; obviously does not scale
to more then a few floor images.

otherwise the file is created as that user, and is then difficult to
remove in floormap_aux.php3 after it is dished out. There is no reason
to run the external script as the user; all it does is build an image.

cached version.

passing this to the newnode client, web page, and viewing and
editing it.

we can use it for a partition number

of my really icky code to start different kinds of servers; basically
you can set the number of servers of each kind, and if a server of
that type exits, another one of the same type is started. The code is
a little easier to follow then it was before, but still quite yucky.

So whats the "right" way? The problem is that if multiple children are
selecting on a set of fd's and an fd comes ready, all of the children
are woken up. This is called a "select storm" since they all wake up,
try to read from the same fd, and all but one go right back to sleep.
Lots of overhead, and programs like apache go to great lengths to
avoid it. Takes a lot code, lots of bookkeeping, lots of goo that is
hard to understand 6 months later. Not worth it for tmcd, at least not
yet. If we start creating many 1000s node experiments, that could
change in a hurry.

format instead of plain old well formed XML. Note this change does not
affect the parser in any way; the parser continues to spit out its own
brand of XML, and xmlconvert treats that special when it reads it.

The XML I spit out now is better formed and makes more sense when you
look at it. It also helps that its much faster to generate, and the
resulting output is much smaller. For example:

	time /usr/testbed/libexec/xmlconvert testbed jail-2440
	real    2m54.229s
	user    1m7.492s
	sys     1m15.927s

	time /usr/testbed/devel/stoller/libexec/xmlconvert testbed jail-2440
	real    0m14.738s
	user    0m5.755s
	sys     0m5.156s

	/tmp/bar*.xml
	-rw-rw-r--  1 stoller  wheel  15595161 Jun  4 11:16 /tmp/rpc.xml
	-rw-rw-r--  1 stoller  wheel   5285690 Jun  4 11:17 /tmp/plain.xml

Thats for a big experiment. For a small experiment:

	time /usr/testbed/libexec/xmlconvert testbed jail-416
	real    0m9.346s
	user    0m5.083s
	sys     0m2.675s

	tim...

wireless.

Parse the ptop file to get information like colocation factors, CPU
speeds, trivial bandwidth, and the like, instead of hard coding them.

Keep features and trivial bandwidth by type (ie. pcvm, pcvm850),
instead of making them the same for all types. This should make
much better conglomeration choices.

 allow boot from partitions other than 1
 allow "-new" versions of freebsd/frisbee MFS

line so that we can see the timestamp in it.

graphviz support seems to be broken in at least some versions of
boost with some versions of gcc .

This mostly required messing with the STL #includes.

Still builds under gcc 2.95, and won't be built with 3.3 by default
until I've spent more time testing it.

One reason for doing this is that gcc 3.3 seems to generate faster
code from templated functions. Tests so far show that the
gcc3-compiled binary shaves 15-30% off of assign's runtime.

The other reason for doing this is forward-looking. When we end up
getting boss running on FreeBSD 5 or a recent Linux distro, the
compiler is likely to be from the gcc 3 branch.

/proj right away so that booting nodes see the current copy, not a
stale one (or none at all).

under-counted.

time it successfully mounts a filesystem.  Since we mount about 80 gazillion
filesystems in jails and these mounts are overlapped with other parts of the
setup process, it is quite likely that some jail's innocent use of
/usr/bin/foo is going to be blown out of the water by a random senseless HUP.

Grisly hack: when setting up jails, rename mountd.pid so mount can't find it.
Hah! hup THIS mount!

work on regular, (as opposed to trivial) links too.

that two identical topologies always produce identical topofiles.

and in jails especially.

These get redirected to a file nowadays, so they shouldn't cause problems.