GitLab

that we do not want to deactivate or change the "end" time of the
reservation, in case we want to abort self destruction. Insert
Star Trek reference here:

experiments are recent too!

determine if reservations are being used. Work in progress.

Really, it is TMHS (Too Much Horizontal Space).
80 column output rules! Welcome to the 1950s.

Not super well testbed yet, but getting there.

1. Fix the user extend modal to show the proper number of days they can
   extend.

2. Fix the admin extend modal warning when the extension would violate
   max extension, it was not showing. Add new alerts when we cannot get
   max extension from the cluster or no extension at all allowed.

3. Reduce number of days in the box to max allowed. Warn loudly if you
   type a different number and its greater then max extension.

4. Add "force" box to override. Use with caution. Added the plumbing
   through to the back end as new force option to RenewSliver().

5. Add check in RenewSliver() to ask the reservation system if extension
   allowed before doing it. This was missing, should solve some of the
   over book problems.

when the repo changed, but not the profile source (some other file changed).

Defaults to 0, which means do not pass user password hashes to nodes via
tmcc. Non-zero will restore the old behavior.

He also tested this on 10.3, and I tested on 10.2 and 9.0. That is
enough backward compat.

We were setting up ipod and then calling "tmcc fullconfig" which re-fetched
the ipod info causing a reset of the one-time secret. Thus the kernel had
the wrong secret.

problem with new moment.js which I updated to fix problems with Chrome.

to display in UTC instead of local timezone.

Update 3.testbed.sh.in to reflect changes made to start shared-node-listener as daemon

See merge request !27

Convert into daemon

See merge request !26

and all projects in all portals.

us to reactivate them first.

There is just too much variance across installed M2Crypto versions
and/or M2Crypto has too much internal churn to enable this by default,
sadly.  It just wasn't designed to expose this feature (the ability to
limit the time spent in SSL accept).

1. New table login_history to save all logins (uid,IP,portal).

2. Send warning email when user who has not been active for over a year
   logs in.

last run of assign, which is especially important on the moonshot
cluster which is multi-architecture.