GitLab

Normally, "pkg" will update itself to the latest version from FreeBSD
Central, but that version is now built with FreeBSD 10.3 and the binary
is incompatible with earlier 10.x versions.

So we go to heroic efforts to install the version from the pre-built
Emulab packages.

event stream while I debug things.

Setting bandwidth==0 in either the sitevars or via subboss_attributes
will now get properly translated to no bandwidth cap in frisbeed.
Previously it was ignored. But I still do not recommend this setting
as slow clients can get swamped.

Allow setting of dynamic BW control along with unlimited bandwidth.
Likewise not recommended (though marginally better than the above).

MAXLINGER is how long to stick around after the last client leaves.
DYNAMICBW can be used to turn on the experimental dynamic bandwidth adjust.

Zero means disable, anything non-zero means "let the server decide".

Make sure server doesn't exit as long as it is getting heartbeats
from known clients. We used to exit when we stopped getting requests,
however clients often finish their network activity long before they
are actually done.

Emulab event now reports Mebibytes rather than bytes. It is accurate
enough and avoids perl bigints in the receiver(s).

The reason for the duplicate profile happens when you instantiate a
version of the profile, then terminate. That takes you back to the
instantiate page with default=uuid-of-profile, and if that is a version
uuid, we end up with a duplicate cause the list is based on the profile
uuid.

This closes issue #190.

I ALMOST got sucked into making big changes that would have required
a version change.

lists on the genirack control switch, to block access to the ILOs. Would
need to be localized to the rack network of course, and I vaguely
remember that some of the switches had different firmware and so the
commands had to be changed. Also note the netmasks are inverted from
what we normally think they should be. OH HP ...

Added PortalProfiles to the systems project list

See merge request !19

placement==SYSVOL blockstores would not work on Linux because of this.

command to set the push url.

before instantiating.

when they have leaked.

take out line with the string SupportAssist

instructions about what to do and stern warnings.

The main point of the changes are to require that the old password is
provided when changing your password. This holds true even for admins
changing their own password in red-dot. Note though, that when an admin
changes another user's password in red-dot, old password is not
required, which is somewhat in conflict with the overall goal, but hey,
we want to be practical too.

I ended up removing password modification from the profile page, and
use the already existing changepswd page, which I cleaned up and turned
into a first class ajax citizen to make the page operate smoother.

If the portal pages are wrapped in an iframe, they notify the outer page as the user navigates around the portal. They also notify the outer page when the user navigates away from the portal.