GitLab

When an image is created successfully, a message stating this fact is printed
to the log.

More importantly, I fixed a bug in the NFS slack factor logic which resulted
in create_image waiting forever for progress to be made.

Also print out the fixed nodes when a virtual node is fixed to a
NS node. Reflects a change in the front end parser.

experiment using jailed nodes.

nodes, so path is consistent).
Also add jail support by looking to see if the node is a jailed node,
and passing that to the client side in the form of a -j option.

replace it eventually). Like the ron nodes, local nodes will now
periodically (once every 5 minutes) send a udp packet to boss to
indicate the node is alive and to see if it needs to check for account
updates. This will replace the once every 5 minute fping we do from
db/node_status (once I whack that script), and will simplify the
existing problem of propogating accounts to nodes (nodes down, nodes
in the swapping phase, etc).

target and changed path of binary.

of stuff in the new image. Also added client side install targets
every place I could think of.

we make, into these makefiles cause we tend to forget things! Also
chain to other makefiles as appropriate, including those in the event
directory and elsehwere to install client side programs and the like.

now used on local nodes. Possibly appropriate for linux too, since
this is mostly just a big wrapper for other scripts.

running (or were running when the node rebooted), and fires them off.
Called from rc.setup.

	xntpd_program="/usr/local/etc/emulab/ntpstart"
	xntpd_flags="/usr/sbin/ntpd -p /var/run/ntpd.pid"

off our ntpstart wrapper. Also a bug fix that was causing the initial
ntpdate to fail (-u option).

before cutting a new image. Note that anacron is mo longer run on the
linux image.

bunch of relocations of things from /etc/testbed in the old world, to
/usr/local/etc/emulab in the new world. Basically, /etc/emulab has
just a few config files that do not change. All of the binaries and
scripts are now placed in /usr/local/etc/emulab, and *all* of the
variable stuff that was written into /etc/testbed is now written into
/var/emulab/{boot,logs,jails,lock,db}.

which Mike added.

supfiles into .in files to be run through configure.

well; do not use a tmcd timeout, but block until tmcd responds.

directories into a common subdir. Also cleaned up some.

client side code. Two new files, to be included by any client side
script, which define all the paths. For /bin/sh scripts:

	. /etc/emulab/paths.sh

and for perl scripts:

	BEGIN { require "/etc/emulab/paths.pm"; import emulabpaths; }

Each defines a number of variables: ETCDIR, BINDIR, VARDIR, BOOTDIR,
LOGDIR, and LOCKDIR. They also set the path properly for the script.

This gets rid of the different hardwired paths, and reduces it to just
one for everyone.

rc.conf: Remove fixed -p argument. Now set by mkjail.
rc.local,jailctl: Update for client side path reorg and cleanup.
jaildog.pl,mkjail.pl: Numerous fixes for jailed nodes.

for BSD of course. First is a "proxy" mode that is used outside of a
jail, to forward tmcc requests from inside the jail to boss over the
normal ssl channel (when a remote node). We remove the pem files from
inside the jail so it has no way to form a secure connection to tmcd
on its own, and tmcd rejects non-ssl connections from remote nodes (it
should probably reject them from local jails too). Second change is a
"unix socket" mode that is the compliment to the proxy; tmcc inside of
a jail connects to the tmcc proxy outside the jail via a unix domain
socket that can be shared between the two because the outer
environment can see inside the jailed filesystems (the jail sees a
chroot environment). When the jail is started, the initial root shell
gets an environment variable called TMCCUNIXPATH which holds the path
to the socket. This makes it easy for anything started from that shell
of course, but its still a minor pain when invoking tmcc from
elsehwere, but that does not really happen, except when running it by
hand. Anyway, tmcc forms a unix socket to the proxy and does its
thing. The proxy filters out VNODE= and PRIVKEY= arguments, and
inserts its own into the command string.  This prevents a jail from
trying to impersonate another vnode.

like the remote nodes do, but for now do not update the up/down status
from that. I need to mess with db/node_status first to make sure there
is agreement between the parties. Note that remote nodes send one UDP
message every 60 seconds (isalive is done with a UDP). Local nodes
will send them at a slower rate, as is the practice in db/node_status
which wakes up every 5 minutes and fpings the world!

message about no libmysql on a testbed node.

some trouble with old logs getting cached in the browser.

Attempts to replay an experiment by rebooting all the nodes, clearing
the various startup bits (ready, startstatus, bootstatus, portstats),
and then restarting the event system. I am dubious that this is a
workable solution because of the asynchronous nature of the testbed
(nodes happily cruise from TBRESET to ISUP and beyond without
stopping), and so its hard to truly replicate the initial lack of
state that a freshly swapped in experiment has. Still, people
requested it and I cheerfully provided it cause thats what I do;
service with a smile and not a wit of complaint. Is anyone reading
this?

node. Used in new tbrestart code for replaying experiments. It remains
to be seen if this is a workable approach.

TBNodeStateWait() is really WaitTillAlive, which I need in several new
spots now. Its not as general purpose as it seems though, since there
are only a couple of terminal states (isup) that you can actually wait
for by querying the DB. But, I'm loathe to add any more event code to
the system.

option is now "[[includevirt] or [virtonly[=<phys>]]]". In other
words, you can ask to include virtual nodes, or you can ask for just
virtual nodes. Optionally, you can ask for the virtual nodes for a
specific physical node. I use this from assign_wrapper to map local
jail nodes.

nodes. The second argument can now be an NS node instead of the name
of a real testbed node. For example:

	tb-set-hardware $node3  pc600
	tb-set-hardware $nodev1 pcvm600
	tb-fix-node $nodev1 $node3

So, "fix" $nodev1 to $node3. The intent is that once $node3 is
allocated by assign to a real testbed node, we can then allocate a
virtual node on pcXX to $nodev1. I did this primarily to allow for
easy testing of jails via my NS file, without having to hack assign
wrapper to deeply. Note there are still hacks in assign_wrapper to
support this, but they are not extensive.

Also my old usewatunnels stuff I never checked in:

	tb-set-usewatunnels 0/1