Thanks all. I agree with Lev, mostly because it's a better experience for
our users. And we typically document workaround type things in the
appendices. I could argue vdsm hooks are all workarounds for something and
we document those pretty extensively :)
Maybe this section would make sense?
https://www.ovirt.org/documentation/admin-guide/appe-Custom_Network_Prope...
Sandro, your opinion please?
Greg
On Wed, Feb 20, 2019 at 7:21 AM Lev Veyde <lveyde(a)redhat.com> wrote:
Hi Edward,
Thanks for your feedback on the issue.
I still think that we do need to to add a note to the documentation, so
that customers/integrators who want to add custom static routes will be
aware of the issue.
As previously discussed we should note of course, that this feature is
currently not officially supported, and adding the routes manually is a
workaround.
Thanks in advance,
On Wed, Feb 20, 2019 at 1:41 PM Edward Haas <edwardh(a)redhat.com> wrote:
> As mentioned in this thread oVirt currently does not support customized
> routes.
> It supports only a host level default route and per network gateways
> (default route per network).
>
> If someone understands well the Linux network details, workarounds may be
> applied to overcome oVirt limitations.
> With that said, as oVirt manages the host network details, the community
> and future development cannot take into account such workarounds.
>
> To solve this problem correctly, oVirt needs to support customize routes.
> From my perspective, this workaround should not be formally documented.
>
> Thanks,
> Edy.
>