Kobi Ianko has posted comments on this change. Change subject: Adding API methods for CPU limit MOM integration ......................................................................
Patch Set 11: Gilad, Thank you for your comment, my thoughts are that we do not need both, the design is to use MOM. MOM works as an automatic mechanism that is checking a status(via collector) and taking actions(via controller). In this particular change we could take the approach of doing it in the create procedure, but thinking on the near future we would like to expand and add a SLA POLICY that will be a complex object, by doing it with MOM we are enabling the possibility of taking actions that are not a user initiative. The overhead of mom will still exist in case we will have both, so no real reason to have them both that I can see -- To view, visit http://gerrit.ovirt.org/28462 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia78529b736ec0c841d232ba8aa1434bd0d0e8e08 Gerrit-PatchSet: 11 Gerrit-Project: vdsm Gerrit-Branch: master Gerrit-Owner: Kobi Ianko <k...@redhat.com> Gerrit-Reviewer: Dan Kenigsberg <dan...@redhat.com> Gerrit-Reviewer: Doron Fediuck <dfedi...@redhat.com> Gerrit-Reviewer: Gilad Chaplik <gchap...@redhat.com> Gerrit-Reviewer: Kobi Ianko <k...@redhat.com> Gerrit-Reviewer: automat...@ovirt.org Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ vdsm-patches mailing list vdsm-patches@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-patches
