MOM runs inside the VDSM process. We want to make it possible to run as standalone process, to the reduce the pressure on the python GIL. Running MOM separately also make it easier to profile and to evaluate the performances of it, and also of VDSM.
ovirt-3.6.0-3 release
martin, please add steps to verify this bug
just to make sure, 3.6 mom installation is still a dependecy of the vdsm rpm or one needs to install mom separately?
Shira: Just start VDSM and run any of your MOM scenarios (ballooning, ksm, …) + check whether there is a separate process running (using for example ps or systemctl status mom-vdsm). Roy: VDSM still depends on mom via RPM dependency.
Verified on : 3.6.0-0.12.master.el6 vdsm-4.17.3-1.el7ev.noarch vdsm-4.17.3-1.el7ev.noarch i run the regular tests and check that the mom service is running : [root@dhcp160-245 ~]# systemctl status mom-vdsm ● mom-vdsm.service - MOM instance configured for VDSM purposes Loaded: loaded (/usr/lib/systemd/system/mom-vdsm.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2015-08-25 10:42:24 IDT; 14min ago Main PID: 9652 (python) CGroup: /system.slice/mom-vdsm.service └─9652 python /usr/sbin/momd -c /etc/vdsm/mom.conf
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0384.html