Hi,
Wouldn't that mean you need the whole authentication and
communication
code duplicated to mom? or is it already in there?
Not really, MOM would connect to the local VDSM (as it does now, just
with a different protocol), not to engine directly. All data will
still flow using the single engine - vdsm connection. VDSM has a
broker part that would then distribute the messages between MOM, VDSM
API and hopefully hosted engine too.
Regards
Martin
On Wed, Jun 22, 2016 at 11:03 AM, Sven Kieske <s.kieske(a)mittwald.de> wrote:
> On 22/06/16 10:39, Michal Skrivanek wrote:
>> bypassing vdsm for mom things is a good idea, but we need to make sure we’re not
killing the rest of the system
>
Wouldn't that mean you need the whole authentication and
communication
code duplicated to mom? or is it already in there?
>
> from a sysadmin perspective I would like to keep the needed ports
> to open between engine and virt-host on a minimum.
>
>
> --
> Mit freundlichen Grüßen / Regards
>
> Sven Kieske
>
> Systemadministrator
> Mittwald CM Service GmbH & Co. KG
> Königsberger Straße 6
> 32339 Espelkamp
> T: +495772 293100
> F: +495772 293333
>
https://www.mittwald.de
> Geschäftsführer: Robert Meyer
> St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/devel