GitLab

of all widearea nodes are now pcvwa/pcvwa, pcvron,pcvron, etc. The
last mile type (pcvroninet, pcwainet) comes from the aux types for the
node.

says to include widearea physnodes, with the types set to those listed
in the node_auxtypes table. Those types will include the last mile
types that a vnode on a pnode can take on. The :count value for the
types is set to the min of the number of *free* vnodes on the pnode,
and the virtnode_capacity in the node_types table. Obviously, if all
the vnodes are allocated, the physnode will not appear in the ptop
file. For plab, virtnode_capacity will get set to one in the
node_types table, thereby preventing "revisitation" of a plab physnode
in an experiment.

swapping.

This is primarily for the "queue an interactive job" form of batching,
but applies to all batch jobs at the moment.

This is primarily for the "queue an interactive job" form of batching,
but applies to all batch jobs at the moment.

dslice re-deployment.

creating the log directory for mysql, which needs to have the correct
permissions.

the types table yesterday, and it is hardwired here. Yuck.

naming scheme that ends in -A, where A is a letter, not a number.

footprint as it runs. All the credit for this one goes to Tim!

node_types table. This should make it easier to assign last mile
types to widearea nodes since a given type can now have as many
subtypes as you like.

Also add cpu_usage and mem_usage to the experiments table. The
user will be able to specify these in the NS file. Currently a
tinyint, where the default is zero, which means ignore.

to avoid hup-me-and-i-will-screw-ya mountd/NFS bug.

Use new -t option (use tmcd) in jails/plab

add -c option to force copying file over locally before untaring,
the copy code knows how to retry read operations that fail

stolen from Leigh's 'ixptest' experiment.

to do the fake links that were our old workaround.

that should be associated with a node when it is put into the ptop
file.

pnode's types were a subset of another's.

verification steps.

as an admin if you go to a users moduserinfo page. I'll be using this
to flag accounts frozen due to email problems.

to not be so (specifically, to support layer 2 and IPv6)

assign what it's a subnode of. Also, if a subnode's parent is not
going to be included in the ptop file, don't include the subnode
either.

Also, re-structure the part in which we generate the 'node' line to
make it cleaner, since it's gotten more complex than that code
originally intended.

{p,v}node object. This way, the parent node doesn't have to be listed
before the child. Wh

I could do this to links too, but it seems to have less of a payoff -
it's easy enough to just do all the nodes, then all the links.

spaces.

execing the program. We had a problem with daemons that detach and
continue to run, holding open all of the same FDs that the web server
had open, including the httpd socket! So it was not possible to
restart the web server cause processes were parked on the socket
holding it open.

I think this is the wrong place for this since there numerous ways to
run programs from the web server, and using suexec is optional (can
just run programs directly). Seems like a problem with php instead,
but the fix is here cause it will solve the problem for us.

top and ptop files, you can put
subnode_of:nodename
Any vnode that is a subnode must be mapped to a pnode that is a a
subnode of the pnode the vnode's parent is mapped to. Read that a few
times slowly, I swear it makes sense.

-I switch now bypasses checks to only run on interfaces that have an
IP addres.

address of the interface instead of the dest&mask, which was bogus
anyway, and now wrong in the presence of variable netmasks for the
destination.

changes; Print a warning when the DB slots are null, and return
standard 255.255.255.0. This is for the transition phase.

Also add version 12 modification to routerconfig; return the "src"
from the virt_routes table, so that the client side can figure out
what interface the route is associated with. There are associated
changes in libsetup to ifconfig,routerconfig,tunnelconfig.

file - if set, it means that the vnode is not allowed to have a
mix of trivial and 'real' links - all must be one type or the other.

your NS file:

	tb-set-netmask $lan0  "255.255.240.0"
	tb-set-netmask $link0 "255.255.255.248"
	tb-set-netmask $link1 "255.255.255.240"

Yep, more rope for the user to hang herself with. Notes:

* You are restricted to 255.255.XXX.XXX. I did not see a reason to
  allow the user that much rope.

* get_subnet can handle 10 or 192.168 addresses so that other sites
  can continue to operate without changing to 10 addresses, although
  they will still be able to change the netmask.

* I've changed the handling for widearea networks to use 192.168, but
  I force the netmask to 255.255.255.248 so that we are not restricted
  to just 255 networks (not that it really matters). To avoid possible
  confusion, the user is not allowed to choose their own IPs for
  widearea networks, and I actually set them to 1.1.x.x, and then
  patch it up later. This is to avoid conflict with existing
  experiments where people may have used tb-set-ip in their NS files.

* There are tmcd and staticroutes and image changes that are required
  to make this all work right!

configure.in.