allow-mac-to-be-updated

Registered by Aaron Rosen on 2013-07-18

Currently we do not allow the mac address on ports to be updated but there is no reason we shouldn't allow this. This will help in decoupling nova from neturon for baremetal.

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Medium
Drafter:
Chuck Carlino
Direction:
Approved
Assignee:
Chuck Carlino
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Kyle Mestery on 2014-12-18
Completed by
Chuck Carlino on 2015-02-26

Related branches

Sprints

Whiteboard

December-15 (mestery): Kilo-2.

Presumably it would be immutable after attachment to an instance? -- ijw
arosen - originally i felt we should allow it to be updated it eitherway but on second thought i think that is a good sugestion. I'll add that constraint.
ChuckC - to allow ironic and sriov nic replacement use cases, allow unbound or failed ports to be updated.

Gerrit topic: https://review.openstack.org/#q,topic:bp/allow-mac-to-be-updated,n,z

Addressed by: https://review.openstack.org/129085 (Merged)
    Allow updating VM port's mac_address

Addressed by: https://review.openstack.org/112129 (Merged)
    Allow port mac_address to be modified

Gerrit topic: https://review.openstack.org/#q,topic:allow-mac-to-be-updated,n,z

Addressed by: https://review.openstack.org/159228
    Make updating port mac_address configurable

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.