Bug 1227714
| Summary: | [RFE] Allow mom to run as standalone process | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Francesco Romani <fromani> |
| Component: | mom | Assignee: | Martin Sivák <msivak> |
| Status: | CLOSED ERRATA | QA Contact: | Shira Maximov <mshira> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.3 | CC: | adahms, dfediuck, gklein, istein, juwu, lsurette, msivak, rgolan, rhodain, sherold, yeylon, ykaul |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature |
| Target Release: | 3.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
With this update, MoM has now been separated from VDSM, and runs as a standalone process that communicates with VDSM using XML-RPC over a UNIX socket. This makes it possible to reduce the number of threads that VDSM creates, and results in almost no busy threads in MoM, resolving an issue with the Python global interpreter lock and improving performance on high-end machines such as those with 100 or more CPUs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-09 14:44:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1240640 | ||
| Bug Blocks: | |||
|
Description
Francesco Romani
2015-06-03 11:16:21 UTC
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 |