network verification checker should test for ovs vlan issues

[Andrew Woodward]

There has been indications from the neutron mos team that newer kernels including Ubuntu nodes may still have issues with ovs vlans. To address this issue we should

add ovs code to bootstrapnode and run ovs-test to confirm if splinters are needed.

from (http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=FAQ;hb=HEAD)
   It is not always easy to tell whether a Linux kernel driver has
   buggy VLAN support. The ovs-vlan-test(8) and ovs-test(8) utilities
   can help you test. See their manpages for details. Of the two
   utilities, ovs-test(8) is newer and more thorough, but
   ovs-vlan-test(8) may be easier to use.

[Dima Shulyak (dshulyak)]

Currently we have limitations for our network verification architecture.
It is ok from the point of orchestration, but pretty ugly in terms of reporting and UI.

Some time ago i was proposing approach where we will have separate tab (or same as HealthCheck)
with all kinds of pre-deployment verifications enabled. It requires significant amount of work todo, and i am not sure
when i will have that free time.

If you want just prepare package and run it manually - it is very simple..
But speaking of automation and integration it with our orchestrator/nailgun - it will require development and
testing, so i prefere to track this activity as BP.

https://blueprints.launchpad.net/fuel/+spec/ovs-test-part-network-verification

[Andrew Woodward (xarses)]

Let's resolve the bug by adding the packages to run the ovs-test command and adding notes to the docs. Lets track having netchecker maybe run it in the bp

[Dmitry Pyzhov (dpyzhov)]

We are lack of resources in 6.1

[Aleksey Kasatkin (alekseyk-ru)]

It's a feature so it's not a subject to solve after FF. Moved to 8.0.

[Andrew Woodward (xarses)]

With advancements in Kernel/OVS and the reduced usage of VLAN in lou of GRE/VxLAN, this likely is not a priority any longer

[Aleksey Kasatkin (alekseyk-ru)]

No fix for stable branch as it is a feature request and in view of comment #5.