Back to bug 1317436

Who When What Removed Added
Yaniv Lavi 2016-03-14 10:01:22 UTC Status NEW POST
Sat6QE Jenkins 2016-03-28 20:15:54 UTC Status POST MODIFIED
Mike McCune 2016-03-28 23:09:17 UTC Status MODIFIED POST
John Skeoch 2016-04-18 07:32:27 UTC CC yeylon srevivo
John Skeoch 2016-04-22 05:00:51 UTC CC atal
Meni Yakove 2016-04-24 08:05:41 UTC Flags testing_ack? testing_ack+
Red Hat Bugzilla Rules Engine 2016-04-24 08:05:50 UTC Flags ovirt-4.0.0? ovirt-4.0.0+
Sandro Bonazzola 2016-05-02 10:09:52 UTC Target Milestone ovirt-4.0.0-alpha ovirt-4.0.0-beta
Michael Burman 2016-05-17 04:58:13 UTC CC mburman
Flags testing_plan_complete?
Yaniv Lavi 2016-05-19 12:20:52 UTC Target Milestone ovirt-4.0.0-beta ovirt-4.0.0-rc
Yaniv Lavi 2016-06-13 11:50:05 UTC Status POST MODIFIED
Target Milestone ovirt-4.0.0-rc ovirt-4.1.0
Flags ovirt-4.0.0+ ovirt-4.1.0+
Yaniv Lavi 2016-06-15 08:51:03 UTC Doc Text Feature: 3.6 feature, MAC address pools per dc, is altered, so that pools can be attached to finer scope, to the cluster.

Reason:

We need this because certain environments requires MAC address pool on cluster level, since they[those environments] inherently does not support Data Center concept.

Result:
MAC address pool is now bounded to cluster instead of Data center.

On REST layer, mac_pool attribute was added to cluster, and can be set/queried. StoragePool resource(represent Data Center) was also altered. When updating its mac_pool_id, all clusters in given Data Center will be updated to use this MAC address pool. When queried StoragePool (DataCenter) using REST GET method, ID of MAC address pool will be reported only when all clusters in given Data Center are using the same MAC address pool. Otherwise user needs to use Cluster resource to get used MAC address pool of each individual cluster.

http://www.ovirt.org/Features/Scoped_MacPoolManager
Itamar Heim 2016-12-04 20:49:39 UTC CC iheim
Sandro Bonazzola 2016-12-12 14:02:40 UTC Status MODIFIED ON_QA
Michael Burman 2016-12-13 13:11:13 UTC Status ON_QA VERIFIED
Flags testing_plan_complete? testing_plan_complete+
Byron Gravenorst 2017-02-07 03:01:46 UTC CC bgraveno
Doc Text Feature: 3.6 feature, MAC address pools per dc, is altered, so that pools can be attached to finer scope, to the cluster.

Reason:

We need this because certain environments requires MAC address pool on cluster level, since they[those environments] inherently does not support Data Center concept.

Result:
MAC address pool is now bounded to cluster instead of Data center.

On REST layer, mac_pool attribute was added to cluster, and can be set/queried. StoragePool resource(represent Data Center) was also altered. When updating its mac_pool_id, all clusters in given Data Center will be updated to use this MAC address pool. When queried StoragePool (DataCenter) using REST GET method, ID of MAC address pool will be reported only when all clusters in given Data Center are using the same MAC address pool. Otherwise user needs to use Cluster resource to get used MAC address pool of each individual cluster.

http://www.ovirt.org/Features/Scoped_MacPoolManager
MAC address pools are now bound to the cluster instead of the data center because certain environments require MAC address pools on the cluster level.

On the REST layer, the mac_pool attribute was added to the cluster, and can be set or queried. The StoragePool resource (represents the Data Center) was also altered. When updating its mac_pool_id, all clusters in given Data Center will be updated to use this MAC address pool. When StoragePool is queried using the REST GET method, the ID of the MAC address pool will be reported only when all clusters in the given Data Center are using the same MAC address pool. Otherwise user needs to use the Cluster resource to get the MAC address pool of each individual cluster.
Byron Gravenorst 2017-02-09 02:40:56 UTC Blocks 1420586
Sandro Bonazzola 2017-02-15 15:05:57 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2017-02-15 10:05:57 UTC

Back to bug 1317436