GitLab

Bad idea. Use an auto_incrementing idx field instead.

Fixed bug where after running out of retry attempts,
swapout was only doing the 'retry' version of cleanup,
when it should have been doing a full cleanup.

and a query returns a null where it ain't supposed to!

by assign_wrapper to help control emulated links. When set for an
emulated link, assign uses the BW spec for mapping the links (onto
phys links) but does not insert a linkdelay to traffic shape it
(unless the link is shaped in some other manner, like a delay or plr,
in which case a linkdelay is inserted, but with no bw cap). This might
be temporary syntax, expecially if we cannot make emulated links work
right!

kernel since its hacks are so untested.

links, no lans. The whole lan thing needs work.

Add better timeout handling code to tmcc, which watches for progress
instead of just dumping after the timeout. This lets really slow
connections proceed okay, but still timeout out if nothing happens at
all.

This new tmcc has been installed into the sup trees for WIDE and RON.

idle but someone logged in sometime today, it meant that someone had
logged in since the most recent slothd report (up to an hour ago). Now
that our time of idleness is much lower than 24 hours, it is easy for
someone to have logged in today and still have it be idle. So remove the
check.

This means that you should wait at least an hour from the time you send a
message before you swap it out, to make sure that your data was correct
when you sent the message. Not optimal, but fixed with the new slothd that
goes in this week.

it was used outside the NTFS code.  imagezip builds correctly once again.

on some plinks, an apparent memory corruption bug.

under pressure; should stick to watching cartoons instead.

Scaling and speed now depends primarily on os_load (and indirectly,
node_reboot). The time a batch spends in the reload_daemon code appears to
be <1s per node now, instead of taking 30s per node to grab, setup, and
reboot.

Also, finally remove the "obsolete section" that's been sitting in there
for a long time. This was the part that did netdisk reloads, and has
already been neutered out of the code path for several months at least.

of emulated and linkdelays on a per-link/lan basis (although you
cannot make a lan emulated at this time).

	tb-set-link-uselinkdelay $link0 1
	tb-set-lan-uselinkdelay $lan0 1
	tb-set-link-emulated $link0 1

Added slots to the virt_lans table, used in assign_wrapper to control
these features on a per link/lan basis. Note, the global options are
still available to prefer/force linkdelays for an entire experiment.
When setting uselinkdelays on a per link/basis, if the link would not
otherwise be shaped, you are requesting that a linkdelay be inserted
anyway (in otherwords, its the equiv of tb-set-forcelinkdelays on an
individual basis).

have gone active again. If you gave it a higher time than the default, and
an idle expt hadn't been idle that long, it would clear the counter when
it shouldn't, making idle expts look like they may have gone active again.
(It didn't ever change any slothd data or cause any activity, you'd just
"forget" that you'd already been sending swap requests. And it only had an
effect when you picked times _higher_ than the default idle time.)

reason is to keep things moving during the high SOSP demand, but it may
stay there or somewhere similar when we deploy the new slothd next week.

parameters). Install target update as well.

Several things have changed; here is an outline:

 - "Thresholds" added to slothd
	These are checked at each iteration against current idle data
        to determine whether or not to set bits in the "active" vector.
	- LAST_TTY_ACT (now) > LAST_TTY_ACT (previous)
        - LOAD > <provided value>
        - EXPER_PKT_COUNT(now) - EXPER_PKT_COUNT(prev) > <provided value>
	- CNTRL_PKT_COUNT(now) - CNTRL_PKT_COUNT(prev) > <provided value>
	- Values passed in via command line: do ./slothd -h for help
 - "Aggressive" mode added to slothd
	When a regular interval's worth of time has passed, and no activity
        has been noted, slothd goes into "aggressive" mode.  In this mode,
	slothd changes its sleep interval, checking for activity much more
	frequently (still reporting every <reg_interval>) until activity
	is noted.  This is based on the threshold logic above.  When activity
	is seen, slothd sends a report, and goes back to "regular" reporting.
	- params passed via command line for regular, and aggressive intervals.
 - sdcollectd updates data in new "node_activity" table
	- Updates timestamps based on activity bits in received slothd packets
	- No new rows are added.
 - Option added to sdcollectd to insert into "old" node_idlestats and
	iface_counters tables
   	- This is not the default (-o)
 - New sdcollectd still accepts old client reports
	- but does not update the node_activity table with them.
 - Misc.
	- Code cleanup
	- Scan "active terminals only" option & code removed from slothd
	- Always send report immediately on startup (no more option)
	- Randomize time of second report to mitigate synchronization
	- Send report on shutdown (receipt of INT, TERM, or QUIT)

when doing emulated links so that ports do not end up in more than
one vlan.

Minor changes: Updated code to work with the new libntfs library, and made the NTFS section of the code adhere to Leigh's 80 column decree.

virtual links.

There will need to be a way to specify this on a per-vlink basis
for jails.

* Make php.ini file

* Edit ssh_config to prefer protocol version 1

* Make /usr/testbed/tftpboot, and link /tftpboot to it

* Make mountpoints for places we mount ops

* Make sure that the DNS names for ops resolve before we put them
  into /etc/fstab

* Chase emulab-boss port version

Change approveproject.php3 stuff so that approving ron includes pcwa.

subdirs and GNUmakefiles

cruft needed to compile ntfs support into imagezip, including the i18n
unicode library
routines from FBSD 5.0.  Most of the magic is in the makefiles, but there
is a patch for the ntfsprogs package we're using to get NTFS support.
(patch contributed by Russ).

Note that the ntfsprogs tarball is located in emulab webspace (like TG).

Don't worry!  You still have to pass --enable-windows to configure in order to
pull any of this in, although it should compile nicely from here on out.

Russ will commit his imagezip changes (hiber, and page file skipping) soon.

without first checking with the power that be.

with the testbed.

First, don't select a plink for an emulated link that would cause us
to go over bandwidth.

Second, make FIX_PLINK_ENDPOINTS the default, and add a #define that
makes it the default (instead of having to specify it on each plink
line.)

tbswap: re-enabled retry (Undid leigh's last change)

assign_wrapper.in:
   was left-joining reserved to nodes to get reserved list;
   This didn't get delays.

   now am doing separate query on reserved, and putting those
   into the %fixed and %alreadyAllocated hashes.

backend, but given that you have to mighty quick on the click, I never
bothered to put in the link. But I hear Mike is the quickest clicker
in the group.

anything conclusive, other than fork confuses mysqld, and our attempt
to unconfuse it by closing/opening the DB connection in the child,
confuses it even more! The parent connection is shutdown and then
restarted as well. In node_reboot, this could happen 10 times in rapid
succession as we fork as child for each node, and that appears to
strain the server even more (with 20 rapid connects).

So, I added a select(0.3) in TBdbfork() (in the child) to see if that
slows things down enough. In my tests, the length of time between the
parent and child operations makes a real difference. With a delay in
the child, the parent connection is not closed/restarted.

The astute reader will realize that I have no actual clue; just
grasping at, uh, threads.