certificate common name. Emulab will now put the full url (with port)
into user certificates, so that we can the RPC server on any node or
port we want.

projects to which they belong.

node type (so, d710 becomes d710-vm).

existing, and skip sending email.

Generate authority certificates for local sub-authorities (i.e. authorities
corresponding to a local project) on demand.

Map per-project URLs to the same XMLRPC server handled in the context of
the authority for the specified project.

Make the SA give out per-project credentials when it's asked for a
GetCredential in a sub-authority.

Lots of minor stuff, interfaces, command line arguments (cleaned up documentation), global rspec attributes, minor node attributes, location tags, bugfixes, etc.

Basic framework is in place. Availability and printability is codified into
functions now. Node.pm modified so that lookups can be done in bulk for
efficiency. When making XML, we now create XML trees rather than printing
out XML fragments.

This only copies over existing schemas and does not build them.

rspec-emulab directory (needs reconfigure) and missing rspec-geni
directory (needs git submodule init/update).

tracking with a git submodule; Move all of the makefiles into a shadow
tree (rspec-emulab), and use VPATH magic (via MOSTLY_SRCDIRS) to
install from the rspec subdir.

GeniAggregates can apparently be used in place of GeniSlivers in some contexts. This bug fix makes them more compatible.

This stuff needs to be fixed up better.

This was masked by the previous bug until it was fixed.

users. This leaves on the creation of non-local projects though, since
that works fine is really no different then putting all slivers in
the GeniSlices project.

legacy slices still in the GeniSlices project.

single GeniSlices project. There two forms to this;

1. If the user is actually a local user, create the sliver in the
   User's "default" project. Later this will change to use use sub
   authorities, when we can generate and read those credentials.

2. If the user is form another SA, create a new non-local project
   named by the SA's domain, and optionally a subgroup named by the
   project sub authority (see above comment).

At the same time, add proper resource usage accounting. In other
words, Show History on the web page works for protogeni experiments
and projects.

the callee might have switched to another user.

executed in order they appear in the XML. Output and status files are
stored /var/tmp/startup-NN.{log,status} for each statement, where NN
is just its ordinal location in the element. There is also an overall
log; /var/tmp/startup.log

into the per-experiment event scheduler for the experiment underneath
the sliver. An example of how to use this is the new test script
called injectevent.py, which you run like:

users> injectevent.py now geni1-program start COMMAND='/bin/ls >& /tmp/foo'

which injects an event for the program agent on your geni1 node.

Note that you have to contact the specfic CM for the node; if you have
multiple nodes spread across several CMs, you have to call this method
at the CM where the node lives.

tevc.