GitLab

The reason we keep these tables by default is for long-term stats
(i.e., for reports and proposals). OTOH, the reason you might want to
flush these tables is if you want to reuse the node name.

same project/name in order to combine the allowed hardware types.
Only when images are in emulab-ops.

least 2009; change min to max of the bw/rbw values, since the link has to
satisfy the direction with the higher bandwidth not the lower bandwidth. We
probably don't run into this very often since people do not often do
asymmetric links like 100Mb/155Mb, on nodes that have both 1Gb and 100Mb
interfaces.

Also through in some warning code to catch this before it gets to snmpit,
which fails when you try to set a 100Mb interface to 1Gb. This might turn
into a fatal error later.

folks.

AddNodes($slice_urn, $credentials, $nodes):

The "nodes" argument is a hash that looks like:

  {"node45" : {"diskimage" : "urn...",
               "startup"   : "/bin/echo",
               "tarballs"  : ["tarball1", "tarball2", ...],
               "lans"      : ["lan1", "lan2", ...]
               "node"      : "pc189"},
   "nodeXX" : {...}}

DeleteNodes($slice_urn, $credentials, $nodes):

The "nodes" argument is a list like:

  ["node45", ...]

Any node can be deleted, but it is not yet clear what happens if all the
nodes of a lan are removed. I probably need to do some work there, but
David can start with this.

Fools! I will constrain you all!

limited to Emulab and APT.

problem of AuditFork after flipping to a new user. Its also convenient, its
annoyed me forever that I can't read the log files in /tmp.

change the images.

import new versions of images).

edit the source code at this time.