This allows other callers than rc.hostnames (i.e. docker clientside) to
generate the hostname list for an experiment.

Usage: checkprofile [-a | pid,name]
Options:
  -a  : Run rspec2genilib converter on all rspec profiles
  -r  : Run converted geni-lib
  -c  : Compare rspecs after running geni-lib
  -t  : Run RTE check on converted geni-lib script
  -g  : Print the geni-lib
  -x  : Only include rspecs with matching token

1. Encapsulate rspec2genilib in a library function.

2. Add a "check" option UpdateDiskImage() to see if any changes are
   actually going to be made so that we do not create a new version of a
   profile that is identical to the previous version.

3. Do not ever create a new version of a script based profile since we
   can never change the script (after a disk snapshot). Unless it is a
   portal converted script, we can do that by changing the rspec and
   then generating a new script.

consistent ordering from one run to the next, so that we can apply
simple diffing in rtecheck.

the fork inside run_with_ssh exits. So use POSIX:_exit() instead.

Also checks, but does not fix, the case where the slicefix script
is out of date w.r.t. sshd_config customization.

We set this attribute for the Moonshot cartridges so that "power cycle"
will force a "power on" if it detects the node is off when attempting
a cycle operation.

Also, implement "power status" for the Moonshot nodes.

If we assign a unique constant random value to every user, and spit that
out in the initial ga() stuff at the beginning of each page load, google
can combine interactions from the same user across different devices.
Say, like work vs home computer.

Also, update linux slicefix script with other recent changes.

When spitting out an advertisement and the default osid is an
image alias, be sure to stick the alias name into the advertisement,
not the first of the images the alias points to. This is wht we
were getting -X86 in Jacks from the moonshot cluster.

Redo the rspectogenilib converter with the goal of supporting both
translation *and* regression testing. A new library is responsible for
taking the output of libXML and creating a data structure representing
the rspec. While this is being done, we look for any constructs or
attributes we cannot handle with geni-lib and report that as an error;
we are not going to convert an rspec unless we can do it correctly. and
completely.

Regression testing is done with another part of this library, that knows
how to compare each element of two rspecs. Basically start at the root
and compare all the way down, failing if the two "parses" of the XML are
not equal at any level.

rspectogenilib now has an option that does regression testing by running
the new geni-lib and comparing the resulting rspec against the original.

On the UI side, there is a new button on existing rspec based
profiles (currently only for admin and studs) called "Convert to
geni-lib" that runs the converter to convert the profile to geni-lib.
The user does not have to accept the new script of course.

However, a converted profile is marked in the database, and the user can
still use Jacks on it, we just run rspectogenilib geni-lib again on the
new rspec. If the user edits the geni-lib, we switch back to normal
geni-lib (clear the flag) when the new version is saved, and Jacks is
once again read-only. This is explained in the UI, and is one of the
things people need to give comment on.

There is also a mode on the Create Profile page for converting new rspec
based profiles to geni-lib, but that is fully turned off for now, we can
get to that later.

So, one reason the fast RPC path is fast cause we do not normally
operate with credentials, but with reservations we have to since we want
the reservation creator to be a real user and of course the project has
to exist. Need credentials for that. But when an admin is editing or
creating a reservation in another project, we need the admin user to
exist too, and we might need the project to be created. That requires
different credentials. So in an attempt to deal more generally with the
admin problem, export an entrypoint to create a user (the admin user)
before trying to create a reservation. Not sure this is the best way to
go but its one way to go.

In general, I think we need a more explicit user/project management API
for the Portal. Needs more thought.

user (read: Mike) so the user (Uh, Mike) does not get all wigged out
about not being able to use the nodes he (Mike?) want to use.

1. Fix up multi architecture code wrt auxtypes (say, pvcm). I was
   failing to treat "d710-vm" as a node with a specified type, and so
   were doing multiple mapper runs with different architectures. This is
   cause an auxtype is not really a first class type object, but it is
   now, enough to recognize it as such.

   Aside; vtypes are still a potential problem, need to give this more
   thought.

2. Use the reservation MaxSwapInMap() to determine if the request is
   asking for more nodes of a specific type then allowed; do not bother
   to run assign, bail right away. We can do this we now track how many
   nodes of a specific type have been requested, for the multi
   architecture stuff. So might as well put to another good use.
   This close issue #236.

3. Add reservation system information dump to resinfo.log for post
   mortem debugging.

have been machine converted from rspecs to geni-lib scripts.

This closes issue #222.

need to call exports_setup.