GitLab

We render them unusable.

based page that looks like the original Begin Experiment page. Be sure
to look at the page in both admin mode and non-admin mode since I had
some trouble determining how swappable is treated these days.

Oh, added the ability to convert non-batch experiments into batch, and
back. The experiment must be unlocked and in the swapped state to go
in either direction.

Also added the cpu_usage and mem_usage slots for editing. I added a
comment about planetlab only, since otherwise we would just confuse
normal users who have no idea what they mean. I could conditionalize
them on having plab nodes, but thats difficult to figure out in the
web page when the experiment is swapped out, so lets not worry about
it.

Usage: plabstats [-dfh] [-CDHILMS]
  -d    print debug diagnostics
  -f    fetch new data, else use what is in /tmp/plabxml
  -h    this help message
  -i    print IP address along with metrics
  -n    do not print hostname with metrics

  -C    print Ganglia CPU metrics, sorted by %CPU usage
  -D    print Ganglia disk metrics, sorted by %disk usage
  -L    print Ganglia load metrics, sorted by one minute load
  -M    print Ganglia memory metrics, sorted by %mem usage
  -S    print Emulab state info, summarizing per-node availability

Default is to print a terse summary of per-node resource usage.
Use "plabstats -f" to get fresh data or try something whacky like:
	plabstats -S | grep accept_3
to get the list of nodes which are currently available for mapping
by a "level 3" (aka, average) resource consuming experiment, or:
	plabstats -S | grep reject
to get info about the nodes that cannot be used along with the reason(s) why.

Needs some refinement:
  plabmetrics should store raw info into the DB where plabstats can get it
  presentation of Emulab state info should be improved

first on plab nodes to fix up sudo.

* New GNUmakefile that produces the rootball - not linked in from
  the main TB build.

  - You can (almost) completely build the plab rootball just from the
    testbed source tree.  The one wrinkle is that you must copy the
    Linux tmcc binary into the tmcd/plab object dir since there is no
    great way to build it automatically, and storing it in CVS is not
    a good idea since its likely to change.

* Removed the suid RPM, no longer needed - added suidperl binary
  since I couldn't think of a better place to put it.

- new SENDMAIL function that mirrors the perl lib's
- retry logic for communicating with the dslice agent when a slice/sliver is
  being deleted (plabnode free)

One thing I'd like to do is write a wrapper class around agent and node
manager communication since it can be flaky - would clean up a and simplify
things.  Maybe just wait since we're going to have to port over to dynamic
slices soon enough.

and in reports.

entry to database-migrate.sql that I forgot with my last commit.

in general, and plab nodes in particular.

link testing stuff, and will eventually be under user control, but for
now we stick this agent into every experiment, although most of the
time no one will be listening for it.

tree gets installed. I've set it for our default defs, and for all
the *-emulab devel defs files.

Features that begin with a '*' have some kind of global scope. Since
that, by itself, doesn't mean much, the second character of the
feature name must tell us what type of global feature it is. The two
currently supported are:

'&' - 'one is okay' - don't penalize the first pnode that has this
    feature, but penalize subsequent ones. Will be used to prefer
    not to give people multiple nodes at the sime widearea site.
'!' - 'more than one is okay' - penalize the first pnode that has
    this feature, but not subsequent ones. This could be used to let
    assign pick experiments to swap out in order to let the current
    experiment map. The idea being that once you've decided that one
    of the experiment's nodes is getting stolen, you might as well
    swap the whole thing.

For now, these global features should not have corresponding desires,
because it's not clear what the right thing to do would be. But, we may
decide to add these semantics someday.

bit based on type (plab nodes allowed to fail).

The default in the DB is nofail for all nodes.

during a modify. Not supposed to!

vnodes when doing the swapout phase. Only do "failed" vnodes, which is
also questionable, but I am leaving that for now.

request. Uses the same sitevar as emulab-recently-active-users.

Parent host is "<ixpname>host" (for now).  Should be done in the ns
front end, but this is something quick for Abhijeet's demo.

so that nodes will get the update flag set.

errors.

We now use a script to install RPMs.
(The only OS dependent thing was the path anyway)

(not to be confused with "tarballs") to download an RPM file.