ProxyService support for different contest RWS

[PPakalns]

ProxyService only supports one parallel contest when sending initial data to listed RWS. After that, it sends all submission changes (even from different contests). These changes are discarded by RWS because of data inconsistency.

This pull request adds support to ProxyService for sending scores to multiple RWS where each of them can show a different subset of contests. This request fixes the problem where ProxyService sends unrelated contest submissions to RWS.

Additionally, this allows to easily set up RW servers for multiple contests that are run in parallel and keep their data unmerged if needed.

---

This change is 

[codecov[bot]]

Codecov Report

Merging #1102 into master will decrease coverage by 0.09%. The diff coverage is 42.62%.

@@            Coverage Diff            @@
##           master    #1102     +/-   ##
=========================================
- Coverage   62.02%   61.92%   -0.1%     
=========================================
  Files         230      230             
  Lines       16587    16598     +11     
=========================================
- Hits        10288    10279      -9     
- Misses       6299     6319     +20

Flag	Coverage Δ
#functionaltests	45.68% <37.7%> (-0.17%)	:arrow_down:
#unittests	43.3% <34.42%> (+0.04%)	:arrow_up:

Impacted Files	Coverage Δ
cms/service/ResourceService.py	59.06% <0%> (+1.07%)	:arrow_up:
cms/conf.py	84.73% <100%> (ø)	:arrow_up:
cms/service/ProxyService.py	60.09% <42.37%> (+0.52%)	:arrow_up:
cms/grading/Job.py	83.88% <0%> (-4.27%)	:arrow_down:
cms/service/EvaluationService.py	65.15% <0%> (-3.2%)	:arrow_down:
cms/io/service.py	68.29% <0%> (-1.22%)	:arrow_down:
cms/server/admin/handlers/dataset.py	24.76% <0%> (-0.93%)	:arrow_down:
cms/db/util.py	50.37% <0%> (-0.75%)	:arrow_down:
cms/grading/Sandbox.py	67.87% <0%> (-0.73%)	:arrow_down:
cms/db/filecacher.py	77.7% <0%> (-0.33%)	:arrow_down:
... and 8 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 584cc42...f311d0a. Read the comment docs.

[wil93]

Did you consider changing the DB model so that a contest can provide a ranking_url as well as other fields already provided like title and description? If the field is null we can fallback to the ranking specified in cms.conf

In this way, proxyservice could send contest data to the right URL for each contest.

If there are multi-day contests we can easily support that by setting the same ranking_url value for both days

[andreyv]

Or leave the upload URL in the config file, but for the contest specify a "contest group" it belongs to, and use this group as the RWS prefix. Empty group would mean the current behavior. Very nice idea, @wil93 :)

[andreyv]

There is one more problem with multiple RankingWebServers, if you run them on the same machine. Not taking into account that each needs a different port number, they also need different log and data directories. By default they all try to use /var/local/log/cms/ranking and /var/local/lib/cms/ranking.

This can be worked around by specifying different log_dir and lib_dir settings and having a separate config file for each RWS instance (overridden using CMS_RANKING_CONFIG).

[andreyv]

To expand on the last idea:

We can add a new "group" field to the contest in DB. Contests in one group would be temporally related, for example, day 1 and day 2. When ProxyService sends data to RWS, it would also send the contest's group along the data.

When RWS receives the data, it would display it under the /<group> URL prefix. An empty group would mean the current behavior.

For example, for the Latvian olympiad with two days and junior/senior student groups, we would have

Contest       Group
===========   ======
junior_day1   junior
senior_day1   senior
junior_day2   junior
senior_day2   senior

and there would be two scoreboards at http://rws/junior and http://rws/senior.

This way there is no need to change cms.conf/cms.ranking.conf each time. Also, as shown above, running multiple RWSs is troublesome too.

A separate question is how to deal with the leaking of the task names from the second day. I think this can be handled in a different issue.