Royce Lv has posted comments on this change.
Change subject: [WIP]change startup process for vdsm and supervdsm
......................................................................
Patch Set 1:
Thanks a lot,Dan, for reviewing this patch, this is just a prototype,
but I really appreciate your opinion about
in which way this should be done so post it with bugs and dirty codes:)
The motivation of this patch is we expect vdsm and supervdsm
can crash independently,let something like respawn/vdsmService
to take care their authorised communication,
We indeed considered to start supervdsm and then let it to fork vdsm,
but we don't want svdsm server be mixed up with startup process,
more over,we expect super vdsm crash will not result in restarting vdsm.
It has been accomplished at this point.
Reason for rewriting respawn in python is
we'd like start up and restart process convenient to debug,
But I agree with you, let systemd or upstart to take care of it is better.
--
To view, visit
http://gerrit.ovirt.org/4145
To unsubscribe, visit
http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I69aae6b0b9529c80291d90c6ad14ff82b21aea53
Gerrit-PatchSet: 1
Gerrit-Project: vdsm
Gerrit-Branch: master
Gerrit-Owner: Royce Lv <lvroyce(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Adam Litke <agl(a)us.ibm.com>
Gerrit-Reviewer: Dan Kenigsberg <danken(a)redhat.com>
Gerrit-Reviewer: Mark Wu <wudxw(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Royce Lv <lvroyce(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Shu Ming <shuming(a)linux.vnet.ibm.com>
Gerrit-Reviewer: Xu He Jie <xuhj(a)linux.vnet.ibm.com>