GitLab

clients so they can create a proper .forward file. 2) Add some
test code for seeing how feasible it is to do accounts on ops/tips
using tmcd instead of direct ssh. Initial results are not good; too
many accounts; does not scale well. Going to need a smarter protocol
for doing hundreds of accounts, but I will leave this code in place
for now. Note, unlike testbed nodes, control nodes must connect with
ssl.

Add better timeout handling code to tmcc, which watches for progress
instead of just dumping after the timeout. This lets really slow
connections proceed okay, but still timeout out if nothing happens at
all.

This new tmcc has been installed into the sup trees for WIDE and RON.

bunch of jail changes. No matter, no one should be installing any of
this stuff to make a new image until I give the okay.

own script. It was just clutter in that library. Kill delay_update
since its not really used anymore, but give a delaysetup a -u option
to do that, just in case.

but eventually did not use it. Current images still make a call to it
from libsetup but will get an empty string that doesn't affect anything.

created by libsetup are now created in /var/emulab/boot; nothing is
written into /etc/emulab or /usr/local/etc/emulab anymore. This was
a requirement for jails, but is also a good thing to do anyway.
There are a number of jail config changes to support the old vnodes
and the new style jail vnodes; specifically, a setup routine to called
from inside the jail when it first boots up to the get the usual
assortmant of config info from tmcd. Also Merge local and remote
update routines into one. Other various little changes for SFS and the
MFS.

use perl dbm code.

destination was the same as hop. We don't need this since staticroutes
never puts such a route into the DB

  - Fixes the routing problem
  - A new type "sim" has been created but not in the DB. node_types and
    nodes remain unchanged. This will change after we figure out how
    to represent in the DB the local multiple virtnodes in one phynode case
    The frontend tb_compat.tcl adds the sim type and ptopgen associates
    a huge number of sim nodes to all local PCs.
  - All simulated nodes go into one pc untill I finish coding the distributed
    nse case. Also, sim nodes go through assign but with an explicit
    "fix-node" directive in the top file. A random free pc is chosen using
    the avail script in assign_wrapper. If we don't fix node it, assign
    maps sim nodes to multiple phy nodes even when a valid all to one
    mapping is possible.
  - Syntax for nse:

   $ns make-simulated {

       set simnode1 [$ns node]
       set simnode2 [$ns node]

   }
   ...

   The old syntax

   set nsenode [$ns nsenode]
   $nsenode make-simulated {
   }

   is deprecated

  - All 38 frontend tests in the testsuite pass

  - A new table v2pmap has been added to handle multiple virt nodes to
    one phy node mapping. This is used in "tmcc hostnames" currently.

  - The phy node that is picked to run nse is loaded with a custom image
    FBSD45-NSE . This can use the default FBSD kernel if there is a mechanism
    to run at 1000HZ, have options IPFIREWALL_FORWARD and PERFMON turned on.
    The image is in the 'testbed' group. Do not delete this image.

  - Static routes now adds routes for the case dst == nexthop. The routing
    graph would be disconnected otherwise and I need to traverse this in
    assign_wrapper for nse. On the client side, such a route is filtered out in
    libsetup.pm

  - sim nodes are also correctly visualized

jailed environments.
Fix up sfs stuff so that warnings and errors from sfskey do not
get printed out on the console.
Add a jailedsetup stub for testing with jails; work in progress.

rc.ifc uses it unconditionally so it needs to exist.

on the RON nodes and in the new widearea image.

files.

scope was inadvartently reduced to the if block instead of the entire
dotrafficconfig() function. This caused nse not to start up automatically

client software to widearea nodes. Most of these changes were to
reduce the embarrassment factor. At some point we need a proper
autoconf and such, but for now there is a makefile in the src dir for
creating the distribution.

I've tested it on a local linux node and mostly on a freebsd node, but
I've moved things around and so updating the RON nodes will require
some hand intervention by me at some point.

* Add ability to control timeout when invoking tmcc, and whether to
  fatally die if tmcc fails. Related change was to allow more options
  to be passed into tmcc by way of an additional options argument.

* Change to pubkey handling. tmcd now returns a list of pubkeys for
  each login. The entire list is written to the authkeys files, and
  the old is backed up (with mod time preserved).

* tmcd now returns a serial number for each use to indicate when
  user info has changed (via the web pages). Only users with updated
  serial numbers get modified (and new authkeys file created). This
  should vastly reduce the passwd/authkeys churning on the ron nodes,
  which periodically check for account updates. The little db file now
  records the serial number too.

* Change to os_usermod; Change the actual password string! Was not
  doing that before.

* Conditionalize all the tmcc.foo stuff that Shashi added; don't want
  any of this on remote nodes yet.

* Remove a bunch of printfs to reduce output clutter.

files are generated.

with cvsup.

in /etc/testbed for use by NSE

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.

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

1) Merge in the accounts code that I did for ron. Instead of resetting
   the password file on each reboot, look at the node status to
   determine if the password/group file should be reset. If the
   node is free, reset it. Otherwise, we track changes to the password
   and group file now, so that users can change it and not have their
   changes wiped out at each reboot. I had to do this for the ron
   nodes so that the testbed software would not alter or delete
   already existing accounts; I keep a couple of little dbm files
   listing all the accounts/groups added. The only downside right now
   is if a node is reallocated before it is wiped clean; I plan to add
   an os_teardown phase to experiment termination asap.

2) Add tunnels support. New DB table (tunnels) provides information
   for running vtund to link up to remote nodes. Creates a vtund.conf
   file on the fly, and fires them off. The complication is that you
   cannot do the ifconfigs or the routes until the tunnels are
   connected, so that stuff has to be configured within the vtund.conf
   file on a per tunnel basis. vtund.conf has some sections for
   running commands when tunnels are brought up or down.

3) Damage the routing configuration code that Mike did. To support
   tunnels, as noted above, rc,route is no longer a simple list of
   commands, but a program that adds/dels routes based on the netmask,
   with a special "enable" section for the other stuff. This allows me
   to call it from vtund.conf for up/down on each tunnel'ed
   interfaces, as needed. Quite gross, but no way around it.

4) For remote nodes, add a vnodesetup script, invoked from boss when
   experiments are setup/torndown. This gets the tunnel/route/trafgen
   configuration and runs them. It then goes into the background
   waiting for a death signal, at which time it brings them down and
   cleans out the vnode state.

Removed rc.route script which is now generated automatically by libsetup
doroutingconfig code.

Random: removed some unused variables from freebsd/liblocsetup
(IFACE, CTLIFACENUM, CTLIFACE) which collectively hardwired the control net,
probably haven't been used in a while.

file in /etc/testbed, and if there such a file, take a different path
through the setup code that is a lot shorter (mounts, accounts,
startupcmd).  All the other stuff is bypassed. There are no
differences though between what you install on the MFS and what you
install on a regular node.  Just run the mfs-install target instead,
which creates the little ismfs file for you.

addr/port.

currently installed tmcd. The version number is passed through on
every tmcc request.