We currently have a number of clean up tasks implemented as cron jobs. This milestone is about implementing a dedicated janitor service (say, grid_janitor.py) , which apart from handling our current cron clean up tasks should also take over the vgrid cache updates and check that pending requests are valid and mark or simply reject them if not.

The current client-driven concurrent vgrid cache updates with http timeout after 300s are fragile and inefficient. They should really be replaced by a single handler without such time limits. The janitor would be an obvious place for taking care of the updates in a simple and efficient way. It can be adjusted to use memory caching of owners and members in mig_system_run for better performance when netfs is a bottleneck.

Site operators report that there's quite a bit of overhead in the existing account handling process and in several cases simple errors or mismatches render the process moot midway through. E.g. if the user already has an account with a slightly different ID or if trying to renew an expired account and not providing the existing password to authenticate it.
The janitor could therefore check pending requests and detect password mismatch, ID clash and invalid peers for starters.
Having password checks in a detached service like that rather than during form submission also allows delaying the check/reject long enough for password guessing that way to remain infeasible.

On-going work to simplify account renewal and password change from the Accounts page will reduce some of the hurdles in account handling but this service would still help reduce the remaining nuisances.