See merge request !134

See merge request nexedi/slapos.package!132

See merge request !131

See merge request !130

Wendelin.core 2 tests need to be able to mlock 64M to run.
Increase corresponding limit for all subprocessed spawned by cron, which
covers slapos -> supervisord -> ...

See added comments in slapos_limit.conf for why this has to be done in
/etc/security/limits.d/slapos.conf instead of
/etc/systemd/system/cron.service.d/override.conf

I testd this to work on a KVM of mine with manually putting
/etc/security/limits.d/slapos.conf in place. Before the patch:

    https://erp5.nexedi.net/test_result_module/20201009-341BCC3C/17
    (lots of "OSError: [Errno 1] Operation not permitted" for mlock requests)

After the patch:

    https://erp5.nexedi.net/test_result_module/20201009-6B97A93B/17
    (test.wcfs/fs passes correctly)

/cc @rafael, @tomo, @luke, @Nicolas

nxd-fuse is fuse package from those distribution with backported
git.kernel.org/linus/ad2ba64dd489 for wendelin.core 2 to be able to
fully and explicitly control OS pagecache for files that wcfs serves.
This patch is very essential for wendelin.core 2.

The sources for nxd-fuse package are located in fs/fuse/ here:

https://lab.nexedi.com/kirr/linux/commits/nxd/fuse/debian/buster	(Debian 10)
https://lab.nexedi.com/kirr/linux/commits/nxd/fuse/debian/stretch	(Debian 9)
https://lab.nexedi.com/kirr/linux/commits/nxd/fuse/ubuntu/xenial	(Ubuntu 16.04)

I tested the package by myself for a long time on my Debian10-based
laptop via go-fuse tests and while working on wendelin.core. Ubuntu
package was also tested for a long time on my KVM via manually running
the same tests and, recently, via running wendelin.core 2 tests on
testnode located on the same KVM. I tested Debian 9 module only briefly
on my Debian 9 KVM, but given that the diff in between nxd-fuse and
std/ fs/fuse/ for that kernel is essentially only
git.kernel.org/linus/ad2ba64dd489, and that the debianisation was
already tested well via Debian10, and that go-fuse and wendelin.core 2
tests pass, it should be ok.

The packages are built on OBS here:

https://build.opensuse.org/package/show/home:VIFIBnexedi/nxd-fuse
https://build.opensuse.org/package/view_file/home:VIFIBnexedi/nxd-fuse/README

I've used vifib-kernel role as the place where to add corresponding
play. Nxd-fuse is tightly related to kernel and requires reboot after
installation, which, if I understood correctly, needs infrastructure
internal to that role to work correctly.

/cc @rafael, @tomo, @vpelletier

There are many fixes in between those versions, including security ones:

https://salsa.debian.org/kernel-team/linux/-/raw/stretch/debian/changelog

those 2 modules can make a system crash at startup. It is true for
Supermicro motherboards and winterfell motherboards.

See https://www.thomas-krenn.com/en/wiki/Resolve_mei:_Init_hw_failure_or_mei:_initialization_failed

This reverts commit 280c9763.

In commit 433f3d22, we disable the test
runners so the instances went back to previous organisation and so the
ports.

See merge request nexedi/slapos.package!128

The 1.0.163 version has instantiation fixed.

It's not needed in this context.

See merge request nexedi/slapos.package!127

See merge request nexedi/slapos.package!126

Also add important note why the SR shall be kept as is.

See merge request nexedi/slapos.package!125

python-requests package doesn't exist anymore on Ubuntu 20.04 so we
convert the upload script to support both python2 and python3 and we use
python3 in Debian >= 10 and Ubuntu >= 20.04.

This let us clean up the imt-vm-bootstrap playbook for Debian 10 (remove
manual installation of python-requests package).

See also nexedi/slapos!720

mroonga should be use by default as full text engine instead of myisam.

See merge request !122