GitLab

complete.

as per issue #440.

... where "selective" means | head -1.  Some pythons spew not only their
version but also the compiler version, so we were getting a multi-line
value for PYTHON_VERSION in some places, which breaks the generated
GNUMakefiles.  configure must be setting some env var that is causing
newer or custom-built pythons to produce this extra information.
Anyway, head -1 should be a fine strategy.

* Add onie-dongle and onie-dongle-install targets, which builds and
  installs (DESTDIR required) the bits and pieces we need. This install
  is intended to update the initram FS. ONIE operates as the admin MFS
  and the "frisbee" MFS, bootinfoclient used to emulate PXEWAIT
  waitmode.

* Need to be build in the ONIE cross compiler environment, see the
  ftos.env and mlnx.env for the environment variables before config and
  build.

* Basic operation is like the old CDROM; use bootinfoclient and tmcc
  bootwhat to drop into "admin" or "frisbee" mode, or boot the NOS. Use
  tmcc loadinfo and call onie-nos-install. Use a grub environment
  variable to tell grub to either boot the NOS (and then clear the
  variable) or boot into ONIE.

We have had issues with uploading images to boss where they are then written
across NFS to ops. That seems to be a network hop too far on CloudLab Utah
where we have a 10Gb control network. We get occasional transcient timeouts
from somewhere in the TCP code. With the convoluted path through real and
virtual NICs, some with offloading, some without, packets wind up getting
out of order and someone gets far enough behind to cause problems.

So we work around it.

If IMAGEUPLOADTOFS is defined in the defs-* file, we will run a frisbee
master server on the fs (ops) node and the image creation path directs the
nodes to use that server. There is a new hack configuration for the master
server "upload-only" which is extremely specific to ops: it validates the
upload with the boss master server and, if allowed, fires up an upload
server for the client to talk to. The image will thus be directly uploaded
to the local (ZFS) /proj or /groups filesystems on ops. This seems to be
enough to get around the problem.

Note that we could allow this master server to serve downloads as well to
avoid the analogous problem in that direction, but this to date has not
been a problem.

NOTE: the ops node must be in the nodes table in the DB or else boss will
not validate proxied requests from it. The standard install procedure is
supposed to add ops, but we have a couple of clusters where it is not in
the table!

pubsubd. The main point is that instead of being able to run the SSL
pubsubd at the Mothership only, any site can be a Portal and needs to
run it. So for example my elabinelab is a real Portal, which is very
handy for testing.

Also, get rid of an extra definition of PORTAL_ENABLE.

This is pretty minimal "support", but it is working.  I have some
uncommitted fixes for event/linktest/iperf, however, as mentioned in
issue #351.

stuff in them.

Add defs-* multiplier factor variable for setting "quota" based on "refquota".
For most sites this will just be 1.0. On the mothership, where we use ZFS
snapshots for backup, we are going to start with 2.0.

(We all build out of the clientside configure dir for actual client
installs, but somebody has a comment in here implying it's good to keep
the file lists in synch, so...)

true *snmpit*, all others are imposters and have been shot.

The snmpit_test directory moved to snmpit. snmpit_old is gone.

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.

Update mothership defs file to enable idle stats collection.

* Move common and client-side stuff to the clientside tree

* Update autconf configure scripts:

This commit bumps the version of the top-level auto-generated
script from 2.68 to 2.69.

When zero, we do not set an expiration on passwords.

us that much anyway.

we already use on the mothership. Enable for the APT cluster.

CLUSTER_PUBSUBD_PORT is the SSL port that pubsubd listens on at the Portal,
and CLUSTER_PORTAL is the hostname of the portal (boss.emulab.net) that
tells clusters to forward geni events.

This will only be for boss and for FreeBSD 10.2 and beyond.

users).

your defs file to avoid a warning.