Comment 6 for bug 2030295

Thanks, for now I've switched this to a public hardening opportunity and marked our advisory task "won't fix" to indicate that the VMT doesn't expect to issue a security advisory about it. If the likely solutions involve better documentation, adding configuration options or fixing/improving non-OpenStack software like OVN, then this is one of class B1, C2 or D in our taxonomy: https://security.openstack.org/vmt-process.html#report-taxonomy