On 12/27/2011 05:22 PM, Miki Kenneth wrote:
Few points: - From requirement perspective - 0-10 scale is OK too.
UI-wise Isn't High-Medium-Low enough? Unless we are going to credit some with extra points (for example, for having a bond) or take off points (for not being connected to the ISO domain, for example) ? We can set in the engine 'High=8, Medium=5, Low=2' and have the API set finer granularity if desired. BTW, I'd do the 2nd order by latency to the master domain, not random. Y.
- There is an RFE to allow manual SPM selection, let's make sure that we clarify how we do that in the scenarios. - There is a case were all Hosts are set as "no SPM" (-1), user should be notify (on the last host?) - Need to be able to view in the GUI: - the SPM priority for all Hosts, on the GRID? - would love to have the spm-priority avail in the search criteria, so I would serach for all hosts that spm-priority==0/-1
Miki
----- Original Message -----
From: "Muli Salem"<msalem@redhat.com> To: engine-devel@ovirt.org Sent: Tuesday, December 27, 2011 3:16:46 PM Subject: [Engine-devel] SPM Priority Design - Wiki Page
Hi all,
In the link below there is a wiki page describing the requirements and design of the SPM Priority feature. The feature allows the admin to define priorities between hosts regarding the SPM selection process
http://www.ovirt.org/wiki/Features/SPMPriority
Please feel free to share your comments.
Thanks, Muli _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel