Add MapToImage() which maps an osinfo to a specific image for a node
type.

Both of these are used in os_setup.

partition table lookups here. Used by os_setup, etc.

osid that is supposed to point to a specific one.

do not mess up existing elabinelab experiments.

elabinelab.

new_interfaces tables, send them over to the inner elab, and tell it
to incorporate them with newnode. If that all works, update the
reserved bit, regen the outer dhcpd conf, and then reboot the nodes.
After reboot, they will be attached to the inner elab.

Also allow tags to be passed in with the -T option.

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.

to lose your elab cause of a swap problem!

group_stats, project_stats).

node; this causes an ambiguity when the proxy is for a local
cluster node (which happens cause all protogeni nodes are considered
remote nodes. The control network IP *does* go into the
widearea_nodeinfo table.

down mode) is powered back on when starting or
deleting the sliver.

Refs can contain slashes.  For example, the short ref for
'refs/heads/foo/bar' is 'foo/bar'.  Previously, we just chopped off
everything up to and including the last slash character, which doesn't
return the correct short ref in this case.

Call git-rev-parse to shorten the ref for us.  In case it doesn't return
anything (which shouldn't happen), fall back to the full ref.

from the old domain no longer exist to avoid strange behavior.

into node_type_attributes for the two node types that were
using nobootinfo.

is 180, which is too short for some calls.

Improve previous fix to use an initialized variable for more predictable
and correct results!

The new d710s have a single-partition image as their default.  As a result,
when they were reloaded, the info for the other partitions (in particular
partition 1) was not being cleared.  So if I were to break my install of
FBSD72-STD on a d710 node and then free it, the reload would not clear
the partition 1 info in the DB.  If someone else came along requesting
FBSD72-STD and got that node assigned, os_load would think that it didn't
need to reload partition 1 and just boot right into the old stale partition.

Now for a "default" reload (i.e., from reload_daemon), a single partition
load will clear all the other partitions.  We don't do this all the time
since a user might want to reload one of the partitions on their allocated
node without clobbering the others.

Don't attempt to run setgroups on non-active accounts.