GitLab

Whee!

- Halved penalty for overshooting bandwidth (undershooting remains the same.)
- Added penalty argument to -m for assessing multiplexing penalties.
- Made a few optimizations.

Small change for expts in TBOPSPID (emulab-ops for us): Instead of vname (which isn't usually defined), show when it was reserved to the expt. Great for checking on reloading nodes, hwdown nodes, etc.

if it fails, we exit gracefully from the node setup instead of
screwing stuff up even worse. Basically, I converted all close($TM) to
CLOSETMCC($TM) which does the proper checks and dies if error.
This is probably not ideal either, but not really sure what the ideal
solution is when tmcc fails.

So, the length of time is set in the .cnf file when signing a cert
with the CA. However, the length of time the CA is good for is not set
in the .cnf file (the entry is ignored). Rather, it has to be on the
command line. So, the certs really were good for 3 years; it was the
CA that had expired, and once that happens the certs are no longer any
good. Very bogus.

for a node, we start up NSE, even if no FullTcp traffic generators
are configured for the node

nodes that get moved to the reload pending experiment.  Without it,
tmcd won't free them from the reloading experiment.

Second, fix the case of freeing from the reloading or reloadpending
experiments.  The old code would get nodes stuck in their holding
experiment.

daemon take care of it.

- Changed internal representation to accommodate >1 vnodes per pnode.

- Added '-m' option to allow the user to specify
the maximum number of vnodes mappable onto each pnode.
(if -m is not specified, only one vnode is allowed per pnode)

- Added ability to "fix" a permanent mapping from a vnode to a pnode.
When specifying a vnode name, use the name of a pnode, with a "*"
prepended. This will be useful to fix one node as "The Testbed Node."

See comments at beginning of source for full documentation.

last_reservation, and letting the reload daemon pick it up from there,
we schedule a reload and stick it directly into the reloadpending
experiment. The effect of this is that the node never ends up in
the free pool before getting reloaded.

(Note: We _don't_ do this if the node is being freed from the reloading
or reloadpeding experiment)

This change may not be permanent.

(/etc/rc.d/testbed/slothd rather than /etc/testbed/slothd)

For consistency's sake.

Slothd changes to force an initial wait of <interval> (def 1hr).  Selectable
with -w.  Also changed to scan ALL ttys by default (can use UTMP with -a).

Finally, deploy script changed a bit to be more robust wrt down nodes.

Jay's request. Its all I can handle before coffee.

more daemons and tcp connections ...

(the base experiment). Also do the proper calculation when inserting
into virt_lans for delay and plr, which is different then when
updating the delays table directly. Change from using ssh to using the
event system to make the change on the node.

were introduced.

Look at comment at beginning of wanlinksolve.cc for full documentation.

Also added -v switch to turn on verbosity (now off by default.)

too much CPU

of just pinging it, poll its eventstate in the database, and wait
until it's reported ISUP. This way, we don't report that a node is
ready before it really is. Also bumped up the timeout by a couple of
minutes to account for the extra time it takes for the OS to boot.

Right now, if the OS is considered pingable, we assume that it will
report ISUP. In the future, however, when the node state is more
formalized, we will have better ways of determining this.