* master:
  Fix "kvm: Increase default VM parameters to match nowadays requirement"
  kvm: Merge tests
  kvm: Allow to specify network adapter
  software/slapos-sr-testing: install new psycopg2 dependency
  recipe/postgres: support non standard port
  recipe/test_postgres: test with a real postgres server
  software/slapos-testing: install psycopg2 for slapos.cookbook
  software/slapos-testing: make postgresql available for tests
  component/psycopg2: new component
  golang: Switch default to Go1.17
  erp5testnode: update deploy script
  stack/slapos: slapos.cookbook version up (1.0.214)
  Release slapos.cookbook (1.0.214)
  test/recipe: update tests for postgres recipe regarding password update
  recipe/postgres: support changing user password after creation
  component/nxdtest: v↑
  golang: v↑ go1.16 (1.16.8 -> 1.16.10)
  golang: v↑ go1.17 (1.17.1 -> 1.17.3)

There was missing change in the default value to calculate default maximum
amount of parameters.

This fixes commit 2e6ccd02.

The default virtio-net-pci is not supported by some legacy OSes, so allow
customize it, to provide such support.

This is a dependency of slapos.cookbook[test] since 90650d2c (
recipe/test_postgres: test with a real postgres server, 2021-11-12) and
because we run software schema tests from slapos.cookbook in
software/slapos-sr-testing, we also need the dependency here.

tests with a real postgresql server, the mocked commands from 261a8e6b (test/recipe: update tests for postgres recipe regarding password update, 2021-11-11) were too unrealistic.

These tests with a real server revealed that the port option of the recipe was not used, this is fixed as well

See merge request nexedi/slapos!1083

even though the recipe has a required option for port, it was not used
and server was always listening on default (5432) port

exposing environment variable SLAPOS_TEST_POSTGRESQL_PREFIX containing
the location where postgresql is installed

taken from unstable lapp stack

Go1.17 is current stable Go release which, besides other improvements,
compared to Go1.16 generates code that runs 5-10-15% faster(*):

https://go.dev/blog/go1.17

It makes sense to use that version by default.

Cc'ing people who might be affected:

- caddy   (@luke)
- hugo    (@lu.xu)
- repman, restic  (@alain.takoudjou, @jerome)
- galene  (@tomo, @alain.takoudjou)
- gitlab  (@alain.takoudjou, @jerome, @lpgeneau)
- grafana (@jerome)
- theia   (@jerome, @xavier_thompson)

If for some reason Go1.17 default does not work for a software,
maintainer of that software release - please pin Go to Go1.16
explicitly inside that particular software-release.

(*) Go blog mentions 5% speedup on the average, but it was reported that
    sometimes for important inner loops the speedup can be as much as 15%.

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1082

The history of deploy script can be seen in slapos.core package with:
git log -p master/bt5/slapos_web_deploy/PathTemplateItem/web_page_module/deploy_*

When server is running, use psql command to connect to server and issue
a query to update password.

This upgrade

- fixes Nxdtest to show proper traceback on error in configuration file

  nexedi/nxdtest@7b5add47

- adds preliminary support for PyLint[2]

  nexedi/nxdtest@72e36088

- and makes nxdtest to emit summary at the end of test run

  nexedi/nxdtest@9f413221

/reviewed-by @jerome
/reviewed-on nexedi/slapos!1081

Going Go1.16.8 -> Go1.16.10 brings in fixes to compiler, runtime and stdlib
including security fixes to linker, archive/zip package.

https://golang.org/doc/devel/release.html#go1.16.minor

Tested via:

- SlapOS.SoftwareReleases.IntegrationTest.Python2 (https://nexedijs.erp5.net/#/test_result_module/20211110-4DA2B2E), and
- SlapOS.SoftwareReleases.IntegrationTest.Python3 (https://nexedijs.erp5.net/#/test_result_module/20211110-40489859)

Going Go1.17.1 -> Go1.17.3 brings in fixes to compiler, runtime and stdlib
including security fixes to linker and archive/zip package.

https://golang.org/doc/devel/release.html#go1.17.minor

Tested via:

- SlapOS.SoftwareReleases.IntegrationTest.Python2 (https://nexedijs.erp5.net/#/test_result_module/20211110-4DA2B2E), and
- SlapOS.SoftwareReleases.IntegrationTest.Python3 (https://nexedijs.erp5.net/#/test_result_module/20211110-40489859)

* master:
  fixup! wendelin.core: Add way to run tests
  Disable DBUS support for zbar as: - it's not used in a SlapOS system (seems only used for webcam support) - it breaks the concept of SlapOs containerization - finally it tries to create a DBUS file in /etc/dbus-1/system.d/ which is NOT   allowed (rightfully) for a slapsoft user
  caucase: set up a host file which specified for it
  software/slapos-testing: add jq, sed and grep in PATH
  software/erp5/test: fix ResourceWarning on python3

In 805374b4 I established the way to run wendelin.core test.  There
component/wendelin.core/test-common.cfg preamble mimics what is setup
by software/neoppod/software-common.cfg in parts for NEO. However I
copied only neoppod into parts without neoppod-develop, and this results
in NEO being installed from PyPI instead of from git checkout.

Let's fix this because everything else - e.g. ERP5 and Wendelin software
releases - use NEO from git checkout which today diverged significantly
from what was last released to PyPI in April of 2019.

Thanks to @jerome for helping to find this out.

See merge request nexedi/slapos!1074

- it's not used in a SlapOS system (seems only used for webcam support)
- it breaks the concept of SlapOs containerization
- finally it tries to create a DBUS file in /etc/dbus-1/system.d/ which is NOT
  allowed (rightfully) for a slapsoft user

This allow caucase test use the random partition IP
address instead of fixed localhost:8000. Which can avoid
the conflict if one test node running multiple test suite.

 - use the requests.Session in a context manager so that resources are
properly closed.
 - close the stdout of caucase process we want to keep silent

See merge request nexedi/slapos!1075

This is used by caucase.sh test

* origin/master: (22 commits)
  component/perl-Image-ExifTool: version up 12.30
  fixup! stack/erp5: use %Ta for timing of haproxy requests
  stack/erp5: use %Ta for timing of haproxy requests
  Revert "kvm: Bang immediately in case of vnc_promise problem"
  kvm: Bang immediately in case of vnc_promise problem
  kvm: Switch mouse to tablet mode
  software/slapos-sr-testing: update doc
  software/slapos-sr-testing: run ERP5 SR test with a python3 slapos.core
  component/depot_tools: check out a fixed revision
  software/erp5/test: add python3 support
  software/galene: use python3
  stack/caucase: Version up caucase 0.9.12
  galene: version up 0.4
  kvm: Increase default VM parameters to match nowadays requirement
  hugo: create tempfiles in a dedicated temporary directory
  component/java-jdk: add missing rpaths
  component/alsa: enable slapos.recipe.cmmi's shared
  kvm: Upgrade default ISO for vm to debian bullseye
  componant/slapos/obs.cfg: update OBS build
  caddy-frontend: Pick up recent kedifa from the distribution
  ...

 - use the requests.Session in a context manager so that resources are
properly closed.
 - close the stdout of caucase process we want to keep silent

%Tt was not good, because it also included the idle time from previous
request when the connection was reused, causing times recorded in log
files to be much longer the actual request duration.

%Ta - which is described as total active time for the HTTP request,
between the moment the proxy received the first byte of the request
header and the emission of the last byte of the response body - is much
more suitable for our use case of measuring requests durations and is
similar to apache's %D

Since nexedi/slapos.core!329 we can run use a python3 slapos.core

See merge request nexedi/slapos!1066

This reverts commit d7721eb4.

The change didn't fix the real problem.

There is no reason to wait before banging the partition if VNC is not
available, as reprocessing is the only way to fix the situation.

See merge request nexedi/slapos!1071

This allows to synchronise server position of the mouse with the client one,
thus making mouse really usable.

See https://wiki.gentoo.org/wiki/QEMU/Options#USB

Now that "the bug in the way promises are run" referenced in the comment
in ${template:test} is being fixed, we can start running ERP5 with
python3 slapos.

This was using master branch and when it got renamed to main this
stopped working and we realized that the revision was not pinned.