GitLab

genilib).

Need to rethink. We still rely on bootinfo sent events on the Moonshots
(e.g., when going into PXEWAIT).

Since the Moonshot cluster will soon have x86 nodes and those nodes do
call bootinfo (unlike the ARM nodes), make sure that bootinfo does not
send PXEBOOTING/BOOTING events (since dhcpd already has) by starting it
with the new -E option.

Formalize by adding a BOOTINFO_EVENTS defs var that defaults to 1.
This ensures that a nobootinfo version of the dhcpd.conf template is
installed and that bootinfo is invoked with the -E option.
Only defs-cloudlab-utah should set it to zero.

Use on Cloudlab Utah where we configure dhcpd to send the events
(needed for the uboot'ed ARM cartridges).

This was rendered obsolete by the addition of the bs-agent 1+ years ago.

This will be used by the power command to tell it to try to power on a
machine that fails to "cycle". ipmitool (or IPMI) seems to fail by default
if you try to cycle a powered-off node.

so that user sees the message (but not us). I feel like we should add a new
response code: GENIRESPONSE_NOTREADY.

vnc windowing system, which has been wonky since I installed El Capitan on
my mac. Damn.

to run the parser in the context of the project so that image/blockstore
tests are done properly.

context for actually creating a profile from an NS script.

geni-lib in the ns2rspec path.

Who knew that Linux and FreeBSD would disagree on something?
(Arguments to qsort_r).

I want to be able to make a client tarball. Actually, I would prefer that
this call was not here at all or was at least the very last thing in a
client install. When I did a build on CentOS 7, the make hung here everytime
before timing out and leaving me with a partial install.

But I ain't gonna touch it...systemd cooties!