GitLab

events that need to be transformed into portal events. This cuts the
number of events received by 50 percent, which keeps pubsub from backing
up on sending the events back. Helpful for really big experiments
(1000+ nodes).

If the TBScriptLock caller provides a debug message, it will be stored
in a file, and other blocked TBScriptLock callers will get (possibly
slightly racy) info about who holds the lock.

Then, use this in libvnode_xen to get some info about long calls to xl
(create|halt|reboot|etc).

Also enable lockdebug in libvnode_xen for now.

This is really only needed on the mothership.

cluster is not reachable or its BUSY. Just mark it canceled so the
apt_daemon will pick it up.

the extend modal, tell the user they cannot extend their experiment
until the cluster is back online, try again later. This is a stopgap, we
probably need a better way to handle transient failure in contacting
clusters when doing extensions.

an experiment from the cluster (say, cause its offline).

1. Reservation system now groks experiment lockdown and swappable. When
   swapping in, lockdown and swappable mean the expected end of the
   experiment is never.

2. Reservation library now handles changes to lockdowm, swappable, and
   autoswap (timeout). editexp now hands these changes off to a new
   script called manage_expsettings, which can be called by hand since
   we might need to force a change (I am not changing the classic UI, if
   a change is not allowed by the res system, we have to do it by hand).

3. Minor fixes to reservation library.

It was printing out the destination (aka, boss) rather than the IP
that was trying to access boss. Very confusing.

with sufficient permission to do anything useful (including geni users).
Head them off at the pass and explain in simple (short), direct (short)
clear (short) text why they can't do what they want to do.

Note that node_type_attributes.bios_waittime could be used to
dynamically adjust the stated timeout, but I don't want to embed
semantics of a particular state in stated, so we would have to
have some more general mechanism to tell stated to adjust the
timeout value based on a database field.

getticket before the underlying experiment is created. This is a temp
fix for Hussam, better fix is under development in my tree.

checker) when the number of nodes is greater then 100. There appears to
be a pathological problem in Jacks that causes it to consume 100% of
your CPU for 5 minutes or so before finishing. The was making it
impossible for David to do his 200+ node tests.

Addendum: while testing this just now, I noticed that the problem is
related to the cross product of nodes and links. 100 nodes and no links
is actually not that bad, but add a lan and watch out!

for a more complete picture of what the user was seeing.

Can't live with em, can't kill em dead... When writing my hack
routine to convert an image path into an imageid, I failed to
consider the .ddz (delta image) suffix.