GitLab

- removed unneeded code

  Adjustment done with a state machine, described below. Time timeout on
  'fping' is proportional to the desired testing rate while in this
  "outage mode".

- Bugfixes for running in an E-lab exp


state transitions
CurrentState   Input                 NextState
----------------------------------------------
normal         gotErr&PrevSucc       highFreq
               else                  normal
highFreq       <60sec&ERR            highFreq
               >60sec&ERR            medFreq
               SUCCESS               outageEnd
medFreq        <10min&ERR            medFreq
               >10min&ERR            lowFreq
               SUCCESS               outageEnd
lowFreq        ERR                   lowFreq
               SUCCESS               outageEnd
outageEnd      <120sec&SUCCESS       outageEnd
               >120sec&SUCCESS       normal
               ERR                   highFreq

* New version of template_record just for ops, since so much is
  different about ops, not bothering to maintain a single version.

* Various fixes to how the recorded events are stored and reconstituted.
  The big fix is to wrap them in a sequence to that they get fired
  properly (waiting for completion of previous event in recording).

* New buttons to Pause and Continue event time, which is used when
  adding recorded events. This allows users to pause time while they
  "think" so when an event is recorded, the thinking time is not actually
  in the timeline. Eventually hope to figure this out automatically, but
  that will take some real, uh, thinking.

* Add a new event editor (linked off the template page) that allows
  you to delete and change the recordings. Note that you can only edit
  the events at the template level; you cannot edit the events of an
  instance (swapped in experiment), and you can only edit the recorded
  events, not any other events. Not sure its useful to be able to do
  either of these yet, but probably not too hard to add at some point.

commit logs in tbsetup for more info.

error.

timestamp of the packet that made us realize we missed them.

This fixes the last error from my washington->oregon trace.

When we detect that we've lost packets in libpcap, compensate by
making some dummy packets to cover the sequence range we missed. Use
a constant to guess how much header we missed. Only flag missed
packets as errors if we miss a lot of them.

Allow for ACKs of partial packets - this is important with the above,
since the fake packets can be larger than the real packets that we
missed.

Mark SACKed packets so we can avoid double-counting them - future
SACKs or ACKs can cover those packets, but, in fact, are not really
ACKing them.

Most of the time spent working on this was dealing with STL semantics.
The more I use the STL, the less respect I have for it.

Added a limit of the maximum number of samples used by LeastSquaresThroughput for slope calculation. Throughput calculation still uses the previous metrics.

problem, which is that swapmod messes up the env that the template
code has carefully setup.

with the old monitor.  Backward compat be damned!

Added debugging information so that it is more clear what port the control server is using on the stub.

think the problem is that the archive is forked for a template
instance, but not committed before the first savepoint. This screws up
the archive cause the datastore directory has not been copied in yet,
and subversion pukes.

kludgy code in template_exprun that tries to ignore dead nodes during
start and stop run.

Rolled the AverageThroughputSensor into a special case of LeastSquaresThroughput. It still uses the same command line arguments/constants.

Bump plab rootball version.

Create event sequences to do the equiv. of start- and stop-experiment.
Rather than using those scripts, you now can use start-run and stop-run
which are just wrappers around tevc to trigger the sequences.

This checking is backward compatible in the sense that you can continue to
use start- and stop-experiment and should never notice a thing.

The new event model doesn't support a couple of things that the old script
based execution did, most notably, you cannot change command line arguments.
It does support real vs. fake runs.

script sticks around so the program agent has something to kill!

will not timeout in the dispatch routine.  It apparently will stay
in recvfrom() til it gets a packet.  This caused stop/snapshot events
(as well as "kill -TERM") to not do anything.

So we blast all the pthreads out of recvfrom with a signal after setting
the flag to force them to return from dispatch (pcap_breakloop).