Replace dropbear by openssh.
Use same rdiff-backup than provided by PBS.
Allow to directly use an IPV6 address with a custom port.

Solve the problem that `slapos` script is missing from slaprunner ( described in !253 ) by adding `slapos.core` egg explicitly.

/reviewed-on !254

Since using apache-2.4[1] the Include directive will fail if no glob
matches, this switch to new, IncludeOptional[2], available since 2.4, in
order to not fail if no configurations are present.

 [1] 1f7bf3d1
 [2] http://httpd.apache.org/docs/2.4/mod/core.html#includeoptional

/reviewed-on !252

  id-store-interval is mandatory now.

See erp5@5169f193

9b5d8262 (v↑ zodbtools (0.0.0.dev4)) added zodburi and in turn ZEO
dependency to neoppod/software-common.cfg because zodburi currently
non-optionally requires ZEO.

However I forgot to notice that if we always pin ZEO to 4.x it will
require `transaction < 2` and this will break neoppod/software-zodb5.cfg
which requires ZODB 5.x and in turn `transaction >= 2`:

	Installing neoppod.
	Version and requirements information containing transaction:
	  [versions] constraint on transaction: 2.1.2
	  Requirement of ZODB==5.3.0: transaction>=2.0.3
	  Requirement of transaction>=2.0.3: zope.interface
	  Requirement of ZEO: transaction<2.0.0
	While:
	  Installing neoppod.
	Error: The requirement ('transaction<2.0.0') is not allowed by your [versions] constraint (2.1.2)

We already have ZODB = 4.x in software-common.cfg and software-zodb5.cfg
overrides it to ZODB = 5.x, but ZEO was left not-overwritten and this
way there becomes conflicting requirement on transaction.

Fix it by also overriding ZEO in software-zodb5.cfg

/reported-and-reviewed-by @jm
/reported-on !242 (comment 49754)

We provide neotest SR which builds current NEO/go together with the
tools which are needed to run the benchmarks. Go part uses
just-introduced in previous commit gowork infrastructure.

The SR does not yet provide automated service to run the tests
automatically periodically and to upload the results to ERP5 (all marked
as TODO).

However with present state it provides all the infrastructure for people
to try to run NEO tests in their webrunner: a `neotest` program is
installed in buildout top-level bin/ . One should use it to run the
tests.

For example:

	slapuser14@vifibcloud-onlinenet-hosting-004:~/srv/runner/t$ ../software/4db21ec948dce895b38ba93c1def3ab1/bin/neotest
	Neotest is a tool to functionally test and benchmark NEO.

	Usage:

	        neotest command [arguments]

	The commands are:

	        bench-local     run benchmarks when client and server are both on the same localhost
	        bench-cluster   run benchmarks when server is local and client is on another node

	        run-client      run client benchmarks against separate server
	        bench-disk      benchmark local disk (already part of bench-{local,cluster})
	        bench-cpu       benchmark local cpu  (already part of bench-{local,cluster})

	        deploy          deploy NEO & needed software for tests to remote host
	        deploy-local    deploy NEO & needed software for tests locally

	        info            print information about a node
	        info-local      print information about local deployment

	Additional utility commands:

	        cpustat         run a command and print CPU-related statistics

	slapuser14@vifibcloud-onlinenet-hosting-004:~/srv/runner/t$ ../software/4db21ec948dce895b38ba93c1def3ab1/bin/neotest info-local
	# Thu, 19 Oct 2017 18:13:35 +0300
	# slapuser14@sd-112617.dedibox.fr (2001:67c:1254:e:8c::1 (+ 20·ipv6) 163.172.70.8 (+ 20·ipv4))
	# Linux vifibcloud-onlinenet-hosting-004 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
	# cpu: Intel(R) Xeon(R) CPU D-1531 @ 2.20GHz
	# cpu[0-11]: freq: intel_pstate/powersave [.80GHz - 2.70GHz]
	# cpu[0-11]: idle: acpi_idle/menu: POLL(0μs) C1(1μs) C2(41μs)
	# cpu: WARNING: frequency not fixed - benchmark timings won't be stable
	# cpu: WARNING: C-state exit-latency is max 41μs - up to that can add to networked and IPC request-reply latency
	# md1 (raid0) -> sda3  sdb3
	# sda: SAMSUNG MZ7LN256  rev 100Q 238.5G
	# sdb: SAMSUNG MZ7LN256  rev 100Q 238.5G
	# eth0: Intel Corporation I350 Gigabit Network Connection rev 01
	# eth0: features: rx tx sg tso !ufo gso gro !lro rxvlan txvlan !ntuple rxhash ...
	# eth0: coalesce: rxc: 3μs/0f/0μs-irq/0f-irq,  txc: 0μs/0f/0μs-irq/0f-irq
	# eth0: up, speed=1000, mtu=1500, txqlen=1000, !gro_flush_timeout
	# eth1: Intel Corporation I350 Gigabit Network Connection rev 01
	# eth1: features: rx tx sg tso !ufo gso gro !lro rxvlan txvlan !ntuple rxhash ...
	# eth1: coalesce: rxc: 3μs/0f/0μs-irq/0f-irq,  txc: 0μs/0f/0μs-irq/0f-irq
	# eth1: down, speed=?, mtu=1500, txqlen=1000, !gro_flush_timeout
	# Python 2.7.14
	# go version go1.9.1 linux/amd64
	# sqlite 3.19.0 (py mod 2.6.0)
	# mysqld  Ver 10.1.28-MariaDB for Linux on x86_64 (MariaDB Server)
	# neo             : v1.8-1326-g4d0cd894
	# zodb            : 4.4.5
	# zeo             : 4.3.1
	# mysqlclient     : 1.3.12
	# wendelin.core   : v0.11-4-g38fbc83

slapuser14@vifibcloud-onlinenet-hosting-004:~/srv/runner/t$ time ../software/4db21ec948dce895b38ba93c1def3ab1/bin/neotest bench-local 2>&1 |tee 1.txt
...
*** FileStorage
Benchmarkvifibcloud-onlinenet-hosting-004/fs1/zhash.py 1 24.4 µs/object # crc32:1552c530  oid=0..2127  nread=8534126  t=0.052s  # POLL·0 C1·49 C2·853
Benchmarkvifibcloud-onlinenet-hosting-004/fs1/zhash.py 1 24.6 µs/object # crc32:1552c530  oid=0..2127  nread=8534126  t=0.052s  # POLL·0 C1·63 C2·894
Benchmarkvifibcloud-onlinenet-hosting-004/fs1/zhash.py 1 20.7 µs/object # crc32:1552c530  oid=0..2127  nread=8534126  t=0.044s  # POLL·0 C1·39 C2·803
Benchmarkvifibcloud-onlinenet-hosting-004/fs1/zhash.py 1 20.8 µs/object # crc32:1552c530  oid=0..2127  nread=8534126  t=0.044s  # POLL·1 C1·18 C2·629
Benchmarkvifibcloud-onlinenet-hosting-004/fs1/zhash.py 1 20.7 µs/object # crc32:1552c530  oid=0..2127  nread=8534126  t=0.044s  # POLL·0 C1·12 C2·669
...

WIP

Starting from this version zodbtools requires zodburi to open ZODB
storages by URL (see zodbtools@db3b84ec
and zodbtools@82b06413)

zodburi in turn requires ZEO (maybe we might patch it to only optionally
depend on it), so we move ZEO requirement from stack/ERP5 to the place
where it is actually first needed.

This reverts merge request !243