GitLab

server additions, made by Eric, Tim and Jay.

so that it issues exit status via startcmddone. User does not need to
do this, which Eric says is less error prone!

node types - the PCs we're dealing with now are their second batch,
so they're type 'i2' - dunno where the 'i' comes from.

this will fix it ...

files! Commit stuff that was supposed to go in with yesterday's
commit.

Lbs

Soon image when the image is not available (cause the renderer is not
finished yet).

The default thumbsize is now 160, so do not call out to the renderer
to generate the thumb on the showexp page; just take it from the DB.

bigger, and avoids an outcall to render the image from the showexp
page; The actual data sizes of the image are about 2% bigger, which
since the images are typically a few hundred bytes, is not that big of
deal, and with big topos, the smaller images are hard to view.

created in /tmp and left behind. I've moved them to the expwork
directory instead, and added a routine in the library to clear them
out.

Clear out the nsfile (stored in /tmp) used in modify. The web page was
creating a temp file, but never removing it. swapexp now copies the
nsfile in so that the web page can remove the temporary after the
script exits. The temp is placed in the expwork directory as well, but
left behind for debugging.

When swapmod fails, send along the nsfile in the email message.

* A node method to create a startup routine:

	$node start-command "$mydir/batchcmd.sh >& $mydir/b1.log"

* And some old style syntactic pepper:

	tb-set-node-startcommand $nodeb1 "$mydir/batchcmd.sh >& $mydir/b1.log"

The latter is intended to replace the exiting tb-set-node-startup
function. The new implementation of the above is to use a program
object that starts at time 0.

their per-node batch command jobs. Termination of batch jobs does not
happen until all nodes have reported status.

on the Emulab web server.

Some notes:

 1) Public user web directories are now disabled
    - links from above the DocumentRoot to user devel trees must now be used.

 2) Internal access exceptions to production and devel directories are specified
    for the testbed root dir, and inherited by upper directories.
    - Simplifies configuration complextity

 3) External access to system (e.g., / /usr /var, etc) are disallowed now
    - Previously, symlinks could allow access to system directories.
    - Individual exceptions must be introducted when access to a specific
      directory is required.

projects during debugging.

has a bunch of data structure hacking in an attempt to bring some
sanity to the code. Still a long way to go ...

short. Sheesh.

* Parser: Added new tb command to set the name of the sync server:

	tb-set-sync-server <node>

  This initializes the sync_server slot of the experiment entry to the
  *vname* of the node that should run the sync server for that
  experiment. In other words, the sync server is per-experiment, runs
  on a node in the experiment, and the user gets to chose which node
  it runs on.

* tmcd and client side setup. Added new syncserver command which
  returns the name of the syncserver and whether the requesting node
  is the lucky one to run the daemon:

    SYNCSERVER SERVER='nodeG.syncserver.testbed.emulab.net' ISSERVER=1

  The name of the syncserver is written to /var/emulab/boot/syncserver
  on the nodes so that clients can easily figure out where the server
  is.

  Aside: The ready bits are now ignored (no DB accesses are made) for
  virtual nodes; they are forced to use the new sync server.

* New os/syncd directory containing the daemon and the client. The
  daemon is pretty simple. It waits for TCP (and UDP, although that
  path is not complete yet) connections, and reads in a little
  structure that gives the name of the "barrier" to wait for, and an
  optional count of clients in the group (this would be used by the
  "master" who initializes barriers for clients). The socket is saved
  (no reply is made, so the client is blocked) until the count reaches
  zero. Then all clients are released by writting back to the
  sockets, and the sockets are closed. Obviously, the number of
  clients is limited by the numbed of FDs (open sockets), hence the
  need for a UDP variant, but that will take more work.

  The client has a simple command line interface:

    usage: emulab-sync [options]
    -n <name>         Optional barrier name; must be less than 64 bytes long
    -d                Turn on debugging
    -s server         Specify a sync server to connect to
    -p portnum        Specify a port number to connect to
    -i count          Initialize named barrier to count waiters
    -u                Use UDP instead of TCP

    The client figures out the server by looking for the file created
    above by libsetup (/var/emulab/boot/syncserver). If you do not
    specify a barrier "name", it uses an internal default. Yes, the
    server can handle multiple barriers (differently named of course)
    at once (non-overlapping clients obviously).

    Clients can wait before a barrier in "initialized." The count on
    the barrier just goes negative until someone initializes the
    barrier using the -i option, which increments the count by the
    count. Therefore, the master does not have to arrange to get there
    "first." As an example, consider a master and one client:

	nodeA> /usr/local/etc/emulab/emulab-sync -n mybarrier
	nodeB> /usr/local/etc/emulab/emulab-sync -n mybarrier -i 1

    Node A waits until Node B initializes the barrier (gives it a
    count).  The count is the number of *waiters*, not including the
    master. The master is also blocked until all of the waiters have
    checked in.

    I have not made an provision for timeouts or crashed clients. Lets
    see how it goes.

* Change Home page title to: Emulab - Network Emulation Testbed Home

* Change mainsite robot meta tags to include a description, set to the
  same as the new home page title above.

* Remote now sites get standard "noindex" robot directive; crawlers will
  follow links on remote sites but not index them in their search engines.

* Add a fixed link to www.emulab.net/netemu.php3 on all sites; used to
  be on mainsite only; that was dumb!

* Minor cosmetic changes to netemu.php3.

Also, allow cisco switch types to be called 'catalyst', since that is
technically a more correct name (ie. there are non-cat Ciscos.)