Moti Asayag has posted comments on this change. Change subject: engine: DB persistent quartz scheduler ......................................................................
Patch Set 4: Couple more questions: 1. How would the management of jobs will be executed ? Would a job-name be preserved per each entity ? or any other logic to associate the job which is scheduled for a certain entity ? 2. What would be the jobs lifecycle ? will you have to introduce a logic to remove those jobs once aren't required any more ? Or to digest the current schedule jobs into a presentable view entities for the user ? 3. How would we verify that the quartz tables are properly managed and upgrade of quartz version will be backward compatible ? IMO since the quartz tables are exposed as DAOs and aren't managed by ovirt, we should have some system test, kind of e2e (install / upgrade / and actual usage of the those tables). -- To view, visit http://gerrit.ovirt.org/36297 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I9a34dac95999cb6b3721d201c116fb5f6089bb61 Gerrit-PatchSet: 4 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Sahina Bose <sab...@redhat.com> Gerrit-Reviewer: Eli Mesika <emes...@redhat.com> Gerrit-Reviewer: Liran Zelkha <lzel...@redhat.com> Gerrit-Reviewer: Moti Asayag <masa...@redhat.com> Gerrit-Reviewer: Oved Ourfali <oourf...@redhat.com> Gerrit-Reviewer: Sahina Bose <sab...@redhat.com> Gerrit-Reviewer: Shubhendu Tripathi <shtri...@redhat.com> Gerrit-Reviewer: Yair Zaslavsky <yzasl...@redhat.com> Gerrit-Reviewer: anmolbabu <anb...@redhat.com> Gerrit-Reviewer: automat...@ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
