GitLab

to a local disk image we were creating a duplicate of the image via
image_import in the project of the experiment. Change LookupByURL() to
notice that the URL refers to a local disk image, and return that image.

the public IP of ops for the mounts.

exported. Does not appear to happen automatically.

We pass through a flag in the tmcd loadinfo call to tell whether to attempt
to do a TRIM when loading the disk (or after loading the disk). If TRIM=1
then we do so.

Since it is not clear from what I have read whether repeated TRIMming is
a detriment to SSD life, we throttle it as follows:

1. We don't TRIM at all unless the sitevariable general/bootdisk_trim_interval
   is non zero. If it is set, we will wait at least that many seconds after
   the previous TRIM before we do it again.

2. We keep track of the last trim via the node_attribute "bootdisk_lasttrim"
   which is a unix timestamp of the last time that tmcd responded to a
   loadinfo request in which it returned TRIM=1.

2. We track, on a per-node basis, whether the boot disk should be TRIMmed
   or not. If the node or node-type attribute "bootdisk_trim" is non-zero,
   we will attempt a trim if the interval has passed since the last trim.

So, we never trim if the sitevariable is 0 (the default value). If it is
non-zero, we only trim the boot disk of those nodes that have the node or
node_type attribute set and only after a sufficient interval has passed.

This does not address non-boot disks, but currently frisbee won't mess
with any other disk anyway. Eventually, we will have to have per-disk or
per-disktype attributes if we want to do this better.

Should be using last rather than next at the end of each "case".

It can interfere with our caller if they are also using it!

In my cleanup of the "doaccounts" code, it looks like I was a bit
overzealous. The logic for detecting when a node is a shared vnode
host was incomplete, and so matched for the vnodes themselves too.

This is more like what bootinfo does, but I haven't resorted to this yet...

Keeping them up to date throughout the node lifecycle is not a lot of fun...

This enhances the power_ipmi module in three ways:

* Will now check for auth creds in the outets_remoteauth table.
  - Previously the module had credentials hard-wired.
  - Key role in table should be "ipmi-passwd".

* Makes it run in parallel for the set of outlets provided
  - via emutil::ParRun().

* HP Moonshot chassis iLO support.
  - Device (node) type == "ipmi-ms".
  - Outlet to ipmi address resolution.
  - Additional required ipmitool parameters ("lanplus" protocol).

* Supports KGKEY for session encryption.
  - KGKEYs can be placed in the DB ("ipmi-kgkey" role, key encoded in hex).

Note that the "status" command doesn't really work presently, but that's
OK since it wasn't ever hooked in.

Apparently at some point in the past, wire info for new nodes moved into
its own table rather than using the switch_* fields of new_interfaces.
For Geniracks or if a certain feature is set, then this new style is used.

However, newscript unconditionally assumed the new format and generated
incomplete entries for non-Geniracks. Newscript now makes the same checks
as newnode.

Move the taint clearing action so that it happens as the node exits
the "reloading" experiment (vs. when it goes into reloading).

Also add utility function to allow the node to get the exact details of
the image it is running ('imageinfo').

Some of the taint checks are rather heavy-handed presently.  Pretty much
any vector that could be used by the user to do something as root has
been severed right at the top of the relevant tmcd calls.

Calls affected:

manifest ('blackbox' and 'useronly' taintstates)
rpms ('blackbox' and 'useronly' taintstates)
tarballs ('blackbox' and 'useronly' taintstates)
blobs ('blackbox' and 'useronly' taintstates)
startupcmd ('blackbox' taintstate)
mounts ('blackbox' taintstate)
programs ('blackbox' taintstate)

Taint handling for the 'accounts' call was dealt with in a prior commit.

Also fix incorrect check for a dictionary entry that doesn't exist.

Conflicts:
	clientside/os/imagezip/ffs/disklabel.h
	config.h.in
	configure
	configure.ac