GitLab

commands to fill a few tables that should be common across most
sites, so that this data can be distributed to them.

The simple single-column table exported_tables controls which tables
are output.

information about which inter-switch links VLANs use, so that snmpit
does not have to re-calculate these paths.

already been approved into another project will show up.

- Fix node total calculation
- Small formatting changes
- Sanity check is now a flag that the expt was used since latest slothd update
- Special case for idle expts without any PCs. Since we expect that they
  won't be giving any slothd reports, just ignore them here.

Added faq entry, added script to generate acl files, and added
menu option (With "howto" link to FAQ") to shownode.

all ".gz"s are installed from /www/downloads

switches, in case we only have wide area nodes. Of course, snmpit
won't _do_ anything, but it shouldn't be an error to run it.

(Client was sending NULLs, which were echoed back

by the server as literally a '^' and a '@'),

Quick fixup of some of the documentation linking while adding info about idleness/swapping out. Added a faq question and a node usage policies document in swapping.html

different. Also for protocol 1 in sshtb. Some error condition
fixes in mkacct as well; the error log was not getting email properly,
and I'm not really sure why.

Also changed PID file from /var/run/slothd to /var/run/slothd.pid

/var/run/slothd to /var/run/slothd.pid

Lets hope I've finally put it in the right place..

links that do not need to get created in the ops install target.

sshtb also checks for unified control nodes, and if the destination
host is one of them, just runs the command, rather than invoking it
remotely via ssh.

when loading the default image.

initiated model for updating remote nodes.

way, this time.

project on a new emulab installation. It puts only the minimum
amount of information in the database, to avoid bitrot, then calls
the mk* scripts. This should help bootstrapping signficantly.

respect the adminoff flag.

This call appears to always reselect the DB, which might be a problem
when the DB is busy.

the actual query.

since we are saving just a single slice, and 0 is actually the MBR (by
local convention).

reporting in isalive status, and since we are returning a "need to
update" flag in the message, and since we are now initiating widearea
account updates by setting the flag for each node, and since tmcd
decrements that flag when the node picks up accounts, it is a simple
matter to do update for remote nodes! Simply, bump the flag in this
script, and then wait a little while to see whose flag does not change
back! Report those in the email message. Works very slick.

This mechanism is going to be generalized some to handle other kinds
of updates. Either via the isalive return value, or via a specialized
TMCD call to return the list of things that need to be updated. The
next most needed update mechanism we need is for the testbed software,
followed closely by user software.