One thread is just too limited to produce a usable instance (for example,
a single-zope setup with default thread count fails to run live tests). It
is also not an advised setting for activity nodes, because of timerserver
still queuing process_timer calls while CMFActivity is busy processing; the
result being a (limited) waste of memory, and hammering mysql after long
processing periods.
Zope's default value must be duplicated because thread-amount is also used
to generate haproxy configuration file (so just not providing the value in
Zope's configuration file is wrong).

Compatibility with runner config is to be checked

If disk is mounted in folder like /data/data* and formated by slapformat
as /data/data*/slappart* for each partition, create a symlink
instance_root/DATA/data* to allow process of partition to write in
in the mounted disk.

Set tap network information in a dict if they are defined