Doron Fediuck has posted comments on this change.
Change subject: [WIP] MOM Integration
......................................................................
Patch Set 6: (4 inline comments)
Hi Mark,
Looks good. Still some minor issues I commented on inline.
From vdsm's point of view, we may want to consider a better
interface / api for monitoring (possibly also executing)
some factors. In this context see my comment in clientIF.py.
....................................................
File vdsm/clientIF.py
Line 92:
Although this works, I'm troubled from developer's point of view.
This means that on each and every point we had and will have regarding ksm,
the developer needs to know whether to call self.ksmMonitor or self.vdsMOM.
Any thoughts about it?
Looking forward I think it will be better to have an interface (Protocol / API) both ksm
and mom will implement, so the developer may call the same thing all over the code.
Does this make sense?
....................................................
File vdsm.spec.in
Line 351: cp %{_sysconfdir}/%{vdsm_name}/mom.conf %{_sysconfdir}/mom.conf
Mark,
Can you please explain this part;
Usually, rpm handles configuration files quite well, so no real need
for such intervention.
If the existing mom.conf belongs to someone else (mom rpm?),
then it's considered a bad practice to overrun it in this way. ie- one
rpm should not mv / rm another rpm's files.
So if I understand correctly, and you're running over the original
mom's conf, I suggest do one of the following:
1. Change mom's default conf file name to mom.conf.samle (or template),
and then it's perfectly fine to cp or generate vdsm conf file for mom.
2. If vdsm creates its own mom-vdsm.conf, mom should be able to
be started with a flag specifying the relevant conf file.
....................................................
File vdsm/supervdsmServer.py
Line 192:
There's a trailing white tab here, which git really hates...
....................................................
File vdsm/vdsMOM.py
Line 35: self.MOM = mom.MOM("/etc/vdsm/mom.conf")
This should probably be taken from vdsm.conf file, thus improving
a previous packaging issue I commented on.
--
To view, visit
http://gerrit.ovirt.org/2367
To unsubscribe, visit
http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I61e68f72e9115a913d5bc0f4903b906b0d0cce2f
Gerrit-PatchSet: 6
Gerrit-Project: vdsm
Gerrit-Branch: master
Gerrit-Owner: Mark Wu <wudxw(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Adam Litke <agl(a)us.ibm.com>
Gerrit-Reviewer: Ayal Baron <abaron(a)redhat.com>
Gerrit-Reviewer: Dan Kenigsberg <danken(a)redhat.com>
Gerrit-Reviewer: Doron Fediuck <dfediuck(a)redhat.com>
Gerrit-Reviewer: Mark Wu <wudxw(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Shu Ming <sming56(a)gmail.com>