[ovirt-devel] Feature Page: Mac Pool per DC

[Yevgeny Zaspitsky]

Martin,

I'd like to propose a different approach on how the ranges to be defined and stored.

Discussing this feature with Moti raised the alternative UX design: 
Defining ranges could be added as a left-tab on create DC dialog and a sub-tab on an existing DC. It would be a table of start and end address fields and we can add a calculated # of MACs in the range and/or summary for the DC. 
Also that will make string parsing unneeded, prevent possible user mistakes in the string format and make possible validating every field of the range on the UI side easier.
As you can see on the screenshot you've attached even a single range doesn't fit to the text box. In case of multiple ranges managing them in a single line textbox would be very uncomfortable.

A range is an object with at least 2 members (start and end). And we have few of these for each data center.
Storing a collection of the objects in a single field in a relational DB seems a bit awkward to me. 
That has few disadvantages:
1. is not normalized
2. make data validation nearly impossible
3. make querying the data very difficult
4. is restraining our ability to extend the object (e.g. a user might like to give a description to a range)
So IMHO a satellite table with the FK to storage_pool would be a more robust design.

Best regards, 
____________________ 
Yevgeny Zaspitsky 
Senior Software Engineer 
Red Hat Israel 


----- Original Message -----
From: "Martin Mucha" <mmucha at redhat.com>
To: users at ovirt.org, devel at ovirt.org
Sent: Thursday, April 10, 2014 9:59:44 AM
Subject: [ovirt-devel] new feature

Hi,

I'd like to notify you about new feature, which allows to specify distinct MAC pools, currently one per data center.
http://www.ovirt.org/Scoped_MacPoolManager

any comments/proposals for improvement are very welcomed.
Martin.
_______________________________________________
Devel mailing list
Devel at ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel