GitLab

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.

Uses the tmcc/ubuntu15 os-dependant directory, which seems to work.

For the case where zapdisk doesn't exist.

also support alterntive ipmi privilege levels

Also need to add support for separate ipmi encryption keys from user
passwords, but it turns out that the current db schema does actually
support that already and at least one script more or less does it
already (power_ipmi.pm), though another doesn't (power_ilo.pm), so we
can fix that separately there.

This is to allow support of additional read-only users for gathering
power data that don't have to also be given the admin password in form
form of the hex encoded Kg key.

Also add a field so that we don't need to assume that the privilege
level is necessarily ADMINISTRATOR.

This was causing eventual unmount of the customized FS to fail and
apparently causing the changes to get lost and/or cause FS problems.

terminates properly (zero status) instead of being killed by
the reboot/halt (and exiting with -1). Noticed on Debian 8.0.

For those of us with 80-column vision...

Awesome.

It took me so long to find this stupid bug, I don't want future me
to have to hunt for it again...

Since this is the obvious fix to libabac not working after the upgrade
to 0.1.9.