This was blowing up the '-N' ("just save it") option of frisbee on big
files.

Use the new event scheduler by default for any
users/groups/experiments configured for it using EmulabFeatures.

Added '-N' option to eventsys.proxy to have it use the new scheduler
(if it exists) instead of the old one.

Added test for NewEventScheduler feature to eventsys_control so that
it will pass the '-N' option to eventsys.proxy for
experiments/users/groups using the feature.

These changes will go away when the new event scheduler replaces the
old one.

Modify the event scheduler to use the BSD-licensed xmlrpc-c library
instead of the LGPL-licensed ulxmlrpcpp.

Merge in Leigh's changes to retry operations on transient errors.
Show a heartbeat when waiting for XMLRPC requests to return.

I had done this a while ago, but broke it slightly when I added MLE
stuff.

When remembering a passphrase, attempt to decrypt the private key with it.
If decryption fails, complain, and try again, and again, and again...

almost impossible to get the shared nodes to be used fairly. Revisit
later.

(busy).

See http://users.emulab.net/trac/emulab/wiki/oml.

Conflicts:
	tbsetup/ns2ir/tb_compat.tcl.in

too busy error.

The test scripts will retry when it sees this error.

wrapper, which means the server is WAY too busy. Instead of just
bailing, retry every 5 seconds. User is free to hit ^C to halt the
loop, no harm done.

Conflicts:
	tbsetup/tbswap.in

use EmulabFeatures;

if (EmulabFeatures->FeatureEnabled("NewMapper", $user, $group, $experiment)) {
   # Do something
}
else {
   # Do something else.
}

where $user, $group, and $experiment is the current Emulab user, group, and
experiment the script is operating as. Any of them can be undef. Note that
features can easily be globally enabled or disabled (bypassing user/group
check). See below.

There are two scripts to deal with features. The easy one is the script to
grant (or revoke) feature usage to a particular user or group or experiment:

boss> wap grantfeature -u stoller NewMapper
boss> wap grantfeature -p geni NewMapper
boss> wap grantfeature -e geni,myexp NewMapper

Add -r to revoke the feature.

The other script is for managing features. To create a new feature:

boss> wap emulabfeature create NewFeature 'A pithy description'

which adds the feature to the emulab_features DB table. Use "delete"
to remove a feature from the DB.

You can globally enable and disable features for all users/groups (the
user/group checks are bypassed). Global disable overrides global
enable. There are actually two different flags. Lots of rope, I mean
flexibility.

boss> wap emulabfeature enable NewFeature 1
boss> wap emulabfeature enable NewFeature 0

boss> wap emulabfeature disable NewFeature 1
boss> wap emulabfeature disable NewFeature 0

To display a list of all features and associated settings:

boss> wap emulabfeature list

To show the details (including the users and groups) of a specific
feature:

boss> wap emulabfeature show NewFeature

Oh, if a test is made in the code for a feature, and that feature is
not in the emulab_features table (as might be the case on other
Emulab's), the feature is "disabled".

swap.

when no nodes can be allocated, but there are nodes available and the
experiment would map.

resource locking issue that iptables should deal with, not me!

address; Try harder to recover instead of bailing.

This is a brute-force hack.  We fail on ANY overlap even though some overlaps
(e.g., with unused partitions) could be handled.  But handling those is a lot
of work for little gain.

Also: removed one last reference to SHD.