In python 2.6, the implementation of serve_forever changed and it invokes
a new method, _handle_request_noblock, instead of handle_request.  The
former is not overridden by m2crypto resulting in m2crypto specific
exceptions (SSLError) not being caught.

It is deprecated as of python 2.6 and we don't appear to actually use it
anyway!

Subbosses authenticate to the XML-RPC server as elabman, which means the
resulting server process runs as the elabman user.  Unfortunately, this
doesn't work well when the subboss wants to launch a frisbeed for an
image for which elabman doesn't have read permission (like images under
/proj).

To fix this, a setuid wrapper script is run instead of trying to run
frisbeelauncher directly.  This script makes sure the calling user is
elabman, and then becomes root and execs frisbee_launcher.

Subbosses make XMLRPC requests as the user 'elabman' which doesn't
belong to any projects, and therefore has no rights to non-global
images.  The easiset way to solve this is to run frisbeelauncher with
admin privileges when a subboss requests it.

We already check to make sure the requesting user has permission to use
the image in libosload well before we hand the request to the subboss,
so if the subboss requests the image we can trust it.

Accidentally got removed by commit
826746ac

broke, but I decided that relying on stdout vs stderr in the xmlrpc
server, to return results is a bad plan. Instead, the rpc server
passes a new option to specify an output file that snmpit.proxyv2
should write the results to. After the proxy runs, grab the contents
of that file and send back to the calling elabinelab.

Note that you will need to update tbsetup/snmpit_remote.in and install
it, in your elabinelab.

an event and to actually fire those events during experiment swapout.

deleted, they still remain in the user table with a status of
"archived", but since all the queries in the system now use uid_idx
instead of uid, it is safe to reuse a uid since they are no longer
ambiguous. 

The reason for not deleting users from the users table is so that the
stats records can refer to the original record (who was that person
named "mike"). This is very handy and worth the additional effort it
has taken.

There is no way to ressurect a user, but it would not be hard to add.

nsfiles table.

The xmlrpc logfile was getting left open in children and things were not
being properly background-ed as a result.

stderr separately to avoid messing up the XML output of the command
due to warning or the like.

of the proxy, from my elabinelab.

swap failure in the xmlrpc server.  To use it, the extra option
"extrainfo" needs to be set to true.  This will cause "value" to be a
structure (in the XML-RPC sence) with useful information instead of
just the exit value of the script.  The structure will contain at
least the following fields:
  cause: "temp", "user", etc
  cause_desc
  mesg: more specific error information
  exitval: script return value
  log: activity log
Note, that value may still be an integer in the case of some other
failure that is not swap related.

To support this, the "-X" option was added to swapexp and batchexp
which will output a RPC-XML method response to stdout when possible.

testbed-ops and the user.  Important email that requires testbed-ops
attention, such as on a recursive cleanup error, will still be sent.
In addition mail normally sent to testbed-logs will still be sent.

Also, add "noemail" option to xmlrpc server methods corresponding to
those commands, and "-N" option to related commands in script_wrapper.

old and new versions for a while so as not to break existing
elabinelabs.

original, but for now the second version is to develop my changes;
instead of processing the arguments and sending things through on
the command line, take the blob of xml and send it through to the
proxy (via a file) and let it convert the xml to a data structure
(the same data structure that the client inside the elabinelab sent).
Much easier and less error prone.

uid of the user. Not sure this change will survive in its present form
since this was done for protogeni and the spec will probably call for
something different. But this is what it is for now. Note that the server
side is backwards compatable with old certs, at least for now.

only).  Also add a util script (meant to be used from a user's desktop)
that contacts the elab and plab xmlrpc servers for the config info, and
writes all that junk to the right places on a dongle or dongle img.