GitLab

email on the first failed attempt!

failure, and that the state of the experiment is set back to NEW. Also
some minor print and email formatting changes to be more informational
when things go wrong.

experiment code. No longer uses another table. Rather, the experiment
record contains a couple of extra fields for the batch system. Also
combined some of the backend code (no longer a killbatch script).
Also added scriptable experiments; the batchexp program in the bin
directory can start an experiment from the command line, and in fact
is used from the web page for both batch experiments and immediate
experiments (-i option). All of the DB code that was in the web
interfaces was moved to batchexp.

that Mike reported.

that Mike reported.

/proj/<proj>/tiplogs/<exp>/ . If set, virutal node name are used for the
destination filename.

Run by batch_daemon on experiment termination, and also available to users
(through paperbag/plasticwrap) any time during an experiment.

and send proper email status.

degree of bit rot. Updated the create batch web page to do
local/remote NS file spec. Switched to libdb interface in the batch
mode scripts. Removed estimated pc/shark slots since we don't support
that anymore, and because the new parser returns proper exit status
when not enough nodes are available. The DB will be updated at that
point, and we can incorporate that info (have not done so yet).
Incorporated node boot status into isexpdone(), since a failed node
will never report startcommand exit status. Clean up email code so
that email goes to user/tblogs/tbops in the proper situations.

can run it from a development tree.

proper headers. Split out some of the mail into testbed-logs,
testbed-ops, and testbed-approval. Added a library for including from
our perl scripts. Contains a couple of mail helper functions, but will
hopefully contain more as time goes by.

Fixed a bug in the web interface that was causing breakage for people
with multiple accounts. Mac and Jay have noticed this, when logging
out and trying to join or create a project under a new or different
name.

every now and then. Also change the way experiments are selected to
be configured. Instead of trying to start the same experiment over and
over every 15 seconds, use a select to pick out experiments that have
not been tried within the last 10 minutes. This will favor brand new
experiments the first time, but after that all failed experiments are
treated the same. The least recently attempted experiment over 10
minutes is selected next.

global unless declared local! Silly. Perl ain't a language!