Ok, I'm going to check how Nova schedules instances with common flavors if cloud has both types of computes with enabled DPDK and default. If such instances (without huge pages) are booted on computes with DPDK (won't be accessible via network), then scheduling mechanism must be improved, not tests. Also since DPDK works with lots of modern NICs, maybe should we force users to enable or disable DPDK on *all* computes? Then we will be able to modify default flavors, so they use huge pages at deployment stage.
Ok, I'm going to check how Nova schedules instances with common flavors if cloud has both types of computes with enabled DPDK and default. If such instances (without huge pages) are booted on computes with DPDK (won't be accessible via network), then scheduling mechanism must be improved, not tests. Also since DPDK works with lots of modern NICs, maybe should we force users to enable or disable DPDK on *all* computes? Then we will be able to modify default flavors, so they use huge pages at deployment stage.