GitLab

appears as a box on the show template page, with a mandatory confirm
checkbox right next to it.

greater the 512K is automatically compressed with gzip. Might need to
make this number bigger; we shall see.

If you run emacs, put this in your .emacs file.

	(load "jka-compr")
	(jka-compr-install)

and any time you visit a file that ends in one of the standard compression
extensions, emacs will automatically do the uncompress for you on the data
in the buffer (not the actual disk file of course). Very convenient.

You can also get your browser to do the same, but I leave that as an
exercise for the reader.

Two-day boondoggle to support "/scratch", an optional large, shared filesystem
for users.  To do this, I needed to find all the instances where /proj is used
and behave accordingly.  The boondoggle part was the decision to gather up all
the hardwired instances of shared directory names ("/proj", "/users", etc.)
so that they are set in a common place (via unexposed configure variables).
This is a boondoggle because:

1. I didn't change the client-side scripts.  They need a different mechanism
   (e.g., tmcd) to get the info, configure is the wrong way.

2. Even if I had done #1 it is likely--no, certain--that something would
   fail if you tried to rename "/proj" to be "/mike".  These names are just
   too ingrained.

3. We may not even use "/scratch" as it turns out.

Note, I also didn't fix any of the .html documentation.  Anyway, it is done.
To maintain my illusion in the future you should:

1. Have perl scripts include "use libtestbed" and use the defined PROJRO...

not swapped in (equiv of plain experiment preload), and then swapped
in later. This fulfills flyspray request FS#100.

condition.

trying to start two runs at a times. Nothing special, only one
operation at a time.

(initial) parameters for a new run. Three choices right now; from the
template itself, from the instance, or from the previous run. On the
web interface this is presented as three buttons. On ops, it is the
the -y option, which takes one of template,instance,lastrun as its
argument (you can of course combine the -y option with an XML file to
override specific params).

At present, there is no default. Lets give it a chance to sink in
before I pick something that will annoy 50% of the people 75% of the
time.

Change the way vnode_setup handles plab nodes a bit to avoid a couple of
buggy situations.

  * Don't try vnodesetup -h on plab nodes

This can hang, or even fail.  Since nothing useful is conveyed by this
step, just skip it, set the node's state to SHUTDOWN, and ask pl_conf
on the node to remove the vserver.

  * Set plab node's alloc state to TBDB_ALLOCSTATE_RES_INIT_DIRTY after
    instantiation.

This avoids a bug where Emulab cluster nodes fail to come up, and so
os_setup never waits on the plab vnodes (now that they are started in
parallel with physical node setup).  Previously their alloc state made
them look clean, and so the vservers would not be reaped during
teardown.

time a run starts. This info is stored in the DB forever, but a file
in the archive is a nice thing too.

instance being replayed, not the template itself.

stuff).

tblog code.

* 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.

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

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.

getting deleted.

* Copy template datastore to instance "datastore" directory, instead of
  "template_datastore" ... avoid mass confusion.

* Change xxx:// mappping from template datastore to the instance datastore.

has two problems:

 * not all LANs might be shaped so there may not be a delay-agent running
   to receive and acknowledge the RESET event, leading to a hang

 * we might wind up resetting a delay node more than once (once for each
   lan it is responsible for); probably not harmful, but might lead to
   again not sending a completion event and a hang.

As long as I can reset the one LAN I care about, or rather all its involved
delay nodes, I should be fine.

inserted for regular experiments as well as template instances.

* Create a per-experiment DB user for the per-experiment DB; the user
  name is equal to the DB name.

* Add a dpdbpassword field to the experiments table; this is the
  randomly generated password for the DB user mentioned above.

* For Templates, use the above user/password in the environment,
  instead of the swapper uid/password.

* Add experiment dbname/dbpassword to the Show Experiment page.