Thanks for this effort, I hope I understand this correctly, that your new API still works the same way? So engine pulls constantly from vdsm?
If I understand the architecture correctly this should not be necessary, so vdsm could push updates to engine, when there are updates and engine could just query vdsm when a specified timeout without push notification occurs. I think this would scale better for higher numbers of vdsm, in fact for very high vdsm numbers connected to one engine something like a message queue implementation would scale even better (zero mq). -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel