Simone Tiraboschi has posted comments on this change. Change subject: First draft for engine-setup splitting ......................................................................
Patch Set 19: I was thinking to that in another patch over this when I'm sure that this is OK. That patch should be much simpler; basically I need to: - move the constants file under packaging/setup/ovirt_engine_setup/ to the right package; maybe it's also a good idea to move them also to different sub-folder just to keep it clearer - move some files from base to engine-common cause they are still in the wrong place Than there is still also an open point with packaging/setup/plugins/ovirt-engine-common/base/core/engine.py but I think that before touch it we really need to understand what service we need to stop during an upgrade in distributed scenario and how (another signal trough the DB?). At this point to ensure the maximum safety we can simply alert the user to stop all the ovirt (backend) services an all the involved machine if he is going to perform an upgrade with a shared DBMS. It should be all. -- To view, visit http://gerrit.ovirt.org/27647 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I4d465766f10a490bd213ca3510d02b3d6fdfa7c6 Gerrit-PatchSet: 19 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Simone Tiraboschi <[email protected]> Gerrit-Reviewer: Alon Bar-Lev <[email protected]> Gerrit-Reviewer: Sandro Bonazzola <[email protected]> Gerrit-Reviewer: Simone Tiraboschi <[email protected]> Gerrit-Reviewer: Yedidyah Bar David <[email protected]> Gerrit-Reviewer: [email protected] Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-patches
