At least in production, some issues happened that required
to have /tmp writable. To preserve the read-only state
of the container, use a small tmpfs that is enough for
the container to run. /run is another that might be needed
so make it part of the defaults used.

This test ensures that the setup feature works properly.

It has been the case for a while for beat/beat.backend.cxx>

- beat.env.python.tests 1.3.0r7
- beat.env.db.examples 1.4.0r7
- beat.env.cxx 2.0.0r4
- beat.env.cxxdev 2.0.0r4

This makes use of the new environment field that can be
added to the database declaration and is then used to
select the runtime environment in place of the database
search done until now.

This replaces the database name based search.

This field will allow to specify which environment should
be used to use a database. If not present, the old detection
process is used.

This ensure that the setup call is properly done

This will allow to improve tests also in beat/beat.cmdline>

Samuel GAIST authored Mar 11, 2020 and Flavio TARSETTI committed Mar 11, 2020

Update all logger.warn calls to logger.warning as warn is obsolete.

Also removes all unused logger instances.

The max length matches the one from the database of beat/beat.web>

The processing nodes are not on Python 3.6 yet
therefore these can not be used.

The other uses are only related to tests and
tasks not done on the processing nodes.

Some execution environments may run CPU as well as GPU
code, this check for Nvidia driver presence will allow
to reuse the same environment on both.

It also updates the GPU option to use the latest version
provided by the nvidia-docker2 documentation.

This avoids accidental writes in the container that
will be lost anyway.

When starting a docker container, use the same user as the one
currently executing the code if nothing else has been put in
the configuration. This allows to have consistent access across
executions.

Samuel GAIST authored Feb 20, 2020 and Samuel GAIST committed Feb 20, 2020

Support giving a custom mount point to use for volume setup.

This will replace the cache path when creating the volumes.

It was not matching the one created by the original discovery
and thus fails to find the environments for the tests.

This will only mount what is needed by the various containers.