GitLab

are two ways this can happen.

1. When allocating the proxy nodes before getting the tickets. This is
   just like the local node case; need to go around the loop again and
   retry with a new node set. 

2. When getting the tickets, someone else got the nodes and gthe
   getticket fails. This is a lot like case 1, but now we have to
   nfree the proxy node, and tell the mapper to try again.

attempts by protogeni code.

The toolchain build should be dependent on an actual file to ensure we
don't rebuilt it for every target that goes into the initramfs.

Also rename old fake tcsh to tcsh.fake, and run a new script that
symlinks tcsh and csh to tcsh.fake if tcsh doesn't exist.  This way tcsh
can be removed from the build but tcsh/csh users can still log in.

or more then one experiment, of course.

commit.

use when (re)loading a node.

<disk_image
   name="urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP" />

In other words, allow "GeniSlices" for the project, so we can add
images to be used from the rspec.

Use 'git diff-tree --no-commit-id --cc' on merge commits to determine if
there are any differences between the merge commit and its parents.
This is the case if any new files were hand-modified or added as part of
the merge (such as when conflicts were resolved).  If git-diff-tree
produces no output, the merge was trivial.

If the merge was trivial, the commit message is checked for an empty
body.  If empty, the commit is skipped when generating the email.  This
way if the committer documents the merge in some way (list of changes,
reason for the merge, etc.) the email includes that information.

impotent, except that actually nalloc the nodes, and retry if the
nodes are sucked up by someone else inthe meantime.

Also, in the CM, add better ssh key checking.

added to pubs.html.

Resolve the slice/sliver credential and use that.