GitLab

Metrics clean

See merge request !190

 - It counts things for a webapp on a period of time [from; to [, with a step of aggregation.

3 metrics are proposed :
 - number of jobs per user
 - number of jobs per result
 - number of jobs created

Add tools folder

See merge request !214

Merge remote-tracking branches 'origin/eof-events', 'origin/image-entrypoint', 'origin/allgo-files-var', 'origin/prevent-option-injections' and 'origin/db-migration' into qualif

A malicious user may submit an input file starting with '-'.
A loosely-implemented webapp entrypoint could misinterpret
it as a command-line option a let the user inject arbitrary
options to the commands executed inside the job.

To prevent this the leading '-' in input filenames are silently
changed into '_'.

Now that users can push their image to the registry, it is much more
straightforward to let them configure the app entrypoint with an
ENTRYPOINT directive in the Dockerfile.

Note: if the image has no entrypoint, then we fall back to the global
entrypoint defined in the webapp (Webapp.entrypoint)

because currently the client cannot tell if a stream was normally or
prematurely terminated (the only reliable approach is to repeat the
request, which is not good)

- the submission order is preserved
- Job.files is a JSON list so that we can expand it later to store
  other details
- in ALLGO_FILES the filenames are line-delimited to allow working
  with input files containing spaces in their name (the IFS env var
  can be tuned for that purpose)

close allgo.inria.fr#11

support edition/deletion/restoration of webapp versions

Closes allgo.inria.fr#5, #44, and #266

See merge request !206

fixes for the qualif deployment

Closes #356, #349, #345, #309, allgo.inria.fr#8, #347, #338, allgo.inria.fr#7, allgo.inria.fr#5, and #44

See merge request !205

add webapp deploy tokens

Closes allgo.inria.fr#5 and #44

See merge request !204

add api endpoint to stream job state updates and logs

Closes allgo.inria.fr#6

See merge request !208

Ignore the image entrypoint when creating job/sandbox containers

See merge request !207

(because it is more common)

Given that user can now push any docker images (!204), we will
have troubles if the user sets an arbitrary entrypoint (eg: using
the ENTRYPOINT instruction in the Dockerfile).

It is wiser to just ignore the entrypoint for the moment.

Note: in the future, we should remove Webapp.entrypoint and use the
ENTRYPOINT defined in the image instead.

- implement the deletion and restoration of webapp versions
- add the WebappVersionUpdate form to:
  - update version fields: number, description, published
  - restore a recently deleted version

- make WebappVersionList a pure list (remove the form) and add control
  buttons to edit/delete/restore the versions
- add the WebappVersion.deleted_at to record the deletion time
- rename the state 'REPLACED' as 'DELETED' (because versions can now be
  deleted explicitley by the user)
- use a common WebappVersionForm for the WebappVesionUpdate and
  WebappSandboxPanel views
- reuse the previous 'published' status by default when replacing
  a version in the sandbox panel
- add the 'ALLGO_EXPUNGE_DELAY' configure when the deleted images are
  destroyed for real