Those are candidates to be shared by some other place, like slapos testing.

boot-image-url-select is used instead of default image being downloaded by the
software release.

If nothing is selected, the default boot-image-url-select is used, but not if
other way to obatin boot image is enabled.

Also nbd2-host and nbd2-port are asserted.

nbd2-host and nbd2-port are asserted too.

Test are reorganized to easily assert mixed scenarios.

Most tests were unaffected by partitions now having different IPv6.
The main issue is that there is now a .slapos-resource file in each
subpartition as well, same as in normal top-level partitions, which
interferes with a hidden behavior of slapconfiguration recipe that
allowed a kvm in a subpartition to transparently use the tap of the
top-level partition. Now we need to explictly take this tap and put
it in the .slapos-resource file of the subpartition.

When IPv6 range is be enabled in testnodes, `_ipv6_address` does not
contain a single IPv6 address shared by all partitions anymore, but
instead the IPv6 range from which each partition will obtain its own
IPv6 address. Instead there is now `computer_partition_ipv6_address`
which contains the IPv6 address of the main partition.

This change blindly replaces all occurences of `_ipv6_address` with
`computer_partition_ipv6_address`, since that will fix most simple
cases. The remaining cases, such as tests with instance trees that
use multiple partitions, can be investigated and fixed individually.

without this cleanup, the software integration tests of KVM were stuck
forever because unittest was waiting for the subprocess to stop.

By inspecting current configuration stored in .data-disk-amount of the
partition configuration directory extend the conflict protection to really
observed configurations.

Adapt the README to follow real messages and explain a bit more the situation.

This was not implemented

bootstrap-script-url and data-to-vm are important features of
enable-http-server and are expected to work correctly, thus cover them
with instance-level testing.

In mean time fix detected issues.

This reverts commit e7b48c0b.

Support absolute and relative paths. Paths starting with "rbd:" are special,
and they point to the rbd endpoint, served by Ceph.

cache parameter is optional, in case if present, will be used as-is, even with
empty cache.

external-disk-number, external-disk-size and external-disk-format has been
removed from the schema to become hidden, nevertheless it's expected to be
fully supported, as long tests are kept.

Loudly fail in case if old and new ways are used in the same time.

default and kvm-cluster software types are now json-in-xml, so they accept
and return json-in-xml.

Update tests to show that xml and json-in-xml serialization works.

Note: There was invective to publish with pure XML serialisation, but it is
wrong idea because:

 1) serialisation in the software.cfg.json is provided for both ways
 2) requesting instances with given serialisation by profiles expect same
    serialisation

Request resilient instances with serialised, as they reply with json-in-xml.

There is no real control over port chosen by push/pull.

There is no reason to keep python2 compatibility, as python3 flavour of the
KVM software release is good enough.

external-disk-* parameters are fully tested, including it's special features
like keeping the image available even in case of dropping them from request
parameters.

Since
nexedi/slapos.core@a8917a3c
and slapos.core https://lab.nexedi.com/nexedi/slapos.core/tags/1.7.4 the
tap_ipv4_addr value is empty by default on the servers, especially test nodes.

To not rely on what is provided on the test environment simply mock the
configuration of the machine so that the test is able to prove profile
functionality.

The test does not require to download some enormous images, so provide small
empty qcow2 images, good enough to start the VM.

The problem has been introduced in 5da9c082
"kvm: Improve boot image url handling".

Note the internal usage of md5sum value as image name in the download config
creator.

The test have incorrect leftover of old limited implementation, now the system
shall update images by itself.

Also the typical scenario - image on first request - was not covered.

Adapt the test to code without needed linking.

As refernce to the network-config-ipv4 part has been removed from the
publish-connection-information the part was not installed anymore, so the
netconfig.sh file was not added.

Fixed it by simply adding this part to the installed ones.

This fixes commit 3f7d8965

Fixes dbd19730

The test was missing change of the generated file.

Fixes 2048ceb8

kvm-exporter supported only disk-type=virtio, as qemuqmpclient.driveBackup
source_drive defaults to virtio0.

For disk-type=ide the source_drive found to be ide0-hd0 by query-block during
runtime, and as it's used, now such disk type is supported.

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

KVM which defaults to 1024 RAM, 10 GB disk and 1 CPU is too small for nowadays
OS requirements, so to avoid confusions, increase the defaults.

Thanks to the new buildout/slapos.recipe.build feature,
we can download the last released version of Debian Stable.

NEO stress testing is changed to run on both Debian 10 & 11.

Keep proposing Debian 10 netinst in kvm SR,
waiting that Debian 11 is more tested.

Thanks to minimising amount of changing parameters of the wrapper, by setting
RAM and CPU to "init" values, it's possible to not restart the wrapper in case
of device hotplugging in for changes of those parameters.

Note that this shows regressiong to enable-device-hotplug which happened
after upgrade to qemu 5.2.0 in 8dc22418.

slapos.toolbox is added in order to use qemuqmpclient.