Bug 1317436

Summary: [RFE] Per cluster MAC address pool
Product: [oVirt] ovirt-engine Reporter: Yaniv Lavi <ylavi>
Component: RFEsAssignee: Martin Mucha <mmucha>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: bdoran, bgraveno, bugs, byount, danken, dsirrine, gchakkar, gklein, jduncan, lpeer, lsurette, mburman, mmucha, myakove, nyechiel, pbatkowski, rbalakri, Rhev-m-bugs, sander.van.dinten, srevivo, tmichett, ykaul, ylavi
Target Milestone: ovirt-4.1.0-alphaKeywords: FutureFeature
Target Release: ---Flags: ylavi: ovirt-4.1+
ylavi: exception+
mburman: testing_plan_complete+
ylavi: planning_ack+
danken: devel_ack+
myakove: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
URL: http://www.ovirt.org/Features/Scoped_MacPoolManager
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
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.
Story Points: ---
Clone Of: 994283 Environment:
Last Closed: 2017-02-15 15:05:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 994283, 1298235, 1420586    

Description Yaniv Lavi 2016-03-14 09:19:22 UTC
For certain environments, there are reasons to have a specific pool of MAC addresses for some systems and a different pool of MACs for other systems on a per cluster basis. Mac address pool per cluster is sometimes needed for security and deployment purposes.

Comment 1 Mike McCune 2016-03-28 23:09:17 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 2 Sandro Bonazzola 2016-05-02 10:09:52 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 3 Sandro Bonazzola 2016-12-12 14:02:40 UTC
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.

Comment 4 Michael Burman 2016-12-13 13:11:13 UTC
Verified on - 4.1.0-0.2.master.20161210231201.git26a385e.el7.centos