[ovirt-devel] ovirt-provider-ovn - appliance inclusion / default enablement

[Sandro Bonazzola]

Hi,
with https://gerrit.ovirt.org/76855 it's requested to increase the
appliance size by adding ovirt-provider-ovn and its dependencies.

This raise a few questions.
The support for ovirt-provider-ovn is enabled by default in engine-setup
and going to be installed by default in the appliance so we're pushing to
use it.
Why not requiring it at ovirt-engine spec file level?
Answer given in the commit message of above patch is:

We do not want to have a hard dependency in the
form of an rpm require.
OVN and openvswitch are relatively heavy and complex,
and are still experimental. We would not want to
force everybody to pull them onto any Engine host.

So why adding it to the appliance, which is the default for hosted engine
which is our recommeded way to deploy oVirt, and enable it by default?

How this differs from DWH? ovirt-engine requires ovirt-engine-setup which
requires ovirt-engine-dwh setup which requires ovirt-engine-dwh.
Why can't we just require ovirt-provider-ovn in ovirt-engine instead of
tweaking the appliance?

If we decide it's not mandatory, why not make the default to not enabling
it in engine-setup and avoid to add it to the appliance?
Being optional, adding it collides with Bug 1401931
<https://bugzilla.redhat.com/show_bug.cgi?id=1401931> - [RFE] reduce the
size of the appliance

Thanks,

-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170516/a13a3cc9/attachment.html>