The NEO/go commit kirr/neo@8c974485
changed the URL with which a NEO/go client can be loaded from

    // neo://name@master1,master2,...,masterN?options

to

    neo(s)://[credentials@]master1,master2,...,masterN/name?options

We need to apply this change in the NEO URL structure to instance-wcfs.cfg.in
to use WCFS with NEO storage.

Why?

The URL in instance-wcfs.cfg.in is finally send to wcfs binary, which
will open a NEO/go client with this URL via the "openClientByURL" function [1].
If the URL formatting instance-wcfs.cfg.in follows the old pattern,
NEO/go is unable to create a NEO/go client and may even raise an
exception [2], because information regarding NEO server is at the wrong
position of the URL.

[1] See https://lab.nexedi.com/kirr/neo/blob/87199da2b163c09ed3946b7ab9bb00a5b987d377/go/neo/client.go#L416-534
for openClientByURL.

[2] For instance when using the old pattern of putting the cluster name
in the "user" part, NEO/go will raise "credentials can be specified only
with neos:// scheme", because NEO/go reserves the "user" part for
encryption information,
see https://lab.nexedi.com/kirr/neo/blob/87199da2b163c09ed3946b7ab9bb00a5b987d377/go/neo/client.go#L449

Before this patch all ERP5 SlapOS Integration tests only run with ZEO
storage. We should also run them against NEO, because we are using
ERP5 with NEO in SlapOS.

For tests which shouldn't be split into NEO/ZEO flavoured test cases,
this patch adds the '__parameterized__' class attribute, which can
be set to 'False'.

with support for aborting query ( https://github.com/mroonga/mroonga/issues/344 )

Configuring failover URL and being able to rely on cached content is not so
simple, thus document the requirement and prove in test, that such
configuration works correctly.

Checking SLAPOS_TEST_DEBUG in the test itself came from ancient history of the
testcase, it's time to drop it and use modern apporach.

This includes xmlsec, the C library and its python bindings in ERP5, using the latest versions that are compatible with python 2.

`1.3.9` is the latest version of the python bindings with python 2 support and `1.2.30` is the latest version of the C library compiling with this version of the python bindings.

See merge request nexedi/slapos!1272

Since slapos.core!436 requesting with `--parameters-file` requires
that a JSON schema exists at <sr-url>.json for the requested SR.

Missing trailing /

See nexedi/slapos@5e1ff2de

zlib source url has been moved. Please see issue
https://github.com/madler/zlib/issues/649 for reference.

See merge request nexedi/slapos!1276

Co-authored-by: Kazuhiko SHIOZAKI <kazuhiko@nexedi.com>

Running test as last makes no sense nowadays, as the site is fully prepared.
Awaiting for each possible log of configured frontend is not worth the
requirement, so make those tests as first ones, which simplifies running only
them with reproducible effect.

All tests which could be affected by that fact has been identified and changed.

otherwise it probably uses system's openssl.

Setting rpath seems not needed because we are using
-DBUILD_SHARED_LIBS=OFF here.

https://github.com/sigoden/dufs

New software to serve static files

See merge request nexedi/slapos!1270

caddy-frontend-N is bad name, it's just frontend-node-N.

This option was useful only during the time, when there were experiments
running on caddy-frontend clusters during switch to HTTP/2.

Currently HTTP/2 is a standard, and there is no reason to disable it globally.

Attention, this change will require manual intervention on the upgraded
cluster with:

sed -i 's/^recipe = caddyprofiledeps/recipe = software/g' .installed*

On each partition.

NAME_BASE is set on top of the file with informative warning, so that
developers are aware of consequences.

instance-slave-caddy-simplified-input-schema.json has been removed, as it is
not useful.

Some profiles were templates and vice versa, which was very
misleading.