To be picked up by TMCD and passed along to the clientside.

Handled outside of the old IP aliases handling path so as not to
conflate things too badly.

we had 768K of real memory left, but we wanted 1024 for a VM.

using a different wiring file, and a bundle of existing certs.

to rebuild the rack. We can't really go back to the original since things
might have changed, and with some racks, we don't actually have the
original ilo file (Utah, UtahDDC).

Stopgap solution - somewhat risky.  What we would prefer is a solution
that requires users to authenticate and grab a new keyed URL each time
they want to connect to a console.

types, until we have image testing and reporting.

errors that report to us, and script/parameter errors that should
got to the user only.

Clear vfs.unmapped_buf_allowed as recommended by the release errata.

an image is loaded on a node. We want to know both success and failure over
time so that we can determine when a image works or does not work on a
particular node/type. This is primarily for the image tracker to determine
what images work on what node types, but might be useful for in other
situations. I realize this duplicates some info we already have in the
image_history table, but that does not record failure, only success, and it
mostly concerned with who is using what images.

for the purposes of updating an image that is copied back to the origin.

We appear to need to specify a user_id even when using a key.
In part, this is to satisfy the check in ipmiexec, but even if we fix
that code and don't pass the user to ipmitool (-U), ipmitool will prompt
for a password.

See USEABACCREDS toplevel variable in APT_Geni.

not just the experiment creator.

imaging (cause of a failure in the backend).

there for 30 minutes or so.

  -- NOTE: These are mostly pulled from ipmitool.  Other protocols may need
  -- other values or not care at all, hence the addition of OTHER to the 
  -- list and a default of NULL.