GitLab

relevant email:

Date: Wed, 18 Apr 2007 21:20:37 -0700
From: Jason Shupe <jshupe@ISI.EDU>
To: Testbed Ops <testbed-ops@emulab.net>
Subject: [patches] tmcd.c (Jason) and elabinelab.in (Keith)

Included in this email are my description of the problem, and my patches
to tmcd.c, followed by more descriptions of the problem and Keith's
patch to elabinelab.in.  I apologize in advance for misquoting,
changing and other wise abusing Keith's prose.

An elab in elab experiment was started from the DeterTest project.  A
simple inner experiment was then started from the emulab-ops project.
During experiment swap in the program agent would fail to start.  If the
same simple inner experiment was started under the DeterTest project or
on the main testbed it would start normally.

It turned out that Keith's account (among others) wasn't getting created
on the inner experimental node.

tmcd was only sending a subset of accounts to the experimental nodes.
By digging through the database queries from tmcd.c I noticed one of the
database responses contained a NULL in the g.unix_gid field.  By
removing the only user from the emulab-ops sub group 'ops-test' it was
then possible to successfully swap in the inner experiment.

I've included two different versions of an untested tmcd.c patch.  Both
versions include changes only to the mysql statement.  Both versions of
the modified mysql statements were tested on the elab in elab database
after the only member of emulab-ops was re-added to the 'ops-test'
group.  Both queries returned all results of the original statements
except the offending record with the 'NULL' value for g.unix_gid.

The first patch directly excludes the offending record(s), and the
second patch simple changes the _left join_'s to just _join_'s (Keith's
suggestion) which also produces the same result for the data set tested.

Ted reminded me that "is not NULL" is better than my initial "!='NULL'",
which also produces the same results.  Other suggestions on this end
include specifically using "inner join", and to use both "inner join"
and "is not NULL".

Date: Tue, 24 Apr 2007 14:44:08 -0700
From: Leigh Stoller <stoller@flux.utah.edu>
Subject: Re: [patches] tmcd.c (Jason) and elabinelab.in (Keith)

Well, unix_gid is not supposed to be null, so we should fix that problem
instead, I would think.

Date: Wed, 25 Apr 2007 00:35:30 -0700 (PDT)
From: Keith Sklower <sklower@vangogh.CS.Berkeley.EDU>
Subject: Re: [Deter-ops] [patches] tmcd.c (Jason) and elabinelab.in (Keith)

It became null because of using an outer join instead of an inner join.

I'll repeat the condition:
1.) the DETER emulab-ops has subgroups
2.) the inner elab group membership table and references to a group
    which was not inherited from the outer boss [pid=emulab-ops,
    gid=test-grup, uid=jhickey]

So, my initial proposal was to be a bit tidier in specifying what
group membership entries should be subsetted.

(the was a phrase which intended to catch the group membership
for anybody currently active in emulab-ops, but it was too encompassing).

Date: Wed, 25 Apr 2007 13:15:51 -0600
From: Robert P Ricci <ricci@cs.utah.edu>
Subject: Re: [Deter-ops] [patches] tmcd.c (Jason) and elabinelab.in (Keith)

I guess, then, I will commit both proposed changes to tmcd - both to
make the existing join more 'correct', and to guard against other ways
(ie. bad/inconsistent DB state) the gid might show up as null.

stuff into the library since we do that in many places.

/var/log/messages.

Fix FS#151  "$ns report" get's called in seemingly random places"

It turns out not to be random. Instead send_report is being called
when something fails in a timeline. The intent here (I assume) is to
inform the user of the error. Unfortunately this has several
undesirable side-effects such as creating an unnecessary zip file and
overwritten the existing contents of report.mail. I fixed this by
creating a new function send_error_report which is like send report
but doesn't have the undesirable side-effects.

statements.

by pid/id since the id is now an integer and not even shown in the
resulting drop-down list.

Also add plabnodehistmetrics, which ranks plab nodes using
libplabnodehist, writes the ranks and metadata to
/share/planetlab/reliable_nodes, and inserts a '+unavail' weight into
node_features for planetlab nodes.

utilities (tevc, linktest, libraries).

everybody's stuff up.

"select" to a "select distinct" on osidtoimageid since there will be
multiple osid entries for combo images.

event clients) need slightly different args.

no complete event to indicate an error condition.

it too, but its not like people use the page that much, so not gonna
bother.

at least under FreeBSD 6.2.  That is, a single kernel for regular, delay
and linkdelay usage.  I got close, still have a second kernel for delay
since it uses DEVICE_POLLING and I haven't had a chance to determine the
impact of the DEVICE_POLLING option when polling is disabled.

[Aside: polling + 10000HZ may be a bad idea.  In 6.2, there seems to be
 a lot more overhead associated with polling, they don't recommend you
 go over 1000HZ with polling turned on.]

Note that the script now checks the running kernel's HZ value, tweaks
/boot/loader.conf, and reboots if it is not correct.  However, this should
not be needed when combined with the latest, spiffy emuboot which can take
a HZ=NNNN command line option and change the kernel setting before loading
the kernel.

These changes should not affect the old 4.x kernels.

will give me a little breathing space (stage things in slower) by
starting just with boss.