that jails do.  sshtb can now handle vnodeid's, and must be given a
vnodeid if it's a Plab node, because the username will differ
depending on this.

really working this time.

I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite
I will not check things in without running the testsuite

I was getting the IP from the hostname, so I switched to the trick
we use on the testbed nodes; use /etc/dhclient-exit-hooks to write
the data into /var/run, and use that in register.sh when the IP=DHCP.

use CONFDIR will work properly. Not tested yet ...

configing the file.

grab that from the bossname using tmcc (be nice if bsd/linux had a
consistent way to get the domainname).

forget to do them all!

the project is different. This is not supposed to happen, but does
when reloading. Sigh.

are necessary to run the Planetlab manager.

service manager and resource broker that works closely with the
control flow through the Emulab experiment swap process.  It keeps all
slice and node data in the DB.  Node allocation automatically unpacks
and configures the node to come up as an Emulab/Plab node when it is
booted (later, via vnode_setup).  It also takes care of other
necessary bits of interfacing with Planetlab, including discovering
which nodes are available, adding new Plab nodes to the DB, and
maintaining status information on Plab nodes.

with views, to give different IPs fro boss and ops to internal hosts
than to external ones.

Needed for Wisconsin.

an interface route when bringing up the interface. To solve this, I don't
do the hostroute optimization (i.e. add the 1st host route as a net route
and add subsequent host routes only if they are different) for directly
connected neighbors.

Jail changes.

> > >is to collapse stuff like:
> > >
> > >         192.168.3          192.168.2.2        UGSc        0       12  veth6
> > >         192.168.3.2        192.168.2.2        UGHS        0        9  veth6
> > >         192.168.3.4        192.168.2.2        UGHS        0       12  veth6
> > >
> > >into the single net route.

Found the problem. My code took care of the case where the net route was
calculated first and if a host route came up for the same subnet with the
same hop, it would skip adding the host route. However, if the host route
were added first before the net route, it was a problem. To illustrate the
problem, the host route to 3.2 is added on FG1 when the net route was
calculated for node 'A' at 7.0 . At this point however, the net route for
3.0 hasn't been defined yet coz that'll come later in the route to dst
'AS1'. Experiment testbed/vroutetest.

The solution is to consider adding host routes only after all net routes
have been added to the DB. Changes to the code weren't trivial this time.
Also, when adding host routes, I add the first one as a net route. If
subsequent host routes have the same hop, they'll get skipped. Otherwise,
a host route with a longer prefix will take precedence. With all these
changes, the number of routes in testbed/vroutetest experiment came down
from 361 (> NxN) to 162 (< NxN) where NxN is 289 . Mike, let me know if
things are alright after rebooting vnodes in your experiment.

skipped.

----------------
    if ($optimize) {
	my $newip = inet_ntoa(inet_aton($dstip) & inet_aton($NETMASK));

	if (defined($netroutes{"$src:$newip"})) {
	    if ($netroutes{"$src:$newip"} ne $hop) {
		die("*** $0:\n".
		    "    network route mismatch: $src:$dst:$hop!\n");
	    }
	    next;
^^^^^^^^^^^^^^^^^^^^^^^^^^
	}

	$netroutes{"$src:$newip"} = $hop;
	$type  = "net";
	$dstip = $newip;
    }

HOSTROUTES:
----------------

If a NET route is already defined for a subnet because of a previous route
(to a different dst on the same LAN), it would skip doing the HOSTROUTES.
This problem wouldn't occur with links alone in the topology. Looks like
it was never caught because no one probably tried pinging IPs of all
interfaces while using LANs. Note that this problem wouldn't occur for
directly connected neighbors (even if they are on a LAN). The latter is
the reason why maryland folks didn't encounter this problem.

The bottomline: We need Dave (West)'s automated testing tool!

Fixed, committed and installed.

Mike, I have fixed the routes in your experiment. Just reboot your
nodes/vnodes.

-Shashi

On Fri, 15 Aug 2003, Mike Hibler wrote:

> I've know we have been round and round this one, but it appears that
> rtproto Static is not producing routes to all IP addrs listed in the
> hosts file.  Again, it is nodes with multiple interfaces and we don't
> have routes to the nodes on all of those interfaces.  I thought we came
> up with some solution (or at least hack) for this?
>
> You can see this in the testbed/vroutetest experiment by logging into
> say EGG1.vroutetest.testbed.emulab.net and trying to ping "F-3".
> Note that this is a vnode so you'll have to slogin from ops or, better,
> use the fine ssh-mime.pl thingee of Leigh's from the web page.
>
> Honestly, I tried going back to the mail archive to find last time this
> came up, but I didn't find anything useful!
>

it.

not linked to yet.

vserver node.  The process starts with rc.vinit, which is called
either by the service manager, the pnode boot, or by a vnode reboot.
rc.vinit calls vnodesetup, which calls rc.inplab, which calls
plabsetup.

iron out.  TMCD/libsetup now has a plabconfig commands that parallels
the jailconfig command.  The Plab boot process has been added to
libsetup and a -p option has been added to vnodesetup to parallel the
-j option.  Parts of the code that were Jail-specific, but labeled
just as vnode stuff have been renamed.  $vnodedir in vnodesetup has
been removed, since it was redunant with libsetup's CONFDIR, and
CONFDIR is much more intelligent.