GlideinWMS

Below is an issue that was discussed over email. Jobs running in partionable subslots are not accounted for correctly, which is easy to see under the main_multicore group at http://osg-flock.grid.iu.edu/vofrontend/monitor/frontendStatus.html

We were trying to understand the occasional gap between "running
jobs" and "claimed glideins" shown at the frontend. Parag explained
it as thus:

[...]

Does this mean we occasionally have large mismatches between what
jobs require and what sites have for us? Could we be providing more
information with pilots before claiming glideins?

In general Parag's explanation is correct, and something we had some
problems with early in the project. With few active users, having one of
them exclude or target a subset of sites will lead to unclaimed
resources. With more active users, like now, this kind of balances out.
If somebody excludes a site in their requirements, somebody else will
probably pick up those slots.

In this case, I think it is a GlideinWMS accounting bug. The reason I
think so is that if you go back to:

http://osg-flock.grid.iu.edu/vofrontend/monitor/frontendStatus.html

For Group=total, you will see the gap

For Group=main, no gap

For Group=main_fnal_nocerts, no gap

For Group=main_multicore, all of it is a gap

So it looks like GlideinWMS does not consider jobs running in the
subslots of the dynamic slots.