Check different virtual network interface options for fuel-qa

[Alexandr Kostrikov]

There are problems with e1000 and virtio.

As they are affecting different parts of fuel in different ways, it is possible to try to check network drivers in fuel-qa/fuel-devops to get best intersection of drivers.

[Alexandr Kostrikov (akostrikov-mirantis)]

Additional options : net.ifnames=1 biosdevname=1
Interface order: enp0s3, enp0s8, enp0s9, enp0s10

[Ivan Suzdal (isuzdal)]

We need try virtio interfaces on master node. With systemd-219 we can use predictable interface naming for virtio-net devices. However, the naming scheme will differ from the one described in manual page. The man page saying that it will named like ensX, but in my case (vbox) i've got enpXsY naming, like with e1k devices with a little difference - e1k names starts from enp0s3 to enp0s8 in steps of 1, on virtio devices it will named: enp0s3, enp0s8, enp0s9 and so.

[Alexandr Kostrikov (akostrikov-mirantis)]

That is impossible to change network drivers on current operating systems without tests degradation.
Possibly, it will we suitable to 10.0.