Allow controlling of site/entry's limits from the frontend
CMS ran into issues where some of the sites were running into either too many glideins or too few glideins and asked for options to control this site specific info from the frontend's side. Ideally this frontend should not have to deal with this settings and take over factory's jobs. This issue could very well be a result of bugs in the accounting of multicore glideins.
For now we need to see if this issue is addressed after accounting related bug fixes in v3.2.13 and if not, investigate possible solutions for this.